Subject: login_cap(2)
To: None <current-users@netbsd.org>
From: john heasley <heas@shrubbery.net>
List: current-users
Date: 01/23/2001 14:04:08
Is it possible to disable login_cap functions?
the problem i am having is that bits, such as cron, do not utilize it;
therefore children of cron do not have their limits set appropriately
(maxproc in particular) but rather assume those of cron from boot-time,
which do not match the entries in login.conf either.
child of cron
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 65536
stack(kbytes) 512
coredump(blocks) unlimited
memory(kbytes) 240200
locked memory(kbytes) 80066
process(processes) 80
nofiles(descriptors) 64
vs child of login
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 262144
stack(kbytes) 262144
coredump(blocks) unlimited
memory(kbytes) unlimited
locked memory(kbytes) unlimited
process(processes) 1044
nofiles(descriptors) 3404
if cron is killed and restarted from a root shell, cron children have
the limits i expect.
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 262144
stack(kbytes) 262144
coredump(blocks) unlimited
memory(kbytes) unlimited
locked memory(kbytes) unlimited
process(processes) 1044
nofiles(descriptors) 3404
since login_cap seems half-baked (and useless for my purposes), i'd
prefer to just disable it. am i missing something?