From owner-freebsd-questions Wed Nov 10 7:33:38 1999 Delivered-To: freebsd-questions@freebsd.org Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (Postfix) with ESMTP id 7C41114DDA for ; Wed, 10 Nov 1999 07:33:34 -0800 (PST) (envelope-from lowell@world.std.com) Received: from world.std.com (lowell@world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with ESMTP id KAA15036; Wed, 10 Nov 1999 10:33:33 -0500 (EST) Received: (from lowell@localhost) by world.std.com (8.9.3/8.9.3) id KAA09443; Wed, 10 Nov 1999 10:33:33 -0500 (EST) Date: Wed, 10 Nov 1999 10:33:33 -0500 (EST) Message-Id: <199911101533.KAA09443@world.std.com> From: Lowell Gilbert To: wdr@tdl.com Cc: freebsd-questions@FreeBSD.ORG In-reply-to: <382917FF.57740A41@tdl.com> (message from William Richard on Tue, 09 Nov 1999 23:00:15 -0800) Subject: Re: XDM question. References: <13D5F9EDFD72D211BC3100105A1C2233054993@akira.lanfear.com> <382882E7.D6E2B076@tdl.com> <382917FF.57740A41@tdl.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Tue, 09 Nov 1999 23:00:15 -0800 From: William Richard Lowell Gilbert wrote: > William Richard writes: > > Marc Wandschneider wrote: > I'd recommend using login.conf for this instead. If anyone ever logs > in *other* than through X, you probably want them to get the same > environment inside a shell that they would by starting a shell in an > xterm under X. This isn't a conclusive test, but I created a /var/run/nologin, and my test showed that xdm(1) is no respecter of /var/run/nologin, and I would think that it's no respecter of /etc/login.conf. The expression login.conf never appears in the xdm(1) manpage. Have you made xdm(1) read login.conf(5)? How so? Resource limits are picked up (and respected) in xdm. Environment settings, I guess, are not. Sorry about that; although I build my paths up in my user startup scripts, I remember being annoyed that I couldn't set BLOCKSIZE in login.conf and have that show up under X. It doesn't seem like it would be that hard to slap together a program to extract those capabilities from login.conf, but you'd have to also grab the class out of the password database, and pick up the results in a parent process. It's not very useful on single-user machines, but maybe I'll have a go at it some time anyway. Be well. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message