From owner-freebsd-questions Thu May 30 08:31:42 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA14277 for questions-outgoing; Thu, 30 May 1996 08:31:42 -0700 (PDT) Received: from gatekeeper.fsl.noaa.gov (gatekeeper.fsl.noaa.gov [137.75.131.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA14263 for ; Thu, 30 May 1996 08:31:39 -0700 (PDT) Received: from emu.fsl.noaa.gov (kelly@emu.fsl.noaa.gov [137.75.60.32]) by gatekeeper.fsl.noaa.gov (8.7.5/8.7.3) with ESMTP id PAA16583; Thu, 30 May 1996 15:28:02 GMT Message-Id: <199605301528.PAA16583@gatekeeper.fsl.noaa.gov> Received: by emu.fsl.noaa.gov (1.40.112.3/16.2) id AA225510077; Thu, 30 May 1996 09:27:57 -0600 Date: Thu, 30 May 1996 09:27:57 -0600 From: Sean Kelly To: richardc@CSUA.Berkeley.EDU Cc: terry@lambert.org, terry@lambert.org, questions@FreeBSD.ORG In-Reply-To: (message from Veggy Vinny on Wed, 29 May 1996 16:02:26 -0700 (PDT)) Subject: Re: long motd files - screen pause? Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>> "Veggy" == Veggy Vinny writes: Veggy> Hmmm, okay but how do some machines make the motd Veggy> pause even before it knows the termcap? By ``cheating'' with the default user setup, perhaps. When creating new users, just give 'em a .hushlogin file so /usr/bin/login won't do any of the normal introductory stuff. Then, give 'em a .login (assuming csh/compatible here) that does the following: 1. Determines the terminal type. 2. Shows if password is about to expire (two week warning). 3. Shows if account is about to expire (two week warning). 4. Show last login. 5. Warn if no kerberos tickets are issued. 6. Show the Regents copyright. 7. Page the motd. 8. Show if there's mail. Step 7 will work as a consequence of step 1. -- Sean Kelly NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/