There's more than one way to do things | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
on Linux, SIGKILL (signal 9) cannot be trapped.... just because a process cannot trap and handle the signal, doesn't mean that the signal is 100% instant and reliable. Indeed. The Uninterruptible sleep state for example. you need to stop it for a while, kill -s STOP <process_number> is a pretty handy facility. Similarly, windows has suspend/resume which I frequently use to pause longing running, CPU intensive tasks when I want to do something else for a while, but don;t want to throw away the work already done. The only downside is that if you are benchmarking the process, the suspend will affect the timing if you use real-time clocks. Recently, I've moved to using clock-cycle counters for important benchmarking for this reason. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
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.
In reply to Re^4: ***Warning! The above post is wrong in almost every possible way***
by BrowserUk
|
|