[lcdproc] Multiple inputs and outputs and clients OH MY!
Wed, 19 Sep 2001 09:53:18 -0400
> --- email@example.com wrote ---
> > OK, question: Do you really (now be honoust) really want to couple
> > these displays to become one large display ? Or do you use the
> > displays all for different functions/programs, so they could better use
> > a separated server ?
> This one woke me up a bit. I hadn't even thought of this to keep things
> simple and easy to cope with.
> One display per server. Make server configurable enough that it can be run
> more than once without stepping on other instances of it.
Also, there IS a distinction between using only ONE display driver per
LCDd invocation and between using multiple displays in the DRIVER.
Thus, while the server no longer has to do a complicated round-robin
among all those differing drivers, et al, the driver if it likes can
drive multiple instances of the SAME device. I believe the Hitachi
driver does this already?
So there's nothing, in my opinion, which would keep a driver from doing
* Send data to multiple serial ports (actual physical devices)
* Send data to a network port (TCP connection to another remote device)
* Send data to a named pipe (to be recieved by an X client acting as a
display on screen)
In FACT - if the driver can do the first, then the others may even not
require any coding:
Instead of using a serial port, use a network pipe or a named pipe. The
network pipe could even be tunneled through SSH, and recieved on the
nc -l 17777 > /dev/lcd
...might even do it. Might even test it soon :)
Note through all of this that the assumption is that the device on the
other end is the SAME - which again Simplifies Coding dramatically.
> Then if a user wants to run multiple displays, he runs one instance of
> LCDproc per display. This means multiple config files (but that should be
> pretty easy to cope with ... --config=/etc/lcdproc/lcdd.bigdisp.conf).
To unsubscribe from this list send a blank message to