Blame SOURCES/1146259-mpo-7.1.0-xinetd.8.patch

c2a259
From 0c22d198fb32b2d516d0dfa05874f046a06f4659 Mon Sep 17 00:00:00 2001
c2a259
From: Jan Chaloupka <jchaloup@redhat.com>
c2a259
Date: Mon, 29 Sep 2014 20:48:26 +0200
c2a259
Subject: [PATCH] xinetd.8 reload termination handling
c2a259
c2a259
---
c2a259
 xinetd/man8/xinetd.8 | 6 ++++++
c2a259
 1 file changed, 6 insertions(+)
c2a259
c2a259
diff --git a/xinetd/man8/xinetd.8 b/xinetd/man8/xinetd.8
c2a259
index d3b900d..c367f9c 100644
c2a259
--- a/xinetd/man8/xinetd.8
c2a259
+++ b/xinetd/man8/xinetd.8
c2a259
@@ -45,6 +45,12 @@ provide features such as access control and logging.  Furthermore,
c2a259
 .I /etc/services.
c2a259
 Therefore, anybody can use \fBxinetd\fP to start special-purpose
c2a259
 servers.
c2a259
+.LP
c2a259
+BEWARE of xinetd reload termination handling.
c2a259
+For services with type = INTERNAL, SIGTERM signal will be sent.
c2a259
+For services without type = INTERNAL, SIGKILL signall will be sent.
c2a259
+Take this into an account when dealing with proper handling of the SIGTERM and SIGKILL.
c2a259
+It is important to be aware of this as your xinetd service could be killed on a xinetd reload.
c2a259
 .\" *************************** OPTIONS *********************************
c2a259
 .SH OPTIONS
c2a259
 .TP
c2a259
-- 
c2a259
1.9.3
c2a259