Sun's JVM supports SNMP monitoring since 1.5, so it'd be great to be able to have the ebuilds pull down net-snmp and the MIB.
Created attachment 161897 [details, diff] Proposed ebuild patch Here is a patch for sun-jdk-1.6.0.07.ebuild. It would be great if it could be added to the 1.5 ebuilds, too.
(In reply to comment #1) > Created an attachment (id=161897) [edit] > Proposed ebuild patch > > Here is a patch for sun-jdk-1.6.0.07.ebuild. It would be great if it could be > added to the 1.5 ebuilds, too. > Do you have a link to the license of that file handy? Many times you aren't allowed to distribute Sun stuff.
(In reply to comment #1) > > Here is a patch for sun-jdk-1.6.0.07.ebuild. It would be great if it could be > added to the 1.5 ebuilds, too. > A patch like this can't be added to 1.5 ebuilds because it would cause a file collision. If we can use the same file for both then we can make a new package for this support that both 1.5 and 1.6 can depend upon.
I do not have the license handy. As for the MIB installation, I didn't think about collisions due to SLOT differences. Rather than create a new package for a single data file, do you think that it would be better to instead add a "java" USE flag to net-analyzer/net-snmp to install the MIB? After all, it installs all of the system MIBs currently. Of course, if we did it as a separate package, we could also include some other files or setup some sensible defaults, but that might be overkill. What do you think?
(In reply to comment #4) > > As for the MIB installation, I didn't think about collisions due to SLOT > differences. Rather than create a new package for a single data file, do you > think that it would be better to instead add a "java" USE flag to > net-analyzer/net-snmp to install the MIB? After all, it installs all of the > system MIBs currently. > Sounds good to me.
OK. I'm working on a new net-snmp ebuild at the moment. I'll attach once ready.
OK, I've added a bug for my new ebuild. I'd still like to see better integration here. Preferably, some way to easily configure the JVM's management support, as it needs to be done on a per-JVM basis. I would think that the preferred "default" configuration would be a simple "public/localhost" read-only community. Should I attach an example management.properties and snmp.acl file? Would you guys even be interested in adding such support to the JVM?
(In reply to comment #7) > > Should I attach an example management.properties and snmp.acl file? Would you > guys even be interested in adding such support to the JVM? > We can add but we don't use this stuff so as long as you can help if any problems come around then it should be fine.
I resolved this issue rather simply. I created an ebuild for the Sun MIB. As such, there isn't anything for the netmon team to do, so I am removing them and reassigning this to the Java team. The support files mentioned above would be added to the JVM's own directories, so it would be SLOT safe. I'm marking this for me to work. If the Java team isn't interested in adding this stuff, just let me know (or close this bug). Thanks
