Yarick, thanks for your reply. I don't see anything that resembles a log verbosity level in nessusd.conf, and since I'm operating on a very large network (/16), my settings needs to be global (ie. not confined to single plugins which may support variable verbosity). Where can I tune this?
Having cron trim my logs is a poor choice in my opinion -- I'd much rather not log useless data in the first place. Regards -rw YARICK wrote: > hi, > please check your verbosity level within nessus and i would look into > using cron for or some other daemon for log rotation. > > > On Tue, May 27, 2008 at 3:00 PM, Rich Whitcroft <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Hi, > > I can't find any facility to control the size/content of > nessusd.messages. I just ran a scan on a /24 subnet and was seeing log > file growth of 1 meg per second. The entire scan lasted 570 > seconds, so > about 600 megs of logs for one subnet. Also, much of the log file > contained entries like this > > [Tue May 27 14:34:19 2008][5455] user operator : Not launching > debian_DSA-829.nasl against 129.100.86.73 <http://129.100.86.73> > because the key > Host/Debian/dpkg-l is missing (this is not an error) > > which seems a little too verbose since these messages are > insignificant. > > I have log_whole_attack and log_plugins_name_at_load set to 'no'. > > Can I control these settings somewhere? It would be nice to avoid > having > to set logfile = /dev/null. > _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
