Date: Thu, 3 Mar 2011 15:11:02 +0300 From: Sergey Kandaurov <pluknet@gmail.com> To: Alex Keda <admin@lissyara.su> Cc: current@freebsd.org Subject: Re: login.conf: maxproc does not work when command running from cron? Message-ID: <AANLkTimM1-GXsi_mf3taC-%2B1X%2B4FgKwrV2-dRAggeq5H@mail.gmail.com> In-Reply-To: <4D6F6110.5060206@lissyara.su> References: <4D6F56B3.2020302@lissyara.su> <4D6F6110.5060206@lissyara.su>
index | next in thread | previous in thread | raw e-mail
2011/3/3 Alex Keda <admin@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. 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. -- wbr, pluknethelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimM1-GXsi_mf3taC-%2B1X%2B4FgKwrV2-dRAggeq5H>