Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!uw-beaver!ssc-vax!uvicctr!sbanner1
From: sbanner1@uvicctr.UUCP
Newsgroups: comp.unix.questions
Subject: Re: .hushlogin
Message-ID: <253@uvicctr.UUCP>
Date: Thu, 21-May-87 17:02:28 EDT
Article-I.D.: uvicctr.253
Posted: Thu May 21 17:02:28 1987
Date-Received: Sat, 23-May-87 08:37:32 EDT
References: <7407@brl-adm.ARPA>
Reply-To: sbanner1@uvicctr.UUCP (S. John Banner)
Organization: University of Victoria, Victoria B.C. Canada
Lines: 30

In article <7407@brl-adm.ARPA> MARSELLE%gmr.com@RELAY.CS.NET writes:
>If I use a .hushlogin which looks like this:
>
>.hushlogin:	/etc/motd
>	cat /etc/motd
>	touch .hushlogin
>
>I get:
>Make: No arguments or description file.  Stop.
 
>I think I'll switch to someone else's suggestion and try:
>
>cmp -s .hushlogin /etc/motd
>if ($status) then
>	cat	/etc/motd | tee .hushlogin
>endif

This is the first thing in my .login, and I have a null .login.  I have
had no problems with it.  I only get the message when the file changes.

# Check for the message of the day.
find /etc/motd -newer ~/.hushlogin -exec cat /etc/motd \;
touch ~/.hushlogin

                      S. John Banner

...!uw-beaver!uvicctr!sol!sbanner1
...!ubc-vision!uvicctr!sol!sbanner1
ccsjb@uvvm
sbanner1@sol.UVIC.CDN