There is always some possibility that the shutdown scripts will not be
able to remount the root filesystem read-only because rogue processes
refuse to die. This is exceptional, and indicates a bug in those
scripts, *not* in sysvinit for failing to kill them (because believe me,
it tries).
Reassig
** Changed in: sysvinit (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/224047
Title:
incorrect system shutdown when running git-daemon-run
To manage notifica
** Description changed:
On hardy, if you install git-daemon-run a new service is created and handled
incorrectly by "runsv" and not "upstart" as all other services
(https://bugs.launchpad.net/ubuntu/+source/git-core/+bug/74135)
On system shutdown we ask "runsv" and "runsvdir" to terminate, b
** Changed in: sysvinit (Ubuntu)
Sourcepackagename: upstart => sysvinit
--
incorrect system shutdown when running git-daemon-run
https://bugs.launchpad.net/bugs/224047
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
1. You set the package to "git". The git I'm talking about it in package
"git-core".
2. I already opened several bug reports in "git-core", but I explicitly left
this one packageless because I think the problem is in another package.
To make myself clear: because git-daemon doesn't want to die
** Changed in: git (Ubuntu)
Sourcepackagename: None => git
--
incorrect system shutdown when running git-daemon-run
https://bugs.launchpad.net/bugs/224047
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
