I have several computers set up with rsa key auth. so that there are no passwords required to execute remote commands using ssh. It seems like the "start" phase of the /etc/init.d/distccd script doesn't like being executed from ssh. Use of the -n option only cause the "start" to fail, instead of hang. Reproducible: Always Steps to Reproduce: 1.Set up distccd as per the official guide on a computer '1'. 2.Set up rsa key authentication so that paswords are not needed to log in to '1' from '2'. 3. On '2' try the following. A.ssh root@1 "/etc/init.d/distccd stop" B.ssh root@1 "/etc/init.d/distccd start" C.ssh root@1 "/etc/init.d/distccd restart" D.ssh -n root@1 "/etc/init.d/distccd [re]start" Actual Results: A. executes fine B. hangs at "* Starting distccd..." C. same D. results in: " * Starting distccd... [ !! ]" Expected Results: A. as expected B. should result in " * Starting distccd... [ ok ]" C. same D. same I thought maybe it was the start-stop-daemon command inside /etc/init.d/distccd; however a similar /etc/init.d script, namely lisa, succeeded all 4 executions listed above. The easy workaround is to provide some useless input on stdin to the /etc/init.d script, ie: ssh -n root@1 "echo \" \" | /etc/init.d/distccd [re]start"
Baselayout guys, is this a bug with the distccd script? or an issue with the way init.d works? or some other issue?
this is more a 'bug' with ssh happens (for me at least) with any app that is started via ssh that the ssh session when exiting hangs/doesnt close right hitting <enter>~. should tell it to disconnect tho i have a feeling tho if you ask openssh upstream its a feature not a bug...
http://openssh.org/faq.html#3.10 http://bugzilla.mindrot.org/show_bug.cgi?id=52
taking into consideration comment 3 and comment 4 i have to close this as it is a problem upstream with openssh.
