fixed my problems with at and cron
John McMillan
jcm at mtune.ATT.COM
Fri Jun 8 05:25:09 AEST 1990
In article <1990Jun06.012638.5293 at uhura.neoucom.EDU> wtm at 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 at mtune.att.com -- muttering for self, only...
More information about the Comp.sys.att
mailing list