Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Having problems with a custom process that I start at boot time using systemd. I am using the Arch Linux distro built for the RPi. There is nothing special about the service I'm starting. Its a server listening on a UDP port for a proprietary protocol responding to requests appropriately (written in C). The problem I am having is when the service is started via systemd, the client has timeout issues every few seconds as queries and responses are sent to and from the server. When I run the service from the command line after I log in, I experience none of these timeout issues. I suspect that there is some kind of process monitoring overhead associated with systemd that is causing a slight slowdown. Is there any documentation describing the types of monitoring overhead that systemd imposes, and how to shut it off? My .service file for the service is trivially simple, following the examples.

As a second approach, I am considering trying the Wheezy distro to see if I get similar timeout issues since I believe the init system is something other than systemd. I want to try this, but I'm not ready to abandon Arch and the effort I've put in.

share|improve this question
Welcome to superuser! Maybe your question will get more attention on or though – Tobias Kienzler Apr 24 '13 at 10:29
As far as I know the only things that systemd uses to monitor services are logging of the output and cgroups. Cgroups are built into the kernel directly and I don't think they create much overhead. – FSMaxB Oct 26 '13 at 8:01

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.