Hi Thomas,
Sorry for not replying earlier...
On Tue, 05 Mar 2013 10:23:24 +0100
Thomas Bächler <thomas@xxxxxxxxxxxxx> wrote:
> Am 04.03.2013 21:26, schrieb Leonid Isaev:
> > Hi,
> >
> > With testing/wpa_actiond-1.4 I am having a minor problem when shutting down
> > net-auto-wireless.service: 'systemctl stop net-auto-wireless.service'
> > pauses for ~10sec before finally disconnecting. Of course, this also
> > occurs on normal system poweroff (which is usually ~5sec). The wifi
> > network is WPA "enterprise" (important entries in wpa_supplicant.conf:
> > key_mgmt=WPA-EAP; eap=PEAP; phase1="peaplabel=0"; phase2="auth=MSCHAPV2"),
> > and piece of daemon.log after the above delay has elapsed:
>
> I've seen this too, but I didn't determine yet that is was wpa_actiond's
> fault. There are several issues here:
wpa_supplicant 2.0 + wpa_actiond 1.3 do not suffer from the above problem,
so...
OTOH, the delay seems to be related to deauthentication. If authentication is
impossible, e.g. due to wrong password (but SSID is still correct), there is
no delay on stop/restart.
>
> 1) I am unsure what exactly terminates wpa_actiond.
Does it really matter, if all wpa* processes are in the same cgroup?
> 2) net-auto-wireless.service is Type=forking, but has no proper MainPID
> detected, so systemd doesn't know what exactly to kill.
>
> This change however seems to be related to Pali's changed, so I'm CC'ing
> him to see if he knows what this might be about.
>
>
My understanding is that netcfg is not maintaned any more, so I'll switch to
netctl to look further into this. But the bigger question which I have is why
do we even need net{cfg,ctl}? Wpa_actiond attaches to wpa_supplicant's socket,
no? So can't we make systemd own this socket and use the netcfg-wpa_actiond
only as a helper for wpa_actiond (i.e. eliminate net-auto-wireless.service
alltogether)?
--
Leonid Isaev
GnuPG key: 0x164B5A6D
Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
Attachment:
signature.asc
Description: PGP signature
