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
Task Type Bug Report
Category Packages
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

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
Comment by Sergej Pupykin (sergej) - Friday, 16 October 2015, 11:04 GMT
If you will implement it, please use %I instead of %i. It allows to use multiple interfaces:

systemctl enable --now ntop@eth0,eth1,eth2
Comment by Drew (Drew) - Wednesday, 03 August 2016, 03:01 GMT
An alternative would be to abandon the interface flag entirely. This is an overly cumbersome way to interact with systemd when upstream ntop already has configuration settings to manage this.

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.

Loading...