From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] systemctl daemon-reload fails
Date: Wed, 28 Oct 2020 08:28:11 +0100 [thread overview]
Message-ID: <20201028072811.GE3084@pengutronix.de> (raw)
In-Reply-To: <20201021072754.GA96000@lenoch>
On Wed, Oct 21, 2020 at 09:27:54AM +0200, Ladislav Michl wrote:
> On Tue, Oct 20, 2020 at 08:57:27AM -0400, Jon Ringle wrote:
> > On Tue, Oct 20, 2020 at 2:06 AM Ladislav Michl <ladis@linux-mips.org> wrote:
> > >
> > > On Mon, Oct 19, 2020 at 02:32:49PM -0400, Jon Ringle wrote:
> > > > I recently updated to ptxdist-2020.10.0 for running on our device that
> > > > has 64MB or physical ram.
> > > > With systemd-246.6 that is installed,I'm finding that systemd
> > > > daemon-reload now fails:
> > > >
> > > > $ sudo systemctl daemon-reload
> > > > Failed to reload daemon: Refusing to reload, not enough space
> > > > available on /run/systemd. Currently, 10.6M are free, but a safety
> > > > buffer of 16.0M is enforced.
> > > >
> > > > Has anyone else encountered this issue?
> > > > What is the recommended way to handle this? I'm hesitant to increase
> > > > the size of /run in fstab because of the limited RAM I have available.
> > >
> > > I lowered RELOAD_DISK_SPACE_MIN with hope for the best. In my scenario,
> > > daemon-reload is almost never called - only in case technician is doing
> > > some tests on device and there is always watchdog to fix failed software.
> >
> > Yeah, I noticed that systemd hardcoded the value of
> > RELOAD_DISK_SPACE_MIN to 16MB.
> > What did you patch your value to be?
>
> 1MB, previously there was no such check and it was added to fix
> https://github.com/systemd/systemd/issues/5016
> and those 16MB seems to be just a number big enough...
For most embedded systemd 16M is probably overkill. But on a server with
thousands of units, it is probably reasonable. A real fix should probably
be something that scales with the number of units.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2020-10-28 7:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 18:32 Jon Ringle
2020-10-19 18:36 ` Jon Ringle
2020-10-20 6:04 ` Ladislav Michl
2020-10-20 12:57 ` Jon Ringle
2020-10-21 7:27 ` Ladislav Michl
2020-10-28 7:28 ` Michael Olbrich [this message]
2020-10-28 7:37 ` Michael Olbrich
2020-10-28 13:27 ` Jon Ringle
2020-10-28 17:40 ` Michael Olbrich
2020-10-29 7:13 ` Alexander Dahl
2020-10-29 8:05 ` Michael Olbrich
2020-10-29 8:33 ` Alexander Dahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201028072811.GE3084@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox