George A. Theall wrote: > On Thu, Jun 22, 2006 at 10:04:22AM +1200, Jason Haar wrote: > > >> I have been using the "logfile = syslog" feature for some time now, and >> have just upgraded from 2.2.5 to 2.2.8. Now whenever I start nessusd, I >> get a file named "syslog" appearing in the directory I started nessusd >> in - instead of piping logging to syslog as expected >> > > Support for logging via syslog was removed in 2.2.6 / 3.0.1. [NB: this > is true despite what nessus-core/configure might suggest.] > > George > That is a pity. Our nessus servers are all over the world, and cannot be scripted to restart at particular times (so as to rotate logfiles) as there is no guarantee it isn't being used at the time. syslog sneaks around that problem nicely.
How can I do the same thing with logfiles? Can nessus close-and-reopen logfiles based on a signal (like a HUP) - even while running scans? -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +64 3 9635 377 Fax: +64 3 9635 417 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
