Arch Linux User Repository

This is an example unit file placed at /usr/lib/systemd/system/renderd.service. The renderd daemon can be started by systemctl start renderd.service, and run journelctl -u renderd.service to check out the logs.

[Unit] Description=renderd Documentation=man:renderd(1)

[Service] Type=forking ExecStart=/usr/bin/renderd

[Install] WantedBy=multi-user.target

<hr>

This unit file does not bother with postgresql service since PostGIS data source is not necessary. (I provide GeoJSON files in my case.) If the feature is needed, put the snippet under [Unit] section to make renderd restart when postgressql restarts.

After=postgresql.service Requires=postgresql.service PartOf=postgresql.service

<hr>

I'm not using systemd, but you're welcome to offer one that works for you. Here are the challenges: You'll need to assume the postgresql cluster to start after; renderd can't properly reestablish connections to the postgresql instance if it restarts. That needs fixing upstream. As a result, renderd also needs to restart whenever postgresql does, otherwise reliability will be bork-tier. But again, that really needs fixing upstream, because it breaks any rendering scripts, that will end immediately having failed all of their rendering commands.

Can you create a systemd service file for renderd?

No specific reason I can remember; except I hadn't tested it on 32bit.

Is there a reason the architecture is restricted to x86_64? I successfully built the package and ran the Apache module mod_tile on an i686 (with prerendered tiles; using a 32 bit system for rendering is probably not recommendable).