It is news to me that PAM changes the application's syslog facility.
That seems, to put it mildly, to be rather unfriendly of it.
It doesn't happen to me on my Mac OS X system at home (which also uses
PAM). I took a look at my Linux test system and at one of our production
Linux servers, and see behavior that seems to confirm your claim. I'm
surprised that nobody has complained about this problem before now.
I don't know what to tell you other than to do as you suggest and reset
the log facility after calling PAM. The best way would be to add another
openlog() call in routine checkpw() in ckp_pam.c (or ckp_pmb.c for Solaris
users)
Please let me know if this solves the problem and does not create any
unpleasant side effects. If it works out alright for you, I'll do the
same thing to imap-2006.
Thanks!
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
