03-11-2013
From the info you provide it seems you're using a chroot'ed environment. I bet the issue relies in how you configured the chroot permissions.
What kind of chroot environment are you using? (manual chroot, OpenSSH jail, rssh, etc?).
Perhaps some ACL getting in the way?
Is the owner of the file the same as the default named user (usually named "named")
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Dear All ,
Kindly i would like to start the named whenever the system reboot , currently i start it manually .
for more info. i have both named , one from SUN , and other one i installed it from internet , now i want the one from SUN to start automatically when rebooting .
its path is :... (5 Replies)
Discussion started by: tamemi
5 Replies
2. UNIX for Advanced & Expert Users
Guys ,
Am using Linux - Red Hat 6.1 .
My DNS and nslookup command was working fine and ppl. can resolve through this server .
but i changed something in /etc/named.conf , that stopped the DNS .
The named proccess is working , but nslookup command is not , i get this error message :
... (3 Replies)
Discussion started by: tamemi
3 Replies
3. Red Hat
hello everyone,
I have install centos 5 recently.The file /etc/named.conf not found. I have installed BIND using yum. so now what to do ?? should i create named.conf file manually ???
please help me.
thanks,
sharlin. :) (1 Reply)
Discussion started by: sharlin
1 Replies
4. Red Hat
Dear Linux Experts,
On my windows 7 desktop with the help of Vmware workstation (Version 7.1),
created virtual machine and installed Centos 5.7 successfully using ISO image.
Query : Is this possible to upgrade the Centos 5.7 using Centos 5.8 ISO image to Centos version 5.8?.. if yes kindly... (2 Replies)
Discussion started by: Ananthcn
2 Replies
5. UNIX for Advanced & Expert Users
Hi Guys,
I am configuring DNS BIND server I am getting following error, can someone please help ...below is my complete /etc/named.caching-nameserver.conf file :-
# service named restart
Stopping named:
Starting named:
Error in named... (1 Reply)
Discussion started by: patibandlavinay
1 Replies
6. UNIX for Dummies Questions & Answers
e.g.
File name: File.txt
cat File.txt
Result:
#INBOUND_QUEUE=FAQ1
INBOUND_QUEUE=FAQ2
I want to get the value for one which is not commented out.
Thanks, (3 Replies)
Discussion started by: Tanu
3 Replies
LEARN ABOUT OPENSOLARIS
chroot
chroot(1M) System Administration Commands chroot(1M)
NAME
chroot - change root directory for a command
SYNOPSIS
/usr/sbin/chroot newroot command
DESCRIPTION
The chroot utility causes command to be executed relative to newroot. The meaning of any initial slashes (/) in the path names is changed
to newroot for command and any of its child processes. Upon execution, the initial working directory is newroot.
Notice that redirecting the output of command to a file,
chroot newroot command >x
will create the file x relative to the original root of command, not the new one.
The new root path name is always relative to the current root. Even if a chroot is currently in effect, the newroot argument is relative to
the current root of the running process.
This command can be run only by the super-user.
RETURN VALUES
The exit status of chroot is the return value of command.
EXAMPLES
Example 1 Using the chroot Utility
The chroot utility provides an easy way to extract tar files (see tar(1)) written with absolute filenames to a different location. It is
necessary to copy the shared libraries used by tar (see ldd(1)) to the newroot filesystem.
example# mkdir /tmp/lib; cd /lib
example# cp ld.so.1 libc.so.1 libcmd.so.1 libdl.so.1
libsec.so.1 /tmp/lib
example# cp /usr/bin/tar /tmp
example# dd if=/dev/rmt/0 | chroot /tmp tar xvf -
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
cd(1), tar(1), chroot(2), ttyname(3C), attributes(5)
NOTES
Exercise extreme caution when referencing device files in the new root file system.
References by routines such as ttyname(3C) to stdin, stdout, and stderr will find that the device associated with the file descriptor is
unknown after chroot is run.
SunOS 5.11 15 Dec 2003 chroot(1M)