[systemd-devel] [PATCH 1/2] wpa_supplicant: Add systemd support

[Lennart Poettering]

On Tue, 12.07.11 16:20, Henry Gebhardt (hsggebhardt at googlemail.com) wrote:

> 
> (To the hostap mailing list: I wasn't subscribed to this list when I
> sent the patches, now I am. Did they reach you?)
> 
> On Mon, Jul 11, 2011 at 10:13:52PM +0000, Alexander E. Patrakov wrote:
> > Henry Gebhardt wrote:
> > 
> > > --- /dev/null
> > > +++ b/wpa_supplicant/systemd/wpa_supplicant at .service @@ -0,0 +1,11 @@
> > > +[Unit]
> > > +Description=WPA supplicant daemon (interface-specific version)
> > > +# NetworkManager users will probably want the dbus version instead.
> > > +[Service]
> > > +Type=simple
> > > +ExecStart=/sbin/wpa_supplicant
> > > -c/etc/wpa_supplicant/wpa_supplicant.conf -i%I
> > > +[Install]
> > > +Alias=network.target.wants/wpa_supplicant at wlan0.service
> > 
> > This is not enough to get a working wpa_supplicant on a wired interface 
> > that uses 802.1X - we need -Dwired in this case.
> 
> I wasn't even aware that possibility existed. :) Do you think it makes
> sense to provide a unit file for each of the driver options? I'm rather
> thinking that providing a template that works for the most common setups
> may be sufficient.

Isn't there an option to add to wpa_supplicant to autodetect this
setting? For example -Dauto or so? Or just leaving it out entirely?

> Ah, right. Is "After=sys-devices-*-net-%I.device" possible and
> sufficient? systemd.unit(5) doesn't say anything about globbing.

Not wildcards like this are not supported, to what should it even be
resolved? At boot time we simply have no idea what devices might pop up
eventually, but without that we don't know how long to wait.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.