On Mon, 25 Aug 2003, Stefano Rivera wrote: >Hi Andreas (2003.08.25_14:56:29_+0200) >> I see no point in "make install" creating a "bincimap.conf.example" if the >> first thing _everyone_ has to do is to rename the file to "bincimap.conf". >Don't forget that the first thing that _everyone_ (who uses >daemontools) has to do is to delete all the "down" files so that they >can start their server...
The down files are there so that the service does not accidentally start before you have configured it. And no, you don't have to remove them - the service starts when you "svc -u" it regardless of the down files. The magic difference is that if svscan restarts for some reason (most likely a reboot), the service will not automatically restart if the down file is there. I have down files in every service directory that I use, because I don't want the service to auto-restart on a reboot. >One more step doesn't matter too much, but as a user who uses the >tarballs (simply because the .debs don't keep up) I would prefer make >install to give me a server that I can start straight away. Which behavior would you personally prefer for "make install" with regards to configuration files? Andy PS - I'm actually quite impressed with how fast the deb files are out :-) -- Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg Author of Binc IMAP | "It is better not to do something | than to do it poorly."
