On Tue, 2003-07-01 at 15:22, Farkas Levente wrote:
as most people point out, it's better not to create subfolders under /var/run (at least with redhat) and it currently still not a god solution.
It doesn't matter where you put the files, as long as different server groups have different login_dir.
anyway what was the group inside the group in the first example?
Well, those are where the logic is still somewhat messy in my head :) I think you would want to have groups which:
- Simply provide default settings for any subgroups without doing anything themselves:
group { protocols = imap # some IMAP defaults for a/b group server-a { ... } group server-b { ... } }
group { protocols = pop3 # different POP3 defaults for a/b group server-a { ... } group server-b { ... } }
- Are servers themselves, providing defaults for subgroups:
group main-server { # defaults login { listen = main.server.org } auth default { # ... } group debug-server { login { listen = debug.main.server.org auth_verbose = yes } # possibly a few other settings changed } }
- Belong to same server instance, but use different settings for different users:
group server { # ... auth default { mechanisms = plain userdb = ldap /etc/main-ldap.conf passdb = ldap /etc/main-ldap.conf } group power-users { # .. different settings for power-users auth power-users { mechanisms = plain userdb = ldap /etc/power-users-ldap.conf passdb = ldap /etc/power-users-ldap.conf } } group lusers { # .. different settings for lusers auth lusers { mechanisms = plain userdb = ldap /etc/lusers-ldap.conf passdb = ldap /etc/lusers-ldap.conf } } }
and what was the anonymous?
Nothing special. Just another server with different settings.
Oh, and the group name doesn't actually matter at all. You wouldn't even need to give it at all. I was also thinking that if group name wasn't given, that would mean that it's a dummy group (type 1 above) which shouldn't tried to be started.