Nagios Support Forum

--0-207874789-1244200832=:87406
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0A=0AAndreas Ericsson wrote:=0A>I like the current behaviour, but I'd acce=
pt a patch to take 'only' or something=0A>as an argument to "use_syslog" to=
make the behaviour you're talking about happen.=0A>=0A>Do note that histor=
y browsing won't work in the CGI's if nagios.log doesn't get=0A>written at =
all, so this option should very, very clearly be marked in such a way=0A>th=
at unsuspecting new users don't shoot themselves in the foot. Recreating a=
=0A>proper nagios.log from the syslog messages is ofcourse possible, but I'=
d rather=0A>avoid having to try it if at all possible. Especially given mos=
t distributions=0A>tendency to only keep syslog files around for four weeks=
before rotating them=0A>into oblivion. Four weeks means users that want av=
ailability reports on a month=0A>or so won't even realize the data they nee=
d isn't where it should be before it=0A>doesn't exist anymore. Bad Thing(tm=
) indeed.=0A=0AI agree totally, but have a slightly related comment.=0A=0AW=
hen using a supervisory process manager, like runit runsv(dir), you really =
do not=0Awant any output to appear on the console. To my knowledge there is=
currently no way=0Ato run Nagios in the foreground and not have any output=
on the console. During=0Astartup you always get something similar to this:=
=0A=0A Nagios 3.0.6=0A Copyright (c) 1999-2008 Ethan Galstad (http://=
www.nagios.org)=0A Last Modified: 12-01-2008=0A License: GPL=0A =
=0A Nagios 3.0.6 starting... (PID=3D2071)=0A Local time is Fri Jun 05=
12:26:53 CEST 2009=0A=0AMy first expectation on use_syslog was at least to=
get rid of this output.=0A=0AOf cause, you may catch console messages when=
using a process supervisor and=0Asetup an alternative log daemon for them,=
but if you want them to end up in=0Asyslog that's quite awkward. Further m=
ore, redirection to /dev/null does not=0Aplay well with process supervisors=
.=0A=0Ause_syslog is probaly not the best fix for this, since you probably =
want to=0Acontrol the Nagios log output in conjuction with a process manage=
r. Maybe a=0Ano_console or a --quiet startup flag is better suited.=0A=0A/S=
-G=0A________________________________________________________=0ASven-G=F6ra=
n Bergh, Systemasis AB=0A__________________________________________________=
______=0A=0A=0A ______________________________________________________=
____=0AG=E5r det l=E5ngsamt? Skaffa dig en snabbare bredbandsuppkoppling. =
=0AS=F6k och j=E4mf=F6r priser hos Kelkoo.=0Ahttp://www.kelkoo.se/c-1000158=
13-bredband.html?partnerId=3D96914325
--0-207874789-1244200832=:87406
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Andreas Ericsson wrot=
e:>I like the current behaviour, but I'd accept a patch to take 'onl=
y' or something>as an argument to "use_syslog" to make the behaviour=
you're talking about happen.>>Do note that history browsing =
won't work in the CGI's if nagios.log doesn't get>written at all, so=
this option should very, very clearly be marked in such a way>that =
unsuspecting new users don't shoot themselves in the foot. Recreating a=
>proper nagios.log from the syslog messages is ofcourse possible, but I'=
d rather>avoid having to try it if at all possible. Especially given
most distributions>tendency to only keep syslog files around for fo=
ur weeks before rotating them>into oblivion. Four weeks means users =
that want availability reports on a month>or so won't even realize t=
he data they need isn't where it should be before it&

...[email truncated]...


This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]