plan9fox/rc/bin/service/tcp17019

#!/bin/rc
netdir=$3
remote=$2!`{cat $3/remote}
fn server {
	echo -n $netdir $remote >/proc/$pid/args
	rm -f /env/'fn#server'
	. <{n=`{read} && ! ~ $#n 0 && read -c $n} >[2=1]
}
exec tlssrv -a /bin/rc -c server
adding experimental rcpu service this is a reimplementation of cpu and import utilities in rc using a tlsclient and tlssrv as the encryption and authentication layers. there is only one new service, which after authentication and encryption setup accepts an arbitrary rc script over the network and executes it with the standard filedescriptors redirected to the conversaion (this is after authentication and in the context of the authorized user). the new rcpu program has a few improvements over cpu(1): - doesnt mangle program arguments - the remote process will get the clients standard file descriptors, so error and output are separated and you can consume the clients input from the remote side :-) - forwards error status of remote process theres no backwards mode for rimport, but a new program called rexport for the same purpose. all these services use exportfs without the bolted on initial handshake, so the hope is to clean up exportfs in the future and remove all the ugly crap in there. 2016-02-14 04:18:33 +00:00			`#!/bin/rc`
			`netdir=$3`
			remote=$2!`{cat $3/remote}
			`fn server {`
			`echo -n $netdir $remote >/proc/$pid/args`
rcpu: make sure not to leak /env/fn#server and /env/fn#aanserver for drawterm (thanks mischief) 2016-04-19 22:41:03 +00:00			`rm -f /env/'fn#server'`
adding experimental rcpu service this is a reimplementation of cpu and import utilities in rc using a tlsclient and tlssrv as the encryption and authentication layers. there is only one new service, which after authentication and encryption setup accepts an arbitrary rc script over the network and executes it with the standard filedescriptors redirected to the conversaion (this is after authentication and in the context of the authorized user). the new rcpu program has a few improvements over cpu(1): - doesnt mangle program arguments - the remote process will get the clients standard file descriptors, so error and output are separated and you can consume the clients input from the remote side :-) - forwards error status of remote process theres no backwards mode for rimport, but a new program called rexport for the same purpose. all these services use exportfs without the bolted on initial handshake, so the hope is to clean up exportfs in the future and remove all the ugly crap in there. 2016-02-14 04:18:33 +00:00			. <{n=`{read} && ! ~ $#n 0 && read -c $n} >[2=1]
			`}`
			`exec tlssrv -a /bin/rc -c server`