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
Currently, dcrstmd dumps all stdout into one file that is named after the day the the daemon is started. As the daemon continues to run over days or even weeks, this makes it difficult to look through the logs (without the use of cat/grep/sed) when trying to troubleshoot matcher service issues.
I would like to see the dcrstmd log files created at the start of each day (assuming dcrstmd is running, of course).
The text was updated successfully, but these errors were encountered:
Right now you can send a SIGHUP to dcrstmd which will cause it to close existing connections (stopping any waiting or in-progress sessions), reload the config and restart the service (creating a new log file in the process).
Ideally the log should be sent to the OS's logging facility (journald, syslog, etc) instead of writing to a dedicated file (which should automatically take care of things like log rotation, etc).
Currently, dcrstmd dumps all stdout into one file that is named after the day the the daemon is started. As the daemon continues to run over days or even weeks, this makes it difficult to look through the logs (without the use of cat/grep/sed) when trying to troubleshoot matcher service issues.
I would like to see the dcrstmd log files created at the start of each day (assuming dcrstmd is running, of course).
The text was updated successfully, but these errors were encountered: