[Buildroot] [PATCH v3 11/13] package/dhcp: systemd: support IPv6 lease file

[Maxime Hadjinlian]

[-SNIP-]

>
> >     A single instance of dhcpd cannot be run with
> >     both '-4' and '-6'. I don't know if it's possible (or desirable) to
> safely run
> >     simultaneously two instances of dhcpd, one with '-4' and the other
> one with
> >     '-6'.
> >
> > Well it could be useful if you are trying to build a network appliance
> and you want to support both stack. So you would want to start two
> processes with different options. Maybe that's something that should be
> left to the users to figure out.
>
> Yes, but should everything be duplicated in Buildroot just for this
> purpose? For
> SysV, it's easy not to duplicate things, but how would you do that with
> systemd?
> How do distributions handle this?
>
I only looked at Arch Linux, they duplicate the service file. It's also
possible to use the template mechanisms in systemd, to have something like
dhcpd at .service and when you enable it, you create a symlink called
dhcpd at 4.service, and the '4' is passed as argument to the template and you
can use it however you want it to.

>
> >     "$OPTIONS" is designed exactly for such things. Users should read
> the man page
> >     of dhcpd to know what may fit in there.
> >
> > I understood what was "$OPTIONS" about, I just worry that it's a bit
> "hidden" for the users, but maybe they should know what they are doing.
>
> It's not possible to document everything, but there are comments about the
> meaning of these variables in the SysV init scripts, so I can add such
> comments
> to the .service files too.
>
Maybe that would be a good thing, I don't have a clear opinion on this, do
other want to weigh in ?

>
> Best regards,
> Benoît
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildroot.org/pipermail/buildroot/attachments/20151104/d07e34d5/attachment-0001.html>