Changes between Initial Version and Version 10 of Ticket #93


Ignore:
Timestamp:
12/18/12 17:25:45 (11 years ago)
Author:
jbs@bbn.com
Comment:

I re-ran EG-MON-1 Step 1 just now, with results at ​http://groups.geni.net/geni/wiki/GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-MON-1#ResultsofStep1from2012-12-18. Search down for "here are the files that aren't from an RPM" and you'll find a list of files that aren't part of RPMs.

I can't easily tell from Luisa's recent update whether she thinks that a site admin could easily tell where each of those files came from. I couldn't at a glance, although it's possible I could track them down with more research.

Luisa, what do you think? Is the existing documentation adequate here, or is more needed?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #93 – Description

    initial v10  
    1 I'm working on EG-MON-1 (http://groups.geni.net/geni/wiki/GENIRacksHome/AcceptanceTests/ExogeniAcceptandceTestsPlan#EG-MON-1:ControlNetworkSoftwareandVLANInspectionTest), and identified six directories that contain software that appears to be listening on the public control network, which don't come from RPMs:
    2  
    3  * /opt/floodlight
    4  * /opt/imageproxy
    5  * /opt/orca-11080
    6  * /opt/orca-12080
    7  * /opt/orca-13080
    8  * /opt/orca-aux
    9  
    10 There's also /omd/sites/rack_bbn/var/tmp/xinetd, which appears to be a copy of /usr/sbin/xinetd.
     1I'm working on EG-MON-1 Step 1 (http://groups.geni.net/geni/wiki/GENIRacksHome/AcceptanceTests/ExogeniAcceptandceTestsPlan#EG-MON-1:ControlNetworkSoftwareandVLANInspectionTest), and identified various files that are part of programs that are listening on the network, but aren't part of RPM packages. How would a site admin find out where those files came from, e.g. if they wanted to review the code?