On Sat, 13 Jan 2007, Steve Langasek wrote:
> > * should packages disable inetd config entries on removal and in
> > preparation for upgrade, and then reenable the entries after upgrade
> > is complete?
>
> No, they shouldn't, because this loses local modifications to the inetd.conf
> line.
Actually it doesn't.
If you call update-inetd with --disable in prerm it just prepends
"#<off># " to your line (if the service is enabled), and when you call
it in postinst with --enable it will remove the "#<off># ".
Running --enable will not touch any lines without the magic '#<off># '
token, so if the admin commented out the line with just # (or anything
not #<off>#) the service will stay disabled, thereby preserving the
admin's configuration.
Peter
--
| .''`. ** Debian GNU/Linux **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `- http://www.debian.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
