On 22 January 2017 at 23:41, Christoph Biedl <[email protected]> wrote: > Arturo Borrero Gonzalez wrote... > >> do you have any other comment? > > I didn't get your message. Please check > https://lists.debian.org/debian-devel/2016/12/msg00613.html > So I found your answers rather by coincidence. > >> Thinking again about this, how have you find the inconsistency you are >> referring to? >> I mean, In which form does this affects users? Were you migrating your >> system from sysvinit to systemd? > > This was an upgrade, I cannot check the version numbers right now. > I guess you introduced the service file rather recently? >
Yes, true. In version 3.1.1-1 dated back in 25 Jul 2016. > However, after that upgrade the daemon was silently started, put eth0 > into promiscuous mode which was quite a bad idea in that very > configuration. I'll check again in a few days. > So, the problem then is upgrading from a sysvinit based debian to a systemd based one.
