Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 15973

Summary:	initlog doesn't start properly chrooted named
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <vilmos>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-02-15 20:55:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Need Real Name 2000-08-11 03:40:38 UTC

I want to run named chrooted, but I cannot start through
/etc/rc.d/init.d/named. This is a slave named, and at most only one
named-xfer succeeds. The commandline within /etc/rc.d/init.d/named is

daemon /home/chroot/named/usr/sbin/named -u named -g named -t
/home/chroot/named -c /named.conf

In syslog, for each failed named-xfer, I see a signal 13 (SIGPIPE).
If I start named from the commandline (without nice and initlog), then it
runs fine and all of the named-xfers succeed. I tracked down the problem to
initlog. If I start the command

initlog -c "/home/chroot/.../named -u named ..."

Then I have the same problem. However, if instead of -c I use -r, then
named will start properly. As a side note, the -q switch is not documented
in the man page. ;-)

Solution? For named, just start with the -r switch. Unfortunately I
couldn't really understand the difference between -c and -r and I don't
know what else it would do.

Thank you for your time, Vilmos Soti

Comment 1 Bill Nottingham 2000-08-11 13:47:40 UTC

-c runs the command and logs its output.

-r runs the command, and initlog stays around looking
for things to log on its own stdin. Presumably what's
happening is that bind is closing its stdin, so initlog
exits.

Comment 2 Bill Nottingham 2001-01-30 20:35:04 UTC

*** Bug 25269 has been marked as a duplicate of this bug. ***

Comment 3 Bill Nottingham 2001-01-30 20:59:58 UTC

(make that, bind is closing its stdout and stderr.)

Comment 4 Bill Nottingham 2001-01-31 17:45:48 UTC

*** Bug 25269 has been marked as a duplicate of this bug. ***

Comment 5 Bill Nottingham 2005-02-15 20:55:13 UTC

Closing out bugs on older, no longer supported, releases.

initlog is no longer in the current devel tree, so it is unlikely to change.