1 |
I tries the following: |
2 |
|
3 |
* Commented out all lines in /etc/init.d/net |
4 |
* emerged dhcdbd and added it to the chain: |
5 |
|
6 |
|
7 |
acpid | default |
8 |
alsasound | boot |
9 |
beagled | default |
10 |
bootmisc | boot |
11 |
checkfs | boot |
12 |
checkroot | boot |
13 |
clock | boot |
14 |
consolefont | boot |
15 |
cpudyn | default |
16 |
cupsd | default |
17 |
dhcdbd | default |
18 |
esound | default |
19 |
gpm | default |
20 |
hald | default |
21 |
hostname | boot |
22 |
ivman-user | default |
23 |
keymaps | boot |
24 |
lm_sensors | boot |
25 |
local | default nonetwork |
26 |
localmount | boot |
27 |
modules | boot |
28 |
net.eth0 | default |
29 |
net.lo | boot |
30 |
netmount | default |
31 |
rmnologin | boot |
32 |
samba | default |
33 |
syslog-ng | default |
34 |
urandom | boot |
35 |
usbd | default |
36 |
vixie-cron | default |
37 |
xdm | default |
38 |
xinetd | default |
39 |
|
40 |
|
41 |
But it did not bring dhcp on at boot. |
42 |
Is there any method I can follow the initialisation process and see if the dhcp daemon is called? |
43 |
|
44 |
Nadav. |
45 |
|
46 |
On Wed, 2008-12-17 at 19:44 +0000, Beso wrote: |
47 |
|
48 |
> 2008/12/16 Nadav Horesh <nadavh@×××××××××××.com>: |
49 |
> > We have a network with a windows dhcp server. Few weeks ago dhcpcd did not function at the boot, and since them I have to bring it up manually: |
50 |
> > |
51 |
> > $ dhcpcd eth0. |
52 |
> > |
53 |
> > Configuration: |
54 |
> > $ rc-update -s |
55 |
> > acpid | default |
56 |
> > alsasound | boot |
57 |
> > beagled | default |
58 |
> > bootmisc | boot |
59 |
> > checkfs | boot |
60 |
> > checkroot | boot |
61 |
> > clock | boot |
62 |
> > consolefont | boot |
63 |
> > cpudyn | default |
64 |
> > cupsd | default |
65 |
> > esound | default |
66 |
> > gpm | default |
67 |
> > hald | default |
68 |
> > hostname | boot |
69 |
> > ivman-user | default |
70 |
> > keymaps | boot |
71 |
> > lm_sensors | boot |
72 |
> > local | default nonetwork |
73 |
> > localmount | boot |
74 |
> > modules | boot |
75 |
> > net.eth0 | default |
76 |
> > net.lo | boot |
77 |
> > netmount | default |
78 |
> > rmnologin | boot |
79 |
> > samba | default |
80 |
> > syslog-ng | default |
81 |
> > urandom | boot |
82 |
> > usbd | default |
83 |
> > vixie-cron | default |
84 |
> > xdm | default |
85 |
> > xinetd | default |
86 |
> > |
87 |
> > The "/etc/conf.d/net" files was initially empty (comments only). Changing to: |
88 |
> > |
89 |
> > $ cat /etc/conf.d/net |
90 |
> > # This blank configuration will automatically use DHCP for any net.* |
91 |
> > # scripts in /etc/init.d. To create a more complete configuration, |
92 |
> > # please review /etc/conf.d/net.example and save your configuration |
93 |
> > # in /etc/conf.d/net (this file :]!). |
94 |
> > modules=( "dhcpcd" ) # to select dhclient over dhcpcd |
95 |
> > config_eth0=( "dhcp" ) |
96 |
> > dhcp_eth0="nontp nonis" |
97 |
> > |
98 |
> > did not help. |
99 |
> > |
100 |
> > Before the login prompt I get the message: |
101 |
> > |
102 |
> > WARNING: netmount is scheduled to start when net.eth0 has started. |
103 |
> > (and a similar warning for the samba services |
104 |
> > |
105 |
> > Any ideas how to get dhcpcd run at boot? |
106 |
> > |
107 |
> > Nadav. |
108 |
> > |
109 |
> i'd put that file to blank again and try using dhcdbd instead of dhcpcd, that |
110 |
> is quite old and almost not used anymore in favor of dhcpclient/dhcdbd. |
111 |
> i've been switching to the later since i've had some problems with it with the |
112 |
> old baselayout 1.2. |
113 |
> |