Package Details: insync 3.9.6.60027-2

Git Clone URL: https://aur.archlinux.org/insync.git (read-only, click to copy)
Package Base: insync
Description: An unofficial Dropbox, Google Drive, and OneDrive client that runs on Linux, with support for various desktops
Upstream URL: https://www.insynchq.com/downloads
Keywords: drive dropbox google onedrive
Licenses: custom:insync
Submitter: xzy3186
Maintainer: thenaterhood
Last Packager: thenaterhood
Votes: 323
Popularity: 0.65
First Submitted: 2012-09-07 17:45 (UTC)
Last Updated: 2025-05-19 12:22 (UTC)

Latest Comments

« First ‹ Previous 1 .. 37 38 39 40 41 42 43 44 45 46 47 .. 66 Next › Last »

colinkeenan commented on 2013-10-14 19:33 (UTC)

I removed the sleep command again. Seems to do better without the sleep command but it doesn't always start regardless. I don't think it has anything to do with the network not being up. I will just have to start it manually sometimes.

colinkeenan commented on 2013-10-13 23:19 (UTC)

I ended up putting the sleep command back in. I don't see why the requires= and after= lines don't always work.

colinkeenan commented on 2013-10-09 02:26 (UTC)

I decided to see what I could understand about systemd from the wiki and found the dependencies section: https://wiki.archlinux.org/index.php/Systemd#Handling_dependencies That section says to put both 'Requires=...' and 'After=...'. I understand why you didn't put 'Requires=...' in there because 'After=...' is telling it to wait until after the network starts so obviously it requires the network. But, following the wiki, I'm seeing what happens if I add the 'Requires=...' to the 'Unit' section. I have again removed the sleep command. Tomorrow, I'll report if this works better.

orschiro commented on 2013-10-08 05:41 (UTC)

@colinkeenan The `After=local-fs.target network.target` part should actually prevent you from this problem. But now you probably see why I created the NetworkManager dispatcher script. For some users even 60 seconds sleep time might not be enough to establish an internet connection. In these cases the dispatcher script comes in handy as it automatically restarts the service after an internet connection was established.

colinkeenan commented on 2013-10-07 23:26 (UTC)

I'm glad my suggestions were incorporated. I'm taking back the idea of removing the sleep 60 though. Without some sleep before starting, insync sometimes doesn't load I guess because the network isn't available when it tries and then it doesn't try again. I put the sleep command back in, but deleted the 0 because sleep 6 works fine for me. If nobody was complaining about the sleep 60, probably best to put it back in.

xzy3186 commented on 2013-10-06 00:49 (UTC)

Thanks to orschiro and colinkeenan, now insync.service has been updated following your suggestion.

orschiro commented on 2013-10-05 11:27 (UTC)

@xzy3186 Together with cilnkeenan we investigated the issue. Can you please update the Insync.service file to reflect the following changes? [Unit] Description=Insync After=local-fs.target network.target [Service] - ExecStartPre=/usr/bin/sleep 60 Environment=DISPLAY=:0 Type=simple ExecStart=/usr/bin/insync_OPTION ExecReload=/bin/kill -HUP $MAINPID KillMode=process - Restart=always + Restart=never User=%I [Install] WantedBy=multi-user.target

colinkeenan commented on 2013-10-04 19:21 (UTC)

Thanks for following up on my investigation of the systemd issue. I forgot to update my system since then or check these comments. Just updated and I have the constantly restarting problem again. So, I changed 'always' to 'never' again on the 'Restart=' line of /usr/lib/systemd/system/insync@.service. I guess I'll followup with orschiro about fixing that in the official file.

orschiro commented on 2013-09-25 11:56 (UTC)

@xzy3186 So far it is still working with my dispatcher package as long as we still allow the service to be run as a user. I think it is safe to include it in the update.

xzy3186 commented on 2013-09-25 01:14 (UTC)

@orschiro I just want to confirm if your package can work properly with the modified service file. If no problem occur, I will include new service file by colinkeenan in the next update.