Someone earlier mentioned a cron job being run at 7:00 AM, complaining
about the heavy CPU/memory usage. I've found another complication.
I had one new hard disk die just after installation. I was in the
process of transferring my Slackware Linux filesystem over to it when
the superblock
David R. Kohel wrote,
:Someone earlier mentioned a cron job being run at 7:00 AM, complaining
:about the heavy CPU/memory usage. I've found another complication.
:Does anyone have any suggestions on disk maintance, and how to keep a
:flawed disk up? Is this truely a hardware problem?
Your
-36.1
and hopefully this will help.
I had problems with cron dying, but one of the new versions fixed it. I'm
using cron 3.0pl1-36.1 now, and cron hasn't died in months..
--
#!/usr/bin/perl -i\$q='$q',\$p='$p';eval\$q.\$\^I\n# # [EMAIL PROTECTED]
$q='print$p$^I\n',$p='#!/usr/bin/perl -i';eval$q
On Jan 15, [EMAIL PROTECTED] (Adam Shand) wrote:
Hi,
I know this has been dealt with before
We're running cron 3.0pl1-32 on a debian 1.1 installation. Ocasionally
cron dies which is rather annoying.
[snip]
I have just upgraded to the latest verion on the FTP site cron 3.0pl1-36.1
The upgrade should solve your problem. The actual problem is
that if syslogd restarts, the syslog(3) call no longer works
for those processes that have used logopen(), because syslogd
is no longer listening on the other end of the pipe; instead,
SIGPIPE is generated. The temporary fix for cron was
Hi,
I know this has been dealt with before
We're running cron 3.0pl1-32 on a debian 1.1 installation. Ocasionally
cron dies which is rather annoying.
I seem to remember a couple people posting that a different version of cron
fixes this (Dylan's cron maybe?).
I have just upgraded to the
6 matches
Mail list logo
