Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!clyde.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!att!emory!swrinde!cs.utexas.edu!romp!auschs!awdprime!heyman.austin.ibm.com!jerry
From: jerry@heyman.austin.ibm.com (Jerry Heyman)
Newsgroups: comp.unix.aix
Subject: Re: SRC
Message-ID: <5181@awdprime.UUCP>
Date: 7 Feb 91 19:11:39 GMT
References: <1991Feb4.135641.12894@odi.com>
Sender: news@awdprime.UUCP
Organization: IBM Austin, TX
Lines: 30
Originator: jerry@heyman.austin.ibm.com

In article <1991Feb4.135641.12894@odi.com> benson@odi.com (Benson I. Margulies) writes:
>I need to define a new src subsystem. The documentation seems to omit
>one critical fact -- what command line arguments does the thing get
>when its started? The definition specifies that an SRC subsystem can
>work with sockets, message queues, or signals, and it gives routines
>for receiving and replying to messages, but no idea of how the
>actually server discovers the socket file descriptor.
>
>Anyone out there know the secret?
>
>-- 
>Benson I. Margulies

When the subsystem is started file descriptor zero is the socket that
the subsystem will use to communicate with SRC.

There are two places that command line arguments can be defined for the
subsystem. using mkssys with the -a option, will allways place this
information as a command line argument for the subsysem. Using startsrc with
the -a option will place this information as a command line argument for
this invocation of the subsystem.

This information should be in the SRC overview section in info.     

jerry
-- 
Jerry Heyman                     IBM T-R: jerry@heyman.austin.ibm.com
AWD Tools Development            VNET   : HEYMAN at AUSVMQ
AWD Austin                       T/L    : 793-3962
*** All opinions expressed are exactly that - my opinions and NOT IBM's