[Replying directly as well, as I believe my MTA is still blacklisted by the OpenBSD mail server. Guess we'll find out! -Adam]

On 2021-01-17 20:09, Tilo Stritzky wrote:
On 14/01/21 17:38  Andrew Grillet wrote:
Hi

I am running OpenBSD on a T2000 (Sparc64).
I was trying to use the serial port from the primary domain, connected via
ssh, and my network lost the connection.
My tty00 is now locked:
jay# stty -f /dev/tty00
stty: /dev/tty00: Device busy
I do not want to reboot the primary, as the guests are running various live
services. I cannot find evidence of a lock file in /dev/spool/lock.
Is there a way out of this predicament?

fstat(1) is your friend here.
Note that each tty has a corresponding cua device, they're both under the
same lock.

tilo

I ran into this exact problem last year.  It'll be in the list archives.
According to Theo (if I understood him correctly) it's partly due to the way BSD serial ports have always worked, i.e. in a rather under-specified manner. Apparently the core tty(4) code around this particular symptom hasn't really changed at all since OpenBSD forked.

My solution was to install Linux, sorry - I never did find a way around the problem on OpenBSD.

-Adam

Reply via email to