Hello Guy,
Guy Durand schrieb am Tue, Jan 15, 2002 at 06:04:29PM -0500:
> Jan 15 17:38:49 tmc230 master[1571]: about to exec
> /usr/cyrus/bin/ctl_mboxlist
> Jan 15 17:38:49 tmc230 master[1571]: about to exec
> /usr/cyrus/bin/ctl_mboxlist
> Jan 15 17:38:49 tmc230 ctl_mboxlist[1571]: running mboxlist recovery
^^^^
> Jan 15 17:38:49 tmc230 ctl_mboxlist[1571]: running mboxlist recovery
> Jan 15 17:38:49 tmc230 master[1570]: process 1571 exited, signaled to
^^^^ ^^^^
> death by 11
> Jan 15 17:38:49 tmc230 master[1570]: process 1571 exited, signaled to
> death by 11
> Jan 15 17:38:49 tmc230 master[1572]: about to exec
> /usr/cyrus/bin/ctl_deliver
> Jan 15 17:38:49 tmc230 master[1572]: about to exec
> /usr/cyrus/bin/ctl_deliver
> Jan 15 17:38:49 tmc230 master[1570]: process 1572 exited, signaled to
> death by 11
> Jan 15 17:38:49 tmc230 master[1570]: process 1572 exited, signaled to
> death by 11
> Jan 15 17:42:04 tmc230 xinetd[313]: Exiting...
your "master" is running quite fine. Note that it works a bit like
an inetd or xinetd: it just starts imapd/pop3d/lmtpd upon incoming
connects on the respective ports (or when configuring prefork). It
also does some background tasks (ctl_mboxlist etc.) What you see is
that it starts them, but these background processes then crash for
reasons yet unknown.
You can start them manually to find out more (see /etc/cyrus.conf for
details), be sure to set CYRUS_HOME and the like correctly before
starting ctl_mboxlist. Maybe you even have to utilise strace(1) or
ltrace(1) to get behind the scenes.
Regards,
- Birger
