On Fri, 19 Feb 2016, The Doctor wrote: > Question: > > Why does make test do this: > run test connect.sh ... [...] > tset: standard error: Operation not supported > 5:27PM up 1 day, 2:57, 1 user, load averages: 4.84, 4.41, 5.99 > USER TTY FROM LOGIN@ IDLE WHAT > doctor p0 ts1p19.nl2k.ab.c Fri12PM 27 script > Filesystem Type Size Used Avail Use% Mounted on > /dev/sd0a ufs 3.9G 1.7G 2.1G 45% / > /dev/sd0h ufs 88G 41G 44G 49% /usr > /dev/sd0g ufs 88G 33G 52G 39% /var > /dev/sd0f ufs 88G 57G 28G 68% /usr/home > mfs:27 mfs 992M 4.2M 939M 1% /tmp > Delete is backspace > /root/.bashrc: line 227: /usr/contrib/lib/news/bin/ctlinnd: No such file or directory > daemon: /var/news/etc/send-uucp: No such file or directory > ok simple connect It looks like you have shell initialisation scripts that produce output for non-interactive shells. This will mess up the tests in all sorts of ways. You should move anything that sends output from .bashrc to .bash_profile. > run test proxy-connect.sh ... > test: syntax error > test: syntax error I'm not sure what is going wrong here, but I suspect that something (more shell initialisation stuff) is messing up the $SSH_CONNECTION variable. > plain username protocol 2 privsep=no comp=no > tset: standard error: Operation not supported Looks like tset is running for non-interactive shells too. > bad SSH_CONNECTION protocol 2 privsep=no comp=no: 5:27PM up 1 day, 2:57, 1 user, load averages: 4.84, 4.41, 5.99 Yeah, SSH_CONNECTION is being clobbered by output from your shell init scripts. -d _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
