Re: Signaling dosemu application to kill itself from Linux

[Stas Sergeev <stsp@aknet.ru>]

Hello.

tonyb@thekrnl.sysdev.org
> Negatory on that, no raw kbd or strange stuff,
> all vanilla...
Yes, your config looks pretty save.
Note: you don't need to uncomment
the options unless you are going to
change them.

Why are you using the direct access
to the serial ports? The emulated
access of the CVS dosemu is nearly
as fast as the real one.
I'd like you to revoke the root
privs from a dosemu process before
the further experementations, but
if you need an LPT too, then that's
a problem.

> Advantek i486 Cytrix tiny mobo.  I do have
> a serial port, can try logging on a getty
> there.
Yes, please do this and produce a
stack trace with gdb when dosemu is
hanging.
Alternatively, send a SIGSEGV to
dosemu when it is hanging, and it
will dump a stack trace into a log.

> just spinning.  There is an assembly language
> TSR that is running that I bet is holding
> the dosemu thread active or hung.
No DOS program should hold a dosemu
when it gets a SIGTERM, or it is a
bug. The stack trace can help.
Also, how exactly are you killing
it? SIGKILL can help too:)

> Is there a way (INT 1Ah?) to force dosemu to reset its time to
> Linux's, on request?
The mentioned patch was just reading
a linux time directly, so with the
$_timemode="linux" you don't need to
reset anything at all.
I am sure however your problem is not
related to RTC, it is a problem of the
PIT most likely. The patch won't help.
You'll have to dig a PIT code, which
is just a big mess :( It boils down to
the cputime.c at one point, but the
parts of it are all around the sources.
You'll certainly have fun tracking it.
One thing to try is $_rdtsc=on/off
(don't remember if I told you that
already)