Henrik Triem
Henrik Triem
I've done some tests, and so far it looks like it might be a usable workaround. I don't entirely feel comfortable with this option though, using the nagios-user. I wonder...
Compared the two packages; there are indeed a lot of checks missing in `monitoring-plugins` compared to `monitoring-plugins-all`, and some do seem to make sense instantly: `monitoring-plugins-zypper` for example is missing...
We have worked on a concept, but nothing related to Icinga code itself, and this issue isn't being currently worked on.
Shouldn't this be fixed by now since our hosting provider has a mirror?
My take: We should visualize the pricing model and take all references to a certain model out of the training - this stuff has changed way too often to have...
Looks cool. Does anybody know what pygments would make of this? Anything useful, or would it be garbage? Might be a cool way to improve our .md file.
Can we discuss in what format this should be drafted - especially in coordination with training? I have a draft, but no idea where it is supposed to go.
@Al2Klimov It's on the right track, but for one we only want the release repo to be implemented, and only for a specific Fedora version. I will implement `dnf config-manager...
Honestly, it just doesn't feel right using the nagios-user when we ship a Icinga user through our packages.