Andrew Shadura wrote:
>By 'running' I meant running in terms of systemd, that is the unit is
>somehow started already. Why this matters: the user might have edited
>the unit file or written one of their own, which potentially uses a
>different configuration file from a different location. If we
On 29 November 2017 at 13:57, RjY wrote:
> Andrew Shadura wrote:
>>On 28 November 2017 at 10:24, RjY wrote:
>>> I'm still observing this on upgrade from 2:2.4-1.1 to 2:2.6-8.
> [...]
>>> As workaround I did "sudo update-rc.d hostapd
Andrew Shadura wrote:
>On 28 November 2017 at 10:24, RjY wrote:
>> I'm still observing this on upgrade from 2:2.4-1.1 to 2:2.6-8.
[...]
>> As workaround I did "sudo update-rc.d hostapd disable" (Wasn't sure what
>> the systemctl equivalent is) then "sudo dpkg
Hi,
On 28 November 2017 at 10:24, RjY wrote:
> I'm still observing this on upgrade from 2:2.4-1.1 to 2:2.6-8.
>
> rjy@vile /tmp % systemctl status hostapd
> ● hostapd.service - Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP
> Authenticator
>
I'm still observing this on upgrade from 2:2.4-1.1 to 2:2.6-8.
rjy@vile /tmp % systemctl status hostapd
● hostapd.service - Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP
Authenticator
Loaded: loaded (/lib/systemd/system/hostapd.service; enabled; vendor
preset: enabled)
Package: hostapd
Version: 2:2.6-7
Severity: normal
The installation of hostapd in Debian sid fails.
Preparing to unpack .../hostapd_2%3a2.6-7_amd64.deb ...
Unpacking hostapd (2:2.6-7) ...
Setting up hostapd (2:2.6-7) ...
Job for hostapd.service failed because the control process exited with
6 matches
Mail list logo