On Sun, Aug 17, 2014 at 09:24:33PM -0700, Ludovico Cavedon wrote: > On Sun, Aug 17, 2014 at 9:14 PM, Josh Triplett <j...@joshtriplett.org> wrote: > > On Sun, Aug 17, 2014 at 08:48:40PM -0700, Ludovico Cavedon wrote: > >> On Sun, Aug 17, 2014 at 1:40 AM, Josh Triplett <j...@joshtriplett.org> > >> wrote: > >> > 3) Teach ntopng to understand /etc/ntopng.conf natively and migrate the > >> > settings there. > >> > >> yes, that would be an option. I forgot to add the requirement "without > >> patching upstream code" :) > > > > Debian is not the only distribution that will ever encounter this > > problem. Rather than hacking around it downstream, why not fix it the > > right way upstream? /etc/default almost always represents a > > Debian-specific hack. > > Well, I do not see this as an upstream bug that needs to be fixed. > If no interface is given, ntopng will autodetect the network > interfaces. If you want to use a different set, you pass them to it on > the command line. > > I agree it could be improved by adding support for a separate > configuration file, but upstream does not have any incentive right now > in doing it, and I do not have the time/interest in working in a > possible large patch to add support for new config file to ntopng.
Then, for now, I'd suggest migrating the settings in /etc/default/ntopng to have a -i in front of each interface, and referencing that from the .service file via EnvironmentFile=-/etc/default/ntopng . - Josh Triplett -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140818043700.GA1964@thin
