Fail early if file system cannot be mounted due to network connectivity.

[harababurel]

If there is no internet connection, GCSF fails to populate the file system which results in the mountpoint containing nothing but an empty "Shared with me" directory.

GCSF should fail early in this case, to make it clear that mounting failed. This will also help systemd detect the process death and restart it accordingly.

[kcallis]

Thank you for the fast response and resolution! I had just subscribed to the mailing list and saw the message about using the systemd service from another user. I am wondering if the service will work for multiple users? For instance, I log in and the gcsf.service mounts the filesystem and life is good. I log out and I assume my Google Drive will umount. If my son logs into the host, will the service automatically mount his google drive (he has already authenticated)?

[harababurel]

Implemented 33f55f3.

[harababurel]

Thank you for the fast response and resolution! I had just subscribed to the mailing list and saw the message about using the systemd service from another user. I am wondering if the service will work for multiple users? For instance, I log in and the gcsf.service mounts the filesystem and life is good. I log out and I assume my Google Drive will umount. If my son logs into the host, will the service automatically mount his google drive (he has already authenticated)?

Released this feature in 0.1.21 (c8d8406). After updating to this version, GCSF should integrate with systemd a bit more nicely.

To answer your question: the setup you've described should work, provided you make some configuration changes. Specifically, each user should have their own service file with the corresponding session name, mountpoint, User and Group. AFAIK, the service is not started at login time, but rather as soon as possible (i.e. after network.target is running, which is unrelated to users logging in). It's also not stopped at logout -- you have to follow these steps to make it happen.

Depending on your privacy concerns, it may also be acceptable to simply enable the service for each user and have all instances run at the same time regardless of who is logged on.

Another alternative is to manually run systemctl start and systemctl stop after logging in and before logging out, respectively.