** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2010-5107
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926468
Title:
Stopping ssh with a logged in user causes init to spin at 100%
** Changed in: upstart
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926468
Title:
Stopping ssh with a logged in user causes init to spin at 100%
To man
Shouldn't this be Fix Released?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926468
Title:
Stopping ssh with a logged in user causes init to spin at 100%
To manage notifications about this bug go
This bug was fixed in the package upstart - 1.4-0ubuntu7
---
upstart (1.4-0ubuntu7) precise; urgency=low
* debian/manpages/upstart-events.7: Added missing events 'container' and
'not-container'.
* Update 'runlevel' event emission time in upstart-events(7) (LP: #921501).
* Me
@Jason: thanks for the feedback.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926468
Title:
Stopping ssh with a logged in user causes init to spin at 100%
To manage notifications about this bug go
Testing 1.4-0ubuntu7~jh I haven't been able to reproduce the issue
using the test code above or commenting out 'console none' in ssh.conf,
so seems to be fixed here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
If you would like to help with testing the fix for this bug, I've put an
updated version of Upstart (version '1.4-0ubuntu7~jh') in my upstart-
job-logging PPA:
https://launchpad.net/~jamesodhunt/+archive/upstart-job-logging/
Please install and provide feedback.
** Changed in: upstart (Ubuntu P
** Branch linked: lp:~jamesodhunt/ubuntu/precise/upstart/fix-for-
bug-926468
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926468
Title:
Stopping ssh with a logged in user causes init to spin at 100
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart
Importance: Undecided => High
** Changed in: upstart
Status: New => Fix Committed
--
You received this bug notifi
** Changed in: upstart (Ubuntu Precise)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926468
Title:
Stopping ssh with a logged in user causes
@Jason: thanks for taking the time to look at this. Yes, I can confirm
your understanding of the problem as I had come to exactly the same
conclusion! :-) I have raised a bug on openssh for the stderr fd leak:
https://bugzilla.mindrot.org/show_bug.cgi?id=1976
** Bug watch added: OpenSSH Portable
This bug was fixed in the package openssh - 1:5.9p1-2ubuntu2
---
openssh (1:5.9p1-2ubuntu2) precise; urgency=low
* Make Upstart job 'console none', to avoid pathological behaviour due to
leaking Upstart's log fd 2 to child processes (LP: #926468).
-- Colin WatsonMon, 06 Feb
** Branch linked: lp:ubuntu/openssh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926468
Title:
Stopping ssh with a logged in user causes init to spin at 100%
To manage notifications about this bug
As discussed with James, we should make openssh use 'console none' to
avoid leaking the fd (well, there are multiple ways to do this, but this
is probably least invasive), but we should also convert log_read_watch
to integrate with upstart's main select loop so that it doesn't behave
this way with
I think the attached source file, along with a simple upstart conf with:
exec /path/to/test-daemon may be a minimal example of the behavior.
sshd is spawned by upstart with -D so the initial process doesn't
daemonize. The upstart logging mechanism will setup a pty for
stdout/stderr. When receiving
** Changed in: upstart (Ubuntu)
Status: New => Triaged
** Changed in: upstart (Ubuntu)
Importance: Undecided => High
** Also affects: upstart (Ubuntu Precise)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
16 matches
Mail list logo
