I have set up SpiderOak to autostart, but it always remains disconnected -- that is, until I quit the application and restart. This must be SpiderOak specific issue because dropbox seems to be able to auto-connect after network becomes available. SpiderOak seems to have abandon their support forums and a general search yields http://www.clausconrad.com/blog/restarting-spideroak-after-switching-networks . Not 100% sure, but from SpiderOak's behavior it looks like, SpiderOak probably latches on to lo interface and waits forever to get online.

Any ideas how I can make applications which are set to autostart wait until network (in my case wireless) is available? I guess I can write a shell-script that just sleeps for some time before starting SpiderOak, but wanted to check with others if they had faced this issue and what the solution was.

Thanks

Yes, I was thinking something basic like that would work. I was trying to make my script a little smarter by checking for network availability. I came across https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ which suggests (or that's how I interpreted) if I have something like following in my KDE user level autostart script, it would work:

#! /bin/sh

echo "Checking network status" > $HOME/net.log

loop_ctr=1
while ! systemctl status network-online.target >> $HOME/net.log && [ $loop_ctr -le 10 ]; do
    echo "Sleeping for 5 seconds" >> $HOME/net.log
    sleep 5
    loop_ctr=$((loop_ctr+1))
done
ip addr list >> $HOME/net.log

/usr/bin/SpiderOakONE

The script didn't work the way I had hoped because network-online.target was active and yet (except for the loopback interface) I didn't have an IP address assigned. I may have misunderstood, but any clue, why network-online.target becomes active before an IP address is obtained?

Thanks

If you go that way than much better to create a .service file for spideroak, set to enable, then let it execute much later, something like 10 seconds after NetworkManager.service see an example at /usr/lib/systemd/system/NetworkManager-wait-online.service

I thought SpiderOak being a user level service and one needing an X session will be complicated managing it with systemd. But it may not be -- I'll explore that as an alternative.

Thanks