Hi, On Mon, 13 May 2019 at 21:42, sergio <sergio...@outerface.net> wrote: > Dear Maintainer, > > after installing hostap on debian buster syslog begin sapammed every > 2 seconds with: > > systemd[1]: hostapd.service: Service RestartSec=2s expired, scheduling > restart. > systemd[1]: hostapd.service: Scheduled restart job, restart counter is at 72. > systemd[1]: Stopped Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP > Authenticator. > systemd[1]: Starting Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP > Authenticator... > hostapd[3500]: Configuration file: /etc/hostapd/hostapd.conf > hostapd[3500]: Could not open configuration file '/etc/hostapd/hostapd.conf' > for reading. > hostapd[3500]: Failed to set up interface with /etc/hostapd/hostapd.conf > hostapd[3500]: Failed to initialize interface > systemd[1]: hostapd.service: Control process exited, code=exited, > status=1/FAILURE > systemd[1]: hostapd.service: Failed with result 'exit-code'. > systemd[1]: Failed to start Advanced IEEE 802.11 AP and IEEE > 802.1X/WPA/WPA2/EAP Authenticator.
Could you please provide more details? The postinst is set up in a way so that if /etc/hostapd/hostapd.conf is not readable or missing, the hostapd.service is masked during the package installation unless it was already running. >From what you wrote it sounds like the package hasn’t been installed before, but then it wouldn’t run by default. -- Cheers, Andrej
