Re: diversion/conffile
On Wed, 20 Feb 2002, Manoj Srivastava wrote:
> >>"martin" == martin f krafft <madduck@madduck.net> writes:
>
> martin> also sprach Colin Watson <cjwatson@debian.org> [2002.02.19.1347 +0100]:
> >> If it's in /etc, please allow the sysadmin to change it, even if it
> >> doesn't seem to you that it might be needed.
>
> martin> okay. so maybe you can advice me. i am providing an add-on to
> martin> an existing daemon. in order for the add-on to be effective,
> martin> i need to use a different init.d script. i also would like to
> martin> disable the original init.d script with chmod 0 since it's
> martin> not needed and might actually lead to security problems.
>
> This is problematic. As it stands, if this file belongs to the
> parent package, it is a conffile of the parent package, and you are
> not supposed to modify a conffile in a script, far less the conffile
> of another package
>
> You should talk to the maintainer of the other package, and
> have his init.d script look for a file that your package creates
> (after asking the user, perhaps) that works kinda like
> /etc/nologin. When the file produced by your package exists, his
> init.d script exits, and yours works. Remove the file, his wirks,
> yours does not.
This is a response to martin, not Manoj.
All init scripts are supposed to function in the event that their package has
been removed, but not purged. This is generally done by checking some binary
for executability.
You can probably divert this binary.
Reply to: