Date: Sun, 27 Feb 2005 21:22:44 +0100 From: Anthony Atkielski <atkielski.anthony@wanadoo.fr> To: freebsd-questions@freebsd.org Subject: Re: Odd message from cron daemon Message-ID: <1923145231.20050227212244@wanadoo.fr> In-Reply-To: <20050227182135.GB44277@slackbox.xs4all.nl> References: <1244061749.20050227165831@wanadoo.fr> <20050227164906.GA44277@slackbox.xs4all.nl> <958577347.20050227184416@wanadoo.fr> <20050227182135.GB44277@slackbox.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Roland Smith writes: > Could it be that the cron output is mailed to someone else on the > production machine? I checked my aliases and stuff and sent some test messages to operator, and they get through okay. Apparently it's not happening on my production box, only on the test box. > It works OK on my 5.3 box, though. My system has revision 1.2 of > /usr/libexec/save-entropy, and it is 3073 bytes. Yours should be the > same, since the revision dates to Januari 2001. Yes, that's what I have as well, on both machines. > Is there any difference between /usr/libexec/save-entropy and > /usr/src/libexec/save-entropy/save-entropy.sh ? They should be > identical. They are the same on my machines. > Hmmm, disk or filesystem trouble maybe? I guess that would show in the > logfile. Maybe an fsck on /usr in single user mode helps? I have tons of SCSI errors on the test machine, for reasons unknown. I don't know if data is actually being lost or not. But even if that were the case, wouldn't I see the corruption in the save-entropy file? -- Anthony
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1923145231.20050227212244>