Markus Feilner wrote:
Am Mittwoch, 21. März 2018, 09:10:57 CET schrieb Markus Feilner:
Hmmm... I am seeing exactly the other side of the story: When I sshfs-mount a remote server, the .bashrc is executed/sourced without leaving a trace in the log files that someone has logged in. Thus I can execute commands and change files without a trace in w, who or last log. Seems weird to me.
Check your ~/.profile, maybe it sources .bashrc? I don't know sshfs, but likely it should use non-interactive shell mode, so indeed it should not read it by default. But as you don't log in (it's not a login-shell!) it is not logged as a login. And you don't need .bashrc for this effect. Just run 'ssh host <command>'. This wil also not leave a trace in w, who or last log.... You do see the ssh connect though in the sshd logs.
Oh, just realising $SUBJECT... my task is not restricted to Tumbleweed, works on all Linuxes I tried. Strange, though
As for my initial issue: That one was caused by an 'error' in /etc/bash.bashrc, which had not been properly updated by zypper/rpm. Normally config files should either be overwritten, or (if changed somehow) renamed to *.rpmsave and replaced, or the new one written as *.rpmnew. *None* of those happened to my /etc/bash.bashrc: It kept the old contents, but neither was a /etc/bash.bashrc.rpmnew created, nor was there any error message from the install. I *think* this is a bug, probably in rpm(?), but have so far not yet reported it separately, only mentioned in the thread of boo#1085834. Guess I should... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org