Description of problem: /etc/resolv.conf file after starting an openconnect VPN connection. It's not restored after the openconnect process receives a SIGTERM. Version-Release number of selected component (if applicable): openconnect-7.03-1.fc21.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start an openconnect VPN connection at the commandline using /usr/sbin/openconnect 2. Send a SIGTERM to the openconnect process using: kill <pid> Actual results: /etc/resolv.conf remains modified even after the openconnect process terminates. Expected results: The original /etc/resolv.conf is restored. Additional info: Reproducing this may depend on whether the VPN gateway provides nameservers.
You should send SIGINT for the client to properly terminate the connection. This is described in the manual: SIGTERM exits immediately without logging off or running vpnc-script. SIGINT performs a clean shutdown by logging the session off, discon‐ necting from the gateway, and running the vpnc-script to restore the network configuration.
This seems a little unintuitive, as SIGTERM is the "polite" way to terminate a process and the SIGTERM signal can be handled in order to perform cleanup tasks (such as a clean shutdown). [1] That said, the SIGINT signal is handled and does cleanup. It's just somewhat less intuitive/convenient when working with a backgrounded openconnect process. Is there a reason why SIGTERM isn't handled more like SIGINT, such that it cleans up before terminating? [1] See http://www.gnu.org/software/libc/manual/html_node/Termination-Signals.html and 'man 7 signal'
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Forwarded to upstream: https://gitlab.com/openconnect/openconnect/issues/9