[Hans Brand]

Dear Ray,

Thanks for the confirmation.
I’ll stop trying to make it work until I hear from you that a new build is available.

Have a lovely holiday period and speak again in the new year.

Kind regards,
Hans

[Hans Brand]

Hi Ray,

Did not know that feature, I have also added it to my programs!

Kind regards,
Hans Brand

[Hans Brand]

Hi Ray,

Just had the opportunity to open a bunch of 10MByte CodeSite log files with the 5.4 FileViewer and the load speed increment is indeed very noticeable! Thanks!

Greetings,
Hans Brand

[Hans Brand]

Hi,

Just an idea for a (temporary) work-around until a proper solution is created.

What I do is, when starting and stopping an application (logging), is insert recognizable entries in the logging.

In my case it is “CodeSite->AddSeparator();” but anything recognizable should work.

You could then try to detect if this “end” entry is in the cls-file.

Then the archiver can be started.

Kind regards,
Hans Brand

 

[Hans Brand]

Dear Ray,

Hope you are still in good health?

I would like to add another request for the CSSearchFile.exe program.
It would really help me when the “Date” and “Time Stamp” columns were included in the output.

Kind regards,
Hans Brand

 

[Hans Brand]

Dear Ray,

I am still using the CSSearchFiles tool with much success, thanks.

I have one request, though.
Would it be possible to do recursive searches down into sub-directories?
I have gathered a lot of logging files into more than 60 sub-folders (different levels deep) and want to quickly see if any event ever occurred in any of these log files. By the way, all my log files have the .csl extension.

Also noticed that the CSSearchFiles is not in the 5.3.4 distribution with C++ Builder?

Kind regards and stay healthy,

Hans Brand

 

[Hans Brand]

Hi Ray,

There was another occurrence of the Out of Memory.

It is not a ‘disk full’ problem, there is plenty space left. Also after restarting no error is given (it would with a full disk, I guess).

Now also the Live Viewer was involved. I can sort of understand that the viewer will run out of memory in time. I will stop activating the Live Viewer, that is no problem. Still logging to disk.

But that the Dispatcher runs out of memory is stranger.

The CSDispatcherLog file was retrieved but that was after the program was restarted and there is no info in it about the previous Out of Memory anymore. I have asked them to first copy this file before restarting.

Below is a screen shot of the Task Manager after the software was restarted. The Memory use of the Dispatcher is seen to rapidly increase while the Live Viewer is not increasing that much. This indeed might lead to an Out of memory soon.

A few hours later:

Are there any hints you can think of to prevent the Dispatcher from eating up all its memory?

Kind regards, Hans

 

[Hans Brand]

Thanks Ray!

Your tool did exactly what I needed it to do! It found that only two *.csl files of the 300+ actually had a warning in it, using this single command:

CSSearchFiles.exe -type:W *feb25*.csl
CodeSite Search Files 5.3.3
Copyright (c) 1998-2018 by Raize Software, Inc. All Rights Reserved.

LaserToolLog2020Feb25_1324_0056.csl
2054 Warning Timeout waiting for BQ_LOW

LaserToolLog2020Feb25_1324_0138.csl
3915 Warning Timeout waiting for BQ_LOW

Greetings, Hans Brand

 

[Hans Brand]

Hello Ray,

Thank you for picking this up so quickly.

Just a list with files containing any warning messages is actually already very helpful to me. Most of the files do not have any warnings in them. I’ll wait for your tool.

Greetings,
Hans

[Author]

Posts