Skip to content
Networks, Applications and Event Monitor
C Shell Makefile M4 Groff Perl Other
Latest commit e4ac825 Jun 22, 2016 @catharsis catharsis workers: Bail out if we can't register wproc query handler
Signed-off-by: Anton Lofgren <alofgren@op5.com>
Failed to load latest commit information.
contrib Give some love to the contrib directory Apr 13, 2015
lib iobroker: Allow polling without registered FDs May 26, 2016
op5build Revert "Revert "Add silent rules"" Feb 3, 2016
sample-config remove enable_environment_macros from sample config Jun 1, 2016
src workers: Bail out if we can't register wproc query handler Jun 23, 2016
t-tap macros: Always get host macros from get_service_macros_r May 17, 2016
t Merge op5 master branch into naemon-core upstream master Feb 24, 2016
tap Remove files which get generated by autoreconf May 24, 2016
tests worker: Don't reap grandchildren immediately Jun 23, 2016
.gitignore Remove files which get generated by autoreconf May 24, 2016
.travis.yml travis: help2man is required for building the manpages Mar 21, 2014
AUTHORS Start fixing the autotools machinery Nov 22, 2013
ChangeLog Start fixing the autotools machinery Nov 22, 2013
LEGAL Remove ancient copyright notice Mar 19, 2014
Makefile.am Handle overflow when diffing times May 31, 2016
NEWS release 1.0.5 Jun 21, 2016
README Start fixing the autotools machinery Nov 22, 2013
README.md Fix url to http://naemon.org in README Feb 11, 2014
THANKS Import the code Nov 1, 2013
UPGRADING finally get rid of the old html files and cgis Nov 22, 2013
acinclude.m4 autotools: Detect supported compiler flags Dec 10, 2013
autogen.sh autogen.sh: Accept and pass on command line arguments Feb 26, 2014
configure.ac Let configure warn if `help2man` is not present on the system May 6, 2016
daemon-init.in Merge op5 master branch into naemon-core upstream master Feb 24, 2016
daemon-systemd.in /var/run/naemon must be created on runtime Mar 8, 2016
functions Import the code Nov 1, 2013
indent-all.sh New indent rules Dec 3, 2013
indent.sh New indent rules Dec 3, 2013
naemon-query.py naemon-query: Avoid debug-printing junk to stdout Apr 10, 2014
naemon-uninstalled.pc.in naemon: Obsolete naemon_user & naemon_group options Mar 2, 2015
naemon.logrotate.in naemon: Obsolete naemon_user & naemon_group options Mar 2, 2015
naemon.pc.in naemon: Obsolete naemon_user & naemon_group options Mar 2, 2015
naemon.tmpfiles.conf Add native systemd support Feb 24, 2014
tap-driver.sh Revert "test: So, tap-driver is installed by autoreconf" Feb 25, 2014
tests.mk Handle overflow when diffing times May 31, 2016
version.sh release 1.0.5 Jun 21, 2016

README.md

Welcome to Naemon Core

Naemon is a host/service/network monitoring program written in C and released under the GNU General Public License. It works by scheduling checks of the configured objects and then invoking plugins to do the actual checking. The plugin interface is 100% Nagios compatible, since Naemon is a fork of the aforementioned project.

Contributing

Contributing to Naemon is meant to be easy, fun and profitable. I'm not sure where the profit will come from, but if you get a warm glow of pride when getting a patch accepted, you can consider that your reward if you like.

The easiest way is probably to fork this project on github, and then send pull requests to the original project. You can also send patches to naemon-dev@monitoring-lists.org.

Commit messages

Commit messages MUST contain a Signed-off-by line and have a proper author name and email address (even though "Anonhacker42 anon@hax.com is considered "proper" in these circles). If you run git commit -s you'll get the signed-off-by for free. The signed-off-by indicates that you're telling us you have the right to submit this patch and that we shouldn't worry about lawyers from whatever company you're working for will come at us later and demand that we remove your contributions from the code. It might not be much of a protection against such things, but it's more or less standard praxis in the git-using projects, so please just stick to it, ok?

Messages MUST contain a brief statement of why the change was made. "Fix bugs" is a bad message, as it means people will have to know which bugs you're fixing. "Make sure we don't segfault when the disk is full" is a useful message, because it points to a problem and makes it clear that the patch should fix it. In case deep analysis was required in order to figure out the root cause of the problem, you're encouraged to also write your findings there. It also makes it look as if you did a whole lot of work and did it thoroughly, which is pretty good for your resumé.

Messages SHOULD be written in imperative form, as if you're giving the code orders on how it should change. It provides a much nicer basis for discussion when a patch has to be reviewed online, as it indicates that the change is about to take place but is open for discussion rather than that it already has and that discussion isn't welcome.

Messages SHOULD have lines shorter than 72 chars. Most of the time, people will inspect logs or blame output in a terminal or in a limited width program, and it's a pain to have to scroll sideways all the time to see the message. Please keep the lines short and it'll save some annoyance on behalf of other people.

Coding standards

Common sense applies.

  • Don't break backwards compatibility without a really good reason.
  • Don't remove or alter API's unless absolutely necessary.
  • Don't write huge functions that do a lot. It's hard to test those, and we do like tests.
  • Use the indentation already found in the files, or reindent to your liking and then run "sh indent-all.sh" when you're done. That should bring the tree back to some semblance of unity.
  • Avoid sending patches with a lot of whitespace changes. They're hard to review so they probably won't be.
  • Don't engage in useless codechurn. If the patch you're submitting doesn't solve an actual problem or paves the way for solving some sort of problem or adding a feature, it's most likely not worth the trouble.

Installing

When installing from a released tarball, all you need to do is to run

./configure
make
sudo make install

If you want to help out with development and hence download the source from git, you instead need to run

./autogen.sh
make
sudo make install

More info

Visit the Naemon homepage at http://naemon.org

Something went wrong with that request. Please try again.