You can set the loglocation, the rotation period and the archive location in
nagios.cfg for starters. There are several other files that you can also
change the location of.
# LOG FILE
# This is the main log file where service and host events are logged
# for historical purposes. This should be the first option specified
# in the config file!!!
log_file=/var/log/nagios/nagios.log
# LOG ROTATION METHOD
# This is the log rotation method that Nagios should use to rotate
# the main log file. Values are as follows..
# n = None - don't rotate the log
# h = Hourly rotation (top of the hour)
# d = Daily rotation (midnight every day)
# w = Weekly rotation (midnight on Saturday evening)
# m = Monthly rotation (midnight last day of month)
log_rotation_method=d
# LOG ARCHIVE PATH
# This is the directory where archived (rotated) log files should be
# placed (assuming you've chosen to do log rotation).
log_archive_path=/var/log/nagios/archives
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Behen, Sean
Sent: Tuesday, December 12, 2006 4:01 PM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] Niagos Low Disk Space
I am receiving alerrt messages about low disk space. Is there a way to move
this log file to a different location, say home or should I relocate another
log file such a as Nessus, is that possible?
Sean Behen
Atlas Group Inc.
Kennebunk, ME 04043
[EMAIL PROTECTED]
(207) 985 - 9844 office
(207) 423 - 2562 mobile
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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
