Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

teleport.service lacks KillMode=process #8

Open
CFSworks opened this issue Jun 20, 2018 · 2 comments
Open

teleport.service lacks KillMode=process #8

CFSworks opened this issue Jun 20, 2018 · 2 comments
Labels

Comments

@CFSworks
Copy link
Contributor

The teleport.service systemd unit installed does not contain KillMode=process, causing systemd to default to killing the whole cgroup when stopping the Teleport service - this includes killing all processes started within Teleport sessions, such as screen/tmux instances.

@woohgit woohgit added the bug label Jun 27, 2018
@woohgit
Copy link
Owner

woohgit commented Jun 27, 2018

@CFSworks Sounds like an issue. Can you send a PR or shall I change it myself?

@iuri-gg
Copy link

iuri-gg commented Jul 23, 2018

@CFSworks @woohgit I just submitted PR #9
It adds support for reloading teleport daemon which forks a new process and lets old connections finish their work instead of killing those processes. Will that address this issue?

CFSworks added a commit to CFSworks/ansible-role-teleport that referenced this issue Sep 22, 2018
This leaves subprocesses created by Teleport sessions alone
when restarting teleport.service

Fixes woohgit#8
akuracy pushed a commit to s3pweb/ansible-role-teleport that referenced this issue Jun 7, 2021
This leaves subprocesses created by Teleport sessions alone
when restarting teleport.service

Fixes woohgit#8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants