Application Development Software

Hello. I've run into the following problem, and hope someone can help.

Was adding a fourth mail partition, and I had problems with the start-msg after doing the stop-msg. Have done this before without any problems.

The start-msg looked as follows:

Starting ENS daemon
/opt/email/server5: Starting STORE daemon ..... done: 14668
/opt/email/server5: Starting POP3 daemon .... done: 14685
/opt/email/server5: Starting IMAP4 daemon ...Cannot bind to port 143: Address already in use

Did a stop/start a second time and the stop complained about no pidfile.imap. Indeed, there is not one. The other services (pop, etc) have
pidfile's.

After doing some reading, I'm thinking the imapd processes were not completely down after the first stop-msg? I see 4 processes now, which
matches the service.imap.numprocesses = 4 config. I was not previously
aware of this number of imapd processes.

Tonight, I will try again. As for the procedure, I plan on waiting a few minutes
to allow imapd processes for finish up so that port 143 can be bound on the
next start. Can those processes be killed if they don't go away? Is there a
method to ensure that the 143 port is ready for a start-msg?

We are on Iplanet MS 5.2. Any help will be much appreciated.

Thank you, Keith