On Sun, 9 Feb 2003 15:45:23 +0100 (CET) Andreas Aardal Hanssen <[EMAIL PROTECTED]> wrote:
AAH> On Sun, 9 Feb 2003, Ivan F. Martinez wrote: AAH> >On Sun, 09 Feb 2003 15:19:34 +0100 AAH> >Philipp Specht <[EMAIL PROTECTED]> wrote: AAH> >PS> This would break "qmail style" compatibility and would be the AAH> >first PS> step to "Courier style" config files. AAH> >PS> Do you really believe that's a step in the right direction? AAH> >:o) One good advantage of using xinetd is to changing config AAH> >without stopping and starting services. As administrator the use AAH> >of .conf files is better than having part of configuration in the AAH> >xinetd config. I don't expect the software to use one style, I AAH> >expect it to be easy to administer, backup, etc... AAH> AAH> I have to agree with both of you. One of the main goals of this AAH> project is to have a service that is very easy to configure, but at AAH> the same time, it is supposed to blend in naturally with the AAH> qmail-style of configuring services. AAH> AAH> The conf file itself is not qmail-style, but I was hoping that it AAH> would be more of a relief than a burden. The IMAP protocol is more AAH> complex and I beleive that the number of configuration options will AAH> grow beyond what's practical to have on the command line. But I'm AAH> open for input here. I could, for instance, allow all conf-settings AAH> to be passed on the command line. AAH> AAH> Since the checkpassword style of authentication is one based on the AAH> invokation pipeline, one process executes its first argument, I AAH> find it natural to be part of the run and xinetd files. AAH> AAH> The down side is that xinetd administrators have to send a SIGHUP AAH> to xinetd, and daemontools administrators have to "svc -du" the AAH> service, every time they change their authentication method. AAH> AAH> For daemontools administrators this is how it's always been and I AAH> beleive that everyone's content with this. AAH> AAH> Question is - should the conf file itself be completely optional? I prefer the conf file, easy to administer, can have comments in many places. The problem I have when started with bincimap was to understand that auth are only configured in command line. And in this case no need for restart or use SIGHUP. The new conections will use the new configuration. Maybe bincimap can support 2 options, if no auth program was passed on command line check for it in configuration file. -- Ivan F. Martinez
