[please don't use -quiet as I didn't received the responses though I want to contribute were I can]
2010/1/4 Patrick Schoenfeld <schoenf...@debian.org>: >> I've noticed in the past that cacti RE-adds the symbolic link >> conf.d/cacti.conf >> on every upgrade even if the source file was *manually* removed by the >> sysadmin. >> This is done to restrict the access to 'cacti' on each virtual web site (the >> default behaviour in Debian). > >> * cacti/webserver: Apache2 > > The question is: Why did you ask to do this in the first place? > (according to your debconf settings) Ok, now I see that this is a way of disabling that symlink. Still, I would like to have the '/etc/cacti/apache.conf' file for reference to update my custom config which simply restricts the access to Intranet. > So sorry for the noise, except that I still not understand why > people answer a priority high question with "Configure my webserver: > apache2" just for removing the symlink, it results into after, that. The debconf question is "Which kind of web server should be used by cacti?" so I answered "apache2". Maybe this question should be updated to better describe its meaning? Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
