On Qnx，Setting the parameter GzipCompression=on will cause problems with the dlt-logstorage-ctrl display configuration file

[hush-soul]

1.no problems storing uncompressed files 2.The same configuration file was successfully compressed in the Linux system

Looking forward to your reply, thank you

[minminlittleshrimp]

Hello @hush-soul I believe in my fix the value for parsing in ON. Kindly testing with the latest dlt version. Also, I wonder if it does not happen with ON_SPECIFIC_SIZE, we might look into the differences/mechanisms behind this sync behavior and the normal mode ON_MSG. A possible issue might come from the fsync phase. Regards

[minminlittleshrimp]

Besides, is this a duplicated one of https://github.com/COVESA/dlt-daemon/issues/644 ?

Update: Sorry didnt notice, this one for QNX. However we can combine them for easier syncing up

[hush-soul]

Hello @hush-soul I believe in my fix the value for parsing in ON. Kindly testing with the latest dlt version. Also, I wonder if it does not happen with ON_SPECIFIC_SIZE, we might look into the differences/mechanisms behind this sync behavior and the normal mode ON_MSG. A possible issue might come from the fsync phase. Regards

The same situation will occur with ON_SPECIFIC_SIZE and ON_MSG

I found some phenomena. It may be a problem with my zlib. It is still being debugged. Thanks for the reply.

[hush-soul]

Hello @hush-soul I believe in my fix the value for parsing in ON. Kindly testing with the latest dlt version. Also, I wonder if it does not happen with ON_SPECIFIC_SIZE, we might look into the differences/mechanisms behind this sync behavior and the normal mode ON_MSG. A possible issue might come from the fsync phase. Regards

I have solved this problem. It was my mistake. The qnx program code was not synchronized to the latest version. Thank you.

[hush-soul]

The new version does not have this problem

[minminlittleshrimp]

I see, thanks for the report. My pleasure to support you 😀