From 1783d66b34ec2775b3d1595f31c0ee21aa2d0676 Mon Sep 17 00:00:00 2001 From: Mark Andrews Date: Tue, 29 Jan 2008 04:27:49 +0000 Subject: [PATCH] document the use of 'modprobe' --- FAQ | 7 ++++++- FAQ.xml | 10 ++++++++-- 2 files changed, 14 insertions(+), 3 deletions(-) diff --git a/FAQ b/FAQ index 90b3ca0453..230616e5de 100644 --- a/FAQ +++ b/FAQ @@ -594,7 +594,12 @@ Q: I get the error message "named: capset failed: Operation not permitted" when starting named. A: The capability module, part of "Linux Security Modules/LSM", has not - been loaded into the kernel. See insmod(8). + been loaded into the kernel. See insmod(8), modprobe(8). + + The relevant modules can be loaded by running: + + modprobe commoncap + modprobe capability Q: I'm running BIND on Red Hat Enterprise Linux or Fedora Core - diff --git a/FAQ.xml b/FAQ.xml index f2b8e3f287..67d7b854bd 100644 --- a/FAQ.xml +++ b/FAQ.xml @@ -17,7 +17,7 @@ - PERFORMANCE OF THIS SOFTWARE. --> - +
Frequently Asked Questions about BIND 9 @@ -1064,7 +1064,13 @@ client: UDP client handler shutting down due to fatal receive error: unexpected The capability module, part of "Linux Security Modules/LSM", - has not been loaded into the kernel. See insmod(8). + has not been loaded into the kernel. See insmod(8), modprobe(8). + + + The relevant modules can be loaded by running: + +modprobe commoncap +modprobe capability -- GitLab