In Xenial it had no native systemd service yet, hence it uses wrappers around the old sysV code which still uses /etc/default/snmpd
Native .service files got added in 5.7.3+dfsg-1.4 which means Bionic and later. Even more so the systemd version relies on the program to not fork for the tracking (-f) while sysV used that. So the systemd service can not just "fetch and use" the arguments from there. Furthermore exporting for MIBS won't work. We could either just drop default file and sysV script which makes it more clean in general. Or we can add a comment in the default file how to update the configs when using systemd. @Andreas my suggestion would be (seems to be inline with yours): - stop shipping sysV file - rm_conffile the sysV file - to keep defaults (and be upgrade compatible) - we could prepend the options with -f and comment that in the default conf - we could use -m $MIBS to pass those (might be compatible with old format?) - we need the OPTS to only kick in if set (I think I have seen that somewhere) I'm concerned of that as an SRU to change behavior unexpectedly. For existing affected releases people should use the override to configure what they need. The only problem with that is that this might then on dist-upgrade to a new release change slightly due to the planned changes. But this is far more acceptable than a normal in-release package upgrade. Hmm this actually looks even more interesting, back in a bit ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829686 Title: systemd ignoring /etc/default/snmpd on U18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1829686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
