Bug 23246 - RFE - support initscripts options, chroot hooks
Summary: RFE - support initscripts options, chroot hooks
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: bind   
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: David Lawrence
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2001-01-03 20:38 UTC by Pekka Savola
Modified: 2007-04-18 16:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-01-04 13:46:23 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
init.d/named patch to be more options/chroot friendly (1.33 KB, patch)
2001-01-03 20:39 UTC, Pekka Savola
no flags Details | Diff

Description Pekka Savola 2001-01-03 20:38:42 UTC
As per testers-list ideas and discussions, I propose /etc/sysconfig/named which could
contain something like:


The default would be to named with OPTIONS=, ROOTDIR=.

init.d/named could be patched as attached (${ROOTDIR}xxx might use some work).

Add /usr/sbin/populate-named-chroot and we have a system ready to be chrooted in a 
jiffy, no pain.

Red Hat could be the first distribution to distribute bind with chroot hooks in place ;-)

Comment 1 Pekka Savola 2001-01-03 20:39:47 UTC
Created attachment 7003 [details]
init.d/named patch to be more options/chroot friendly

Comment 2 Pekka Savola 2001-01-03 20:41:16 UTC
Disclaimer: Not really tested.

Comment 3 R P Herrold 2001-01-04 02:13:43 UTC
As a matter of coding defensively, PLEASE place options variables as
shown inside double quotes, thus:

OPTIONS=" -t "

... with the /etc/sysconfig/network-scripts/ifcfg-eth0:1 aliases,
omitting the quotes confused the updated initscript in 6.0 or 6.1 for
/etc/rc.d/init.d/network ... It would have avoided much pain ...

Comment 4 Bernhard Rosenkraenzer 2001-01-04 14:15:05 UTC
Done in 9.1.0-0.b1.1
The attached patch is quite broken, but a modified form thereof works, thanks.

Comment 5 Pekka Savola 2001-01-04 14:24:26 UTC
Now that I think about this.. if you want to rndc.conf to reside inside chroot,
you probably must
pass ROOTDIR to rndc with -c (configuration file)

Comment 6 Bernhard Rosenkraenzer 2001-01-04 14:29:40 UTC
Having rndc.conf residing in the chroot structure is not a good idea.
rndc.conf contains secret keys; if someone manages to break into the system over
bind, he shouldn't have access to this file.
He won't if it's outside the chroot jail.

Comment 7 Daniel Roesen 2001-01-04 14:33:45 UTC
Uhm... btw... is Florence planned to come with bind9 only, or will bind8 still
be provided (hopefully as default)?

Note You need to log in before you can comment on or make changes to this bug.