From ArchWiki
Revision as of 17:20, 3 February 2013 by Fa2k (Talk | contribs) (Should the section "writing a custom .service" be expanded?)

Jump to: navigation, search

LVM2 section

The section on LVM is incorrect. There is no lvm-monitoring.service. The proper way to enable LVM2 is through systemctl enable lvm. Theking2 (talk) 19:15, 13 December 2012 (UTC)

Should the section "writing a custom .service" be expanded?

I think so.. as long as I got, this is necessary to run self-made scripts during the boot process, but this is not clear and the structure of the files is not well presented.

Moreover, when explain how to transit from the initscript, some referrals on how to move the old custom hooks in /etc/rc.d/functions.d to be executed by systemd, should be made.

--DarioP (talk) 12:42, 18 November 2012 (UTC)

- I think it needs to be expanded indeed. As a newbie, it is easy to grasp the concept of "put your code in rc.local", and it's not clear how to transition. It should not require me to read more than a wiki page to run a command on boot. Specific questions, as also mentioned by DarioP: In what directory should I place my service definition? On the examples page, there are some files named with an at-sign, what difference does that make? It would be very helpful to have a complete example for running a single command at boot (my example: "echo noop > /sys/block/sdb/queue/scheduler").

Display manager fails to load with fast SSD

I was having a problem with my display manager (LXDM) not loading on my laptop, which has a Sandisk Extreme SSD. Xorg.log would show errors like "No screens found."

I eventually figured out that the problem was that my computer was booting so fast that KMS didn't have enough time to kick in before X was started. I solved by adding the KMS driver (i915 in my case) to the initramfs.

Just a tip for SSD users, not sure if it should be added to the page or not.
--Steev (talk) 16:59, 2 September 2012 (UTC)

This is a general problem that needs to be solved in the display manager. GDM already implements the bits for the CanGraphical flag.
-- Falconindy (talk) 21:34, 2 September 2012 (UTC)

Should we add a note about CUPS under 'Transitioning from initscripts to systemd'?

Are there any more sockets that change?

Copied from the CUPS wiki:


Systemd uses a different CUPS socket file located at:


The default CUPS socket file is located at:


Edit /etc/cups/cupsd.conf and /etc/cups/client.conf as root to use the systemd socket instead of the default. Make sure to restart CUPS when you are done:

# systemctl restart cups

-- JKAbrams 5 November 2012

This sounds more like a cups packaging bug that should just be fixed.
-- Jstjohn (talk) 01:11, 8 November 2012 (UTC)
It sounds like someone who doesn't have a clue about systemd. That cups.socket file is a systemd unit file of type socket, which contains the location of the socket file for CUPS (and that is still /var/run/cups/cups.sock).
Raynman (talk) 22:49, 9 November 2012 (UTC)

Systemd defaults / to rshared, gotcha

Still reading up on this, so I'm not 100% solid but I discovered during the systemd transition that it defaults the / mount to rshared (see Shared subtree for definitions). Excerpted from core/mount-setup.c in systemd github:
/* Mark the root directory as shared in regards to mount
 * propagation. The kernel defaults to "private", but we think
 * it makes more sense to have a default of "shared" so that
 * nspawn and the container tools work out of the box. If
 * specific setups need other settings they can reset the
 * propagation mode to private if needed. */
if (detect_container(NULL) <= 0)
        if (mount(NULL, "/", NULL, MS_REC|MS_SHARED, NULL) < 0)
                log_warning("Failed to set up the root directory for shared mount propagation: %m");

This means that all bind mounts made through fstab will default to shared behavior, not private. For those users who depend on non-recursive bind mounts, this can be a very big gotcha (as the mount propagation effectively nullifies the non-recursion). I think it should be at least noted under Filesystem Mounts, since fstab bind entries definitely may not preserve behavior across the systemd transition and there are definitely some systems that would fail to start up/operate properly due to this, perhaps even silently.

As a side note, for nested bind mounts this also results in multiplicative bloat of the mount table, depending on what kind of nesting structure is used (it's actually relatively easy to construct a nesting sequence that makes 2^n mounts out of n mount calls).

Still looking into good (and easy) configuration solutions.

Compgamer89 (talk) 07:16, 4 December 2012 (UTC)

You may find this commit useful. --David Strauss (talk) 22:58, 13 December 2012 (UTC)