breun wrote, On 12/2/2008 10:18 AM: > jmp242 wrote: >> You never want to bind ethernetCsmacd to a class... That will break things. > > > Yeah, I found out the hard way. If it breaks things, then why can you do it? > Should I report this as a bug? > > Hmmm - I'd guess because they are managed like templates. This might be a UI bug, so I suppose you can go ahead and submit it. >> Generally, the Template bindings are inherited, so you won't need to >> bind IPService etc below /Devices ... > > > If I don't bind the Device template to /Devices/Server/Linux, then the > devices in that class don't have any performance graphs, even though the > Device template is bound to /Devices. So apparently they are not inherited. > Or am I missing something? > Hmm, they may be inherited when you create a new subclass, but don't travel down old subclasses... > >> I'd use the default bindings and play around with a subclass you can >> delete if it all goes pear-shaped... > > > The problem was that I already messed up the default bindings and didn't know > what they were. Resetting the bindings apparently just clears all bindings, > instead of resetting them to the defaults. > > Could you tell me what the default bindings for /Devices, /Devices/Server and > /Devices/Server/Linux are? > On 2.2.4, all have Device bound.
Seems to work for me... _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
