I agree with mark Fosters proposal on names...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios3 in Ubuntu.
https://bugs.launchpad.net/bugs/300660
Title:
"nagios3-common" package should not have configuration files named as
"
** Changed in: nagios3 (Ubuntu)
Importance: Undecided => Wishlist
Status: New => Confirmed
--
"nagios3-common" package should not have configuration files named as
"*-nagios2.cfg"
https://bugs.launchpad.net/bugs/300660
You received this bug notification because you are a member of Ubun
This is also a good idea... Actually, it's better than mine.
Anyway... I just wish not to mix "nagios3" & "nagios2" terms in paths...
This mix seems so strange...
--
"nagios3-common" package should not have configuration files named as
"*-nagios2.cfg"
https://bugs.launchpad.net/bugs/300660
You
I respectfully disagree.
IMO they should not have "nagios3" or "nagios2" in the path names at all,
instead...
/etc/nagios/conf.d/contacts.cfg
/etc/nagios/conf.d/extinfo.cfg
This matches up with the paths from nagios-plugins and is the better
approach.
Nobody is going to feasibly run nagios2 & n
