From owner-freebsd-questions Thu May 30 15:10:56 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA05048 for questions-outgoing; Thu, 30 May 1996 15:10:56 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA05033; Thu, 30 May 1996 15:10:54 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id PAA10623; Thu, 30 May 1996 15:10:25 -0700 Date: Thu, 30 May 1996 15:10:23 -0700 (PDT) From: Veggy Vinny To: Mike Pritchard cc: kelly@fsl.noaa.gov, terry@lambert.org, questions@FreeBSD.ORG Subject: Re: long motd files - screen pause? In-Reply-To: <199605302136.OAA29042@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 30 May 1996, Mike Pritchard wrote: > Veggy Vinny wrote: > > > > On Thu, 30 May 1996, Mike Pritchard wrote: > > > > > Sean Kelly wrote: > > > > > > > > >>>>> "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. > > > > > > If all you want is to have the thing paged, just run > > > it through more. If the term type is undefined, more > > > will simply pause after 24 lines, assuming that it is > > > a simple "dumb" terminal. You can't screw up too > > > much by assuming that (hard copy terminal maybe, but > > > the right options to more might even eliminate that). > > > If you get lucky, and the terminal type has been supplied > > > by rlogin or whatever, you are even better off. > > > > How do you get the motd to be displayed through more like what > > needs to be done? > > You would need to modify the login program to exec to fork and exec more > on /etc/motd. Hmm, okay... > However, I like the other alternatives mentioned before better. > Mostly because having a /etc/motd file that is automatically > paged at login could possibly cause problems for automated login > scripts. My ISP's PPP connection method used to require that > you fully login first and then run a command to establish the > PPP connection. It would have been a pain if I had to worry about > sending an extra c/r or two to make the motd display go away > when using my automated PPP scripts. > > Plus very long motds can cause problems if the user uses > something like "qterm" in their .login, since the output > might not drain in time, and qterm will timeout and not > set the terminal type correctly. > > Try using "msgs" or something else instead of overly long > motds, as was suggested by someone else. You can > always put "msgs -q" in /etc/csh.cshrc and /etc/profile > to notify users that there are new messages available. > If the message is really that important, a few line description in > /etc/motd pointing them at the "msgs" message should suffice. One question though, is there like a way to do a system default .hushlogin since there is one for .cshrc and .login in /etc/csh.cshrc and /etc/csh.login as it'll be hard putting one in evey users directory on the system as there are over 1500 users in the database. Also, is there a way to change everyone's group numbers to 32 without doing each one manually in vipw? Vince