Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!odi!benson
From: benson@odi.com (Benson I. Margulies)
Newsgroups: comp.unix.aix
Subject: Re: SRC
Message-ID: <1991Feb10.041824.19763@odi.com>
Date: 10 Feb 91 04:18:24 GMT
References: <1991Feb4.135641.12894@odi.com> <5181@awdprime.UUCP>
Reply-To: benson@odi.com (Benson I. Margulies)
Organization: Object Design Inc., Burlington, MA
Lines: 35

In article <5181@awdprime.UUCP> jerry@heyman.austin.ibm.com (Jerry Heyman) writes:
>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.     
>

As should the facts about message queues, like the need to set
a special #define for spc.h. Also, just what values turn up
in param1 and param2 for what requests. Also, what of the
myriad SRC error codes should be returned for common cases like
" I don't support TRACE".

Thanks, though, for the help.
-- 
Benson I. Margulies