Michael Friedrich b960850ce3 DB IDO: Only update 'next_check' column when manually scheduling a check ... Otherwise the changes from #7287 already take care of setting the proper next check time from inside ProcessCheckResult(). There is no need to use the generic OnNextCheckChanged signal but instead we're using a new one, locally just for DB IDO. fixes #11019		2016-01-22 18:42:15 +01:00
..
base	Support TLSv1.1 and TLSv1.2 for the cluster transport encryption	2016-01-20 16:48:00 +01:00
checker	Update copyright headers for 2016	2016-01-12 08:29:59 +01:00
cli	Fix: Escaped sequences not properly generated with 'node update-config'	2016-01-21 18:14:53 +01:00
compat	Properly set the next check time for active and passive checks	2016-01-22 18:40:14 +01:00
config	Update copyright headers for 2016	2016-01-12 08:29:59 +01:00
db_ido	DB IDO: Only update 'next_check' column when manually scheduling a check	2016-01-22 18:42:15 +01:00
db_ido_mysql	Update copyright headers for 2016	2016-01-12 08:29:59 +01:00
db_ido_pgsql	Update copyright headers for 2016	2016-01-12 08:29:59 +01:00
demo	Update copyright headers for 2016	2016-01-12 08:29:59 +01:00
hello	Update copyright headers for 2016	2016-01-12 08:29:59 +01:00
icinga	DB IDO: Only update 'next_check' column when manually scheduling a check	2016-01-22 18:42:15 +01:00
livestatus	Update copyright headers for 2016	2016-01-12 08:29:59 +01:00
methods	Update copyright headers for 2016	2016-01-12 08:29:59 +01:00
notification	Update copyright headers for 2016	2016-01-12 08:29:59 +01:00
perfdata	Update copyright headers for 2016	2016-01-12 08:29:59 +01:00
remote	Remove redundant log messages	2016-01-21 13:02:53 +01:00
CMakeLists.txt	Update copyright headers for 2016	2016-01-12 08:29:59 +01:00