Talk:Systemd

Redundant service entries
What about removing custom service pastes we have in systemd-units ebuild already? I feel a little wated when seeing them already well prepared and kind of (!) copy'n'pasted here in the wiki aswell.

If someone wants to contribute a new service file, then go to the Gentoo ticket :)
 * Ideally only "custom" services should be here. /Ni1s 14:12, 3 June 2011 (GMT)

CUPS Socket activation
How do we get CUPS with socket activation (via cups.path/cups.socket) so that it's stopped if it's not printing? Is there a patch somewhere? Is it in CUPS 1.5? --Alec 15:27, 20 June 2011 (GMT)

Hey Alec, Lennart Poettering just published an article for developers explaining how he patched CUPS in order to get it to support systemd natively. He also explains why CUPS path and hardware activation should work. Is it not working for you? -- Natunobilis 21:09, 6 July 2011 (GMT)

That works :) I just posted a bug with the modified ebuild here: https://bugs.gentoo.org/show_bug.cgi?id=376021 --Alec 17:29, 22 July 2011 (GMT)

Getting rid of conf.d & co.
Although systemd supports configuration files through its, the author suggests (and I agree) that unit files under   are meant to be editable by the sysadmin.

So, if the sysadmin wants to customize their daemon's start parameters, they should edit  directly. It's a  file, after all.

However, if you really enjoy using variables -- or are very worried that inexperienced sysadmins might bork their systems by ruining their  lines, then I guess we should only employ the   directive. It lives within the unit file (thus reducing the number of files and syscalls for starting each unit), and it also successfully limits the extent of borking caused by incorrect editing.

Sunset period
If  requires a sunset period, then it's also OK: unit files are allowed to have both   and   directives, with the latter taking precedence. Perfect, huh? -- Natunobilis 21:25, 6 July 2011 (GMT)

No service to clean /tmp?
Hi, is there any service that cleans temporary files at startup? Writing one seems to be pretty easy, however some of my services do early writes into it and can crash if it gets removed. Could anyone suggest right way to do this (presumably removing them right after mount ??). Thanks for suggestions.

| LPs latest missive on SystemD (part 12) describes tmp handling very well. Basically, you can have per process private /tmp created on the fly and cleaned up afterwards.

openrc service
I looked as hard as I could after looking around my system after installing systemd, but there is no openrc-init.service like this article claims. Did I miss a step?-- 24.116.90.172 22:11, 2 December 2011 (GMT)

Systemd-39+ broken sudo
Adding both pam_loginuid.so and pam_systemd.so to /etc/pam.d/system-auth doesn't work here. With pam_loginuid.so only it works, and there's no need to edit /etc/pam.d/sudo or /etc/pam.d/su.