Date: Sat, 15 Dec 2007 16:18:31 -0600 From: Kevin Kinsey <kdk@daleco.biz> To: Rudy <crapsh@monkeybrains.net> Cc: FreeBSD <questions@freebsd.org> Subject: Re: cron pile up! Lot's of "cron: running job (cron)" Message-ID: <476452B7.4050205@daleco.biz> In-Reply-To: <47630ED2.5090400@monkeybrains.net> References: <4754C19E.5060708@monkeybrains.net> <4754CD5B.90605@daleco.biz> <4754DD17.6050701@monkeybrains.net> <20071204074444.GB12505@dan.emsphone.com> <476198EB.5010802@monkeybrains.net> <4761B4B4.8080100@daleco.biz> <4762FA39.50602@monkeybrains.net> <47630ED2.5090400@monkeybrains.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Rudy wrote: >> The thing is, sometimes it runs fine, other times it backlogs (It may >> complete at a latter date... the PID 82253 is still waiting ... Gonna >> see it it completes instead of killing all the stuck crons...). >> > > All the crons are cleared out right now... 'ps' shows only crond. > Related to putting the other cron job in " marks??? > Well, I think I messed up in my suggestion, by omitting the CRON at the end. My point/thought was, put the entire command "/path/to/script.sh ARG" in quotes. Cron is pretty archaic, and I wondered if it was trying to run "/path/to/script.sh" and "ARG" as two jobs instead of one, and hanging on "ARG" since CRON is something of a reserved word. IANAE, YMMV, and all that. Kevin Kinsey -- I like myself, but I won't say I'm as handsome as the bull that kidnapped Europa. -- Marcus Tullius Cicero
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?476452B7.4050205>