Kenneth Ψstby wrote:
It seems like the correct way to go is to trap some sort of
keyboard/network/interrupt. How is the right way to trap those
?
AFAIK, the correct way to trap those things is to modify the Mach
kernel.
Now the next question, is there some documentation about the workings
Follow-up Comment #2, bug #18349 (project hurd):
It has been suggested already, and is certain now, that the problem actually
happens under high network load, probably if the network connection is more
or
less saturated: I can reproduce it pretty reliably by running gv with a very
large PS figure
Hello!
#v+
[EMAIL PROTECTED]:~ $ tail -n 0 -F /var/log/syslog &
[1] 8701
[EMAIL PROTECTED]:~ $ for n in `seq 0 20`; do logger TEST\ $n; sleep 1; done
Feb 12 22:40:12 leibniz thomas: TEST 0
Feb 12 22:40:14 leibniz thomas: TEST 2
Feb 12 22:40:16 leibniz thomas: TEST 4
Feb 12 22:40:19 leibniz thomas:
Hello!
On Sun, Feb 11, 2007 at 12:37:30PM -0800, Roland McGrath wrote:
> Before you start trying a subhurd, [...]
Roland, many thanks for the helpful hints! I'll make sure to get them
archived at a proper place in our documentation.
However, as I'm currently much more short on time than on com
