Re: conf.d usage
Hi again! On 2004-01-01 13:47 +0100, Martin Pitt wrote: > Recently, the conf.d directory was added to better support this kind > of applications. So I tried to put this line into > /etc/apache/conf.d/fibusql, but it does not work. Please excuse the noise, it works now. Stupid small error... > I could not find any documentation how to use conf.d, can you point > me to any? I would still be interested in this. The problem that this configuration may not work with more complex setups (several virtual hosts, stricter security settings) remains. What would you propose for this case? Explain the situation in README.Debian and have the administrator fix the configuration file manually? Maybe display a warning debconf note in addition? Thanks again, Martin -- Martin Pitt Debian GNU/Linux Developer [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.piware.de http://www.debian.org signature.asc Description: Digital signature
Re: conf.d usage
--On Thursday, January 01, 2004 13:59 +0100 Martin Pitt <[EMAIL PROTECTED]> wrote: Hi again! On 2004-01-01 13:47 +0100, Martin Pitt wrote: I could not find any documentation how to use conf.d, can you point me to any? I would still be interested in this. The problem that this configuration may not work with more complex setups (several virtual hosts, stricter security settings) remains. What would you propose for this case? Explain the situation in README.Debian and have the administrator fix the configuration file manually? Maybe display a warning debconf note in addition? Putting a file in a conf.d is equivalent to writing those directives in the httpd.conf file. There are no restrictions. -- Michael Loftis Modwest Sr. Systems Administrator Powerful, Affordable Web Hosting
Re: Re: conf.d usage
Michael Loftis wrote: > Putting a file in a conf.d is equivalent to writing those directives > in the httpd.conf file. There are no restrictions. A follow-up question, as a package maintainer: if my package wants to install a snippet of config (or a symlink) into conf.d and the file already exists (eg created by the user), what should the package do ? Or is there a naming scheme I could follow (eg name-of-package.conf), and assume that a user will not manually create such files ? Frederic
Re: Re: conf.d usage
Hi Frederic, On Thu, 22 Jan 2004, Frederic Schutz wrote: > Michael Loftis wrote: > > > Putting a file in a conf.d is equivalent to writing those directives > > in the httpd.conf file. There are no restrictions. > > A follow-up question, as a package maintainer: if my package wants to > install a snippet of config (or a symlink) into conf.d and the file > already exists (eg created by the user), what should the package do ? You have to preserve the user file or symlink or directory. > Or is there a naming scheme I could follow (eg name-of-package.conf), > and assume that a user will not manually create such files ? I would suggest pkgname.conf but you still have to check if it has been created by you, modified by the user and so on before touching it. You still have the option to prompt the user for a proper action to take in case. Fabio -- Our mission: make IPv6 the default IP protocol "We are on a mission from God" - Elwood Blues http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html
