Replies: 1 comment
-
|
Thank you for your feedback, I will consider this. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Our company's VPN disconnects every now and then, so I used a shell script to wrap the gpconnect call in an endless loop.
This however makes voluntarily disconnects difficult. I was looking at the exit code but it is zero either way.
I could
teethe output into a file and look at that but that may be cumbersome.Having the exit code reflect the disconnect reason somehow would solve that.
For my case at least being able to detect this case:
^C[2025-08-06T05:30:49Z INFO gpclient::connect] Received the interrupt signal, disconnecting...is sufficient.
Perhaps there is another solution to this?
Edit: I'm using the cli-version
Beta Was this translation helpful? Give feedback.
All reactions