Hi, I have the same problem. Thanks to your research I got a little closer. But not quite there yet. First I would like to add you should keep your string in service keys simple. Something like "myservice http 1.1" won't work. Once I change it to 'myservice' I got a little closer.
2nd: there seems to be a bug open about this for already a while: http://dev.zenoss.com/trac/ticket/5040 3rd: for me it basically still doesn't work. for example i have a 2 tcp services defined. one on 10080 and one on 10009. I have various issues such as Zenoss thinking that's the amanda (ok, understandable, amanda is a common tool that uses these ports) but when I change the name and save, it always reverts to the old name. Sometimes the just added service just doesn't appear, and when I select the 10009 one in "add Ipservice" it shows me the menu for the 10080 one. And remodeling the device does not cause any autodetection. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=37121#37121 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
