From 3a3ef53624823f79d935f68d074d73aad9033a2d Mon Sep 17 00:00:00 2001
From: Mattias Andrée <maandree@operamail.com>
Date: Sun, 12 Apr 2015 05:09:13 +0200
Subject: valgrind is not using sigrtmin, it is using sigrtmax
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Signed-off-by: Mattias Andrée <maandree@operamail.com>
---
doc/info/mds.texinfo | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
(limited to 'doc')
diff --git a/doc/info/mds.texinfo b/doc/info/mds.texinfo
index a051a6c..0806894 100644
--- a/doc/info/mds.texinfo
+++ b/doc/info/mds.texinfo
@@ -425,12 +425,8 @@ instead of @command{SIGUSR1}.
If you need servers to free up allocated
memory that they do not use, send the signal
@command{SIGDANGER}, or if not defined
-@command{SIGRTMIN + 1}@footnote{@command{valgrind}
-uses @command{SIGRTMIN} for internal stuff, so
-we cannot use @command{SIGRTMIN} as it is hence
-unavailable when running under @command{valgrind}}.
-Unimportant servers may choose to die on
-@command{SIGDANGER}.
+@command{SIGRTMIN + 1}. Unimportant servers
+may choose to die on @command{SIGDANGER}.
Server may also choose to support the signal
@command{SIGINFO}, or if not defined
@@ -441,6 +437,11 @@ is send by a user to the server, if she wants
the server to dump information about the
server's state or statistics to the TTY.
+@command{valgrind} uses @command{SIGRTMAX} for
+its own internal stuff. Therefore servers must
+not use @command{SIGRTMAX} as it is hence unavailable
+when running under @command{valgrind}.
+
@node Filesystem
--
cgit v1.2.3-70-g09d2