Andreas Aardal Hanssen said: > Yes, sysconfdir now places the conf file, and localstatedir sets the > location for logs and service scripts. I should have notified you of this > when the release was done.
Thanks for that, by the way. > DjB's solution is to use a symlink A very good solution, too. Otherwise you may want to remove a service, and without thinking, remove all the service files without thinking about it. This way, you just remove the symlink, keeping the service files intact. And it's faster, too. > which forces one to keep "two locations" of the same stuff. How do you figure? It's just a symlink... You can adjust your shell prompt to show the real directory that you're in as opposed to the virtual directory when you cd into a symlinked directory, too. > DjB uses /etc/tinydns etc, but on qmail.org the recommendation is > /var/service/tinydns symlinked to /service/tinydns. I've thought about this some bit, admittedly not without opinion fluctuation, but I currently think that the service files should go in /etc/service. My service directory (the one with the symlinks) used to be /etc/service, but I have since moved it /var/service (/service is just plain evil, IMHO. If you don't want it in /service, you can recompile to have the service directory wherever you like). So, the configuration files in /etc, and the localstate files in /var, just as it should be, as I see it. The problem I see now is that if I install bincimap-1.2.6 with localstatedir=/var and sysconfdir=/etc, the service files will overwrite what I have in /var/service. Ideally I'd like bincimap.conf to land in $sysconfdir, the service files in $sysconfdir/service, and the log files in $localstatedir/log. > It's to prevent the services from popping up before they are configured. > Of course, since the symlinking is done manually these days (it was > automated in old versions of Binc) these files no longer seem necessary. I agree. -- Casey Allen Shobe Open Source Software Solutions [EMAIL PROTECTED]
