summaryrefslogtreecommitdiff
path: root/manifests/irc_bot
AgeCommit message (Collapse)Author
2012-04-18Fully qualify facter variables to suppress warningsChristian G. Warden
merge conflict due to immerda's branch not being up-to-date on the bot
2011-07-14Merge remote-tracking branch 'remotes/lelutin/bot_fixes'Micah Anderson
Conflicts: manifests/irc_bot.pp Had to merge in the use_notices change that we had in our branch
2011-07-14IRC-bot: split up manifests by OSGabriel Filion
This gives us the possibility of using the nagios::irc_bot::disable class without having any config variable set. When using nagios::irc_bot, we still get yelled at when we didn't define the appropriate variables. While we're moving the code around, change the group applied on the different files from 'root' to '0' for better portability.
2011-07-14IRC-bot: rename nagios::irc_bot::disabled to nagios::irc_bot::disableGabriel Filion
All classes serving the same purpose as this one are called 'disable', so let's follow this standard.
2011-07-14IRC-bot: use 'enable' for DebianGabriel Filion
Since the service "disable" bug was fixed in the debian service provider [1] in the puppet 2.6.2-5 package in squeeze, let's switch from the manual calls to the "enable" feature. [1]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573551 Also add a requirement between service[nagios-nsa] and file[/etc/init.d/nagios-nsa]. This was ensured in Debian with the exec that we're now replacing but didn't find its way through the centosification.
2011-07-14IRC bot: add a 'disabled' classGabriel Filion
For when you need to ensure that the bot doesn't start on a server.