Thomas Aeby

Ah, yes, had a look at your bb-display.cfg sample. Something like %table ALL within a view will display a table with all hosts, thus all hosts make part of this view. It's essential to only use groups containing no more than what you want to display in the respective view. Best regards, Tom

Thanks a lot, great job! Regarding the objects to be seen within a view: yes, sure, the point of a view is, that only the referenced objects are accessible within the view. Most probably I misunderstood your comment. Of course, you have to avoid referencing objects that you do not want to be visible, such as the famous "ALL" group, for instance. Best regards, Tom

I am afraid that Frameset always makes use of the "global" skin so currently it is impossible to have multiple Framesets each with distinct skin. As a workaround you should be able to remove the two buttons in question globally. In order to fix this, one would need to alter DisplayCFG::read_file() ("Frameset" section, store skin like it is done in the "Page" section) and Display::create_frameset(). Unless I am missing an important point, this should be a rather simple&straight forward modification....

Thank you very much for your good explanation! Most admins install the BigSister server on a Unixoid, so the option to install it on a Windows server has been quite neglected. Thus, your efforts are really appreciated!

procs shows incorrect count

With Perl v5.14.2, use of qw(...) as parentheses is deprecated in bs_evgen.pm and DisplayCFG.pm

Node Director 4.6.6

BigSister 1.12 released