mitch@rock.sgi.com (Tom Mitchell) (03/01/90)
In article <51649@sgi.sgi.com> brendan@illyria.wpd.sgi.com (Brendan Eich) writes: * In article <9002220905.aa28986@VAT.BRL.MIL>, jra@BRL.MIL ("John R. Anderson", VLD/ASB) writes: * > 1. The other day, I changed the net addresses on our PI's, and * > at the same time I happened to place a notice to the user's in /etc/motd. * > Afterwards, "rcp" no longer worked correctly. * The BSD rcp protocol is fragile: as the friendly manual page says in its * BUGS section: * * [Rcp is] confused by any output generated by commands in a .login, * .profile, or .cshrc file on the remote host. * Good stuff about 'cat'ing the motd. One other common hit on this same problem is with the shell prompt. It is useful to ALWAYS check to see it the prompt variable exists and then iff it exists set it to your liking. EXAMPLE for csh: if ($?prompt) set prompt = "csh--`hostname`[\!] " I learned this the hard way with the take option of BSD's tip program. What if one did: "if ($?prompt) cat /etc/motd"? Thomas P. Mitchell -- mitch@sgi.com "All things in moderation; including moderation."