Hi! On Thu, 17 May 2007, [EMAIL PROTECTED] wrote: > Hari Sekhon wrote: >> Hugo van der Kooij wrote: >> > On Wed, 16 May 2007, RR wrote: >> >> I'm relatively new to Nagios and am looking for cool front end tools >> >> to managing the config files. >> >> >> >> Of these, which ones do other users recommend? >> >> >> > vi. ;-) >> > >> > But I never understood the need for 'cool'. I want my tools to be fit >> > for the job and I do not care what they look like that much. >> > >> adding my 2 cents... >> >> I agree with Hugo, I also use vi(m). >> >> front end configuration tools? >> more fluff and less understanding, why bother? >> > I feel it is much better to understand the layout and structure to the > config files than to hide it all behind a gui type front end. > > You learn a lot more about how nagios hangs together by making config > files, running pre-flight checks and getting errors. You then correct > the errors, normally a simple typo or an omitted name in another config > file. This all builds a great understanding of Nagios. > > And well who needs cool, vi is brilliant and in its on way is "cool" as > you get it on most flavours of unix/linux. > > Well that's my six shillings worth
Same here, vim. But, and I can not stress this enough, keep your config in some kinde of version control system. I personally use Subversion, but there are lots of others out ther (CVS, RCS, Bitkeeper, git, ...). This is especially true if more than one person edits the config. Regards, Tobias -- In the future, everyone will be anonymous for 15 minutes. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null