Modify the remote poller to make it friendlier to run multiple instances on the same machine
Description
From NMS-5067:
Also, another annoyance is that when running the remote poller it creates ~/.opennms and stores it's ID in a file there. I've looked at the source and tried to find where it gets that part from, but can't find it.
In previous versions, it used to accept Dpoller.home=${FOO}/etc/ and store it there. Ideally it should follow poller.configuration=${FOO}/etc/remote-poller${SITE}.properties.
This would help a lot when running multiple remote pollers from the same box.
I've looked in ./features/remote-poller/src/main/java/org/opennms/poller/remote, but can't figure out where the ".opennms" comes from.
There's one thing left in ./opennms-services/src/main/java/org/opennms/netmgt/poller/remote/support/DefaultPollerSettings.java that needs taking care of. m_configResource.getFile() still thinks the saved poller ID should go in .opennms/remote-poller.properties; this should be ableto be specified better, or mulitple pollers on the same machine won't work. Where does this setting come from?
Alexander Hoogerhuis May 12, 2012 at 5:21 PM
Make the remote poller take the log file argument from system properties, and not go off making up stuff unless left clueless by user.
From NMS-5067:
Also, another annoyance is that when running the remote poller it creates ~/.opennms and stores it's ID in a file there. I've looked at the source and tried to find where it gets that part from, but can't find it.
In previous versions, it used to accept Dpoller.home=${FOO}/etc/ and store it there. Ideally it should follow poller.configuration=${FOO}/etc/remote-poller${SITE}.properties.
This would help a lot when running multiple remote pollers from the same box.
I've looked in ./features/remote-poller/src/main/java/org/opennms/poller/remote, but can't figure out where the ".opennms" comes from.