public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Francesco Talamona <francesco.talamona@know.eu>
Subject: Re: [gentoo-user] Re: vixie-cron keeps stopping
Date: Fri, 16 Apr 2010 23:33:39 +0200	[thread overview]
Message-ID: <201004162333.39669.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <201004161958.24097.francesco.talamona@know.eu>

On Friday 16 April 2010 19:58:23 Francesco Talamona wrote:
> On Thursday 15 April 2010, Alan McKinnon wrote:
> > On Thursday 15 April 2010 02:58:15 Matt Harrison wrote:
> > > I apologise if this has come twice, it didn't appear to post
> > > correctly first time, not even on the archives.
> > > 
> > > Its been happening for a while but I haven't got round to find out
> > > why, but every so often (anything between a week or an hour)
> > > vixie-cron just stops. There's nothing in the logs, the service
> > > just stops.
> > > 
> > > I have no idea where to start looking for a culprit so I'm hoping
> > > someone here has some good ideas :)
> > > 
> > > thanks in advance
> > > 
> > > Matt
> > 
> > You probably don't want to hear this, but:
> > 
> > vixie-cron is problematic in the extreme. I have endless hassle with
> > it's weird behaviours.
> > 
> > Use a different cron daemon.
> 
> Your advice is vague :)

To answer this point:

vixie-cron does not reliably restart. You have to remember to kill it, verify 
that it is indeed dead, then start it.

Of course, my use case is a lot more complex than just /etc/cron.*/* and yes, 
I do expect a cron daemon to cope with my needs in it's stride. It's not hard 
to cope with a 1000 line crontab. I have auth daemons running on ancient 
hardware with 256M RAM that have to deal with 100+ auth requests a second and 
a 5000-line config file. Despite my needs being complex, any cron daemon 
should cope with that without breaking a sweat

-- 
alan dot mckinnon at gmail dot com



  parent reply	other threads:[~2010-04-16 21:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-15  0:58 [gentoo-user] vixie-cron keeps stopping Matt Harrison
2010-04-15  1:58 ` Mark Knecht
2010-04-15  8:20 ` Alan McKinnon
2010-04-16  1:27   ` Matt Harrison
2010-04-16 17:58   ` [gentoo-user] " Francesco Talamona
2010-04-16 18:09     ` Stroller
2010-04-16 21:33     ` Alan McKinnon [this message]
2010-04-16 18:22   ` [gentoo-user] " kashani
2010-04-16 18:58     ` Mick
2010-04-16 18:29   ` Dale
2010-04-16 21:25     ` Alan McKinnon
2010-04-17  8:47       ` Mick
2010-04-17 10:25         ` Alan McKinnon
2010-04-17 12:59         ` [gentoo-user] " Lie Ryan
2010-04-17 13:08           ` Alan McKinnon
2010-04-17 14:19             ` Lie Ryan
2010-04-17 15:10             ` Mick
2010-04-17 15:39               ` Alan McKinnon
2010-04-17 18:12                 ` Mick
2010-04-17 19:52                   ` walt
2010-04-17 20:55                   ` Alan McKinnon
2010-04-17 22:01                     ` Mick
2010-04-17 22:05                       ` Mick
2010-04-17 13:13           ` David Relson
     [not found] <ezlKF-2tK-3@gated-at.bofh.it>
     [not found] ` <eAirn-1r6-1@gated-at.bofh.it>
     [not found]   ` <eAlyW-6UZ-19@gated-at.bofh.it>
     [not found]     ` <eAnr3-1Ei-5@gated-at.bofh.it>
2010-04-17 22:27       ` David W Noon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201004162333.39669.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=francesco.talamona@know.eu \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox