FS#41849 - [ntop] Hardcoded interface
Attached to Project:
Community Packages
Opened by Johannes Ernst (jernst) - Saturday, 06 September 2014, 23:09 GMT
Last edited by Morten Linderud (Foxboron) - Friday, 16 October 2020, 14:56 GMT
Opened by Johannes Ernst (jernst) - Saturday, 06 September 2014, 23:09 GMT
Last edited by Morten Linderud (Foxboron) - Friday, 16 October 2020, 14:56 GMT
|
Details
What about renaming ntop.service to ntop@.service, and
instead of hard-coding eth0 in it, using %i?
E.g. on my "systemctl start ntop.service" fails because I don't have an eth0, but "systemctl start ntop@enp4s1" does work after the above change. |
This task depends upon
Closed by Morten Linderud (Foxboron)
Friday, 16 October 2020, 14:56 GMT
Reason for closing: Won't fix
Additional comments about closing: ntop is not in active development
Friday, 16 October 2020, 14:56 GMT
Reason for closing: Won't fix
Additional comments about closing: ntop is not in active development
systemctl enable --now ntop@eth0,eth1,eth2
systemctl status ntop@enp13s0,tun0,bridge0
Oh wait did I do that wrong? Maybe it was in a different order...
systemctl status ntop@enp13s0,bridge0,tun0
Here's what mine looks like:
ExecStart=/usr/bin/ntop -w 3000
Regardless, we need to get eth0 out of there. eth0 isn't even an interface name that would exist in a modern systemd system, so I can't understand why it is being used in a systemd service.