Hey, Marc. Thanks so much for the bug report. Questions below: On Fri, 09 Apr 2010 17:26:31 +0200, Marc Haber <[email protected]> wrote: > when I have a session for /dev/ttyUSB0 defined, cereal won't let me > create a second one ('/dev/ttyUSB0' is already being monitored by > session 'other-session-name'). I can think of two trivial situations > where this may be desired:
This is not possible because two screen sessions can't be bound to the same tty device. This isn't a limitation of cereal, but of character tty devices like serial ports. They're just not designed to handle multiple inputs. > (1) > I am using the same port to connect to different hosts that need > different settings, for example a different baud rate I'm not sure I understand what you're describing here. You're physically disconnecting the serial port from one host, and then connecting it to another? So cereal was definitely not designed to support what you're describing, because of the real limitations of the tty devices mentioned above. Even if it could, using serial for what I think you're describing seems a little confusing to me. If you had two sessions, A and B, monitoring a single serial port that is being moved between multiple devices, say X and Y, then the logs of both A and B would show information from both X and Y. How would you expect to distinguish them? Maybe if you describe your situation a little more we can come up with a different solution that would work for your special circumstance. I have doubts whether cereal can be part of the solution, though. jamie.
pgpYqOhb5y2d0.pgp
Description: PGP signature
