Dne, 06. 12. 2010 03:00:12 je D G Teed napisal(a):
Are there any suggestions on how I can trace what is happening
while at the same time not causing too much disruption for users?
Generally I have to get the service back up for them quickly,
but I might have a minute or so to gather some sort
of information when the thing fails.
The information I see in the mail logs looks like normal
authentication
failures, which happen once in awhile for the normal reasons,
so there isn't much to see there.
You could try increasing saslauthd's log verbosity, if it supports
that. Many daemons do.
--
Cheerio,
Klistvud
http://bufferoverflow.tiddlyspot.com
Certifiable Loonix User #481801 Please reply to the list, not to
me.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1291633981.2659...@compax
