[dataloss bug] Log file truncated on disk

[fraserhess]

I'm not sure if this is new in 1.3 or because of a finishedTrigger in 1.3, but let me explain.

Reproducibly, I have an incomplete log file at /Library/Logs/Setup Manager.log. It's around 12Kb in size and stops in the middle of a log message. (I am happy to provide an example file privately.)

Perhaps relevant to 1.3, I am testing a finishedTrigger that installs Jamf Connect and restarts. It's possible that either the Jamf Connect install kills the loginwidow and Setup Manager processes is doing so before the log file is written to disk or the shutdown command is cancelling a deferred write.

[fraserhess]

12458 bytes seems to be the important limit.

Testing results:
1.3 beta with 1.3 configuration (finalAction: none; finishedTrigger): log truncated at 12458 bytes
1.3 beta with 1.2 configuration (finalAction: restart; no finishedTrigger): log is still truncated at 12458 bytes
1.2.2 with 1.2 configuration: log is 65652 bytes

[scriptingosx]

fixed in 1.3