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-entr
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 dir
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 B
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
#x27;--' 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/s
tartup 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
Su
UCH 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=/bi
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:
&
-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@freeb
> 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
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
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 morning
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
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/
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
L 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
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 ---
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
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
19 matches
Mail list logo
