ypbind taking port of imaps on reboot. Please help

[ravangrid]

Dear all,

Upon reboot, ypbind takes the port of imaps. Upon reboot, ypbind starts earlier than imaps. Sometimes ypbind takes 993 and sometimes 995, both cause problems for imaps to start on reboot. My system is RHEL 5. I need both the services to be ON. (I have many other services also running which should be ON, like vsftpd, sshd, nfs, cups, ntpd, httpd, etc. And, SE-Linux has to be in "enforcing" mode.)

I tried the following:

# service dovecot status

(its not running and stopped)

# netstat -tanp | grep 993
# netstat -tanp | grep 995

(these show that ypbind has taken either of these ports)

# service ypbind stop
# service dovecot start
# chkconfig dovecot on
# service ypbind start
# chkconfig ypbind on

(Now, dovecot first takes its appropriate port. 
Next, ypbind too takes its appropriate port.)

However, upon reboot, sometimes the problem appears again that imaps is not able to start because its ports is taken (mostly by ypbind).

Please help guys.

---------------------------------------------------------------------

[Lazydog]

Look in /etc/rc.d/rc#.d and change the starting order if there is no other way to tell your programs what port they should be using. I haven't played with ypbind so I do not know if it is possible to tell it what port it must use.

S## is the thing you want to look at. Services are started in numerical order. I would say start imaps just before ypbind.