Help - Search - Members - Calendar
Full Version: Syslog & Named Fails At Boot?
Linuxhelp > Support > Technical Support
I'm running FC3. My server was running fine for a long while. I restarted it the other day a boom, both the syslog and named failed to start at boot. I also tried to start them once in the O.S. and all I get is this error message:

Starting named: named: chroot(): Permission denied

and when trying to start syslog, it just sits at the command prompt. I do updates when necessary. I'm thinking an update might have affected something, but I'm really not sure.

Can someone please help me out?

Thanks in advance,


The BIND nameserver has had its security tightened.
The /var/named/ directory is no longer owned by
"named", but rather by "root". Slave zone files should
now be stored in the new /var/named/slaves/ directory,
which is owned by "named". In addition, a new
bind-chroot package makes it possible to run the
named daemon in a chroot() "jail" (located in
/var/named/chroot/) for greater security.

I'm not sure how to proceed at this point.
Do I need to change the ownership?
I don't have the bind-chroot package as far as I know.
I also don't have a /var/named/chroot directory, as I
never ran bind in chroot.


this might help you

Robert B
awsome! let me see if i can work this out...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2018 Invision Power Services, Inc.