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
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
Created by mfriedrich on 2010-05-27 18:10:14 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2010-07-28 20:15:04 +00:00)
Target Version: 1.0.3
Last Update: 2014-12-08 14:34:36 +00:00 (in Redmine)
usecase1: if ido2db closes itsself (the child) and sighandler is called, there should be an output to the syslog at least. right now, idomod writes a lot, but nobody can see what ido2db is really doing.
this should not be all and everything, just useful information in case.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/465
Created by mfriedrich on 2010-05-27 18:10:14 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2010-07-28 20:15:04 +00:00)
Target Version: 1.0.3
Last Update: 2014-12-08 14:34:36 +00:00 (in Redmine)
usecase1: if ido2db closes itsself (the child) and sighandler is called, there should be an output to the syslog at least. right now, idomod writes a lot, but nobody can see what ido2db is really doing.
this should not be all and everything, just useful information in case.
Changesets
2010-07-28 20:11:46 +00:00 by mfriedrich 7217f28
The text was updated successfully, but these errors were encountered: