From owner-freebsd-questions Tue Nov 25 12:46:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA25982 for questions-outgoing; Tue, 25 Nov 1997 12:46:46 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA25967 for ; Tue, 25 Nov 1997 12:46:40 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.7) with SMTP id MAA17568; Tue, 25 Nov 1997 12:46:30 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Tue, 25 Nov 1997 12:46:30 -0800 (PST) From: Doug White Reply-To: Doug White To: Weldon S Godfrey 3 cc: questions@FreeBSD.ORG Subject: Re: idletime in login.conf In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 22 Nov 1997, Weldon S Godfrey 3 wrote: > I placed in /etc/login.conf and ran cap_mkdb...I also tried placing a > .login_conf in the user directory. > > The entry looked liked this > > lgroup|Login group:idletime=20s: As mentioned before, this isn't implemented yet. However, tcsh and other c-shell deriviatives have a timeout that you can set through /etc/cshrc. Unfortunately the user can override this if they opt to, but I guess that depends how savvy your userbase is. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major