Core 2: rndc failure to communicate

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: fedora-list@xxxxxxxxxx
Subject: Core 2: rndc failure to communicate
From: Jan Houtsma <list@xxxxxxxxxxx>
Date: Mon, 24 May 2004 17:01:40 +0200
Reply-to: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
User-agent: Mozilla Thunderbird 0.6 (Windows/20040502)

Caused by the fact that the -t option is specified in /etc/sysconfig/named (which is passed to the named daemon on the commandline for chroot to another directory).

After removing that line from that file rndc was able to build the socket succesfully on l27.0.0.1:953.

--
jan

Follow-Ups:
- Re: Core 2: rndc failure to communicate
  - From: Alexander Dalloz

Prev by Date: [FC2] Gnome Lock Screen?
Next by Date: Re: MS Access alternative.
Previous by thread: [FC2] Gnome Lock Screen?
Next by thread: Re: Core 2: rndc failure to communicate
Index(es):
- Date
- Thread

[Index of Archives] [Current Fedora Users] [Fedora Desktop] [Fedora SELinux] [Yosemite News] [Yosemite Photos] [KDE Users] [Fedora Tools] [Fedora Docs]