On Fri, Jun 23, 2023 at 01:48:53PM +0200, Ben Franksen wrote: > thanks for the heads-up; this is certainly an interesting project, but for > me to start playing with it only makes sense if and when it has matured to > the point where there is a minimum of documentation (-h/--help or something > like that) and ideally some sort of revision control, too. I may be (barely) > able to debug such low-level C code if I notice it misbehaving but to > reverse-engineer what it is supposed to do is beyond my abilities.
The source code pasted above are indeed of a preview nature; the more formal documentation will probably be written in the internal testing here. recordln works quite like recordio and the command line usage are identical; the former is just more line-oriented. The command line usage of iotrap and ipctee are printed when `-h' is given; below is a brief summary of them. iotrap works like the trap program from execline, but the signals currently cannot be customised. When iotrap receives a terminating signal, the spawned subprocess is sent an EOF; after this, if the subprocess does not exit before the timeout tunable by the `-t' option, the previous signal is forwarded. ipctee listens to a pair of input and output sockets, the first accepts at most 1 connection and the latter multiple connections. (The input socket is for the IOC; the output socket is for "procServ clients".) For each connected client, the bytes it writes are forwarded to all other clients connected at the time. (You may realise ipctee is essentially a "chatting server" for all connected clients, and it may seem that ipctee can be furtherly simplified by eliminating the input socket and treating all clients fully equal. However, for certain use cases, we may disallow writes from the output socket; this is why there is a `-r' option for the "readonly" mode, and why the program is called "ipctee" not "ipcchat".) -- My current OpenPGP key: RSA4096/0x227E8CAAB7AA186C (expires: 2024.09.30) 7077 7781 B859 5166 AE07 0286 227E 8CAA B7AA 186C