/var/lib/dhcp/dhclient.leases is empty (after successfully negotiating a lease with a DHCP server). Reproducible: Always Steps to Reproduce: 1. Set iface_eth0="dhcp" in /etc/conf.d/net 2. connect computer to network where there's a DHCP server working. 3. (Without any dhclient.conf file) start dhcp by issuing /etc/init.d/net start 4. Check `config -a` to verify that networking has been configured. Actual Results: /var/lib/dhcp/dhclient.leases remains empty Expected Results: /var/lib/dhcp/dhclient.leases should contain lease info about the current network configuration. from the dhclient man-page: In order to keep track of leases across system reboots and server restarts, dhclient keeps a list of leases it has been assigned in the dhclient.leases(5) file.... When a new lease is acquired, it is appended to the end of the dhclient.leases file. The DHCP client normally gets its configuration information from ETCDIR/dhclient.conf, its lease database from DBDIR/dhclient.leases, stores its process ID in a file called RUNDIR/dhclient.pid, and configures the network interface using CLIENTBINDIR/dhclient-script
*** This bug has been marked as a duplicate of 27079 ***
This bug is NOT a duplicate of 27079: Bug 27079 relates to dhcpd-3.0. This bug relates to dhcpcd-1.3.
Eric, in your original comment, you describe things that are related to dhcp (not dhcpcd). I.e. /var/lib/dhcp/dhclient.leases is part of dhcp. The client program dhcpcd has nothing to do with that file -- it uses /var/lib/dhcpc in which it places a file like "dhcpcd-eth0.info". Therefore, obviously, dhclient.leases will remain empty. Please confirm that /var/lib/dhcpc/dhcpcd-eth0.info gets populated with some data.
You are correct! I apologize. Did I misread the documentation?... from the dhclient man-page: In order to keep track of leases across system reboots and server restarts, dhclient keeps a list of leases it has been assigned in the dhclient.leases(5) file.... When a new lease is acquired, it is appended to the end of the dhclient.leases file. The DHCP client normally gets its configuration information from ETCDIR/dhclient.conf, its lease database from DBDIR/dhclient.leases, stores its process ID in a file called RUNDIR/dhclient.pid, and configures the network interface using CLIENTBINDIR/dhclient-script ...or is it just wrong?
