Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!rice!sun-spots-request
From: sxm@philabs.philips.com (Sandeep Mehta)
Newsgroups: comp.sys.sun
Subject: passing signal numbers via rexecd
Keywords: Miscellaneous
Message-ID: <5028@brazos.Rice.edu>
Date: 15 Feb 90 22:03:45 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 23
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 9, Issue 45, message 6

According to the documentation on rexec(), when a non-zero value is used
as the (last) argument then an auxiliary channel (simply, a socket
descriptor) is set up between the master and the control process of the
slave. the control process is supposed to accept signal numbers (as bytes
written to it) which are passed onto the process group of the command
invoked by in.rexecd.

I can get rexec to behave as described in all the other aspects (i.e., I/O
using the default and auxiliary channels (sockets)) except using signals
to control it via the aux channel. the only other option is to use OOB
data (which according to TFM, *may* work).

the synopsis of rexec is as follows:
	sd = rexec (char **host, u_short port, char *user, char *passwd,
		char *cmd, int *fd2p)
	sd is the SOCK_STREAM channel
	fd2p is the auxiliary channel.
	port is (getservbyname("exec","tcp"))->s_port

Has anyone gotten this feature of rexec working. any clues or code frags
welcome.

sxm@philabs.philips.com                             ...to be or not to bop ?