On Wed, Jun 15, 2016 at 7:22 AM, Martin Pieuchot <[email protected]> wrote: > On 11/06/16(Sat) 16:44, Marcus Glocker wrote: >> Currently one can open multiple instances of /dev/ttyU* since ucom(4) >> just checks 'TS_ISOPEN' against /dev/cuaU* access. There are quiet a >> lot of flags in ucom.c so it's a bit difficult to understand what the >> initial idea was. But moving the 'TS_ISOPEN' check before the UCOMCUA >> branch makes /dev/ttyU* access also return EBUSY if already opened. >> >> Ok? Or better ideas to fix this? > > No idea how this is supposed to work but com(4) contains the exact same > code, so if this is a bug it should probably fixed there too.
If I'm logged in on /dev/ttyU0, shouldn't I be able to open my tty, such as with "stty < /dev/ttyU0". Wouldn't this change break that? What's the problem with multiple opens of the incoming call device? Philip Guenther
