works as expected:
# dhcpcd --dumplease -4 eth0
reason=REBOOT
interface=eth0
protocol=dhcp
ip_address=10.0.0.4
subnet_cidr=24
broadcast_address=10.0.0.255
network_number=10.0.0.0
server_name=IAD201121002027
subnet_mask=255.255.255.0
classless_static_routes=0.0.0.0/0 10.0.0.1 168.63.129.16/32 10.0.0.1 169.254.169.254/32 10.0.0.1
routers=10.0.0.1
domain_name_servers=168.63.129.16
domain_name=v1n0blf1qpvufijtbcm2fvnk3c.bx.internal.cloudapp.net
dhcp_lease_time=4294967295
dhcp_message_type=5
dhcp_server_identifier=168.63.129.16
dhcp_renewal_time=4294967295
dhcp_rebinding_time=4294967295
without the daemon, this surprisingly fails
root@SRU-worked-azure:/home/ubuntu/dhcpcd-10.0.6# pkill -9 dhcpcd
root@SRU-worked-azure:/home/ubuntu/dhcpcd-10.0.6# dhcpcd --dumplease -4 eth0
dhcpcd is not running
Inspecting the code, it appears that if no data is read from the input buffer, the manager daemon is always contacted. This means that parsing via stdin (which is broken) is the only way to run --dumplease without contacting the manager daemon.
works as expected:
without the daemon, this surprisingly fails
Inspecting the code, it appears that if no data is read from the input buffer, the manager daemon is always contacted. This means that parsing via stdin (which is broken) is the only way to run
--dumpleasewithout contacting the manager daemon.