From c46413a31172a46ad4b522a614b130a202cc6b2a Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Sun, 4 Mar 2012 11:54:00 +0000 Subject: [PATCH] Update 'Signals' section, the only explicitly handled signals are SIGINT, SIGTERM and SIGHUP --- doc/source/privoxy-man-page.sgml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/source/privoxy-man-page.sgml b/doc/source/privoxy-man-page.sgml index 22e426c3..41d7dab6 100644 --- a/doc/source/privoxy-man-page.sgml +++ b/doc/source/privoxy-man-page.sgml @@ -5,7 +5,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: privoxy-man-page.sgml,v 2.39 2011/11/13 17:03:54 fabiankeil Exp $ + $Id: privoxy-man-page.sgml,v 2.40 2011/12/26 17:05:40 fabiankeil Exp $ Copyright (C) 2001-2009 Privoxy Developers http://www.privoxy.org/ See LICENSE. @@ -294,13 +294,14 @@ Signals - Privoxy terminates on the SIGINT, - SIGTERM and SIGABRT signals. Log + Privoxy terminates on the SIGINT + and SIGTERM signals. Log rotation scripts may cause a re-opening of the logfile by sending a SIGHUP to Privoxy. Note that unlike other daemons, Privoxy does not need to be made aware of config file changes by SIGHUP -- it will detect them - automatically. + automatically. Signals other than the ones listed above aren't explicitly + handled and result in the default action defined by the operating system. -- 2.39.2