IFD log size value

[Bob Coleman]

For either "/logl:n" or "LogMaxSize=n", in what units is the value of "n".

Would "LogMaxSize=n" go in the "[Options]" section of IFD.INI?

[TeraByte Support(PP)]

For "/logl" (LogLevel) it's just a number. Normally, 1 through 10, though higher may be necessary for debugging information. For example, LogLevel=3.

For "LogMaxSize" you can use bytes, KiB, or MiB to specify the size. For example: LogMaxSize=32768 or LogMaxSize=32KiB. The program will convert the number to bytes when it updates it.

Both go in the [Options] section.

[Bob Coleman]

On the BIBM partition, I have an IFD.INI containing

[Options]
LogMaxSize=32768

The current size of IFD.LOG is 35,390 and it continues to grow.

[Bob Coleman]

I still don't understand how to successfully manage the size of IFD.LOG. LogMaxSize=n in IFD.INI doesn't seem to have any effect.

/logmax:n on the Image command where n is less than the current size of IFD.LOG causes IFD.LOG to be deleted.

[TeraByte Support(PP)]

You need to add LogMaxSize to the [Options] section of the bootitbm.ini file since you're using it with BIBM. Also, there appears to be a problem currently with the file being reduced. The temp file (reduced in size) remains instead of being renamed back to IFD.LOG.

[TeraByte Support]

under TBOS the rename currently can't have a path, but it does when it
renames the file so the temp file will still be out there instead.

"Bob Coleman" wrote in message news:[email protected]...

I still don't understand how to successfully manage the size of IFD.LOG.
LogMaxSize=n in IFD.INI doesn't seem to have any effect.

/logmax:n on the Image command where n is less than the current size of
IFD.LOG causes IFD.LOG to be deleted.

[Bob Coleman]

This seems to be working correctly in BIBM 1.19/IFD 2.82a.