On Wed, 22 Mar 2017 23:57:56 -0500 Les Mikesell <lesmikes...@gmail.com> wrote:
Hi Les, sorry for the delayed follow-up, You were absolutely right: my (bad) habit to insert echoes in root's .bashrc (to remind me I've some things to do on the machine when I ssh it) was the reason it failed; commenting all echo lines re-established a normal behavior, thanks ! :) Jean-Yves > The remote system is sending some output before starting rsync over > the ssh login. There is probably something being started in > /etc/profile, /etc/bashrc or root's .profile or .bashrc that is > complaining about not having TERM set - which it won't with ssh trying > to start a command remotely. > On Wed, Mar 22, 2017 at 11:48 PM, Bzzzz <lazyvi...@gmx.com> wrote: > > > > Got remote protocol 1297237332 > > Fatal error (bad version): TERM environment variable not set. > > > > Sent exclude: /1.8EB_01 > > … > > > > > > The bad listing issued is all trashed (many characters like little > > boxes w/ points in, no text alignement, almost unreadable). > > > > I see the "Got remote protocol" is wrong, but can't figure why; I > > do not understand either the "TERM envvar not set" as it is set! > > > > as the BPC user: > > $ echo $TERM > > xterm > > > > Does anybody have a clue about that ? > > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
