Skip to content
This repository was archived by the owner on Feb 8, 2021. It is now read-only.

check the result of killing a container #361

Merged
merged 1 commit into from
Aug 2, 2018

Conversation

gnawux
Copy link
Member

@gnawux gnawux commented Aug 2, 2018

The same as the #359 on maintenance_1 branch

the kill(2) may have some failure condition:

RETURN VALUE
       On success (at least one signal was sent), zero is returned.  On error, -1 is returned, and errno is set appropriately.

ERRORS
       EINVAL An invalid signal was specified.

       EPERM  The process does not have permission to send the signal to any of the target processes.

       ESRCH  The process or process group does not exist.  Note that an existing process might be a zombie, a process that has terminated execution, but has not yet been wait(2)ed for.

Signed-off-by: Wang Xu gnawux@gmail.com

the kill(2) may have some failure condition:

```
RETURN VALUE
       On success (at least one signal was sent), zero is returned.  On error, -1 is returned, and errno is set appropriately.

ERRORS
       EINVAL An invalid signal was specified.

       EPERM  The process does not have permission to send the signal to any of the target processes.

       ESRCH  The process or process group does not exist.  Note that an existing process might be a zombie, a process that has terminated execution, but has not yet been wait(2)ed for.
```

Signed-off-by: Wang Xu <gnawux@gmail.com>
@bergwolf
Copy link
Member

bergwolf commented Aug 2, 2018

lgtm

@bergwolf bergwolf merged commit f2af9a5 into hyperhq:master Aug 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants