Just wanted to pass along something that threw me for a quick loop in hopes it
might save someone else time. I needed to disable the snmpXdmid service on a
recent S10u4 build. This is accomplished using:
# svcadm disable dmi
However After running the command, the security scanner still detected the
service as being active. The test is looking for a response form RPC program #
100249.
A bit of research told me that until the system either reboots or the
portmapper (rpc/bind) is tickled, the snmpXdmid service remains registered. I
did a quick scan of the svc method (/lib/svc/method/svc-dmi) and modified the
stop code block slightly to fix it. The line looks like this before
modification:
/usr/bin/pkill -9 -x -u 0 -z ${_INIT_ZONENAME:=`/sbin/zonename`}
'(snmpXdmid|dmispd)'
By modifying it as follows I was able to correct the problem with snmpXdmid:
/usr/bin/pkill -9 -x -u 0 -z ${_INIT_ZONENAME:=`/sbin/zonename`} \
'(snmpXdmid|dmispd)' && /usr/bin/rpcinfo -d 100249 1
At first glance it seems this may be a bug in the method, although I'm sure its
far from a priority. I dug through SunSolve and more Google hits than I care
to recall and didn't find anything indicating this was a known issue, so
hopefully this will get indexed and save someone some time...
This message posted from opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
[email protected]
