- make sure you have all the necessary software and a working mySetup.csh.
- If you start a new shell, source mySetup.csh to set up the paths and environment variables correctly.
Some of what follows is wrapped up in scripts like "start" but the principle that underlies such scripts goes like this:
- nothing much will work till you have an ipc partition called "initial" so start one with
- [localhost]$
- [localhost]$ ipc_server &
- [localhost]$
- thereafter "ipc_ls" will show you the contents of this partition, eg
- [localhost]$
- [localhost]$ ipc_ls
- initial
- [localhost]$
- still not much else will work till you create a "partition" called "SCT" within the one called "initial" that we just started. You can do this with:
- [localhost]$
- [localhost]$ ipc_server -p SCT &
- 3/6/04 18:16:47 :: ipc_server for partition "SCT" has been started.
- [localhost]$
- which you can check with:
- [localhost]$
- [localhost]$ ipc_ls
- initial
- partitions:
- SCT
- partitions:
- [localhost]$
- or
- [localhost]$
- [localhost]$ ipc_ls -p SCT
- SCT
- [localhost]$
- What uses the SCT partition we made above? One user is a "mrs_server":
- [localhost]$
- [localhost]$ mrs_server -p SCT &
- [localhost]$
- A mrs_server is a bit like a named pipe. Error messages from programs go there, but disappear unless you set up some listeners to report on the messages they hear arriving. Start a listener printing received messages to std::out with the following
- [localhost]$
- [localhost]$ mrs_receiver -p SCT
- messages appear here when they arrive ...
- Another important user (or should that be "group of users) of the SCT partition is the is_server. Start one which is capable of serving EventData, for example, as follows:
- [localhost]$
- [localhost]$ is_server -p SCT -n EventData &
- [localhost]$
- The FittingService requires that there be an is_server publishing event data. If you have already set one up, you can start the fitting service simply by
- [localhost]$
- [localhost]$ FittingService &
- [localhost]$