[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-bugs
Subject:    system/878: cron leaks resources?
From:       chris () dqc ! org
Date:       1999-07-19 16:36:01
[Download RAW message or body]


>Number:         878
>Category:       system
>Synopsis:       cron leaks resources?
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 19 10:40:01 MDT 1999
>Last-Modified:
>Originator:     Chris Cappuccio
>Organization:
>Release:        2.5-current
>Environment:
	
	System      : OpenBSD 2.5
	Architecture: OpenBSD.i386
	Machine     : i386
>Description:
	Cron will die eating 100% cpu after a while if given the right
	circumstances...
>How-To-Repeat:
	*/1 * * * * /home/cricket/cricket/collect-subtrees normal
	*/3 * * * * /home/cricket/chttp

	Running cricket http://www.munitions.com/~jra/cricket
	every minute, cron will eventually stop doing anything
	and will eat 100% CPU.  Cricket has been running for about 3
	days once per minute...

	collect-subtrees runs some perl stuff that goes out and does
	snmp queries on various routers, it usually runs and is done
	in 10 seconds or less...

	'chttp' is a separate script that runs
	/home/cricket/cricket/collector /http-performance>&/dev/null

	This may also be a kernel resource problem, as after cron ate 100%
	strange things seem to happen randomly, and frequently, rebooting
	fixes it..

	dqc:pci {163} ls
	-csh in malloc(): error: recursive call.
	Abort (core dumped)
>Fix:
	Unknown!!!

>Audit-Trail:
>Unformatted:

[prev in list] [next in list] [prev in thread] [next in thread]