How do I stop daemonized OpenVPN connection?
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
I started a VPN connection with sudo openvpn --daemon --config connection.ovpn
. Is there a way to terminate this connection without using ps
to search for the process and then kill
it myself?
command-line openvpn daemon
add a comment |Â
up vote
3
down vote
favorite
I started a VPN connection with sudo openvpn --daemon --config connection.ovpn
. Is there a way to terminate this connection without using ps
to search for the process and then kill
it myself?
command-line openvpn daemon
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I started a VPN connection with sudo openvpn --daemon --config connection.ovpn
. Is there a way to terminate this connection without using ps
to search for the process and then kill
it myself?
command-line openvpn daemon
I started a VPN connection with sudo openvpn --daemon --config connection.ovpn
. Is there a way to terminate this connection without using ps
to search for the process and then kill
it myself?
command-line openvpn daemon
asked Feb 17 at 4:35
d3vid
741427
741427
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
2
down vote
Since OpenVPN does not seem to offer any function of its own for this, you are probably looking for pkill <process-name>
, which will search for all processes matching the given name, and kill them.
If you got multiple instances running, but would like to kill only a specific one, the -f
option allows you to match against the full process-call including parameters, e.g. pkill -f "openvpn --config cpnnection.ovpn"
.
See the output from ps x
or pgrep -lf <process-name>
(same as pkill
, but doesn't kill them, so essentially similar to ps | grep <name>
) to find out with which parameters the daemon was started.
add a comment |Â
up vote
2
down vote
No, you will need to kill the process. In fairness a daemon management script would do just that. You can use pgrep or pkill to make your life easier.
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
Since OpenVPN does not seem to offer any function of its own for this, you are probably looking for pkill <process-name>
, which will search for all processes matching the given name, and kill them.
If you got multiple instances running, but would like to kill only a specific one, the -f
option allows you to match against the full process-call including parameters, e.g. pkill -f "openvpn --config cpnnection.ovpn"
.
See the output from ps x
or pgrep -lf <process-name>
(same as pkill
, but doesn't kill them, so essentially similar to ps | grep <name>
) to find out with which parameters the daemon was started.
add a comment |Â
up vote
2
down vote
Since OpenVPN does not seem to offer any function of its own for this, you are probably looking for pkill <process-name>
, which will search for all processes matching the given name, and kill them.
If you got multiple instances running, but would like to kill only a specific one, the -f
option allows you to match against the full process-call including parameters, e.g. pkill -f "openvpn --config cpnnection.ovpn"
.
See the output from ps x
or pgrep -lf <process-name>
(same as pkill
, but doesn't kill them, so essentially similar to ps | grep <name>
) to find out with which parameters the daemon was started.
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Since OpenVPN does not seem to offer any function of its own for this, you are probably looking for pkill <process-name>
, which will search for all processes matching the given name, and kill them.
If you got multiple instances running, but would like to kill only a specific one, the -f
option allows you to match against the full process-call including parameters, e.g. pkill -f "openvpn --config cpnnection.ovpn"
.
See the output from ps x
or pgrep -lf <process-name>
(same as pkill
, but doesn't kill them, so essentially similar to ps | grep <name>
) to find out with which parameters the daemon was started.
Since OpenVPN does not seem to offer any function of its own for this, you are probably looking for pkill <process-name>
, which will search for all processes matching the given name, and kill them.
If you got multiple instances running, but would like to kill only a specific one, the -f
option allows you to match against the full process-call including parameters, e.g. pkill -f "openvpn --config cpnnection.ovpn"
.
See the output from ps x
or pgrep -lf <process-name>
(same as pkill
, but doesn't kill them, so essentially similar to ps | grep <name>
) to find out with which parameters the daemon was started.
answered Feb 17 at 17:05
Folfy
1415
1415
add a comment |Â
add a comment |Â
up vote
2
down vote
No, you will need to kill the process. In fairness a daemon management script would do just that. You can use pgrep or pkill to make your life easier.
add a comment |Â
up vote
2
down vote
No, you will need to kill the process. In fairness a daemon management script would do just that. You can use pgrep or pkill to make your life easier.
add a comment |Â
up vote
2
down vote
up vote
2
down vote
No, you will need to kill the process. In fairness a daemon management script would do just that. You can use pgrep or pkill to make your life easier.
No, you will need to kill the process. In fairness a daemon management script would do just that. You can use pgrep or pkill to make your life easier.
answered Feb 19 at 13:53
Pedro
59429
59429
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f424719%2fhow-do-i-stop-daemonized-openvpn-connection%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password