24 Feb
2016
24 Feb
'16
3:01 p.m.
Hi,
I am using syslog from uclibc-ng (1.0.5) on an ARM board. I am working in a multi thread
environment.
I can see that some message are never saved in my syslog file..
Any problem to use syslog with thread ? or emmc ?
In some piece of my current code, I can loose almost 70% of the messages. By adding a
dirty call : system ("/bin/sync");
No more lost message in syslog.
Is it a normal behavior ? Do I have a problem in my flash driver ? Is it a bug wyth syslog
?
Thanks,
Arthur.
24 Feb
24 Feb
9:25 p.m.
Hi Arthur,
Arthur LAMBERT wrote,
Hi,
I am using syslog from uclibc-ng (1.0.5) on an ARM board. I am working in a multi thread
environment.
I can see that some message are never saved in my syslog file..
Can you retry with 1.0.12? It should be simple to update just the
version and add any patches from current git just for the uClibc-ng
package in buildroot.
I remember some updates regarding lost messages...
What syslog server are you using?
Any problem to use syslog with thread ? or emmc ?
In some piece of my current code, I can loose almost 70% of the messages. By adding a
dirty call : system ("/bin/sync");
No more lost message in syslog.
Is it a normal behavior ? Do I have a problem in my flash driver ? Is it a bug wyth
syslog ?
Could you provide a complete sample application which reproduces the
failure with 1.0.12?
best regards
Waldemar
25 Feb
25 Feb
11:22 a.m.
Can you retry with 1.0.12? It should be simple to
update just the
version and add any patches from current git just for the uClibc-ng
package in buildroot.
I remember some updates regarding lost messages...
I run a new test with the 1.0.12 version. It seems to fix the problem.
Last stable version of buildroot seems to use 1.0.9. I will retry with
this version.
Is it easy to find the bug which involves syslog between 1.0.5 & 1.0.12 ?
I guess that I can use git log on syslog dictectory to find all fixes.
Because the best solution for me to validate the fix will be to backport the
fix on 1.0.5 version and make a new test.
What syslog server are you using?
syslogd from busybox
Could you provide a complete sample application which
reproduces the
failure with 1.0.12?
Unfortunately I cannot share the code :(.
Arthur.
26 Feb
26 Feb
5:23 a.m.
Hi Arthur,
Arthur LAMBERT wrote,
Try these two commits:
eaedbdaa0877ec6d0501b8c19ad5175c80764c67
64917add7f4aeec8720d2fba5e96ea39aac35623
I mean a complete test case showing the failure.
But if 1.0.12 fixes these, I am fine with it.
best regards
Waldemar
Can you retry
with 1.0.12? It should be simple to update just the
version and add any patches from current git just for the uClibc-ng
package in buildroot.
I remember some updates regarding lost messages...
I run a new test with the 1.0.12 version. It seems to fix the problem.
Last stable version of buildroot seems to use 1.0.9. I will retry with
this version.
Is it easy to find the bug which involves syslog between 1.0.5 & 1.0.12 ?
I guess that I can use git log on syslog dictectory to find all fixes.
Because the best solution for me to validate the fix will be to backport the
fix on 1.0.5 version and make a new test.
What syslog server are you using?
syslogd from busybox
Could you provide a complete sample application
which reproduces the
failure with 1.0.12?
Unfortunately I cannot share the code :(.
3192
days inactive
3194
days old
3 comments
2 participants
participants (2)
-
Arthur LAMBERT -
Waldemar Brodkorb