From owner-freebsd-current Sat Apr 24 7:39: 9 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 34AD514CB9 for ; Sat, 24 Apr 1999 07:39:07 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id F286C18C6; Sat, 24 Apr 1999 16:39:20 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id ED2AA49BD; Sat, 24 Apr 1999 16:39:20 +0200 (CEST) Date: Sat, 24 Apr 1999 16:39:20 +0200 (CEST) From: Andrzej Bialecki To: Stephane Legrand Cc: Luigi Rizzo , current@FreeBSD.ORG Subject: Re: does login.conf limitations work ? In-Reply-To: <199904241337.PAA01205@sequoia.mondomaineamoi.megalo> 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 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. 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