From owner-freebsd-current Sat Apr 24 2:35:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 376F814E6C for ; Sat, 24 Apr 1999 02:35:09 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 5A29A18C6; Sat, 24 Apr 1999 11:35:22 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 571C349C2; Sat, 24 Apr 1999 11:35:22 +0200 (CEST) Date: Sat, 24 Apr 1999 11:35:21 +0200 (CEST) From: Andrzej Bialecki To: Luigi Rizzo Cc: current@FreeBSD.ORG Subject: Re: does login.conf limitations work ? In-Reply-To: <199904231110.NAA00657@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Apr 1999, Luigi Rizzo wrote: > Hi, > > i was wondering if the limitations that are supposed to be enforced via > the login.conf mechanism do really work... > > In particular, i have tried (on 3.1 something, but don't think that > current is much different in this respect) to enforce the daily etc. > login times but the system seems to ignore them. > > I think /etc/login.conf is properly parsed, because if i assign a user > to a class that is not defined in login.conf i get complaints, but > other than that i am unable to limit login time... > > Any hints ? 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? Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message