Good day, I've been running an ssh tunnel with keepalives as systemd service with "Restart=always" option (since network connection there goes down quite frequently), and it worked fairly well until this happened:
May 25 20:41:47 daemon.info<30> systemd[1]: net-rathole.service holdoff time over, scheduling restart. May 25 20:41:47 daemon.warning<28> systemd[1]: net-rathole.service start request repeated too quickly, refusing to start. After the last message systemd just stopped restarting the service, which I think isn't supposed to happen. Is this really a bug or Restart= should work this way? Machine is running systemd 26 or 27, unfortunately I can't access machine via ssh (because of the service in question, got syslog lines mailed in the report) to get exact version. RestartSec= option isn't set there, so I guess default 100ms holdoff is used. -- Mike Kazantsev // fraggod.net _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
