> How is systemd relevant?
Because it replaced upstart, and support for discontinued software tends
to get much less attention. If the issue was known for years and wasn't
fixed while the software still had a future, it became extremely
unlikely to be fixed once it didn't have a future.
>
** Tags removed: glucid lucid
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/703800
Title:
init: restart command fails to restart main process when
How is systemd relevant?
Precise is still supported. Trusty will be supported until 2019.
Neither of those have systemd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
Given the age of this bug and the fact that the switch is being made to
systemd, I doubt this will ever be fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/703800
Guys, it has been 5(!!!) years, since this bug has been reported. Any
chance for a fix?
Please raise severity to major, to reflect that this is a MAJOR issue
with a CORE component in ubuntu, that affects a lot of services that
would use pre-stop
Workaround-ish: service xxx restart works, because
Is there a workaround to get pre-stop and restart to work together? I
want to use pre-stop to leave a pid file behind should the process die.
I can't do that with a post-stop because there is no way to tell if the
post-stop is being called because a stop was issued or if the respawn
limit was
6 matches
Mail list logo
