Re: Following upgrade 6.3 >7.0 /usr/libexec/save-entropy query
David Southwell wrote: Receiving Automated message from cron No such messages under 6.3 Is there anything I need to attend to here? Subject: Cron <...> /usr/libexec/save-entropy Date: Thursday 17 July 2008 From: Cron Daemon To: >[EMAIL PROTECTED] unlink: /var/db/entropy/saved-entropy.8: No such file or directory mv: /var/db/entropy/saved-entropy.7: No such file or directory mv: /var/db/entropy/saved-entropy.5: No such file or directory mv: /var/db/entropy/saved-entropy.1: No such file or directory Looks like some of those files went missing, but not all. This problem will correct itself in roughly 88 minutes, but if it hasn't, or if it's annoying you, just 'rm /var/db/entropy/*' and let it start from scratch. hth, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Following upgrade 6.3 >7.0 /usr/libexec/save-entropy query
Receiving Automated message from cron No such messages under 6.3 Is there anything I need to attend to here? Subject: Cron <...> /usr/libexec/save-entropy Date: Thursday 17 July 2008 From: Cron Daemon To: >[EMAIL PROTECTED] unlink: /var/db/entropy/saved-entropy.8: No such file or directory mv: /var/db/entropy/saved-entropy.7: No such file or directory mv: /var/db/entropy/saved-entropy.5: No such file or directory mv: /var/db/entropy/saved-entropy.1: No such file or directory David unlink: /var/db/entropy/saved-entropy.8: No such file or directory mv: /var/db/entropy/saved-entropy.7: No such file or directory mv: /var/db/entropy/saved-entropy.5: No such file or directory mv: /var/db/entropy/saved-entropy.1: No such file or directory ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[Fwd: cvs commit: src/libexec/save-entropy save-entropy.sh]
FYI, I just MFC'ed this change to RELENG_6. I do not plan to MFC it to
RELENG_5. I believe this will help avoid the symptoms of the most common
user errors that we see complaints about on the mailing list, and my
personal mailbox.
I tested the changes thoroughly on both HEAD and RELENG_6, so I do not
anticipate any problems, but please consider this a mini-heads up.
Doug
--
This .signature sanitized for your protection
Original Message
Subject: cvs commit: src/libexec/save-entropy save-entropy.sh
Date: Mon, 28 Aug 2006 06:41:50 + (UTC)
From: Doug Barton <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED], cvs-all@FreeBSD.org
dougb 2006-08-28 06:41:50 UTC
FreeBSD src repository
Modified files:
libexec/save-entropy save-entropy.sh
Log:
1. Attempt to take one bullet out of the foot-shooting gun by silently
ignoring errors when sourcing rc.conf* files. The most common error
occurs when users put a command of some sort into those files.
(ifconfig is a popular choice)
2. Make the file rotation logic simpler by starting one down from
the "top" of the list, rather than at the top.
3. Try to make file rotation more secure by calling unlink(1) on all
new file names before rotating an old file to the new name, rather than
merely calling 'rm -f' on any files that exceed the number of files
to save.
Revision ChangesPath
1.4 +10 -10src/libexec/save-entropy/save-entropy.sh
http://www.FreeBSD.org/cgi/cvsweb.cgi/src/libexec/save-entropy/save-entropy.sh.diff?&r1=1.3&r2=1.4&f=h
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: save-entropy
Olivier,
That process is meant to be there. I don't know why it has the '--' argument
but it isn't likely to be a symptom of the problem you are having.
Try
sh -x /usr/libexec/save-entropy
To get more insight into when it is failing. This will show you surrounding
commands which will give you a better chance of working out what is failing in
the script.
At least 20% of my students run into this sort of problem when I have them
configure FreeBSD systems. While normally its their rc.conf file that gets
messed up, in your case it apparently isn't so I suppose I'm still suggesting
ways of finding out what file/line has the problem.
Good luck,
Brian
-Original Message-
From: olivier.taylor [mailto:[EMAIL PROTECTED]
Sent: Friday, 16 June 2006 3:47 PM
To: Scott, Brian
Cc: freebsd-stable@freebsd.org
Subject: Re: save-entropy
Thanks Scott,
But unfortunately, that's not the case...
With ps ax I found a process
1 ?? ILs0:00.00 /sbin/init --
Strange stuff, grrr
The server is on a datacenter, I don't see the startup messages...
Olivier
Scott, Brian a écrit :
> 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}
Re: save-entropy
Thanks Scott,
But unfortunately, that's not the case...
With ps ax I found a process
1 ?? ILs0:00.00 /sbin/init --
Strange stuff, grrr
The server is on a datacenter, I don't see the startup messages...
Olivier
Scott, Brian a écrit :
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-fro
RE: save-entropy
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]<
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:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
--: 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 PROTECT
RE: save-entropy
> 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: <[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 <[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: <[EMAIL PROTECTED]> > From: [EMAIL PROTECTED] (Cron Daemon) > To: [EMAIL PROTECTED] > Subject: Cron <[EMAIL PROTECTED]> /usr/libexec/save-entropy > X-Cron-Env: > X-Cron-Env: > X-Cron-Env: > X-Cron-Env: > X-Cron-Env: > > --: not found > FreeBSD version? Contents of /usr/libexec/save-entropy? DS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
save-entropy
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: <[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 <[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: <[EMAIL PROTECTED]> From: [EMAIL PROTECTED] (Cron Daemon) To: [EMAIL PROTECTED] Subject: Cron <[EMAIL PROTECTED]> /usr/libexec/save-entropy X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: --: not found ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/libexec/save-entropy, IPv4: not found
> What happens if you run it from the command line? Same thing. The problem's now gone away though following an installworld. -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/libexec/save-entropy, IPv4: not found
Pete French wrote: > About an hour ago I started getting regular > messages from cron running /usr/libexec/save-entropy which > contail the single line "IPv4: not found" What happens if you run it from the command line? Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/usr/libexec/save-entropy, IPv4: not found
About an hour ago I started getting regular messages from cron running /usr/libexec/save-entropy which contail the single line "IPv4: not found" Anybody got any ideas ? The only thing I did at that porint was to do an 'rm' of /usr/obj in preparation for compiling this mornings 61 code to test it. Removing /usr/obj should not affect a running system at all. The box is currently running 6.1-RC from last wednesday. When my compile finished I will do a re-install of world, but I am still curious as to what might be causing this! -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: save-entropy errors on jail after update to 5.4-RELEASE
Renato Botelho wrote: I updated my box and a jail that runs inside this box to 5.4-RELEASE yesterday. After it, I'm receiving emails from this jail with error messages about /usr/libexec/save-entropy I'm receiving messages like this: mv: /var/db/entropy/saved-entropy.7: No such file or directory mv: /var/db/entropy/saved-entropy.5: No such file or directory override r operator/operator for /var/db/entropy/saved-entropy.5? (y/n [n]) not overwritten override r operator/operator for /var/db/entropy/saved-entropy.4? (y/n [n]) not overwritten override r operator/operator for /var/db/entropy/saved-entropy.3? (y/n [n]) not overwritten override r operator/operator for /var/db/entropy/saved-entropy.2? (y/n [n]) not overwritten here is the files inside the jail: [EMAIL PROTECTED]:~> sudo ls -l /var/db/entropy/ total 16 -r 1 operator operator 2048 May 11 10:33 saved-entropy.1 -r 1 operator operator 2048 May 11 10:33 saved-entropy.2 -r 1 operator operator 2048 May 11 10:22 saved-entropy.3 -r 1 operator operator 2048 May 11 10:22 saved-entropy.4 -r 1 operator operator 2048 May 11 10:11 saved-entropy.5 -r 1 operator operator 2048 May 11 10:11 saved-entropy.6 -r 1 operator operator 2048 May 11 10:00 saved-entropy.7 -r 1 operator operator 2048 May 11 10:00 saved-entropy.8 Anybody could help me to fix it? thanks in advance I suspect this happens because of concurrent access to /dev/random from multiple save-entropy scripts launched exactly as the same time by jailed cron daemons. I got rid of those emails by putting entropy_dir="NO" into rc.conf of all jails. I'm not shure, is this secure? Also consider enabling cron time jitter for jailed crons, by putting something like this into jail rc.conf: cron_flags="-J10" -- Alexander Rusinov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
save-entropy errors on jail after update to 5.4-RELEASE
I updated my box and a jail that runs inside this box to 5.4-RELEASE yesterday. After it, I'm receiving emails from this jail with error messages about /usr/libexec/save-entropy I'm receiving messages like this: mv: /var/db/entropy/saved-entropy.7: No such file or directory mv: /var/db/entropy/saved-entropy.5: No such file or directory override r operator/operator for /var/db/entropy/saved-entropy.5? (y/n [n]) not overwritten override r operator/operator for /var/db/entropy/saved-entropy.4? (y/n [n]) not overwritten override r operator/operator for /var/db/entropy/saved-entropy.3? (y/n [n]) not overwritten override r operator/operator for /var/db/entropy/saved-entropy.2? (y/n [n]) not overwritten here is the files inside the jail: [EMAIL PROTECTED]:~> sudo ls -l /var/db/entropy/ total 16 -r 1 operator operator 2048 May 11 10:33 saved-entropy.1 -r 1 operator operator 2048 May 11 10:33 saved-entropy.2 -r 1 operator operator 2048 May 11 10:22 saved-entropy.3 -r 1 operator operator 2048 May 11 10:22 saved-entropy.4 -r 1 operator operator 2048 May 11 10:11 saved-entropy.5 -r 1 operator operator 2048 May 11 10:11 saved-entropy.6 -r 1 operator operator 2048 May 11 10:00 saved-entropy.7 -r 1 operator operator 2048 May 11 10:00 saved-entropy.8 Anybody could help me to fix it? thanks in advance -- Renato Botelho ICQ: 54596223 AIM: RBGargaBR ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Fwd: Cron <[EMAIL PROTECTED]> /usr/libexec/save-entropy]
Karol Kwiatkowski wrote: I'm not using 5.4 but I would look in the save-entropy script for a line that starts with 'X '. Also, looking at the source, have a look at /etc/rc.conf and/or /etc/defaults/rc.conf as they are read at the beginning of that script. Actually, I can reproduce such message by adding line with 'X ' at the beginning in /etc/rc.conf Thanks ... that was the tip I needed. I had the following in my /etc/rc.conf file: xfs_enable="NO" X font server I was missing the comment hash. Tom Veldhouse ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Fwd: Cron <[EMAIL PROTECTED]> /usr/libexec/save-entropy]
Thomas T. Veldhouse wrote: > Can anybody indicate to me what is causing the attached email and how to > fix it? I upgraded to the 5.4-STABLE as of yesterday and I am now > getting the attached email several time a day. Is this simply a script > error? [snip] > Cron <[EMAIL PROTECTED]> /usr/libexec/save-entropy > X: not found I'm not using 5.4 but I would look in the save-entropy script for a line that starts with 'X '. Also, looking at the source, have a look at /etc/rc.conf and/or /etc/defaults/rc.conf as they are read at the beginning of that script. Actually, I can reproduce such message by adding line with 'X ' at the beginning in /etc/rc.conf. Regards, Karol -- Karol Kwiatkowski ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[Fwd: Cron <[EMAIL PROTECTED]> /usr/libexec/save-entropy]
Can anybody indicate to me what is causing the attached email and how to fix it? I upgraded to the 5.4-STABLE as of yesterday and I am now getting the attached email several time a day. Is this simply a script error? Thanks, Tom Veldhouse --- Begin Message --- X: not found --- End Message --- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: save-entropy never exits
Giovanni P. Tirloni wrote: Hi, save-entropy never exists and eats all CPU. # uname -a FreeBSD srv-01 5.3-STABLE-SNAP001 FreeBSD 5.3-STABLE-SNAP001 #0: Sun Jan 30 03:57:47 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 # ps axl |grep entropy 2 14833 14832 0 8 0 1640 928 wait Is??0:00.03 /bin/sh -c /usr/libexec/save-entropy 2 14834 14833 263 128 0 1680 980 - R ?? 1884:17.36 /bin/sh /usr/libexec/save-entropy # uptime 11:56AM up 5 days, 19:14, 1 user, load averages: 1.00, 1.00, 1.00 [...] Sorry about replying to myself. I ran save-entropy by hand and it exits normally. This machine was running 5.2.1-RELEASE and had the same problem. I always had to kill it. I think it must be something related to the hardware but I'm not sure. -- Giovanni ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
save-entropy never exits
Hi, save-entropy never exists and eats all CPU. # uname -a FreeBSD srv-01 5.3-STABLE-SNAP001 FreeBSD 5.3-STABLE-SNAP001 #0: Sun Jan 30 03:57:47 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 # ps axl |grep entropy 2 14833 14832 0 8 0 1640 928 wait Is??0:00.03 /bin/sh -c /usr/libexec/save-entropy 2 14834 14833 263 128 0 1680 980 - R ?? 1884:17.36 /bin/sh /usr/libexec/save-entropy # uptime 11:56AM up 5 days, 19:14, 1 user, load averages: 1.00, 1.00, 1.00 # dmesg Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE-SNAP001 #0: Sun Jan 30 03:57:47 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD-K6tm w/ multimedia extensions (300.01-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x570 Stepping = 0 Features=0x8001bf AMD Features=0x400<> real memory = 96403456 (91 MB) avail memory = 84684800 (80 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 $PIR: No matching entry for 0.0.INTA agp0: mem 0xd000-0xd3ff at device 0.0 on pci0 atapci0: port 0x4000-0x400f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 14 at device 0.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xd5901000-0xd5901fff irq 9 at device 1.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pcib1: at device 2.0 on pci0 pci1: on pcib1 $PIR: ROUTE_INTERRUPT failed. pci1: at device 0.0 (no driver attached) xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xd000-0xd07f mem 0xd590-0xd590007f irq 10 at device 10.0 on pci0 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:50:04:d9:a8:78 rl0: port 0xd400-0xd4ff mem 0xd5902000-0xd59020ff irq 12 at device 11.0 on pci0 miibus1: on rl0 rlphy0: on miibus1 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:e0:7d:8c:32:47 xl1: <3Com 3c905B-TX Fast Etherlink XL> port 0xd800-0xd87f mem 0xd5903000-0xd590307f irq 5 at device 12.0 on pci0 miibus2: on xl1 xlphy1: <3Com internal media interface> on miibus2 xlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl1: Ethernet address: 00:10:5a:9f:df:89 pci0: at device 13.0 (no driver attached) cpu0 on motherboard orm0: at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounter "TSC" frequency 300012360 Hz quality 800 Timecounters tick every 10.000 msec ad0: 1222MB [2484/16/63] at ata0-master WDMA2 Mounting root from ufs:/dev/ad0s1a Does anyone have any idea about why it never exists and stays there eating all CPU ? -- Giovanni ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
