in reply to control-C to "jumpstart" windows process

Here's hoping this bump will get some responses...

jimt, I have the exact same problem as you describe, using:
Windows XP SP2 [Version 5.1.2600]

perl, v5.8.8 built for MSWin32-x86-multi-thread with 25 registered pat
+ches
Binary build 817 [257965] provided by ActiveState http://www.ActiveSta
+te.com
Built Mar 20 2006 17:54:25

[download]
- the script starts to run, creating data.
- after some amount of time, the script pauses in execution. The process is still listed under the process tab, but its processor time counter is not increasing.
- 20 hours later, I hit control-c and get a printed status update on the console (from 7 hours after execution started) and the script starts creating data again.

The script is doing a lot of file I/O on local storage, but no DBI calls. My boss says he's had this happen with ActiveState before, too, in a script that was doing both a bunch of DBI work and file I/O.

Did you ever find a cause/solution to this problem? Any help would be appreciated in getting my actual processing time as close to my estimate of four days as possible. :)

Cheers!

---Chaos, fear and disorder. My work here is done.

Replies are listed 'Best First'.
Re^2: control-C to "jumpstart" windows process
by BrowserUk (Patriarch) on Aug 09, 2007 at 21:13 UTC

    Next time it happens, before you use ^C, check the titlebar of the console window and see if the first word there is either 'Mark' or 'Select'. If it is, hit the Esc key and that word should disappear and the process continue.

    If that works, learn (or instruct whomever is doing it), to be more careful when switching to the command session window using the mouse.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom