misc/155480: login.conf: maxproc does not work when command running from cron

[Alex Keda]

>Number:         155480
>Category:       misc
>Synopsis:       login.conf: maxproc does not work when command running from cron
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Mar 11 18:40:05 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     Alex Keda
>Release:        8.2-RELEASE
>Organization:
USSR
>Environment:
FreeBSD srv2.host-food.ru 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Tue Mar  1 21:17:04 MSK 2011     lissyara at srv10.host-food.ru:/home/usr_moved/obj/home/usr_moved/src/sys/HOST-FOOD  amd64

>Description:
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#

then, run command:

lissyara# cap_mkdb -v /etc/login.conf
cap_mkdb: 10 capability records
lissyara#

add user:

lissyara# grep ^test1234 /etc/master.passwd
test1234:$1$kj/WOTuN$vLGcOBPv9ro8eljOe.ChA1:1002:1004:id100:0:0:User &:/home/test1234:/bin/sh
lissyara#

add cron job for user:

lissyara# crontab -l -u test1234
* * * * * /bin/sleep 72000
* * * * * /bin/sleep 72000
* * * * * /bin/sleep 72000
* * * * * /bin/sleep 72000
* * * * * /bin/sleep 72000
* * * * * /bin/sleep 72000
* * * * * /bin/sleep 72000
* * * * * /bin/sleep 72000
* * * * * /bin/sleep 72000
* * * * * /bin/sleep 72000
* * * * * /bin/sleep 72000
* * * * * /bin/sleep 72000
* * * * * /bin/sleep 72000
lissyara#

after some time I see lot sleep processes in ps output

lissyara# ps -auxww | grep ^test1234 | grep sleep | wc -l
     130
lissyara#

130 > 12

========
If I running commands from ssh session - all OK, I cannot run more than maxproc processes...

http://lists.freebsd.org/pipermail/freebsd-current/2011-March/023234.html

It's very serious problem - for shared hostings servers and such other applications where users have access to create cron jobs
>How-To-Repeat:
see full desc
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: