On Wed, Aug 06, 2008 at 07:09:04PM +0000, webpass wrote:
Yeah, I'd like an explanation about this... I don't want to use
autodiscover, ever! Or else I'd end up with thousands of workstations
and crap I don't need to monitor. > >My workaround for now is that
I choose "Discovery Protocol: None" and then manually model the
device. > >The changelog for 2.2.3 mentions the following: > >3255
Use zendisc for adding devices > (http://dev.zenoss.org/trac/ticket/3255)
>3305 Zendisc add device needs to be refactored
(http://dev.zenoss.org/trac/ticket/3305) > >But I can't find an
explanation anywhere...
Since zendisc is not started as a daemon by the ~/bin/zenoss script, the only
danger of this is if we were to manually initiate an unrestricted autodiscover,
as far as I can tell. Right? From either the web interface or command shell.
In fact I just surprised myself to notice that I had *not* set
zAutoDiscover to False at the network root on my systems.
--
*Not speaking on behalf of my employer unless otherwise noted*
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
