Arch Linux User Repository

@vaski seems like you don't have [D-Bus set up in your systemd user session][1], do you? The old "btsync@user.service" and the new "--user btsync.service" differ slightly in more than just invocation syntax. The former runs in the system instance of systemd, while the latter runs in a user instance. [1]: https://wiki.archlinux.org/index.php/Systemd/User#Basic_setup

I get this, with or without sudo $ systemctl --user start btsync Failed to get D-Bus connection: Connection refused @mielouk, was dropping the sudo all you did?

@Vodun THX, up and running again :)

1/ Try without sudo: systemctl --user start btsync 2/ There is no more 'btsync@user' service. (replaced by method 1)

After updating my server and my desktop over the last few days, my btsync setup got broken. I'm not able to start btsync@user on either machine. $ sudo systemctl --user start btsync Failed to get D-Bus connection: Connection refused $ sudo systemctl start btsync@X Failed to start btsync@X.service: Unit btsync@X.service failed to load: No such file or directory. I didn't change any settings or made any changes on the system. Might you have some suggestions on how this might have happened or how to fix this?

@emlun Thanks for sharing this. Current implementation is redirecting all output to the sync.log using btsync in daemon mode. If somebody want part of the output go to the journal, he/she may follow approach your are pointing to: switch btsync to non-daemon mode and wrap it with the shell script. @djhaines I saw somewhere on the forums, that btsync since version 1.3 has log rotation built-in and strips the log files to 10 megabytes by default. I am not a heavy btsync user, so I can't confirm this myself, but I believe some of the users can (like @dam5h), so lets wait for more feedback. Anyway, I think btsync developers should implement log level configuration from config file to let people select logging level for their needs. In this case logging to journal will be safe and trouble-free. P.S. thank you, I really appreciate the kind words I've heard from you.

Here's a gist showing what I was trying to explain earlier: https://gist.github.com/emlun/6f847a74e0136188d7a4 If you want some of the output in the journal, but not all of it, you could just monkey patch the executable with a shell script that filters the output. As shown in the example, you can *also* save it to a file if you so prefer. I hope it might be of use to someone. :)

Also, I would like to thank you, ava1ar, for being one of the truly good maintainers on the AUR. Over time, you have exhibited a tremendous capacity to actually listen and respond to your userbase. It's much appreciated.