Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
hush-soul opened this issue Jun 26, 2024 · 6 comments
Assignees
Labels

Comments

@hush-soul
Copy link

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

1
2

Looking forward to your reply, thank you

@minminlittleshrimp
Copy link
Collaborator

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
Copy link
Collaborator

minminlittleshrimp commented Jun 26, 2024

Besides, is this a duplicated one of #644 ?

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

@hush-soul
Copy link
Author

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
Copy link
Author

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
Copy link
Author

The new version does not have this problem

@minminlittleshrimp
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants