From owner-freebsd-current Sat Apr 24 9: 8:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 23F0515368 for ; Sat, 24 Apr 1999 09:08:17 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA17473; Sun, 25 Apr 1999 01:07:57 +0900 (JST) Message-ID: <3721E5EA.672014EB@newsguy.com> Date: Sun, 25 Apr 1999 00:40:26 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Andrzej Bialecki Cc: Stephane Legrand , Luigi Rizzo , current@FreeBSD.ORG Subject: Re: does login.conf limitations work ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > > On Sat, 24 Apr 1999, Stephane Legrand wrote: > > > > That's also my impression. I glipmsed the whole source tree and I couldn't > > > find any place where the limits are enforced. BTW. what entity should > > > enforce login time limits? Kernel? Some user-space daemon? > > > > To report a login.conf success, i've used on a 2.2.8 system the > > "cputime" ressource limit. I set it to zero and that worked very > > well. So may be only some limits are implemented ? > > You're right, this part works. However, I was talking about login time > (which is how long can user be logged on to the system), which isn't > checked anywhere. It isn't. Login.conf, just like, now, pam, is one of those cases of a wonderful clean, orthogonal solution which is only partially implemented. I personally think login time should be enforced through tty revocation. The main problem is that no solution exists which will do the right thing regarding processes to kill for all processes. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message