Am Dienstag 12 Dezember 2006 14:59 schrieb Jorey Bump: > Timo Veith wrote: > > Does a service name in /etc/cyrus.conf must be unique? > > Yes, it isn't really a service name (i.e. from /etc/services), but a > unique identifier. This allows you to assign names for multiple > configurations of the same network service, so you can manipulate them > separately in imapd.conf. I'm sorry I didn't see that in your original > post. You need to fix this for all of the services you've duplicated. > > In practice, this allows you to preface certain configuration > directives with the unique service name. For example, you might set a > global TLS key that all services will use by default: > > tls_key_file: /etc/ssl/imapd.key > > But you might also have a uniquely named imapd that uses a different > key: > > imapdlo_tls_key_file: /etc/ssl/imapdlo.key > > In cyrus.conf, this alternate imapd might coexist with your regular > imapd like this: > > imap cmd="imapd" listen="192.168.1.4:imap" prefork=0 > imapdlo cmd="imapd" listen="127.0.0.1:imap" prefork=0 > > Note that the listen parameter uses the actual service name defined in > /etc/services. Hello Jorey, hello list readers this is what I was already doing (using different config files for different services). But I didn't noticed that I need unique names for them in cyrus.conf. So, let me repeat my suggestion: How would it be to have the master daemon parse the config file for mistakes like this one? It could just refuse to start or log an error message. I was looking at the logs with level debug and also with CYRUS_VERBOSE and -D as start option, but found nothing. A small extension of the manual page would also be good. Any developers around, who could pick this up? Kind regards, Timo ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
