Skip to contentSkip to conversation

Signaling dosemu application to kill itself from Linux

DISCUSSION Stas Sergeev 4 participants 6 messages Apr 7, 2005

lore
Share & tools
lore
#1 lore raw
Quoted 6 lines · Stas Sergeev
Quoted 1 line · Gene Heskett

Mmm, what is this time patch, and where can it be obtained?

But I won't count too much on it, as the guys who submitted it, disappeared.

Not disappeared at all, still lurking. But our patch was broken up when applied to CVS and we haven't found the time yet to work out which bits were applied, which changed and which left out :-(

Actually I've got a patch for the patch; you should change ds70 = tm->tm_yday + (year-1970)*365L + (year-1970)/4; to
ds70 = tm->tm_yday + (year-1970)*365L + (year-1969)/4;

Andrew

#2 lore raw
Quoted 10 lines · On Thu, 07 Apr 2005 10:07:26 +0100 Andrew Brooks <[email protected]> wrote:
Quoted 6 lines · Stas Sergeev
Quoted 1 line · Gene Heskett

Mmm, what is this time patch, and where can it be obtained?

But I won't count too much on it, as the guys who submitted it, disappeared.

Not disappeared at all, still lurking. But our patch was broken up when applied to CVS and we haven't found the time yet to work

We applied your patch in the hope it would fix a date/time corruption that happens after about 3wks of uptime. But it didn't. That is why we are trying to force a weekly restart of dosemu, by killing it from crond. So that it syncs with the Linux clock again.

Is there a way (INT 1Ah?) to force dosemu to reset its time to Linux's, on request? Looking at the dosemu code, it only does that once, at dosemu start...

TonyB

--
__ __ _ I N C. http://www.sysdev.org

/ __|\\// __||  \  __   __          /         [email protected]
\__ \ \/\__ \||)|/ O_)\/ /        \/  System Tools / Utilities
|___/ || ___/|_ /\___|\_/        WIntel / Linux Device Drivers
#3 lore raw
Quoted 18 lines · On Thursday 07 April 2005 12:23, [email protected] wrote:

On Thu, 07 Apr 2005 10:07:26 +0100

Quoted 9 lines · Andrew Brooks
Quoted 5 lines · Stas Sergeev
Quoted 1 line · Gene Heskett

Mmm, what is this time patch, and where can it be obtained?

But I won't count too much on it, as the guys who submitted it, disappeared.

Not disappeared at all, still lurking. But our patch was broken up when applied to CVS and we haven't found the time yet to work

We applied your patch in the hope it would fix a date/time corruption that happens after about 3wks of uptime. But it didn't. That is why we are trying to force a weekly restart of dosemu, by killing it from crond. So that it syncs with the Linux clock again.

Quoted 5 lines

Is there a way (INT 1Ah?) to force dosemu to reset its time to Linux's, on request? Looking at the dosemu code, it only does that once, at dosemu start...

TonyB

Oh oh, this can and will be a problem where the scaling app is used as I doubt the boxes will be shut down at night. So I'm watching this thread carefully for the difinitive answer.

Signature · 8 lines
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.34% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
#4 lore raw
In reply to Stas Sergeev
Quoted 10 lines · Stas Sergeev

Hello.

Quoted 1 line · Gene Heskett

Mmm, what is this time patch, and where can it be obtained?

Here:
http://sourceforge.net/tracker/index.php?func=detail&aid=1034800&gro
up_id=49784&atid=457449 But I won't count too much on it, as the guys who submitted it,
disappeared.

Hummm, scratching thinning hair here.

Then maybe the better question is: what bug does it address so that we may ascertain if we need it or not? And, is it against 1.3.1?

Signature · 8 lines
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.34% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
#5 lore raw
Quoted 3 lines · Gene Heskett

Then maybe the better question is: what bug does it address so that we may ascertain if we need it or not? And, is it against 1.3.1?

The patch was originally against 1.2.0 or 1.2.1 (I forget which). It was not to fix a "bug" as such, rather that DOS time drifts in respect to Linux/real time so the patch simply reads Linux time when a program asks for DOS time. The web page describes the gory details:
http://sourceforge.net/tracker/index.php?func=detail&aid=1034800&group_id=49784&atid=457449

Quoted 2 lines · [email protected] wrote:

We applied your patch in the hope it would fix a date/time corruption that happens after about 3wks of uptime.

We never found a "corruption", just a slow drift. To me "corruption" means badly/randomly wrong and that would suggest a different cause.

Andrew