Scenario:
When bore can't connect to remote, say be cause the machine running it changed network, bore service continues to run tough connection is broken. This behavior doesn't work well with systems service. Though a restart of bore would solve said connection lost, systemd sees the process is still running and won't restart, requiring using manual intervention.
Proposed solution:
Add a cmd arg, say --exit-on-connection-lost, that does what the flag says, defaults to off to preserve behavior compatibility
Scenario:
When bore can't connect to remote, say be cause the machine running it changed network, bore service continues to run tough connection is broken. This behavior doesn't work well with systems service. Though a restart of bore would solve said connection lost, systemd sees the process is still running and won't restart, requiring using manual intervention.
Proposed solution:
Add a cmd arg, say --exit-on-connection-lost, that does what the flag says, defaults to off to preserve behavior compatibility