Following upgrade 6.3 7.0 /usr/libexec/save-entropy query

2008-07-17 Thread David Southwell
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

Re: Following upgrade 6.3 7.0 /usr/libexec/save-entropy query

2008-07-17 Thread Doug Barton
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

[Fwd: cvs commit: src/libexec/save-entropy save-entropy.sh]

2006-09-01 Thread Doug Barton
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

RE: save-entropy

2006-06-19 Thread Scott, Brian
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

save-entropy

2006-06-15 Thread Olivier Taylor
] 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

RE: save-entropy

2006-06-15 Thread David Schwartz
-Id: [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

Re: save-entropy

2006-06-15 Thread olivier.taylor
. # # $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

RE: save-entropy

2006-06-15 Thread Scott, Brian
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

Re: save-entropy

2006-06-15 Thread olivier.taylor
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

Re: /usr/libexec/save-entropy, IPv4: not found

2006-04-26 Thread Pete French
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

/usr/libexec/save-entropy, IPv4: not found

2006-04-25 Thread Pete French
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

Re: /usr/libexec/save-entropy, IPv4: not found

2006-04-25 Thread Doug Barton
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

save-entropy errors on jail after update to 5.4-RELEASE

2005-05-11 Thread Renato Botelho
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

Re: save-entropy errors on jail after update to 5.4-RELEASE

2005-05-11 Thread Alexander Rusinov
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

[Fwd: Cron [EMAIL PROTECTED] /usr/libexec/save-entropy]

2005-05-05 Thread Thomas T. Veldhouse
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 ---BeginMessage--- X: not found ---End Message---

Re: [Fwd: Cron [EMAIL PROTECTED] /usr/libexec/save-entropy]

2005-05-05 Thread Karol Kwiatkowski
/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

Re: [Fwd: Cron [EMAIL PROTECTED] /usr/libexec/save-entropy]

2005-05-05 Thread Thomas T. Veldhouse
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

save-entropy never exits

2005-03-16 Thread Giovanni P. Tirloni
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

Re: save-entropy never exits

2005-03-16 Thread Giovanni P. Tirloni
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