login.conf: maxproc does not work when command running from cron?

Alex Keda admin at lissyara.su
Thu Mar 3 12:16:17 UTC 2011

03.03.2011 15:11, Sergey Kandaurov пишет:
> 2011/3/3 Alex Keda<admin at lissyara.su>:
>> 03.03.2011 11:52, Alex Keda пишет:
>>> I create login class:
>>> lissyara# grep id100 --after-context=7 /etc/login.conf
>>> id100:\
>>>         :coredumpsize=1:\
>>>         :cputime=60s:\
>>>         :maxproc=12:\
>>>         :openfiles=32:\
>>>         :priority=20:\
>>>         :tc=default:
>>> lissyara#
>> another parameters (I test cputime, priority) work correct
> Indeed. and I was able to reproduce it too, fyi.
> That doesn't really work because cron doesn't perform further
> fork()s after RLIMIT_NPROC limit is set, but it only exec() a task.
it's not good. it's problem for some situations - hosting servers, etc...

> E.g. my cron implementation used at work does an additional fork
> necessary for some teardown work thus it doesn't suffer from
> this problem.
what's your cron implementation?

More information about the freebsd-current mailing list