limit size of log file

[mmoalem]

Hi there all - I am using this to log the progress of my running script: 

now my script runs 24.7 and I have no idea how to limit the size of the log file so it doesnt get out of hand - maybe periodically erase the first 100 lines or so... any ideas?

 

[alien4u]

If you are going to limit Size and not the amount of lines on the logfile you could check the logfile size and if is greater than your define max size then take the last 200 lines and delete your old logfile and create a new one with only the last 200 lines of the old one.

Something like this could give you some ideas:

#include <File.au3>
$iFileSize = FileGetSize(@ScriptDir&"\logfile.log")
$iMaxSize = 540708 ; ~528kb
If $iFileSize >= $iMaxSize Then
    $countLines = _FileCountLines(@ScriptDir&"\logfile.log")
EndIf
; Take for example last 200 lines
$startLine = $countLines - 200
For $i = $startLine To $countLines
    $lines = FileReadLine(@ScriptDir&"\logfile.log",$i)
Next

Regards
Alien.
 

[AutoBert]

Make each day a new logfile and delete older files than 1 week.

Edited April 19, 2016 by AutoBert

[mmoalem]

Thanks for the suggestions guys - I prefer the option of a new log file once a day.  The problem I have is that I cant delete the old log file as I get 'It is being used by another application' - any idea how do I 'release' it?

[InunoTaishou]

Probably need to close it in your script you're using.

Close it then copy the file to something like Logs.old with a date. I usually have all of my logs formatted as

Quote

[MM/DD/YYYY] [HH:MM:SS] Line of log data

[MM/DD/YYYY] [HH:MM:SS] Line of log data

[MM/DD/YYYY] [HH:MM:SS] Line of log data

[MM/DD/YYYY] [HH:MM:SS] Line of log data

So it's easy to fetch the first and last line, extract the data (even time if I wanted that for my file) and use that for the file name.

[alien4u]

Like @InunoTaishou said.
You need to Close the file, maybe you need to close the file each time you finish to write to it.
Then If your script is not writing to the file you are not going to get 'It is being used by another application'.

Regards
Alien.

[jchd]

11 minutes ago, InunoTaishou said:

[MM/DD/YYYY] [HH:MM:SS] Line of log data

Isn't that a terrible date format? YYYY-MM-DD is the only one that lets you easily grab entries between two given dates, for instance. Then display dates according to your locale (or favorite) format for human consumption.

[alien4u]

1 hour ago, jchd said:

Isn't that a terrible date format? YYYY-MM-DD is the only one that lets you easily grab entries between two given dates, for instance. Then display dates according to your locale (or favorite) format for human consumption.

Why YYYY-MM-DD is better than MM-DD-YYYY or better than DD-MM-YYYY I don't mean to make a dispute, i'm just curious to know and learn.

Regards
Alien.

[AutoBert]

5 minutes ago, alien4u said:

Why YYYY-MM-DD is better than MM-DD-YYYY or better than DD-MM-YYYY

It's easier for sorting by date.

[iamtheky]

10 minutes ago, alien4u said:

Why YYYY-MM-DD is better than MM-DD-YYYY or better than DD-MM-YYYY I don't mean to make a dispute, i'm just curious to know and learn.

YYYYMMDDhh:mm.ss

The same reason thousands,hundreds,tens,ones.tenthshundreths  is the best way to group your money

[alien4u]

1 hour ago, iamtheky said:

YYYYMMDDhh:mm.ss

The same reason thousands,hundreds,tens,ones.tenthshundreths  is the best way to group your money

Base on this then should be:
YYYYmmssDDhhMM (Years > mm = ss > DD>hh>>MM.

I think there is no better Date Format, otherwise there will be a unified one? don't you think so?

Regards
Alien.

Edited April 20, 2016 by alien4u
Wrong example before.

[AutoBert]

YYYY-MM-DD is good for normal sorting by year/month/day

DD-MM-YYYY is good when you like to sort by day,e.g. each 1. of month remember for paying bill for parking

MM-DD-YYYY is good for sorting for birthday dates e.g. who has this month birthday

But with all formats you can get a solution, but not necessary shortest/fasted  scriptcode

 

 

Edited April 20, 2016 by AutoBert

[iamtheky]

Sure, but if generic logging is the goal.  Setting ranges seems easier.  It's sure as hell better than everything being the number of seconds since jan. 1 1970.  Screw that format.

[alien4u]

@iamtheky I understand you and you are right with that.
@AutoBert you have a very good point here and good examples.

Regards
Alien.

[InunoTaishou]

The reason, are you really going to be looking at log files from 2014 in 2016?

The only time it might be relevant is around the new year. If they're grouped by 2016 then I'm going to have dozens of files all starting with the same 2016 and then have to go to month. If I start with month then I know exactly what month it's going to be in and I can narrow it down to the day I want. (And obviously don't start with day because then you could have 3 files starting with 01-MM-YYYY)

[BrewManNH]

11 hours ago, alien4u said:

I think there is no better Date Format, otherwise there will be a unified one? don't you think so?

There is a unified one, it's called ISO 8601 and is THE standard date format that's used internationally to represent how dates/times should be formatted.

[Skysnake]

Is there a standard Microsoft way to access this ISO8601 date on any Windows?

Is there an AutoIt macro that will always return ISO8601 dates?

Quote

ISO 8601 tackles this uncertainty by setting out an internationally agreed way to represent dates:

YYYY-MM-DD

For example, September 27, 2012 is represented as 2012-09-27.

I read somewhere once, someone mentioning "20120927" not looking much like a date... I save documents with this date format...