You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried the application and encountered a few hickups:
-I got some data at year 2555 ?!? which I thought should not occur has this is an issue that has been flagged and solved.
-The application suddenly crashed.
I wonder Is there a way to have logs when it is daemonized ?
I am not a programmer so I have no real clue. I suppose that it is in daemonize.c where stdout & stderr are redirected to /dev/null but I am not sure.
Br
The text was updated successfully, but these errors were encountered:
A check has been added in cm160.c at line 75 to discard invalid values that seems to be sometimes sent by the device (this check is maybe not complete... personally the app is running at my side for almost two years without a break and I've never had the problem, so it is difficult for me to validate the fix).
Indeed you can redirect the logs into file by replacing /dev/null by a log file path.
But If I were you I should first try to reproduce the problem in the console (start the app without -d)...
Hello,
I tried the application and encountered a few hickups:
-I got some data at year 2555 ?!? which I thought should not occur has this is an issue that has been flagged and solved.
-The application suddenly crashed.
I wonder Is there a way to have logs when it is daemonized ?
I am not a programmer so I have no real clue. I suppose that it is in daemonize.c where stdout & stderr are redirected to /dev/null but I am not sure.
Br
The text was updated successfully, but these errors were encountered: