> dh_installinit's default behaviour should be to not stop daemons,
> but to issue a reload, restart, or force-restart in the .postinst.

JFTR, doing a simple reload on upgrade is _always_ wrong. After an 
upgrade the new executables must be running, not the old ones. For 
example, the old executables might still contain security issues.

And the current debhelper behaviour is the safer way and should be the 
default. A daemon crashing because some of its data files no longer 
fit to the running process can cause much more severe data loss than 
just some down time. And a maintainer would have to check on every 
upload if and for which old versions it is safe not to stop the 
daemon before replacing the files. This would doubtless lead to many 
other bugs.

Cheers,
Stefan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to