Comment 5 for bug 1466790

Revision history for this message
Stefan Bader (smb) wrote : Re: dhclient not started on boot

Hm -s did not work. So I used -l instead. Clearly it gets started. It just feels like it gets ended when ifup exits. As if not damonized enough...

<email address hidden> - ifup for eth0
   Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: enabled)
   Active: active (exited) since Fr 2015-06-19 13:49:09 CEST; 1h 29min ago
  Process: 748 ExecStartPost=/sbin/ifquery --state %I (code=exited, status=0/SUCCESS)
  Process: 456 ExecStartPost=/sbin/ifup --allow=auto %I (code=exited, status=0/SUCCESS)
  Process: 455 ExecStart=/sbin/ifup --allow=hotplug %I (code=exited, status=0/SUCCESS)
 Main PID: 455 (code=exited, status=0/SUCCESS)
   CGroup: /<email address hidden>

Jun 19 13:49:08 lam-wily6401 dhclient[488]: DHCPREQUEST of 192.168.2.189 on eth0 to 255.255.255.255 port 67 (xid=0x31afa115)
Jun 19 13:49:08 lam-wily6401 dhclient[488]: DHCPOFFER of 192.168.2.189 from 192.168.2.1
Jun 19 13:49:08 lam-wily6401 ifup[456]: DHCPREQUEST of 192.168.2.189 on eth0 to 255.255.255.255 port 67 (xid=0x31afa115)
Jun 19 13:49:08 lam-wily6401 ifup[456]: DHCPOFFER of 192.168.2.189 from 192.168.2.1
Jun 19 13:49:09 lam-wily6401 dhclient[488]: DHCPACK of 192.168.2.189 from 192.168.2.1
Jun 19 13:49:09 lam-wily6401 ifup[456]: DHCPACK of 192.168.2.189 from 192.168.2.1
Jun 19 13:49:09 lam-wily6401 dhclient[488]: bound to 192.168.2.189 -- renewal in 297 seconds.
Jun 19 13:49:09 lam-wily6401 ifup[456]: bound to 192.168.2.189 -- renewal in 297 seconds.
Jun 19 13:49:09 lam-wily6401 ifquery[748]: eth0=eth0
Jun 19 13:49:09 lam-wily6401 systemd[1]: Started ifup for eth0.