Newsgroups: comp.unix.questions
Path: utzoo!utgpu!jmason
From: jmason@gpu.utcs.utoronto.ca (Jamie Mason)
Subject: Re: More uucico problems
Message-ID: <1991Feb10.043722.14454@gpu.utcs.utoronto.ca>
Organization: University of Toronto Computer Science Undergraduate Student
References: <1991Feb8.231342.23814@cs.umn.edu> <1991Feb9.222138.6831@informix.com>
Date: Sun, 10 Feb 91 04:37:22 GMT

In article <1991Feb8.231342.23814@cs.umn.edu> ianhogg@cs.umn.edu (Ian J. Hogg) writes:
>I've got past part of my uucp problems.  I've got a SparcStation with 

[ Stuff deleted ]

>Here is the full output from uucico on the Sun:

[ Stuff deleted ]

In article <1991Feb9.222138.6831@informix.com> dberg@informix.com (David I. Berg) writes:
>I recall from the backroads of my mind that there is a limit to how much in
>the way of login messages uucico will tolerate before surrendering. There
>was message traffic a few months ago about how to preclude a user (ie.
>uucp) from receiving login messages, but, alas, I didn't keep it. If
>this is, indeed, why uucico is failing, perhaps another netter will have
>kept that material.

	I do not know if this is system dependant or not, but on the
SunOS machines which I use, LOGIN(1) will refrain from printing the
message of the day, the check for mail, and the time of the last login,
if there is a file called ".hushlogin" in the user's home directory.

  I use it in one of my accounts where the "message of the day" does not
change for weeks, and is long and gets on my nerves.  I then have my
.login do the mail check, display the time of last login, and show the
MOTD itself...  But my .login only displays it if it has changed since I
last read it.  This way I only have to endure each MOTD once.

Jamie  ...  "Who was that Masked Interrupt?"
Written On  Saturday, February 9, 1991  at  11:34:45pm EST