On 9/16/11 7:45 AM, "Ken Schweigert" wrote:
> Thinking maybe something happened to these devices, I listed them out
> and didn't see anything obviously wrong:
>
> [root@ns1 dev]# ls -l /dev/null
> crw-rw-rw- 1 root root 1, 3 Apr 8 14:46 /dev/null
> [root@ns1 dev]# ls -l /chroot/named/dev/null
>
Thanks everyone for showing me the null built-in. I will change it to
that and that will probably fix my problem.
-ken
On Fri, Sep 16, 2011 at 11:04 AM, Phil Mayers wrote:
> On 16/09/11 15:45, Ken Schweigert wrote:
>
>> logging {
>> ...
>> channel "dev_null_log" {
>> file "/dev/nul
On 16/09/11 15:45, Ken Schweigert wrote:
logging {
...
channel "dev_null_log" {
file "/dev/null";
};
…
category lame-servers { dev_null_log; };
Why not just:
category lame-servers { null; };
...which is built-in?
___
Please vis
On Fri, 16 Sep 2011, Ken Schweigert wrote:
Looking through my named.conf the only reference I have to /dev/null is:
logging {
...
channel "dev_null_log" {
file "/dev/null";
};
…
category lame-servers { dev_null_log; };
…
I'd really like to not lose this channel because of how m
Ken Schweigert wrote:
>
> logging {
> ...
> channel "dev_null_log" {
> file "/dev/null";
> };
> …
> category lame-servers { dev_null_log; };
> …
Use the built-in "null" channel instead.
Tony.
--
f.anthony.n.finchhttp://dotat.at/
Irish Sea: South or southeast veering west o
I've been running a bind server for many years and have never had a
problem with upgrading until last night. My needs for the bind server
are pretty meager, just hosting a few hundred zones without DNSSEC.
It is set up in a chroot jail according to a linux howto I found years
ago.
When compiling,
6 matches
Mail list logo
