Bug #426
dSS not working properly without debug log
| Status: | Closed | Start date: | 07/30/2010 | |
|---|---|---|---|---|
| Priority: | (P3) Normal | Due date: | ||
| Assignee: | Christoph Hofmann | % Done: | 0% |
|
| Category: | - | |||
| Target version: | 0.9.0-alpha5 | |||
| Severity: | Normal | Target: | ||
| Story points | - | |||
| Velocity based estimate | - |
Description
If the (current) debug log is disabled, the dSS does not work properly. Please check this.
History
Updated by Miguel Rodriguez over 1 year ago
- Status changed from New to Assigned
- Assignee set to Michael Troß
- Target version set to 0.9.0-alpha2
Please verify if moving to logrotate has solved this issue
Updated by Michael Troß over 1 year ago
- Status changed from Assigned to Feedback
- Assignee changed from Michael Troß to Sergey Bostandzhyan
Turns out to be an issue with the stdout/printf messages spread across some modules. When running daemonized all writes to stdout may block and especially the serial interface thread is effectively inactive.
The correct behaviour stdout/cout and daemon() has to be verified, or probably a safer implementation of daemonize should be used.
Updated by Miguel Rodriguez over 1 year ago
- Target version changed from 0.9.0-alpha2 to 0.9.0-alpha3
Updated by Miguel Rodriguez over 1 year ago
- Target version changed from 0.9.0-alpha3 to 0.9.0-alpha5
Updated by Sergey Bostandzhyan about 1 year ago
- Status changed from Feedback to Resolved
- Assignee changed from Sergey Bostandzhyan to Christoph Hofmann
The daemon call redirects redirects standard input, standard output and standard error to /dev/null, this does work.
Our problem was that we wanted log output, at the same time the system was too slow to write the output to disk. The ds485 thread was quite timing sensitive, so ds485 communication got distrupted by the log messages that were stalling execution.
This should not be the case anymore; excessive logging was removed after swithing to the ds485 libraries, all time-critical actions related to the ds485 bus take place in the library and not in the dSS now.
Updated by Christoph Hofmann 9 months ago
- Status changed from Resolved to Closed