Bug#903303: Acknowledgement (fireqos: Fireqos fails to start on boot)

2018-07-12 Thread Cesare Leonardi 
First, to the bug report context I add that my network is managed by 
NetworkManager and I use a wifi network (so slower to come up than a 
cable network).


Since on one occasion the service started ok on boot, with my basic 
systemd knowledge I analyzed the fireqos.service and I think the problem 
is the lack of something that tells the service to start only after some 
conditions are met. I don't know exactly what are those conditions but 
at least the networks to which fireqos rules are referred should be up.


I've experimented that overriding the fireqos service (systemctl edit 
fireqos.service) with the following lines, worked for me:

---
[Unit]
After=network-online.target
---

I'm sure it's suboptimal, but I tried "After=network.target" and it 
didn't suffice.


Cesare.

Bug#903303: Acknowledgement (fireqos: Fireqos fails to start on boot)

2018-07-09 Thread Jerome BENOIT 
Hello Cesare, thanks for your report.
As I am not so comfortable with service stuff, I am on my way to forward to 
report to the FireHOL forum:
let see what happens .
Jerome

On 08/07/18 21:08, Cesare Leonardi wrote:
> Since on my system I have kept some old kernel installed, I've just tried to 
> boot with the following kernels but the the service still doesn't starts:
> linux-image-4.7.0-1-amd64 (4.7.8-1)
> linux-image-4.15.0-3-amd64 (4.15.17-1)
> 
> Cesare.

-- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B



signature.asc
Description: OpenPGP digital signature

Bug#903303: Acknowledgement (fireqos: Fireqos fails to start on boot)

2018-07-08 Thread Cesare Leonardi 
Since on my system I have kept some old kernel installed, I've just 
tried to boot with the following kernels but the the service still 
doesn't starts:

linux-image-4.7.0-1-amd64 (4.7.8-1)
linux-image-4.15.0-3-amd64 (4.15.17-1)

Cesare.