From owner-freebsd-questions Wed Dec 13 23: 2:22 2000 From owner-freebsd-questions@FreeBSD.ORG Wed Dec 13 23:02:21 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.219.91]) by hub.freebsd.org (Postfix) with SMTP id 063CF37B402 for ; Wed, 13 Dec 2000 23:02:10 -0800 (PST) Received: (qmail 3188 invoked from network); 14 Dec 2000 06:57:22 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 14 Dec 2000 06:57:22 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.9.3/8.9.3) with ESMTP id MAA30889; Thu, 14 Dec 2000 12:55:52 +0600 Date: Thu, 14 Dec 2000 12:55:52 +0600 (NOVT) From: Alexey Dokuchaev To: Guy Helmer Cc: questions@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: How come accounting limits of login.conf still doesn't work?! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Dec 2000, Guy Helmer wrote: > On Tue, 12 Dec 2000, Alexey Dokuchaev wrote: > > > There've been a nasty situation for quite a long time already with > > various accounting limits of login.conf... > > > > How come that all kewl features, such as sessionlimits, idletimes, etc all > > are documented in man login.conf(5), but never seemed to work? It's 4.2 > > already, and it still doesn't make any difference? > > The problem is that no process hangs around after a login to enforce these > limits. > > I have some dusty code that enforces time limits that I've been thinking > about improving (to handle all the "kewl" features you mention) and > bringing into (or invoking from) login(1). It would mean an extra process > hanging around for each login, but processes are cheap :-) So, is your code in usable stage and available as a patch? Do you have any plans committing into main source tree? Thanks. -- With all due respect, DAN Fe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message