Hi... I got bitten by this bug earlier today.
I was attempting to set 'autossh' to be respawned, via a new autossh.conf file. I copied the cron.conf file, and changed the exec line to the appropriate autossh command line, and left the rest the same. The mistake was that autossh doesn't fork into the background, but 'expect fork' was set. The outcome was that 'initctl stop autossh' and 'initctl start autossh' both hang, and I had to copy autossh.conf to autossh2.conf and delete the 'expect fork' line before I could get autossh to run. I can't get rid of the old autossh entry in 'initctl list', except possibly by rebooting. Since I'm remotely logged in, I don't want to do that unless I'm confident my connection is going to work... yay, catch-22. exec /usr/bin/autossh -M 81 -N -R 29:127.0.0.1:22 servername -- init: job stuck with expect fork/daemon when parent reaps child https://bugs.launchpad.net/bugs/406397 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
