[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
Note that this also causes libc6 upgrades to not restart the ssh service. See more info in the duplicate report bug #709468. Submitting merge proposal which causes the init.d script to run /lib/init/upstart-job when it is not running in a chroot. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/531912 Title: /etc/init.d/ssh seems to work, but actually upstart is used. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
** Branch linked: lp:~clint-fewbar/ubuntu/natty/openssh/init.d-chroot- aware -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/531912 Title: /etc/init.d/ssh seems to work, but actually upstart is used. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
Thank you for your answer Colin. I reported the SIGHUP part in this bug because this seems to be what the traditional init script does when doing a reload of ssh, and this is the reason why such an operation fails to combine with Upstart. -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
The state in lucid is really problematic. Afaik, the init.d scripts are supposed to provide wrappers for upstart in the transition period, and we are using them in a lot of old scripts to manage our fleet. Reloading ssh with /etc/init.d/ssh reload resulted in a weird state where upstart believes ssh is stopped, while it's still up but upstart has no way to control it until the service is stopped from the init.d script. Additionally, doing a kill -1 on sshd leads to the same bug: upstart thinks sshd is stopped when it's really reloaded. Is there a fix planned in -updates for lucid? What is planned for future releases? -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
This upstart-'upgrade' (along with plymouth implementation) is one of the points where Canonical chose to neglect the LTS part and implement unfinished beta stuff in a version of Ubuntu on which everyone should be able to rely. Unfortunatly, they are now busy dropping gnome, X and god knows what. So I'm afraid this will be a long running bug... -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
Mark, I understand you're upset, but your comment is quite unhelpful really, and the state of GNOME/gnome-shell/Unity and X/Wayland is entirely irrelevant to Upstart and OpenSSH. Apart from anything else the people doing the latter have nothing, zero, zilch, nada to do with the former. If you're upset with Canonical, I'm not sure there's any point in taking that up with me. I do plan to figure out some better scripting for this. The real fix needs Upstart to be able to supervise chroots, which is hard, but it should be possible to detect the situation in the init.d script and arrange for some kind of sensible fallback behaviour. If I find time for that then I will certainly backport the fix to lucid. It's not accurate to say that the intention of the init.d script was to provide a wrapper for Upstart in the transition period. The wrapper is 'service', as in 'service ssh start' etc. Normally, the init.d scripts go away on transitioning to Upstart, but in this case I kept it around because there was no other way to deal with sshd in a chroot which I knew to be a common situation. I'm sorry I didn't quite manage to do a complete job of it, but I really wasn't expecting it to be used as a wrapper for Upstart when I made those changes. Regarding what happens when you send SIGHUP to ssh, I think that's really a separate bug from this one, and it doesn't much help to combine them. The plan in Upstart for this is to use the proc connector rather than the short-lived ptrace hack to supervise processes changing pids, at which point it will be able to notice that sshd now has a new pid and smoothly switch over to supervising it. The only connection to this bug is that it might make sense for the init.d script to notice the situation and do a full restart rather than sending SIGHUP. -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
Linked to bug 617515 -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
off-topic: Did the upstart maintainer say how configuration is done in upstart? When I look to /etc/init, there are also other scripts using /etc/default $ grep -rl /etc/default/ /etc/init /etc/init/apport.conf /etc/init/gssd.conf /etc/init/idmapd.conf /etc/init/rpc_pipefs.conf /etc/init/hwclock.conf /etc/init/mountall.conf /etc/init/portmap.conf /etc/init/statd.conf /etc/init/hwclock-save.conf /etc/init/gdm.conf $ -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
Scott's recommendation, in general, is that Upstart jobs should be simple enough that it's reasonable to edit them directly. /etc/default/ was introduced in the first place because /etc/init.d/ scripts were hard to edit and it was even harder to keep changes merged. One goal of Upstart is that this should not be the case for Upstart jobs. On Thu, Jul 01, 2010 at 11:38:07AM -, Patrick Cervicek wrote: $ grep -rl /etc/default/ /etc/init You have some false positives here - a number of these are reading system configuration files (/etc/default/locale, /etc/default/rcS) rather than files specific to that service. My comments only apply to the latter. -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
Attached patch allows /etc/init/ssh.conf to use also the SSHD_OPTS from /etc/default/ssh. So it doesn't matter how sshd is started (but it should be clarified for the future!) ** Patch added: ssh_conf.diff http://launchpadlibrarian.net/51173516/ssh_conf.diff -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
The Upstart maintainer explicitly asked me not to do this. -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
** Tags added: patch -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
On Thu, May 06, 2010 at 09:31:06PM -, rswan wrote: So how does one start and stop ssh? I used to use the /etc/init.d script to start and stop sshd, which no longer works. If I kill the sshd process a new one starts up. 'stop ssh' 'start ssh' 'restart ssh' It's rather confusing, this transition period. -- Mark Schouten m...@prevented.net -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
So how does one start and stop ssh? I used to use the /etc/init.d script to start and stop sshd, which no longer works. If I kill the sshd process a new one starts up. -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
** Changed in: openssh (Ubuntu) Importance: Undecided = Medium ** Changed in: openssh (Ubuntu) Status: New = Triaged -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
