[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: runaway crons



On Tue, May 30, 2000 at 09:17:40PM -0500, Brad wrote:
> On Tue, May 30, 2000 at 11:50:12AM -0700, kmself@ix.netcom.com wrote:
> > I hit my work system remotely this morning to check mail and got
> > 
> >    bash:  fork: resource temporarily unavailable
> >
> [SNIP]
> > there too).  pstree showed a heck of a lot of cron jobs.  Found and
> > killed the root cron process, then slaughtered the rest with:
> 
> Do any of your users have anything in their crontabs (look in
> /var/spool/cron/crontabs)? Is there anything odd in /etc/cron*? Any
> funny-looking entries in /var/log/syslog, /var/log/cron.log, or wherever
> else cron logs to on your system?

hmm that brings up an interesting question, is there a way to enforce
resource limits on users' cron jobs?  that would seem to be a
convenient way to bypass the pam based resource limits, that would
ordinarly stop things like fork bombs or such...

> 
> -- 
>   finger for GPG public key.



-- 
Ethan Benson
http://www.alaska.net/~erbenson/

Attachment: pgpFCci0AI53I.pgp
Description: PGP signature


Reply to: