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 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 after ten seconds have elapsed, it sends a SIGKILL; but it still tries to lock the lock file.

A hanging -stop means that something has the lock file locked, and it escaped SIGKILL.

Attachment: pgp7uMBgYEEiw.pgp
Description: PGP signature

------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to