# Keeping Syncthing Running: Systemd & regular /etc/init.d

**URL:** https://forum.syncthing.net/t/keeping-syncthing-running-systemd-regular-etc-init-d/402
**Category:** Howto
**Created:** [June 17, 2014, 11:58am UTC](https://forum.syncthing.net/t/keeping-syncthing-running-systemd-regular-etc-init-d/402 "2014-06-17T11:58:55Z")
**Posts on this page:** 1
**Showing post:** 27

<div class="post-metadata">

### Author: ![hobarrera](https://forum.syncthing.net/user_avatar/forum.syncthing.net/hobarrera/32/519_2.png) [@hobarrera](https://forum.syncthing.net/u/hobarrera)
#### Post date: [October 30, 2014, 7:52am UTC](https://forum.syncthing.net/t/keeping-syncthing-running-systemd-regular-etc-init-d/402/27 "2014-10-30T07:52:55Z")

</div>

> [@thfr](#):
>
> I know for a single user system there is no difference but for multi user systems it makes sense to use the user service manager and I am always glad to keep my activities in user space

As I said before, the above script runs the service as the configured your (eg: your user, not root), even if it’s started by root (systemd will change user before starting the process). (I’m assuming that’s what you refer to with “user space”, since syncthing can’t run outside user space).

I do agree on the multi-user point; syncthing _may_ degrade performance on shared hosts or have other undesired effects. Just also keep in mind that by running with `systemd --user` syncthing will not sync files until you log in on more than one host simultaneously.

---

_[View the full topic](https://forum.syncthing.net/t/keeping-syncthing-running-systemd-regular-etc-init-d/402)._