-
Notifications
You must be signed in to change notification settings - Fork 315
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
Run as system daemon #93
Comments
Hi @nidico, You need to create a systemd config file (either in
Once done:
|
For others looking at this: This isn't working (i.e. automatically restarting) for me as it is (though a similar systemd unit in general is). I haven't spend more time since and setup a cron job which restarts the systemd service if the connection is down. |
This is my service running at boot in CentOS 7.4: Description = OpenFortiVPN [Service] [Install] |
Type=forking , otherwise systemd will show active status even if VPN connection is not established. |
|
my bad, the service is not start with forking or simple type, only with Type=idle as mentioned r3tr0g4m3r. |
Type |
@DimitriPapadopoulos I was setting up this and when I switch to
|
In which state? How does it fail? |
With
as opposed to using
I see nothing useful in syslog or with journalctl, if I do
|
Version 1.6.0 is pretty old and does not call |
Also see #948. |
The standard lease time for fortify vpn server side is 8 hours. Has as anyone figured out how to automatically reconnect if the connection is lost or the lease time expires. |
@requa3r0 see the above discussion about how to start |
@mrbaseman If the connection is based on a username + password combination, is it possible to implement auto-reconnect? |
@kardoka Really this daemon reconnects for days...1 sec after the lease time is over. |
@kardoka @mrbaseman [Unit] StartLimitIntervalSec=500 [Service] ExecStart=/usr/bin/openfortivpn [Install] |
What's the best practice in order to run openfortivpn as a system daemon, e.g. as a systemd unit? I'm particularly concerned about automatic reconnection in case of connection loss.
The text was updated successfully, but these errors were encountered: