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.
Assignee: Wolfgang
Status: Resolved (closed on 2011-05-18 19:15:44 +00:00)
Target Version: 1.5
Last Update: 2011-05-18 19:15:44 +00:00 (in Redmine)
Need a mention in the docs for a new option related to the tac header. Ricardo slipped in the added feature of showing pending states in the tac header while addressing the counts in Bug #1508 and I made it optional and off by default in a commit with some follow-up corrections.
I set it as off by default due to potential space issues for people with smaller screens (not to mention there are quite a few people who just don't especially need it).
The cgi.cfg entry itself is:
# SHOW PENDING IN TAC HEADER
# This options enables the display of pending counts in
# the tac header. If your display is less than 1024x768
# and this is enabled, the tactical information may not
# fit well in the top frame.
# By default it is disabled.
show_tac_header_pending=0
The text was updated successfully, but these errors were encountered:
This issue has been migrated from Redmine: https://dev.icinga.com/issues/1529
Created by mjbrooks on 2011-05-17 12:13:33 +00:00
Assignee: Wolfgang
Status: Resolved (closed on 2011-05-18 19:15:44 +00:00)
Target Version: 1.5
Last Update: 2011-05-18 19:15:44 +00:00 (in Redmine)
Need a mention in the docs for a new option related to the tac header. Ricardo slipped in the added feature of showing pending states in the tac header while addressing the counts in Bug #1508 and I made it optional and off by default in a commit with some follow-up corrections.
I set it as off by default due to potential space issues for people with smaller screens (not to mention there are quite a few people who just don't especially need it).
The cgi.cfg entry itself is:
The text was updated successfully, but these errors were encountered: