A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the
tarball here:
https://github.com/systemd/systemd/archive/v248-rc1.tar.gz
NOTE: This is ☠️ pre-release ☠️ software. Do not run this on production
systems, but please test this and report any issues you find to
Hi all,
I've been looking to dynamically create .conf files at boot depending on
the hardware that I'm running on (to set MemoryMax, if it's relevant). I'd
assumed that the proper way to do this would be by using a generator, since
the .conf file won't automatically be loaded and would require
On Thu, 18 Feb 2021, Lennart Poettering wrote:
> On Do, 18.02.21 11:48, Robert P. J. Day (rpj...@crashcourse.ca) wrote:
>
> > A colleague has reported the following apparent issue in a fairly
> > old (v230) version of systemd -- this is in a Yocto Project Wind River
> > Linux 9 build, hence the
On Mon, Feb 22, 2021 at 06:22:44AM -0500, Robert P. J. Day wrote:
> On Thu, 18 Feb 2021, Lennart Poettering wrote:
>
> > On Do, 18.02.21 11:48, Robert P. J. Day (rpj...@crashcourse.ca) wrote:
> >
> > > A colleague has reported the following apparent issue in a fairly
> > > old (v230) version of
On Mon, 22 Feb 2021, Greg KH wrote:
> On Mon, Feb 22, 2021 at 06:22:44AM -0500, Robert P. J. Day wrote:
> > On Thu, 18 Feb 2021, Lennart Poettering wrote:
> >
> > > On Do, 18.02.21 11:48, Robert P. J. Day (rpj...@crashcourse.ca) wrote:
> > >
> > > > A colleague has reported the following
On Mon, Feb 22, 2021 at 8:22 AM Robert P. J. Day
wrote:
> On Thu, 18 Feb 2021, Lennart Poettering wrote:
>
> > On Do, 18.02.21 11:48, Robert P. J. Day (rpj...@crashcourse.ca) wrote:
> >
> > > A colleague has reported the following apparent issue in a fairly
> > > old (v230) version of systemd
On Mo, 22.02.21 06:22, Robert P. J. Day (rpj...@crashcourse.ca) wrote:
> well, we seem to have isolated the issue, here it is in a nutshell
> based on a condensed note i got from someone who tracked it down this
> weekend. the memory leak is triggered by:
>
> $ ssh root@ -p 830 -s netconf
I'm trying to understand some implications of the way systemd loads
/etc/machine-id.
My understanding is, first: systemd reads /etc/machine-id during *early
boot.* At that point, I'm only guaranteed that the *root* filesystem will
be there for me.
Second: there's no way to delay that machine-id
