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
I made a mistake. All disk operations are assuming the files are on the current filesystem. They will not work for remote systems. I'm not sure how to make it possible for remote as well.
I guess the best thing to do right now is to abort disk operation when the remote is not localhost and print a warning.
Secondly, a workaround to run disk operations on remote is to use them in callbacks on the remote server, with the aria2p listen -c /path/to/callbacks.py functionality. Run the aria2p listen command in a background process (&, maybe followed by disown, or with nohup).
Eventually, maybe we could implement a way to communicate between different aria2p instances, to be able to run disk operations on remotes.
Boost priority
Boost priority in our backlog through Polar.sh. Higher pledge, higher priority.
Minimum pledge by user/organization is $5, minimum amount for boost is $30.
I made a mistake. All disk operations are assuming the files are on the current filesystem. They will not work for remote systems. I'm not sure how to make it possible for remote as well.
I guess the best thing to do right now is to abort disk operation when the remote is not localhost and print a warning.
Secondly, a workaround to run disk operations on remote is to use them in callbacks on the remote server, with the
aria2p listen -c /path/to/callbacks.py
functionality. Run thearia2p listen
command in a background process (&
, maybe followed bydisown
, or withnohup
).Eventually, maybe we could implement a way to communicate between different
aria2p
instances, to be able to run disk operations on remotes.Boost priority
The text was updated successfully, but these errors were encountered: