[dev.icinga.com #465] more logoutput of idoutils #233

Closed
icinga-migration opened this Issue May 27, 2010 · 6 comments

Projects

None yet

1 participant

@icinga-migration
Member

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

idoutils: add syslog output for start/stop, client connecting

fixes #465
@icinga-migration
Member

Updated by mfriedrich on 2010-06-14 10:43:49 +00:00

  • Target Version deleted 1.0.2
@icinga-migration
Member

Updated by mfriedrich on 2010-07-09 14:15:36 +00:00

  • Project changed from Core, Classic UI, IDOUtils to 18
  • Category deleted Event Broker
@icinga-migration
Member

Updated by mfriedrich on 2010-07-20 12:26:42 +00:00

  • Category set to 25
  • Target Version set to 1.0.3
  • Done % changed from 0 to 30

when idomod connects, syslog output is given. comes with the pgsql implementation in #622

@icinga-migration
Member

Updated by mfriedrich on 2010-07-28 20:11:20 +00:00

  • Tracker changed from Support to Feature
@icinga-migration
Member

Updated by mfriedrich on 2010-07-28 20:15:04 +00:00

  • Status changed from New to Resolved
  • Done % changed from 30 to 100

Applied in changeset commit:"7217f2868dc8037ea548e91f895459bd26f7bc53".

@icinga-migration
Member

Updated by mfriedrich on 2014-12-08 14:34:36 +00:00

  • Project changed from 18 to Core, Classic UI, IDOUtils
  • Category changed from 25 to IDOUtils
@icinga-migration icinga-migration added this to the 1.0.3 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment