It is indeed aborted when a user logs out. This is particularly troubling during a restore, since it is not atomic, does not resume, and can leave incomplete files behind.
In another thread this was discussed with the solution of running the server on a per user basis using a Linux service template file. (Slightly unfinished as of now, since there needs to be a customization of port number by user name, but a final service file will be posted there once written and tested.)
Thanks for the help!