I have fish (2.1.1) set as my default login shell now on my Ubuntu (14.04.1) host. Mostly it works fine, but when I ssh into the host to run a command, so fish runs non-interactively, I get a bunch of errors:
andrex@helium ~> ssh helium w set_color: Could not set up terminal set_color: Could not set up terminal set_color: Could not set up terminal set_color: Could not set up terminal set_color: Could not set up terminal set_color: Could not set up terminal sed: -e expression #1, char 1: unknown command: `-' 22:27:09 up 15:53, 5 users, load average: 1.26, 1.96, 1.50 ... Requesting a TTY makes the errors go away: andrex@helium ~> ssh -t helium w 22:27:52 up 15:54, 6 users, load average: 1.57, 1.96, 1.52 ... But that sometimes has undesirable side effects, and it doesn't fix the problem in other non-interactive cases. For example, I get the same set of errors when root runs /bin/su -c 'run-parts --report /home/andrex/.cron.hourly 2>&1' andrex and in that case there's no easy way to ask for a TTY. Does anyone know what causes this problem, or how to fix it? Anyone else even seen it? Thanks, Andrew. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
