One thought about “stop / suspend / resume” functionality is that you don't know exactly what the process is doing at the moment you suspe
roblem exists with resum
... it just freezes in its tracks, not necessarily at what you would consider to be an appropriate stopping po
So, I think, what you really want to do is to use some kind of a semaphore system, like a traffic light. Each process, during its usual work-cycle, periodically tests to see if the light is red. If so, it pauses, in an orderly fashion, perhaps indicating through another semaphore that it has now done so, and waits for the light to turn green. Ditto for indicating that the process should terminate itself. It will not do so “instantly,” but it will do so very quickly and in an orderly fashion. When pausing, it should do this by blocking on an appropriate (Perl ...) operating-system mutual exclusion object, so that it does not consume CPU time while waiting. There are many ways to implement this.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||