From mboxrd@z Thu Jan 1 00:00:00 1970 From: tonyb@thekrnl.sysdev.org Subject: Re: Signaling dosemu application to kill itself from Linux Date: Thu, 7 Apr 2005 08:23:07 -0800 Message-ID: <20050407082307.66dec8e2.tonyb@sysdev.org> References: <4254ACBE.3070504@aknet.ru> <4254F84E.636A@sat.dundee.ac.uk> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4254F84E.636A@sat.dundee.ac.uk> Sender: linux-msdos-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii" To: linux-msdos@vger.kernel.org On Thu, 07 Apr 2005 10:07:26 +0100 Andrew Brooks wrote: > Stas Sergeev wrote: > > > > Gene Heskett wrote: > > > 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 / __|\\// __|| \ __ __ / tonyb@sysdev.org \__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities |___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers