You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be nice if rclone would support this too. In the presence of the LISTEN_PID env var, it could automatically bind to FD 3 - or the --addr CLI arg could get additional syntax for this, similar to the (undocumented in the --help output) unix:// syntax.
How to use GitHub
Please use the 👍 reaction to show that you are affected by the same issue.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.
The text was updated successfully, but these errors were encountered:
The associated forum post URL from
https://forum.rclone.org
https://forum.rclone.org/t/systemd-socket-activation-for-rclone-serve/45644
What is your current rclone version (output from
rclone version
)?1.66.0
What problem are you are trying to solve?
I'd like to create some
rclone serve
processes, and use systemd socket activation to start them on demand.How do you think rclone should be changed to solve that?
Essentially, sockets are passed as FDs directly to the process.
https://darkcoding.net/software/systemd-socket-activation-in-go/ describes a golang-only solution to implement this.
It'd be nice if rclone would support this too. In the presence of the
LISTEN_PID
env var, it could automatically bind to FD 3 - or the--addr
CLI arg could get additional syntax for this, similar to the (undocumented in the--help
output)unix://
syntax.How to use GitHub
The text was updated successfully, but these errors were encountered: