On Sun, Jul 1, 2018 at 9:40 PM Andrew Udvare <audv...@gmail.com> wrote:
>
> YMMV on what processes will actually work properly after a SIGCONT. If
> anything a process does is not re-entrant, then you could have very
> unpredictable things happen including corruption of data.
>

If a process corrupts data of any significance after being stopped it
should be considered a bug.

Obviously if the process has sockets open there is a good chance that
timeouts/etc will happen, and the process needs to handle that.
However, the same is true if the network goes down/etc, or the system
is suspended, or even if the system just gets really highly loaded and
doesn't give the process much time.

As others have pointed out, once the process stops running it is going
to be a relatively high priority for swapping without having to try to
do anything else to force things, and it won't come back unless you
wake it up.

-- 
Rich

Reply via email to