Sam Varshavchik writes:
Gordon Messmer writes:
courierlogger is set to courier_exec_t:
/etc/selinux/targeted/contexts/files/file_contexts:/usr/sbin/courierlogger
-- system_u:object_r:courier_exec_t:s0
# ls -lZ /usr/sbin/courierlogger
-rwxr-xr-x. daemon daemon
Gordon Messmer writes:
courierlogger is set to courier_exec_t:
/etc/selinux/targeted/contexts/files/file_contexts:/usr/sbin/courierlogger
-- system_u:object_r:courier_exec_t:s0
# ls -lZ /usr/sbin/courierlogger
-rwxr-xr-x. daemon daemon system_u:object_r:courier_exec_t:s0
On 07/06/2015 04:14 AM, Sam Varshavchik wrote:
Looks to me like someone added these SELinux entries ages ago, before
courier-authlib became a separate package, and nobody has maintained
these entries ever since.
authlib has contexts defined, too. That's not the problem. I don't
know who
I had two minor problems with the upgrade to Courier 0.75 and authlib
0.66.3.
The first is that Courier needs ps to build, and the spec need to be
updated to reflect that. Otherwise, it doesn't build in mock.
BuildRequires: procps-ng
The other is that courier-authlib preuninstall script runs
Gordon Messmer writes:
The other is that courier-authlib preuninstall script runs authdaemond
stop and for some reason, that caused my rpm upgrade to hang. The
process tree looked like this. I should have straced the children to
see what they were doing, and I didn't. My bad. I was tired.
On 07/05/2015 04:22 PM, Sam Varshavchik wrote:
Did the systemd-initiated stop complete immediately, or did it also hang
for a while.
It was immediate.
If I see a similar hang in the future, I'll try to trace the process and
see what's going on.
Gordon Messmer writes:
On 07/05/2015 04:22 PM, Sam Varshavchik wrote:
Did the systemd-initiated stop complete immediately, or did it also hang
for a while.
It was immediate.
If I see a similar hang in the future, I'll try to trace the process and
see what's going on.
Also, look at the pid
On 07/05/2015 06:35 PM, Sam Varshavchik wrote:
Also, look at the pid and the lock files, and do an fuser to see who has
the pid and the lock files open.
-stop tries to lock the lock file, if it can't, it reads the pid from
the pid file, sends a SIGTERM. If it's still can't lock the lock file
