Re: [gentoo-user] problems getting systemd to work

[Stefan G. Weichinger]

Am 15.05.2014 11:39, schrieb covici@××××××××××.com:

> I did not try the -H, I may test with that later.
>
>
> I did look at the --print-cmdline and copied the volumes they mentioned,
> but I have other lvm volumes in my fstab and none of them were activated,
> only the ones I specified in the command line!  This is where I have run
> into problems.  I have quite a few lvms, I want them all activated!

Sure. I remember having an extra lvm.service for systemd to have all the
LVs activated ... with that unit-file it worked more reliably for me
(maybe not needed since some time).

For sure that service file is only run *after* the initrd has
found/activated/mounted your LVM-based root ... might be a workaround to
specify the root-LV in the kernel command line (plus maybe "rd.auto
rd.lvm=1" ?) and then let the service file activate the rest of the LVs.

Just to get you started at last ;-)


> Also, since I wrote the last message, I have been looking at the
> journalctl output and discovered a couple of things which I would like
> some help on, but getting the lvms to work is more important.
>
> First, whatever happened to DefaultControllers -- I want to disable
> those cpu hierarchies, but that option seems to have disappeared without
> a trace, although you can google and see it in some documentation.
>
> The keyword also was not accepted in an install section I have, what is
> the matter with that?

What keyword? I don't understand right now.

>  I want to use my sysklogd for my syslog, how can
> I use that with systemd?

systemd's journal will be written to a socket if you configure it in
/etc/systemd/journald.conf

I would check "man journald.conf" and the option:

ForwardToSyslog=

and then let your chosen log-daemon listen there.

IMO you should take a look at journalctl then anyway ... new concepts,
but powerful features.

Stefan