[systemd-devel] networkd - DHCP timeout ?

[Lennart Poettering]

On Wed, 11.02.15 21:00, Kai Krakow (hurikhan77 at gmail.com) wrote:

> Lennart Poettering <lennart at poettering.net> schrieb:
> 
> > On Wed, 11.02.15 16:08, Vasiliy Tolstov (v.tolstov at selfip.ru) wrote:
> > 
> >> 2015-02-11 14:42 GMT+03:00 Tom Gundersen <teg at jklm.no>:
> >> > systemd-networkd-wait-online gained two new features in git (online
> >> > manpages are still lagging):
> >> >
> >> >        --ignore=
> >> >            Network interfaces to be ignored when deciding if the
> >> > system is online. By default only the loopback interface is ignored.
> >> > This option may be used more than once to ignore multiple network
> >> > interfaces.
> >> >
> >> >        --timeout=
> >> >            Fail the service if the network is not online by the time
> >> > the timeout elapses. A timeout of 0 disables the timeout. Defaults to
> >> > 120 seconds.
> >> >
> >> >
> >> > So you'll just have to override that unit file to add what you want.
> >> 
> >> Thanks! Why not add ability to read environment file for options?
> > 
> > It's a generic tool, people might call with different arguments,
> > waiting for different interface. I am not sure it's a good idea to
> > introduce a singular config file for that, given the number of
> > different contexts this tool might be useful in.
> 
> I think you are covering the idea of loading the config file from within the 
> tool... But how about adding an EnvironmentFile to the service (using the 
> dash prefix) and passing the values from there to ExecStart, defaulting to 
> 120...

EnvironemntFile is a work-around for certain things, I am pretty sure
we shouldn't intrdouce new "fake" configuration files with it.

> Tho, personally I don't see a need for this as "systemctl edit xyz.service" 
> is already a nice configuration tool to personalize services without the 
> need for all those extra configuration files. But people new to the systemd 
> concept tend to love their old concepts of having configuration and scripts 
> everywhere... ;-)

Yeah, "systemctl edit" is the nicer option, I fully agree.

Lennart

-- 
Lennart Poettering, Red Hat