why allocate a pseudo-terminal to each coprocess?

[garlick]

Problem: for whatever reason, powermand starts coprocesses using forkpty(3), but it's not clear why coprocesses would require a terminal. As there may be a fixed number of ptys available, let's not use them unless there is a good reason.

[garlick]

This might provide a hint as to the reason:

/* Create "pipe device" data struct.
 * cmdline would normally look something like "/usr/bin/conman -j -Q bay0 |&"
 * (Korn shell style "coprocess" syntax)
 */

Seems like the only reason to use conman there is if conman "owns" a terminal server that happens to have a port connected to a serial-connected power control device. A workaround could be to just have powerman connect to the host:port of the terminal server directly.

Trying this out, the tests all pass except the bashfun test, which is arguably just a stupid stunt.