Date: Fri, 16 Aug 2002 20:00:29 -0700 (PDT) From: Toby Burress <tburress@sjca.edu> To: freebsd-gnats-submit@FreeBSD.org Subject: i386/41741: Cron calling periodic spawns hundreds of sh Message-ID: <200208170300.g7H30TXY094108@www.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 41741 >Category: i386 >Synopsis: Cron calling periodic spawns hundreds of sh >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Aug 16 20:10:05 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Toby Burress >Release: 4.6-STABLE, 4.6-RELEASE >Organization: >Environment: FreeBSD newton.kurin.d2g.com 4.6-STABLE FreeBSD 4.6-STABLE #1: Tue Aug 13 13:24:27 EDT 2002 root@:/usr/obj/usr/src/sys/NEWTON i386 >Description: I have an Intel Celeron 333 with 208MB of RAM. Whenever Periodic is called by cron, so many sh will spawn that all processes lock up and I get "bash: fork: Resource temporarily unavailable" and have to hard-reboot. As root (under csh) the error simply is "no more processes." >How-To-Repeat: I think this problem is very hardware specific, as Google searches result in nothing and neither have I found anything here, but there have been no other odd errors (I've built world from -RELEASE to -STABLE with no problem) and I can call periodic manually with no problem. To repeat the problem, simply let cron call periodic daily|weekly|monthly. >Fix: No known fix. Comment out the cron and do it manually. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200208170300.g7H30TXY094108>