We’re in the South. I think that’s be a no. ☺
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: [email protected] [mailto:[email protected]] On
Behalf Of Richard Stovall
Sent: Monday, February 1, 2016 12:37 PM
To: [email protected]
Subject: Re: [NTSysADM] Scheduled task weirdness
Is it a union task?
(Sorry...)
On Mon, Feb 1, 2016 at 12:26 PM, Melvin Backus
<[email protected]<mailto:[email protected]>> wrote:
Hi folks,
I’ve been debugging a process we run via scheduled task every night. Since it
deals with a variable size data set it runs for different periods every night
which is expected. However I discovered while I was reviewing logs that it
doesn’t always finish. It appears that a good portion of the time it’s getting
killed after 8 hours by the system. This has happened about a dozen times
since mid-December. The stop time is exactly 8 hours after the task started,
but the task is configured to run for up to 3 days before being stopped.
Any ideas on what might be going on or pointers on where to look for additional
info? My google results have shown a couple of similar questions but no
resolutions.
For now I’ve disabled the “Stop the task” portion so that it should run
indefinitely if needed.
Thanks
--------------------
Melvin Backus | Sr. Systems Engineer | Byers Engineering Company |
404.497.1565<tel:404.497.1565>
Service Desk | 404-497-1599<tel:404-497-1599> | http://servicedesk.byers.com
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
