man8/DOSEserv

Table of Contents

Name

DOSEserv - Dosimetry system message control center.

Synopsis

DOSEserv <argument list>

Description

DOSEserv is the message control center for the NEC AMS system. It performs a number of functions such as passing messages between DMANserv and the IO clients.

This program is part of the NEC AMS system.

This program runs as daemon unless overriden with the --no_daemon argument and should NOT be started in the background.

Arguments

Argument processing is done using Unix long argument syntax.

The values of all of the parameters listed here (whether or not they were supplied on the command line) are printed on stderr when the program starts.

--dbman_host <hn>

The host where dbman is running.

If this argument is not supplied the default is "localhost".

If present the DBMAN_HOST environment variable is used.

--bind_host <hn>

Host name to bind DOSEserv’s listener socket to.

If this is not specified then DOSEserv will bind to all interfaces on the host.

--mngr <hn>

The pathname to the CONFLIST type configuration file.

This defaults to "MNGRconf" if not supplied.

--mngr_pn <pn>

The program name to use when parsing the CONFLIST file.

This defaults to "DOSEserv" if not supplied.

--no_daemon

If this argument is present the program doesn’t become a daemon.
--show_tbl

If this argument is present the CONFLIST is printed to stderr after it is loaded.
--help

If this argument is present the program prints its internal help and exits.

CONFIG table group name usage

Configuration groups are mapped to entities in the DOSE protocol. Configuration functions are mapped to parameters within each entity. See "CONFIG table func usage" below.

The group mappings are:


CFG1 - le_cup1
CFG2 - le_cup2
CFG3 - le_cup3
CFG4 - le_cup4
CFG5 - le_cup5
CFG6 - le_cup6


CFG7 - he_cup1
CFG8 - he_cup2
CFG9 - he_cup3
CFG10 - he_cup4
CFG11 - he_cup5
CFG12 - he_cup6

CONFIG table func usage

read1

SRSscale - used with TRtask to set CR scaling
read2

SRSoffse - used with TRtask to set CR offset

Configuration file example


This shows mappings for two low energy cups and two high energy cups.

#
# Dosimetry Server definitions
#
# le cups
#
DOSEserv|g1|read1 |0|SRS 02-1|SRSscale|
DOSEserv|g2|read1 |0|SRS 02-2|SRSscale|
DOSEserv|g1|read2 |0|SRS 02-1|SRSoffse|
DOSEserv|g2|read2 |0|SRS 02-2|SRSoffse|
#
# he cups
#
DOSEserv|g7|read1 |0|SRS 04-1|SRSscale|
DOSEserv|g8|read1 |0|SRS 04-2|SRSscale|
DOSEserv|g7|read2 |0|SRS 04-1|SRSoffse|
DOSEserv|g8|read2 |0|SRS 04-2|SRSoffse|

Notes

The entire config group and function mappings for providing the scaling and offset could go away and be replaced with DevKeys which map the values for TRtask.

This is already the case with PPCItask. It subscribes directly to the parameters it needs to do its scaling.

The problem was that TRtask used the DATA interface and the foresight to add new DevKeys was lacking when this was designed so it was patched into the DOSE protocol.

The --bind_host argument probably isn’t all that useful anymore. It’s only capable of making the program bind to one interface. Linux iptables is probably the better way of shielding the listener socket from snoopers.

Manual Page Revision

$Id: DOSEserv.8,v 1.6 2008/06/03 18:43:42 kitchen Exp $

Table of Contents