This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

File Size of .log

Hello once again pretor989 here

I just have a qucik question concerning the .log-files which are created by the Virtualization Scan Controller.

According to the documentation of the Controller it automatically creates a log file and once a specific size is reached it creates a new file while at the same time renaming the old one. (from savscancontroller.log >> savscancontroller.log.1).

By doing this there are up to 5 consecutive log files in existence at once. Unfortunately the "oldest" data will be lost once the maximum file size is exceded and another new file created. Because of this it sometimes happens that we can not easily reconstruct if every specified server was scanned or not because the "new" log files are flooded with reports concerning the wait states of the machines.

Now the question is: Is there any way to raise either the maximum file size of the log-files (currently at about 49KB) or the number of log files?

Or maybe there exists some way to write the data into the savscancontroller.log file and simultaneously into a file I create?

If not, does anyone have a suggestion how to implement a function or script to copy the log files before they get overwritten/deleted?

For example: when savscancontroller.log is renamed into savscancontroller.log.1 the .log.1 file gets copied into a different folder.

I already tried to implement something like this but have not yet succeded because I don't have an idea how to "recognize" the renaming without utilizing external software like WatchDirectory...

I welcome any suggestions and thank you for taking the time to read this post/problem

sincerely pretor989

:26955


This thread was automatically locked due to age.
Parents
  • Hi pretor989 here

    I just wanted to let anyone interested in this know that we simply implemented a custom task which checks the alteration date of the oldest log file and backs the information up once the date and time change. This task is started in regular intervals during the night and saves everything inside a document entitled with the corresponding date.

    This might be a crude solution but for now it works.

    Still if anybody were to find something concerning my earlier questions I would appreciate any insight or impulses.

    Sincerely pretor989

    :27083
Reply
  • Hi pretor989 here

    I just wanted to let anyone interested in this know that we simply implemented a custom task which checks the alteration date of the oldest log file and backs the information up once the date and time change. This task is started in regular intervals during the night and saves everything inside a document entitled with the corresponding date.

    This might be a crude solution but for now it works.

    Still if anybody were to find something concerning my earlier questions I would appreciate any insight or impulses.

    Sincerely pretor989

    :27083
Children
No Data