That would be the old 'accidentally deleted a # from a line in rc.conf' problem. There are likely to be several lines beginning '# -- ' in the file. New users often accidentally remove the # making the '--' into a command. There will also be a few messages during startup that will also complain about the '--' command but most people ignore these.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of olivier.taylor Sent: Thursday, 15 June 2006 8:59 PM To: [EMAIL PROTECTED] Cc: freebsd-stable@freebsd.org Subject: Re: save-entropy freebsd 5.4 #!/bin/sh # # Copyright (c) 2001-2005 Douglas Barton, [EMAIL PROTECTED] # All rights reserved. # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions # are met: # 1. Redistributions of source code must retain the above copyright # notice, this list of conditions and the following disclaimer. # 2. Redistributions in binary form must reproduce the above copyright # notice, this list of conditions and the following disclaimer in the # documentation and/or other materials provided with the distribution. # # THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND # ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE # ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE # FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL # DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS # OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT # LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF # SUCH DAMAGE. # # $FreeBSD: src/libexec/save-entropy/save-entropy.sh,v 1.2.12.1 2005/04/14 21:49:13 dougb Exp $ # This script is called by cron to store bits of randomness which are # then used to seed /dev/random on boot. # Originally developed by Doug Barton, [EMAIL PROTECTED] PATH=/bin:/usr/bin # If there is a global system configuration file, suck it in. # if [ -r /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf source_rc_confs elif [ -r /etc/rc.conf ]; then . /etc/rc.conf fi case ${entropy_dir} in [Nn][Oo]) exit 0 ;; *) entropy_dir=${entropy_dir:-/var/db/entropy} ;; esac entropy_save_sz=${entropy_save_sz:-2048} entropy_save_num=${entropy_save_num:-8} if [ ! -d "${entropy_dir}" ]; then umask 077 mkdir "${entropy_dir}" || { logger -is -t "$0" The entropy directory "${entropy_dir}" does not \ exist, and cannot be created. Therefore no entropy can be saved. ; exit 1;} /usr/sbin/chown operator:operator "${entropy_dir}" chmod 0700 "${entropy_dir}" fi umask 377 for file_num in `jot ${entropy_save_num} ${entropy_save_num} 1`; do if [ -e "${entropy_dir}/saved-entropy.${file_num}" ]; then if [ -f "${entropy_dir}/saved-entropy.${file_num}" ]; then new_num=$(($file_num + 1)) if [ "${new_num}" -gt "${entropy_save_num}" ]; then rm -f "${entropy_dir}/saved-entropy.${file_num}" else mv "${entropy_dir}/saved-entropy.${file_num}" \ "${entropy_dir}/saved-entropy.${new_num}" fi else logger -is -t "$0" \ "${entropy_dir}/saved-entropy.${file_num} is not a regular file, and therefore \ it will not be rotated. Entropy file harvesting is aborted." exit 1 fi fi done dd if=/dev/random of="${entropy_dir}/saved-entropy.1" \ bs="$entropy_save_sz" count=1 2> /dev/null exit 0 David Schwartz a écrit : Since a few days, I receive this in /var/mail/root Any idea? Olivier From [EMAIL PROTECTED] Thu Jun 15 11:11:00 2006 Return-Path: [4]<[EMAIL PROTECTED]> Received: from xxx.be (localhost [127.0.0.1]) by finalcut.be (8.13.3/8.13.3) with ESMTP id k5F9B0Pu051577 for [5]<[EMAIL PROTECTED]>; Thu, 15 Jun 2006 11:11:00 +0200 (CEST) (envelope-from [EMAIL PROTECTED]) Received: (from [EMAIL PROTECTED]) by finalcut.be (8.13.3/8.13.3/Submit) id k5F9B0jf051566; Thu, 15 Jun 2006 11:11:00 +0200 (CEST) (envelope-from operator) Date: Thu, 15 Jun 2006 11:11:00 +0200 (CEST) Message-Id: [7]<[EMAIL PROTECTED]> From: [EMAIL PROTECTED] (Cron Daemon) To: [EMAIL PROTECTED] Subject: Cron <[EMAIL PROTECTED]> /usr/libexec/save-entropy X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin> X-Cron-Env: <HOME=/> X-Cron-Env: <LOGNAME=operator> X-Cron-Env: <USER=operator> --: not found FreeBSD version? Contents of /usr/libexec/save-entropy? DS _______________________________________________ [EMAIL PROTECTED] mailing list [11]http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [12]"[EMAIL PROTECTED]" References 1. mailto:[EMAIL PROTECTED] 2. mailto:[EMAIL PROTECTED] 3. mailto:[EMAIL PROTECTED] 4. mailto:[EMAIL PROTECTED] 5. mailto:[EMAIL PROTECTED] 6. mailto:[EMAIL PROTECTED] 7. mailto:[EMAIL PROTECTED] 8. mailto:[EMAIL PROTECTED] 9. mailto:[EMAIL PROTECTED] 10. mailto:freebsd-stable@freebsd.org 11. http://lists.freebsd.org/mailman/listinfo/freebsd-stable 12. mailto:[EMAIL PROTECTED] _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ********************************************************************** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ********************************************************************** _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"