Windows logs.

Folks,

Attached is two files - one for parsing through a directory looking for
Log files and returning key pieces of information; the other for
searching the windows Event Log using WMI.

The Event Log parser will only work on Windows 2003 server I believe.
The support folder of a Windows 2000 server probably contains a command
line driven applet for interrogating the event log.

Hope this helps.


-Gerard

-----Original Message-----
From: ZanDAhaR [mailto:user-42a3456c44ef@xymon.invalid] Sent: Tuesday, 22 November 2005 22:21
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Windows logs.

Thomas wrote:

Yes this is what I ended up doing. I noticed that if I do a dir /X then the 8.3 format is shown, but then I ran into the next problem and

this is wildcard filnames ie. syslog*.log as the logs are named with the date in the filename. This require a total rewrite of the bb-msgs.pl script as far as I could see.

So I told the managers that this was not possible given the timeframe on a windows box. :-( no happy about it.

Thanks for replying.

/Thomas

ZanDAhaR wrote:

Thomas wrote:

Hi !
Any of you had to monitor logs on a windows box where the file is located in a directory with spaces in ?

bb-msgs.pl version 1.1 breaks if I try.

/Thomas

Have you tried taking out the space ? Convert the folder to dos 8.3 format so for eg Program Files ends up being progra~1   Everything gets truncated to 6 chars + ~1. I know its Perl and not dos but it cant hurt to try :)

Allan

I'm sure someone else could help you out with the perl expression but I think maybe it should be %syslog* or something. I'm not a perl junkie so

dont take my word as gospel :)

HTH

Allan