On Thu, Sep 29, 2016 at 03:33:48PM +0300, Evgeny Grin wrote: > > > On 29.09.2016 13:57, Otto Moerbeek wrote: > > On Thu, Sep 29, 2016 at 11:45:21AM +0300, Evgeny Grin wrote: > >> May be it also worth to mention in /etc/login.conf comments, that if > >> both '-max' and '-cur' were set for "default" class, it's required to > >> override explicitly both values in other classes, because 'openfiles' > >> (without suffix) setting will be ineffective. > > > > I don't think that is true in general. That only holds for daemon. > > > > Other cases are handled by login. > > OK, let's add comment at least for "daemon". > > And it's not clear from man pages: what will happen if 'openfiles-max' > and 'openfiles-cur' set for "default" class and 'openfiles' set for > "staff" class. Which value will be prioritized? > And vice versa - if 'openfiles' set for "default" class and > 'openfiles-max', 'openfiles-cur' set for "staff" class, which value will > be effective? > > 'openfiles' used only as example - it can be any of cputime, filesize, > datasize, stacksize, coredumpsize, memoryuse, memorylocked and maxproc. > > Is it possible to get right value with this API? > http://man.openbsd.org/login_cap.3 > > -- > Best Wishes, > Evgeny Grin
Th actual function (gsetrl()) to compute the resource limits is not exported from libc. If a name without a suffix is specified before any more specifc (-min or -max) name in the fully expanded record any -max or -min value will be ignored. getcap() does not implement this logic. -Otto