2008/12/22 Nadav Horesh <[email protected]>:
> I tries the following:
>
> Commented out all lines in /etc/init.d/net
> emerged dhcdbd and added it to the chain:
>
>                acpid |      default
>            alsasound | boot
>              beagled |      default
>             bootmisc | boot
>              checkfs | boot
>            checkroot | boot
>                clock | boot
>          consolefont | boot
>               cpudyn |      default
>                cupsd |      default
>               dhcdbd |      default
>               esound |      default
>                  gpm |      default
>                 hald |      default
>             hostname | boot
>           ivman-user |      default
>              keymaps | boot
>           lm_sensors | boot
>                local |      default nonetwork
>           localmount | boot
>              modules | boot
>             net.eth0 |      default
>               net.lo | boot
>             netmount |      default
>            rmnologin | boot
>                samba |      default
>            syslog-ng |      default
>              urandom | boot
>                 usbd |      default
>           vixie-cron |      default
>                  xdm |      default
>               xinetd |      default
>
>
> But it did not bring dhcp on at boot.
> Is there any method I can follow the initialisation process and see if the
> dhcp daemon is called?
>
>   Nadav.
>
try to see the status of dhcdbd with /etc/init.d/dhcdbd status
after you've ascertained that it has been started then you have to see
the system
logs for eventual errors: /var/log/messages contain the logs and dmesg
give infos
about them. i suspect that dhcdbd starts but cannot find a suitable dhcp server
and thus it cannot assign the address.
the other problem might be that you are starting in a different
runlevel which doesn't
have the service, but i doubt that this is the case. try to see the
initial boot process
and see if you're starting in default runlevel.

in my logs i can get the following:

Dec 22 19:45:28 [dhcdbd] Started up.
Dec 22 19:45:33 [dhcdbd] message_handler: message handler not found
under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.reason
Dec 22 20:45:34 [dhclient] wmaster0: unknown hardware address type 801
Dec 22 20:45:34 [dhclient] can't create
/var/lib/dhclient/dhclient-eth2.leases: No such file or directory
Dec 22 20:45:35 [dhclient] wmaster0: unknown hardware address type 801
Dec 22 20:45:36 [dhclient] DHCPDISCOVER on eth2 to 255.255.255.255
port 67 interval 4
Dec 22 20:45:36 [dhclient] DHCPOFFER from 192.168.0.1
Dec 22 20:45:36 [dhclient] DHCPREQUEST on eth2 to 255.255.255.255 port 67
Dec 22 20:45:36 [dhclient] DHCPACK from 192.168.0.1
Dec 22 20:45:36 [dhclient] can't create
/var/lib/dhclient/dhclient-eth2.leases: No such file or directory
Dec 22 20:45:36 [dhclient] bound to 192.168.0.6 -- renewal in 42566 seconds.
Dec 22 19:45:36 [dhcdbd] message_handler: message handler not found
under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.host_name
Dec 22 19:45:36 [dhcdbd] message_handler: message handler not found
under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.domain_name
Dec 22 19:45:36 [dhcdbd] message_handler: message handler not found
under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.nis_domain
Dec 22 19:45:36 [dhcdbd] message_handler: message handler not found
under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.nis_servers
Dec 22 19:45:36 [dhcdbd] message_handler: message handler not found
under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.interface_mtu

you might have different formats, but the content should be similar.

-- 
dott. ing. beso

Reply via email to