I think the assistant should have a delay before starting so it doesn't impact on the system boot performance.
I know this can be configured per user (I have it set to 5min), but I think 2min is a sane default.
I don't really know how to submit patches (I can't attach it), so I simply copy it here. It's trivial enough.
From bc6b90ce333659bd2511eedd4ab9067241f73780 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jon=20Ander=20Pe=C3=B1alba?= <jonander.penalba@gmail.com>
Date: Wed, 28 Oct 2015 12:00:51 +0100
Subject: [PATCH] When autostarting the assistant on boot delay the execution
2min
---
Assistant/Install/AutoStart.hs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Assistant/Install/AutoStart.hs b/Assistant/Install/AutoStart.hs
index 5745030..6a09c3a 100644
--- a/Assistant/Install/AutoStart.hs
+++ b/Assistant/Install/AutoStart.hs
@@ -35,6 +35,6 @@ fdoAutostart command = genDesktopEntry
"Git Annex Assistant"
"Autostart"
False
- (command ++ " assistant --autostart")
+ (command ++ " assistant --autostart --startdelay=120")
Nothing
[]
--
2.6.2
There's actually an undocumented default startdelay of 5 seconds when using autostart. I've now documented it.
Maybe 5 seconds is too little. OTOH, 2 minutes may be a bit too much; if the user is booting up their computer to access a new file in their annex they'd expect it to start syncing ASAP.
I think my justification for the 5 seconds default was that about how long it seems to take a typical desktop system to get loaded (after the login screen) and for the user to open a web browser, on reasonably modern hardware. Even windows in an emulator doesn't take much longer than that.