The current init.d script for tftpd-hpa uses start-stop-daemon --oknodo
and the manpage for said program says:
start-stop-daemon returns 0 [...] if --oknodo is specified and [...]
--stop was specified and there were no matching processes.
Therefore, its script should act normally now. Closing
Steve, is it correct that /etc/init.d/whatever scripts should return
zero status when the daemon was already stopped?
--
debhelper script creates prerm script that causes daemon removal to be
impossible
https://bugs.launchpad.net/bugs/119454
You received this bug notification because you are a m
Thank you for taking the time to report this issue and help to improve
Ubuntu.
The behavior of debhelper here is correct; any init script which exits
non-zero when trying to stop a daemon that isn't running is buggy and
should be fixed. This will be clarified in an upcoming update to Debian
polic
** Also affects: tftp-hpa (Ubuntu)
Importance: Undecided
Status: New
--
debhelper script creates prerm script that causes daemon removal to be
impossible
https://bugs.launchpad.net/bugs/119454
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I came into #ubuntu with problems regarding vmware-player, and the chmod
-x helped. Too bad you can't vote for bugs, like on bugs.kde.org, since
that's something I would otherwise have definitely done for this bug.
** Attachment added: "Console output showing that this fix worked fine"
http://l
** Changed in: debhelper (Ubuntu)
Sourcepackagename: None => debhelper
--
debhelper script creates prerm script that causes daemon removal to be
impossible
https://bugs.launchpad.net/bugs/119454
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
