[yocto] Problems enabling systemd

[Matt Schuckmann]

> -----Original Message-----
> From: Bruce Ashfield [mailto:bruce.ashfield at windriver.com]
> Sent: Monday, April 20, 2015 7:52 AM
> To: Matt Schuckmann; Yocto Project
> Subject: Re: [yocto] Problems enabling systemd
> 
> On 04/20/2015 04:43 AM, Anders Darander wrote:
> > * Matt Schuckmann <Matt.Schuckmann at planar.com> [150417 23:27]:
> >> I've got an image for a AM3352 system based on Dylan and Arago and
> >> I'm trying to switch to systemd for init.
> >
> >> So far I haven't had much luck.
> >> First off I'm getting different results depending on where I turn it
> on.
> >> I'm turning it on via the following 2 lines:
> >
> >> DISTRO_FEATURES_append = " systemd"
> >> VIRTUAL-RUNTIME_init_manager = "systemd"
> >
> > These two lines looks correct, though, if you're building a
> > systemd-only distro & image, you migth want to add:
> >
> > DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
> >
> >> If I place these lines in my_image.bb file I seem to get a partial
> >> install of systemd, systemd_udev is there and seems to run but
> that's
> >> about it, there is no systemctrl journalctl and the sysvinit init
> >> scripts still seem to be called.
> 
> 
> And also on this point, make sure to check your PACKAGECONFIG values
> for systemd. The optional utilities like networkd are not enabled by
> default, and a bbapend of the systemd recipe is needed to enable them
> via PACKAGECONFIG.
> 
> Cheers,
> 
> Bruce

Thanks for the info, Bruce I'll try a take a look. Are there any good examples for what to do with PACKAGECONFIG? the Yocto manual doesn't mention this at all for systemd. 

> 
> >
> > DISTRO_FEATURES is a distro (policy) configuration, and thus, can't
> be
> > modfied in a recipe. The correct way would be to add this in your own
> > my_distro.conf.
> >
> >> If I place these lines in either local.conf or my_distrobution.conf
> >> all of the systemd utility seem to get installed and systemd
> startups
> >> up but it's clearly not configured correctly.
> >
> > Good that it seems to be installed OK.
> >
> >> For starters the systemd dbus isn't getting created and that seems
> to
> >> lead to a whole host of other problems, including journald constant
> >> spewing the following error messages:
> >
> >> [   55.926223] systemd-journald[715]: Failed to write entry,
> ignoring: Argument list too long
> >> [   55.936931] systemd-journald[715]: Failed to rotate
> /run/log/journal/c37feca280b74ec583564afcc2a93f0a/system.journal: No
> such file or directory
> >> [   55.950911] systemd-journald[715]: Failed to write entry,
> ignoring: Argument list too long
> >> [   55.961580] systemd-journald[715]: Failed to rotate
> /run/log/journal/c37feca280b74ec583564afcc2a93f0a/system.journal: No
> such file or directory
> >> [   55.975568] systemd-journald[715]: Failed to write entry,
> ignoring: Argument list too long
> >> [   55.986329] systemd-journald[715]: Failed to rotate
> /run/log/journal/c37feca280b74ec583564afcc2a93f0a/system.journal: No
> such file or directory
> >
> >> I don't know if it matters but this system has no display at all,
> >> it's a strictly embedded installation.
> >
> > That shouldn't really matter, I'm running systemd in headless setups.
> >
> > I'd guess that you're getting some errors earlier than this in the
> > bootlog? Could you paste them?
> >
> > Cheers,
> > Anders
> >
> >