Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!dptg!mtune!jcm
From: jcm@mtune.ATT.COM (John McMillan)
Newsgroups: comp.sys.att
Subject: Re: fixed my problems with at and cron
Message-ID: <611@mtune.ATT.COM>
Date: 7 Jun 90 19:25:09 GMT
References: <1990Jun06.012638.5293@uhura.neoucom.EDU>
Distribution: na
Organization: AT&T BL Middletown/Lincroft NJ USA
Lines: 27

In article <1990Jun06.012638.5293@uhura.neoucom.EDU> wtm@uhura.neoucom.EDU (Bill Mayhew) writes:
>Hi,
>
>Thanks to all who mailed suggestions!
>
>What had happened is that my /etc/default/login file was specifying
>a ulimit of 4096.  A check in /etc/conf/cf.d/mtune showed that the
>kernel had been linked with a default value of 3072.  Adjusting the
>default/login file to agree with 3072 allowed files queued with at
>to be properly processed by cron.
:
>Thanks to the people who sent mail to help out.  I felt pretty dumb
>when I discovered the cause of the bug.
:
	Given the hundreds [thousands?] of folk who have tripped over
	this little gem, the only "pretty dumb" aspect is that the
	'init' code fails to announce the discrepancy during boot.

	And/or, during 'init [23]', just something like...:

	if ( K_ULIMIT < D_ULIMIT )	/* compare Tuning to Default data */
	    system("/bin/echo 'ULIMIT conflict: /etc/default/login vs stune' |\
			/bin/mail root");
	
	It takes so little and it means so much...

john mcmillan -- jcm@mtune.att.com -- muttering for self, only...