<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>System Service on Michael’s Domain</title><link>https://jeltsch.org/en/tags/system-service/</link><description>Recent content in System Service on Michael’s Domain</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2002 - 2026 Michael Jeltsch.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:18:18 +0300</lastBuildDate><atom:link href="https://jeltsch.org/en/tags/system-service/index.xml" rel="self" type="application/rss+xml"/><item><title>Syncthing</title><link>https://jeltsch.org/en/syncthing/</link><pubDate>Wed, 24 Jan 2018 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/syncthing/</guid><description>&lt;p&gt;
 &lt;a href="https://syncthing.net" target="_blank" rel="noopener noreferrer nofollow"&gt;Syncthing&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 is one of the best tools for keeping folders synchronized across the internet. However, for one or the other reason, it occasionally stops to work on my Ubuntu 16.04 and because I use it in a &amp;ldquo;set it and forget it&amp;rdquo; fashion, I also forget how to check that it is operational.Make it start automatically at boot time (as a system service): &lt;code&gt;systemctl enable syncthing@username.service&lt;/code&gt;Start the service: &lt;code&gt;systemctl start syncthing@username.service&lt;/code&gt;Check the status: &lt;code&gt;systemctl status syncthing@username.service&lt;/code&gt;The URL of the GUI: 
 &lt;a href="https://127.0.0.1:8384" target="_blank" rel="noopener noreferrer nofollow"&gt;https://127.0.0.1:8384&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
However, the above solution does not work well if e.g. the files to syncronize reside on an encrypted folder which is mounted only after the user has logged in (e.g. in Ubuntu 16.04, there was the possibility to encrypt the user folder, which was only unlocked during user login). Alternatively, one can run the service as a &amp;ldquo;user service&amp;rdquo; like this:&lt;code&gt;cp /usr/lib/systemd/user/syncthing.service ~/.config/systemd/user/systemctl --user enable syncthing.servicesystemctl --user start syncthing.service&lt;/code&gt;Syncthing seems to regularly loose a file called &amp;ldquo;.stfolder&amp;rdquo;, which is supposed to be in the root of any shared folder (or it gets converted into a folder). For me the problem gets usually fixed by simply recreating that (empty) file (and deleting the folder with the same name if it exists).&lt;/p&gt;</description></item><item><title>Start netatalk as system service during bootup on Suse Linux 9</title><link>https://jeltsch.org/en/start_netatalk_as_system_service_during_bootup_on_suse_linux_9/</link><pubDate>Thu, 05 Apr 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/start_netatalk_as_system_service_during_bootup_on_suse_linux_9/</guid><description>&lt;p&gt;I am missing from Suse Linux 9 a nice GUI that collects ALL system services with the options &amp;ldquo;start&amp;rdquo;, &amp;ldquo;stop&amp;rdquo; and &amp;ldquo;start on every system boot&amp;rdquo;. RedHat 9 has something like that. There is Yast2, but under the services, netatalk is not even listed. To boot netatalk during system boot, I just create manually a link: &lt;code&gt;cd /etc/init.d/rc5.d sudo ln -s ../atalk S22atalk&lt;/code&gt; After rebooting (and to my surprise) my computer froze. No Ctrl-Alt-F2, no access via ssh; the only rescue being the physical reboot button button (something I am only used to from my Macintosh times). After rebooting in safe mode and removing the link everything is fine again. When I manually start atalk, the system freezes in the same way after a couple of seconds…&lt;/p&gt;</description></item></channel></rss>