From owner-freebsd-current@FreeBSD.ORG Thu Mar 3 12:16:17 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0A29106566C for ; Thu, 3 Mar 2011 12:16:17 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from mx.lissyara.su (mx.lissyara.su [77.73.25.118]) by mx1.freebsd.org (Postfix) with ESMTP id 56FA88FC15 for ; Thu, 3 Mar 2011 12:16:17 +0000 (UTC) Received: from [195.93.240.106] (port=32319 helo=lissyara.moskb.local) by mx.lissyara.su with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.74 (FreeBSD)) (envelope-from ) id 1Pv7S4-000A4F-3E for current@freebsd.org; Thu, 03 Mar 2011 15:16:16 +0300 Message-ID: <4D6F8690.3010108@lissyara.su> Date: Thu, 03 Mar 2011 15:16:16 +0300 From: Alex Keda User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; ru-RU; rv:1.8.1.23) Gecko/20091202 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 References: <4D6F56B3.2020302@lissyara.su> <4D6F6110.5060206@lissyara.su> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-White-List: YES X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: mx.lissyara.su Cc: current@freebsd.org Subject: Re: login.conf: maxproc does not work when command running from cron? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2011 12:16:17 -0000 03.03.2011 15:11, Sergey Kandaurov пишет: > 2011/3/3 Alex Keda: >> 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?