On Thu, 27 Nov 2003, Dave Oxley wrote: > I've got this working now. It seems saslauthd wasn't started. I think > there is a bug with chkconfig on Fedora Core 1. > I had to change: > chkconfig: - 95 05 > to > chkconfig: 2345 95 05 > in /etc/init.d/saslauthd because with the '-' chkconfig didn't turn the > service on for any level when doing chkconfig --add saslauthd. That is not a bug in chkconfig. That is a bug in your init script for saslaythd. Chkconfig did exactly what it was told to do. ..................Tom
