Hi Jon, It's a little unclear who does what. There was no question, but if it is why nxlog writes foo.log.1 instead of foo.log I guess it is because the log rotation script renames the file without telling nxlog about this. You can either use the internal log rotation facility or restart nxlog when you rotate with the script.
Regards, Botond On Tue, 23 Sep 2014 15:23:05 -0400 Jon Brouse <jbro...@zonoff.com> wrote: > At the beginning of a script I am running savelog to rotate old log files. > So log file foo.log becomes foo.log.0 and foo.log.0 becomes foo.log.1 > > After savelog runs, logsave writes to foo.log. On the nxlog server foo.log > is blank and all output is written to foo.log.1 ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ nxlog-ce-users mailing list nxlog-ce-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
