Something is wrong with the stop_child stuff

[davidw]

I'm not sure entirely what yet, but there is something wrong with the stop_child code.

I've been doing some debugging, and get very strange result for the time difference. I think it has something to do with this:

    uint32_t sec()      const   { return m_tv.tv_sec;  }

By returning it unsigned, it's causing problems, because in reality the difference is a negative number.

[davidw]

Another data point:

Something is calling kill(-1, SIGKILL), which has the rather unpleasant side effect of terminating everything - desktop, editors, erlang, window manager, ssh... all of it.

This looks like it might be the culprit:

        kill(ci.kill_cmd_pid, SIGKILL);

[saleyn]

I am currently on vacation. Will try to take a look at it after Jun 20th or so.

[davidw]

We need to fix it, so hopefully I'll be able to send a pull request soon.

[davidw]

I think I have identified and fixed a few of the problems:

#12

Some tests would be really good to have, though.