We saw that all the sysadmins in need of SNMP preferred to use the command line to configure it.
If thousands of sysadmin change their mind and want a cockpit page to configure the server, there’s nothing stopping us from developing a new cockpit app.
But don’t forget the fact that the SNMP config isn’t changeable, and as-is basically unusable, so forcing us sysadmins to use command line to do it…
Similiar to the way the NUT support had a hard coded password for a long time, way into 7.x…
Sorry @Andy_Wismer, I don’t understand the meaning of your sentence.
Could you please clarify it (maybe with a real-world example)?
To change the settings of snmpd you have to change its configuration file (/etc/snmp/snmpd.conf).
You have to use the old UI or the config DB or templates. In the future, you could modify the file directly.
But, as I said, I think I haven’t understood what you mean.
But, as I also say, for a long time unix sysadmin, even that is more or less scripted - including the template file…
Note: I’m NOT complaining!
This is Open Source: Don’t bitch about it, but improve it or else contribute to make it better!
This is part of my way of contributing, to make this a better software.
I am a sysadmin. I have NO problems to do certain stuff with command line or scripts.
I’m also noting, that the built in support for NUT in NethServer 7 had at the beginning a hard coded password - that’s long since been corrected! This is an example where things improve with time…
Rome wasn’t built in a day, as the saying goes.
As a matter of fact, as any roman will confirm: They’re still building!
Same goes for any living city - or community: there’s always something to improve!
Hint in cockpit, and leave the rest to sysadmins.
Also remove the template, and leave the snmpd.conf as-is, provided from upstream.
Just for your info, I use exactly the same commands on NethServer, Centos (no wonder!), but also on Proxmox and Raspberry, two very different Debian distro based…