RE: about a syslog serverFrom: Tucker, Jason (JTucker@libertymgt.com)
- Previous message: Mike V: "Vulnerability scanners:"
- Maybe in reply to: firstname.lastname@example.org: "about a syslog server"
- Next in thread: Evan Pierce: "Re: about a syslog server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Tucker, Jason" <JTucker@libertymgt.com> To: "'email@example.com'" <firstname.lastname@example.org>, email@example.com Date: Fri, 1 Feb 2002 13:38:14 -0500
Check out the Kiwi syslog at http://www.kiwi-enterprises.com
I run it here on a Win2K system and it works great. It has a customizable
set of filters, you should be able to get it to log just about any
combination of levels that you want.
I don't know of any type of rulesets for determining how much space your log
files will take up, but I can tell you I have 10 fairly chatty systems
dumping events into it, and my log files average about 500KB a day.
Hello all. I am researching the creation of a syslog
server on a WinNT or Win2k platform. My goal is to
enable 24/7 logging of 25+ Cisco routers (no
servers). There is a mix of Internet and Intranet
routers involved. I have 3 questions about this. First,
is there a solid 3rd party syslog program that anyone
can recommend for this? Second, is it true that by
choosing to log level 4 (warning) issues that I will also
automatically log levels 0 thru 3? Finally, is there a
any documented baseline rule for determining how
much disk space usage I can expect to accumulate
per day? I have to find out what size drive I would
need. This last question has been a tough one; I
haven't been able to locate any documented formula
for this. Thanks in advance for your help.