Date: Mon, 11 Jan 1999 01:33:00 -0600 (CST) From: Kevin Day <toasty@home.dragondata.com> To: abial@nask.pl (Andrzej Bialecki) Cc: robert+freebsd@cyrus.watson.org, des@flood.ping.uio.no, hackers@FreeBSD.ORG Subject: Re: proposed mod to ps(1) Message-ID: <199901110733.BAA15813@home.dragondata.com> In-Reply-To: <Pine.BSF.4.02A.9901110835120.6084-100000@korin.warman.org.pl> from Andrzej Bialecki at "Jan 11, 1999 8:36:55 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sun, 10 Jan 1999, Robert Watson wrote: > > > On 7 Jan 1999, Dag-Erling Smorgrav wrote: > > > > > Wouldn't it make sense to add an option to ps(1) to display the login > > > class of each process? > > > > I was under the impression that 'login class' was really a property of the > > class database in userland, and that the kernel didn't know what class you > > were in, just the current process properties (resource limits, etc). > > Programs such as 'login' set their resource limitations based on these > > class entries. As such, ps would not know the 'class' on a per-process > > while on the subject... Does any of you know how login time limits are > enforced? I couldn't find any place where it is done, and the real-life > evidence seems to support my view that currently they are being just > ignored... > AFAIK, the only way to enforce login time limits is through idled, which is in ports. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901110733.BAA15813>