https://bugzilla.novell.com/show_bug.cgi?id=741469 https://bugzilla.novell.com/show_bug.cgi?id=741469#c6 --- Comment #6 from Neil Rickert <nrickert@ameritech.net> 2012-01-17 06:35:41 UTC ---
At least /var/spool/clientmqueue is owner mail:mail and it is not wordreadable and the pid is stored exactly there.
The readability of the pid file was never an issue in that placement. I think it was my suggestion (to sendmail.org) to put the pid file in the clientmqueue directory. The problem (as best I remember it) was that sendmail would start as root, write the file, then change to mail:mail (or whatever user is defined for that). But, if restarted by sending a SIGHUP, it was unable to write to update its pidfile. So the pidfile had to be placed somewhere that the limited privilege sendmail daemon could write to it. And the clientmqueue directory was an obvious choice. I don't know of any reason why there's a problem reading the file. There's probably some other bug involved. Looking at "lsof" output, sendmail has a write lock on the pidfile. It's an advisory lock so can be ignored. But if systemd is attempting to lock the file before reading, it might well be locked out. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.