ALICE TRD fxsproxy README ========================= fxsproxy is a tool for the retrieval of all TRD FEE configuration information via DIM acknowledge channel, triggered by a DIM command including the run number. This command can be launched from everywhere, preferably from within the PVSS SOR script. In case of any problems, please contact: Frederick.Kramer@cern.ch REQUIREMENTS ------------ The Library libdim is necessary for this package, the dim headers and a dim_dns has to be running. INSTALLATION ------------ There are two possible ways for the installation: A: install from rpm B: install from source A) rpm -U fxsproxy-X.X-X.i386.rpm Files that are installed are: /usr/bin/fxsproxy_server the command line proxy /usr/bin/fxsproxy_testclient a client to send a command /usr/bin/fxsproxyd the daemon version of the server (not ready yet) /etc/rc.d/init.d/fxsproxyd the service script for the daemon /etc/trd/fxsproxy.conf the file including all config information of the proxy /etc/trd/fxsproxy_xml_displayer.xsl the style sheet for viewing the xml output in a browser B) The installation procedure from source makes use of the GNU quasi-standard autoreconfigure, which is creating a configure script which then provides the actual makefiles. The standard installation procedure comprises the following steps: 1. unpack & enter the package: tar zxfv fxsproxy.tar.gz cd fxsproxy 2. create the makefiles with the prefix / ./configure --prefix=/ 3. compile the code and test the output make 4. install the fxsproxy (you need to be root for this) (su) make install (exit) Like this, the files will be installed to the directories: /bin /etc/rc.d/init.d /etc/trd If you don't give the prefix, the above three directories will be preceeded by /usr/local INSTALLATION/DE-INSTALLATION OPTIONS ----------------------------------- A) rpm -e fxsproxy B) - remove the installed files make uninstall - erase what has been built make clean - additionally erase anything './configure' has created make distclean OPERATION --------- This package comes with 3 binary programs: 1. a command-line proxy: fxsproxy_server, which sends output to stdout. if you give the full path and name of a config file as single argument, this will be read, otherwise the standard location will be searched for. 2. a test-client: fxsproxy_testclient, which takes the run number as unique argument - use 1 for testing purposes 3. the daemon fxsproxyd, which contains the same functionalities like fxsproxy_server but runs as a background process, puts output to /var/log/messages and can be controlled in the normal fashoined way, e.g. "/sbin/service fxsproxyd [arg]" while arg can be one out of start/stop/status