> Nothing related in /var/log/messages or any other logs? If there are no > other errors relating to saslauthd itself I'd suspect a segfault.
The only thing that is strange is the entry I found in /var/log/messages: (This happened right after I first fired up nscd) ------ Sep 1 13:18:33 rusty nscd: Stopping Name Switch Cache Daemon succeeded Sep 1 13:18:48 rusty nscd: nscd startup succeeded Sep 2 13:06:01 rusty saslauthd: saslauthd shutdown succeeded Sep 2 13:06:01 rusty saslauthd: saslauthd startup succeeded Sep 2 13:06:02 rusty httpd: httpd shutdown succeeded Sep 2 13:06:08 rusty httpd: httpd startup succeeded Sep 2 13:06:13 rusty mailman: Stopping mailman: succeeded Sep 2 13:06:14 rusty mailman: python startup succeeded Sep 2 13:06:14 rusty mailman: Starting mailman: succeeded ------ Funny, I didn't tell it to restart all of those services... They all rely on auth, so perhaps it knew to restart them? Last night when the problem happened, my boss decided that a complete reboot would fix it... so, he rebooted. ------ Sep 6 19:13:51 rusty init: Switching to runlevel: 6 Sep 6 19:13:52 rusty mailman: Stopping mailman: Sep 6 19:13:52 rusty mailman: Stopping mailman: succeeded Sep 6 19:13:52 rusty mailman: ^[[60G[ Sep 6 19:13:52 rusty mailman: Sep 6 19:13:52 rusty rc: Stopping mailman: succeeded Sep 6 19:13:52 rusty httpd: httpd shutdown succeeded Sep 6 19:13:58 rusty postfix: Stopping Postfix: succeeded Sep 6 19:13:58 rusty saslauthd: Stopping saslauthd: Sep 6 19:13:58 rusty saslauthd: /etc/rc6.d/K52saslauthd: line 53: kill: (3520) - No such process Sep 6 19:13:58 rusty saslauthd: shutdown failed Sep 6 19:13:58 rusty saslauthd: ^[[60G Sep 6 19:13:58 rusty saslauthd: Sep 6 19:13:58 rusty rc: Stopping saslauthd: failed Sep 6 19:13:58 rusty sshd: sshd shutdown succeeded Sep 6 19:13:58 rusty fcron: fcron shutdown succeeded Sep 6 19:13:58 rusty nscd: Stopping Name Switch Cache Daemon succeeded ------ Looks like saslauthd was already dead, so it wouldn't be killed upon shutdown... But other than that, nothing in the logs.... Segfault looks probable? Perhaps a bug report is in order... Mike _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
