2011/3/11 Anton Maksimenkov :
>> If some process can catch COM port in a way that noone can use the
>> port and noone can kill that process - it is wrong situation.
I think this would be a little bit better:
--- /usr/origsrc/sys/kern/tty.c Mon Oct 11 22:20:15 2010
+++ /usr/src/sys/kern/tty.c
2011/3/11 Anton Maksimenkov :
> If some process can catch COM port in a way that noone can use the
> port and noone can kill that process - it is wrong situation.
And here is the quick path which solves the problem:
--- /usr/origsrc/sys/kern/tty.c Mon Oct 11 22:20:15 2010
+++ /usr/src/sys/kern/tt
2011/3/11 Amit Kulkarni :
> I tried to do a similar thing, Ctrl + C on a fsck, kill -9 the fsck
> pid. But the process is not able to be killed. Finally found out that
> I/O stuff can't be killed in OpenBSD. Since you do I/O to COM port,
> and try to kill it... I don't know if its a bug though.
An
I tried to do a similar thing, Ctrl + C on a fsck, kill -9 the fsck
pid. But the process is not able to be killed. Finally found out that
I/O stuff can't be killed in OpenBSD. Since you do I/O to COM port,
and try to kill it... I don't know if its a bug though.
hope that helps you
On Thu, Mar 10,
Hi.
It seems I catched some bug in kernel. I use some ugly program which
connects to COM-port and tries to do some activity.
You can see it's source here http://pastebin.com/kHLy26GD
I start it and try to kill it
# ./ct
writing bytes 36[ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 ff
