On 2014-06-12 22:36, Pat Riehecky wrote: > On 06/12/2014 03:25 PM, Karanbir Singh wrote: >> On 06/12/2014 09:22 PM, Les Mikesell wrote: >>> Minor warning: if you are using backuppc to back up a host with rsync >>> over ssh, it will fail if there is any output before the rsync >>> startup. Native rsync will ignore it, but not the backuppc server's >>> rsync-in-perl implementation. So, randomly adding messages at login >>> may have side effects. >>> >> does it fail, with enough context to figure out what happened ? if so, >> we then just need to make it easy to turn off. >> >> > Similarly, putting the content in /etc/motd may have issues. > > A few remote connection protocols offer up /etc/motd before users > authenticate. Sending out to anonymous users "You've got 300 un-applied > updates" might be bad. > > Pat > Isn't that what /etc/issue is for? Sounds like something that should be reported as a bug and/or worked around regardless. /etc/motd is not displayed on non-interactive ssh logins (at least not in the one case I have available to test with).