Re: Completely off topic: supervise cron?
> From: [EMAIL PROTECTED] > Date: 9 Jun 1999 13:38:21 -0400 > > >> On Wed, 09 Jun 1999 09:26:11 -0500, > >> "Chris Garrigues" <[EMAIL PROTECTED]> said: > > C> I've got a system on which cron keeps dying. Would it work to run cron > C> under supervise? > >Probably, but I'd recommend fixing the root problem by replacing your >cron with something more robust. I had the same problem under >Solaris-2.5.1, and replaced the system cron with another version called >"dcron": >ftp://sunsite.unc.edu/pub/Linux/system/daemons/cron/dcron-2.3.3.tar.gz > >As it turns out, something I did was causing cron to die periodically, >but I still like the new one better: > >a. I can schedule jobs to run every 5 minutes starting 3 minutes after > the hour by using something like this in the "minutes" field: 3-58/5 I don't need that, but cute nevertheless. >b. I use accustamp, tailocal, and cyclog to handle all logging, so I > don't have to restart cron just to clean up log files. So you're saying dcron works with djb's tools? >c. It's written very cleanly, and it's smaller than Vixie-cron. That's a plus. I've been hoping not to modify the distribution too much since I have to replicate it, but you're making a pretty good case. I'll take a look. Do you know if it's been RPM'd? Chris -- Chris Garrigues virCIO +1 512 432 4046 4314 Avenue CO- http://www.DeepEddy.Com/~cwg/ Austin, TX 78751-3709 +1 512 374 0500 My email address is an experiment in SPAM elimination. For an explanation of what we're doing, see http://www.DeepEddy.Com/tms.html Nobody ever got fired for buying Microsoft, but they could get fired for relying on Microsoft. PGP signature
cron complaing about qmail [was Re: Completely off topic: supervise cron?]
> From: "Chris Garrigues" <[EMAIL PROTECTED]> > Date: Wed, 09 Jun 1999 09:26:11 -0500 > > I've got a system on which cron keeps dying. > > Would it work to run cron under supervise? As I worked on tracking this problem down, I found that the last log entries for vixie-cron were: root (06/06-00:00:15-15757) MAIL (mailed 11060 bytes of output but got status 0x006f ) root (06/06-00:00:15-30191) MAIL (mailed 11839 bytes of output but got status 0x006f ) root (06/06-00:00:15-17528) MAIL (mailed 7360 bytes of output but got status 0x006f ) root (06/06-00:00:15-4607) MAIL (mailed 13738 bytes of output but got status 0x006f ) and Vixie asked me why qmail was sending a non-zero error code. here's the qmail log from that time (run through tailocal): 1999-06-06 00:00:15.087851 new msg 4386 1999-06-06 00:00:15.087860 info msg 4386: bytes 2004 from <[EMAIL PROTECTED]> qp 23495 uid 0 1999-06-06 00:00:15.091695 starting delivery 6975: msg 4386 to local [EMAIL PROTECTED] 1999-06-06 00:00:15.091713 status: local 1/10 remote 0/20 1999-06-06 00:00:15.547616 new msg 4387 1999-06-06 00:00:15.547625 info msg 4387: bytes 2117 from <[EMAIL PROTECTED]> qp 23501 uid 7790 1999-06-06 00:00:15.577459 starting delivery 6976: msg 4387 to local [EMAIL PROTECTED] 1999-06-06 00:00:15.577476 status: local 2/10 remote 0/20 1999-06-06 00:00:15.577487 delivery 6975: success: [EMAIL PROTECTED]/forward:_qp_23501/did_0+0+1/ 1999-06-06 00:00:15.577510 status: local 1/10 remote 0/20 1999-06-06 00:00:15.577521 end msg 4386 1999-06-06 00:00:16.077629 new msg 4386 1999-06-06 00:00:16.077638 info msg 4386: bytes 2226 from <[EMAIL PROTECTED]> qp 23504 uid 7790 1999-06-06 00:00:16.127659 starting delivery 6977: msg 4386 to local [EMAIL PROTECTED] 1999-06-06 00:00:16.127677 status: local 2/10 remote 0/20 1999-06-06 00:00:16.127688 starting delivery 6978: msg 4386 to remote [EMAIL PROTECTED] 1999-06-06 00:00:16.127705 status: local 2/10 remote 1/20 1999-06-06 00:00:16.127716 delivery 6976: success: did_0+4+0/qp_23504/ 1999-06-06 00:00:16.127728 status: local 1/10 remote 1/20 1999-06-06 00:00:16.127739 starting delivery 6979: msg 4386 to local [EMAIL PROTECTED] 1999-06-06 00:00:16.127756 status: local 2/10 remote 1/20 1999-06-06 00:00:16.127767 end msg 4387 1999-06-06 00:00:16.128615 starting delivery 6980: msg 4386 to local [EMAIL PROTECTED] 1999-06-06 00:00:16.128633 status: local 3/10 remote 1/20 1999-06-06 00:00:16.450693 delivery 6978: success: 10.1.1.1_accepted_message./Remote_host_said:_250_ok_928645216_qp_24445/ 1999-06-06 00:00:16.450716 status: local 3/10 remote 0/20 1999-06-06 00:00:16.910468 new msg 4389 1999-06-06 00:00:16.910478 info msg 4389: bytes 2341 from <[EMAIL PROTECTED]> qp 23522 uid 7790 1999-06-06 00:00:16.912152 starting delivery 6981: msg 4389 to remote [EMAIL PROTECTED] 1999-06-06 00:00:16.912170 status: local 3/10 remote 1/20 1999-06-06 00:00:16.914047 delivery 6977: success: [EMAIL PROTECTED]/forward:_qp_23522/did_0+0+1/ 1999-06-06 00:00:16.914072 status: local 2/10 remote 1/20 1999-06-06 00:00:16.917547 new msg 4387 1999-06-06 00:00:16.917555 info msg 4387: bytes 2339 from <[EMAIL PROTECTED]> qp 23521 uid 7790 1999-06-06 00:00:16.919209 starting delivery 6982: msg 4387 to remote [EMAIL PROTECTED] 1999-06-06 00:00:16.919227 status: local 2/10 remote 2/20 1999-06-06 00:00:16.919747 delivery 6979: success: [EMAIL PROTECTED]/forward:_qp_23521/did_0+0+1/ 1999-06-06 00:00:16.919771 status: local 1/10 remote 2/20 -- Chris Garrigues virCIO +1 512 432 4046 4314 Avenue CO- http://www.DeepEddy.Com/~cwg/ Austin, TX 78751-3709 +1 512 374 0500 My email address is an experiment in SPAM elimination. For an explanation of what we're doing, see http://www.DeepEddy.Com/tms.html Nobody ever got fired for buying Microsoft, but they could get fired for relying on Microsoft. PGP signature
Re: Completely off topic: supervise cron?
>> On Wed, 09 Jun 1999 09:26:11 -0500, >> "Chris Garrigues" <[EMAIL PROTECTED]> said: C> I've got a system on which cron keeps dying. Would it work to run cron C> under supervise? Probably, but I'd recommend fixing the root problem by replacing your cron with something more robust. I had the same problem under Solaris-2.5.1, and replaced the system cron with another version called "dcron": ftp://sunsite.unc.edu/pub/Linux/system/daemons/cron/dcron-2.3.3.tar.gz As it turns out, something I did was causing cron to die periodically, but I still like the new one better: a. I can schedule jobs to run every 5 minutes starting 3 minutes after the hour by using something like this in the "minutes" field: 3-58/5 b. I use accustamp, tailocal, and cyclog to handle all logging, so I don't have to restart cron just to clean up log files. c. It's written very cleanly, and it's smaller than Vixie-cron. I had to add some code to make it work under Solaris. If anyone's interested, let me know. -- Karl Vogel ASC/YCOA, Wright-Patterson AFB, OH 45433, USA [EMAIL PROTECTED] or [EMAIL PROTECTED] I was thrown out of college for cheating on the metaphysics exam; I looked into the soul of the boy next to me. --Woody Allen
Re: Completely off topic: supervise cron?
On Wed, Jun 09, 1999 at 04:26:11PM +0200, Chris Garrigues wrote: > Would it work to run cron under supervise? All cron's I know daemonize themselves (by, say, double-forking and disassociating themselves from their ctty). Hence: no. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/_/ [EMAIL PROTECTED] _/_/ _/_/_/ use Std::Disclaimer;
Completely off topic: supervise cron?
I've got a system on which cron keeps dying. Would it work to run cron under supervise? Chris -- Chris Garrigues virCIO +1 512 432 4046 4314 Avenue CO- http://www.DeepEddy.Com/~cwg/ Austin, TX 78751-3709 +1 512 374 0500 My email address is an experiment in SPAM elimination. For an explanation of what we're doing, see http://www.DeepEddy.Com/tms.html Nobody ever got fired for buying Microsoft, but they could get fired for relying on Microsoft. PGP signature
