by
lr » Wed Jan 17, 2018 2:43 pm
No, the message doesn't bother rsync or scp when they run ssh internally. Now, if someone were to run commands remotely via ssh *and* parse the output, they would see that message. Dumb example: Do a "ssh <user>@sh.sonic.net ls -1": you will see one extra line at the beginning, which is not a file name, but the message. Personally, I don't think it's worth much of your time to work around; people who parse ssh output should know how to take life in their own hands
Completely unrelated observation, in case someone else trips over it: If you have ancient C or C++ executables that were compiled on shell, they may not work on sh, and give you this error message: "error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory". The correct response to this is (in my not at all humble opinion): recompile and relink your program, and don't bother the sys admin with this kind of minor stuff.