Is it a normal behavior?

Hi friends,

i have got a suse machine, where ISC Bind and ISC Dhcp installed with chroot.

#uname -a
Linux lab-suse-bind 2.6.34-12-desktop #1 SMP PREEMPT 2010-06-29 02:39:08 +0200 x86_64 x86_64 x86_64 GNU/Linux

#ps -A -o comm,pid,args | grep dhcpd

dhcpd 30143 /usr/sbin/dhcpd -4 -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid -chroot /var/lib/dhcp -lf /db/dhcpd.leases -user dhcpd -group nogroup eth0

as per my research on ISC bind and DHCP on other distribution , when machine is configured with chroot, then the config file will be available in (/configfilepath)

  • But this machine has config file in both /etc/dhcpd.conf and /var/lib/dhcp/etc/dhcpd.conf

in every restart It copies file from “etc/dhcpd.conf” to " /var/lib/dhcp/etc/dhcpd.conf " and start the service

i just want to know , is it a normal behavior in suse, because i do not find similarity in other distribution . (other distributions do point to a single file , and no replacing in every restart)

Thanks
Joe

I think the first thing we need to do is establish which kind of SUSE and which version? There’s SUSE Linux Enterprise Desktop which is the subject of this forum, SUSE Linux Enterprise Serverforums for which are at https://forums.suse.com/forumdisplay.php?8-SUSE-Linux-Enterprise-Server and openSUSE, the forums for which are at http://forums.opensuse.org/

Can you post the output of

$ cat /etc/*release*

I’m fairly certain 2.6.34 is not a Kernel version I recall seeing in use in SLED or SLES and it’s not on the list at http://wiki.novell.com/index.php/Kernel_versions

Hi Thanks for the reply ,

hear is the ouput,

lab-suse-bind:~ # cat /etc/release
openSUSE 11.3 (x86_64)
VERSION = 11.3

You probably want the openSUSE forums, then, which are hosted at
http://forums.opensuse.org/ but before you head over there you may also
want to either patch or be clear in the version of openSUSE used by
providing the information you gave us just now.

This is normal functionality. I do not know for sure why it is done, but
my guess is that it is to help make the migration from an environment that
is not chrooted to one that is chrooted easier by helping copy over
required files. If you look at the /etc/init.d/dhcpd script, at least on
my system which is much newer than yours (and still outdated since 13.1 is
out), you’ll see some logic that copies various files to the chroot
environment onstartup.


Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…

Hi Joe,

although your question actually applies to openSUSE, the answer is the same both for openSUSE, SLED and SLES: Yes, this is normal behavior.

It helps to keep configuration at a standard location (/etc/named*) and makes sure that everything is “in place” when you decide to change the run-time location (i.e. when running in a chroot jail).

Regards,
Jens