> > > Could a previous cronjob be hanging, waiting for the initscript to finish?
> > >
> > > I bet the daemon doesn't die as expected sometimes.
> >
> > Aha! looking at 'ps aux' we have:
> >
> > crond
> > /bin/bash /usr/bin/run-parts /etc/cron.daily
> > awk -v progname=/etc/cron.daily/gk-restart ..
On Wed, Dec 19, 2007 at 11:24:46AM -0600, Jeff Larsen alleged:
> > Could a previous cronjob be hanging, waiting for the initscript to finish?
> >
> > I bet the daemon doesn't die as expected sometimes.
>
> Aha! looking at 'ps aux' we have:
>
> crond
> /bin/bash /usr/bin/run-parts /etc/cron.daily
On Wed, Dec 19, 2007 at 10:52:43AM -0600, Jeff Larsen alleged:
> We have some third party software running on a CentOS 4.5 virtual
> machine. The software is delivered as compiled python and I wrote an
> init script for it myself (/etc/init.d/gk). Because the software lacks
> the usual robustness o
> Could a previous cronjob be hanging, waiting for the initscript to finish?
>
> I bet the daemon doesn't die as expected sometimes.
Aha! looking at 'ps aux' we have:
crond
/bin/bash /usr/bin/run-parts /etc/cron.daily
awk -v progname=/etc/cron.daily/gk-restart ...
All at 4:02 AM which is when c
4 matches
Mail list logo