[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2011-01-31 Thread Clint Byrum
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

[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2011-01-31 Thread Launchpad Bug Tracker
** 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

[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2010-11-18 Thread Raphaël Pinson
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

[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2010-11-17 Thread Raphaël Pinson
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

[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2010-11-17 Thread Mark Schouten
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.

Re: [Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2010-11-17 Thread Colin Watson
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

[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2010-08-26 Thread Thierry Carrez
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

[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2010-07-01 Thread Patrick Cervicek
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

Re: [Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2010-07-01 Thread Colin Watson
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

[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2010-06-30 Thread Patrick Cervicek
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

Re: [Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2010-06-30 Thread Colin Watson
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.

[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2010-06-30 Thread Brian Murray
** 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

Re: [Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2010-05-07 Thread Mark Schouten
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

[Bug 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2010-05-06 Thread rswan
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 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.

2010-03-04 Thread Colin Watson
** 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