Re: help understanding cua/tty EBUSY behaviour?

2019-08-07 Thread Theo de Raadt
Adam Thompson wrote: > On 2019-08-03 18:14, Theo de Raadt wrote: > > Adam Thompson wrote: > > > >> Summary: I open cua0 with cu(1), quit cu(1), try to re-open with > >> cu(1) but now it immediately fails with EBUSY. *Usually* doesn't > >> happen with USB-to-serial (cuaU[0-9]) but have still

Re: help understanding cua/tty EBUSY behaviour?

2019-08-07 Thread Adam Thompson
On 2019-08-03 18:14, Theo de Raadt wrote: Adam Thompson wrote: Summary: I open cua0 with cu(1), quit cu(1), try to re-open with cu(1) but now it immediately fails with EBUSY. *Usually* doesn't happen with USB-to-serial (cuaU[0-9]) but have still seen it once or twice. [...] You are

Re: help understanding cua/tty EBUSY behaviour?

2019-08-03 Thread Theo de Raadt
Adam Thompson wrote: > Summary: I open cua0 with cu(1), quit cu(1), try to re-open with > cu(1) but now it immediately fails with EBUSY. *Usually* doesn't > happen with USB-to-serial (cuaU[0-9]) but have still seen it once or > twice. > > I've seen this behaviour on OpenBSD 6.4, OpenBSD 6.5,

help understanding cua/tty EBUSY behaviour?

2019-08-03 Thread Adam Thompson
Summary: I open cua0 with cu(1), quit cu(1), try to re-open with cu(1) but now it immediately fails with EBUSY. *Usually* doesn't happen with USB-to-serial (cuaU[0-9]) but have still seen it once or twice. I've seen this behaviour on OpenBSD 6.4, OpenBSD 6.5, and FreeBSD 11.2, and on 3