Date: Tue, 11 Mar 2003 13:24:54 +0700 (KRAT) From: Eugene Grosbein <eugen@grosbein.pp.ru> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/49096: cron(8) may segfault when system open file table is full Message-ID: <200303110624.h2B6OsXP056404@gw2.svzserv.kemerovo.su>
next in thread | raw e-mail | index | archive | help
>Number: 49096 >Category: bin >Synopsis: cron(8) may segfault when system open file table is full >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Mar 10 22:30:04 PST 2003 >Closed-Date: >Last-Modified: >Originator: Eugene Grosbein >Release: FreeBSD 4.8-RC i386 >Organization: Svyaz Service JSC >Environment: System: FreeBSD gw2.svzserv.kemerovo.su 4.8-RC FreeBSD 4.8-RC #12: Tue Mar 4 02:15:40 KRAT 2003 sa@gw2.svzserv.kemerovo.su:/usr/obj/usr/src/sys/GW2 i386 >Description: I've found that cron(8) can segfault easily when a system table of open files is full or nearly full. I tried to rebuild cron with -O0 -g to analyze core dump, reproduced the problem but stack seems to be corrupted completely and gdb does not help. >How-To-Repeat: Run 'sysctl -a | grep files'. Make kern.maxfilesfiles and kern.maxfilesperproc so small that kernel table would be nearly full. Wait for cron to segfault. >Fix: Unknown for me. Eugene Grosbein >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?200303110624.h2B6OsXP056404>