Scalix Forums

What is the "blessed" method to completely restart the entire mail subsystem, including scalix, tomcat, postgres, ldapmapper, sendmail etc., that each service is stopped and then started in the right succession? Is there a specific sequence that works better than others? We are using Scalix 11 and sendmail.

Also, what is the difference between

service ldapmapper stop
service ldapmapper start

AND

omoff -d0 ldap
omon ldap

What exactly is being restarted in each case?

Thanks.

Yuri O.

The LDAP server provides directory (address book) capabilities. The ldapmapper is used by sendmail to look up whether an address is destined for Scalix or not.

transmodus wrote:What is the "blessed" method to completely restart the entire mail subsystem, including scalix, tomcat, postgres, ldapmapper, sendmail etc

Valerion alreadt picked up on slapd v. ldapmapper above - here are a couple of thoughts on restarting things.

If you look at the dependencies:

- tomcat depends on postgres
- tomcat depends on scalix
- scalix depends on nothing
- nothing depends on sendmail
- sendmail depends on ldapmapper
- ldapmapper depends on scalix

Using a fiendishly complicated algorithm of my own design, I'd draw the following conclusion to start order (reverse for stop order):

scalix
postgres
tomcat
ldapmapper
sendmail

That way you never have a service running without another service on which it depends.

Chris

EDIT: the reason I say that nothing depends on sendmail is because there will be no error if scalix has to wait for sendmail to come on line. As soon as it's there the UNIX queue will flow through.

Thanks, that's just the info I've been looking for. Strange that it has not been covered elsewhere...

/YO