Policy proposal: 'local-foo' for system-specific init.d files

["Karsten M. Self" <kmself@ix.netcom.com>]

I made this suggestion earlier on d-u.  Sean Perry thought it worth
posting here:

This question (where do I put local init.d scripts) comes up enough that
a policy ought IMVAO be set for it.

Viz:  

    any rc script named local-foo is considered local and sacrosanct by
    the system, where "-foo" could have any arbitrary value, including
    null (for the single instance of a local script).

    But this way I could, say, run four local webservers as
    local-apache-mydom0, local-apache-mydom1, local-apache-mydom2, and
    local-apache-mydom3, without worrying about how they're treated by
    Debian.

    So:

       /etc/init.d/local:	Arbitrary local commands
       /etc/init.d/local-squid:	A locally maintained (and possibly
                                separate instance of a) squid proxy

Thoughts?

-- 
Karsten M. Self <kmself@ix.netcom.com>      http://kmself.home.netcom.com/
 What part of "Gestalt" don't you understand?          
   Keep software free.         Oppose the CBDTPA.         Kill S.2048 dead. 
           http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html

Attachment: pgpDaGHZWdSt0.pgp
Description: PGP signature