Re: Time allowed for service shutdown
From: Martin Kochanski (nothing_at_nobody.net)
Date: 03/13/04
- Next message: Gary Chanson: "Re: Time allowed for service shutdown"
- Previous message: Gary Chanson: "Re: Time allowed for service shutdown"
- In reply to: Gary Chanson: "Re: Time allowed for service shutdown"
- Next in thread: Gary Chanson: "Re: Time allowed for service shutdown"
- Reply: Gary Chanson: "Re: Time allowed for service shutdown"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 13 Mar 2004 22:39:11 +0000
The more I think about this the more I agree.
Do developers in fact "fix their programs so that [data loss on
shutdown] can't happen"? Judging from the newsgroups, Exchange Server
isn't fixed (it sets a 10-minute timeout instead). Is Exchange Server
the exception, or do most programs behave that badly in practice?
[I'm not seeking an excuse not to do the work, I just want an excuse to
look extra smug when I've done it].
Gary Chanson wrote:
> It's possibly even worse then this. There have been reports that the
> SCM timeout is hardwired and raising WaitToKillServiceTimeout is
> ineffective.
>
> The proper way to deal with this is not to allow the situation to occur
> in the first place. The manager can't prevent the corruption and the
> developer should fix his program so that it can't happen.
>
> --
> -GJC [MS Windows SDK MVP]
> -Software Consultant (Embedded systems and Real Time Controls)
> - http://www.mvps.org/ArcaneIncantations/consulting.htm
> -gchanson@mvps.org
- Next message: Gary Chanson: "Re: Time allowed for service shutdown"
- Previous message: Gary Chanson: "Re: Time allowed for service shutdown"
- In reply to: Gary Chanson: "Re: Time allowed for service shutdown"
- Next in thread: Gary Chanson: "Re: Time allowed for service shutdown"
- Reply: Gary Chanson: "Re: Time allowed for service shutdown"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|