mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] systemctl daemon-reload fails
Date: Tue, 20 Oct 2020 08:04:58 +0200	[thread overview]
Message-ID: <20201020060458.GA68883@lenoch> (raw)
In-Reply-To: <CAMwGMjzH4-OxG0Hx4JqDv87hf_LT8OUH5j+oJSwxfWcAzVghxw@mail.gmail.com>

On Mon, Oct 19, 2020 at 02:32:49PM -0400, Jon Ringle wrote:
> I recently updated to ptxdist-2020.08.0 for running on our device that
> has 64MB or physical ram.

Same here (but running ptxdist-2020.10.0)

> 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.

(we are slowly reaching point where this devices will be unable to run
recent kernel and systemd)

	ladis

> Thanks
> -Jon
> 
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

  parent reply	other threads:[~2020-10-20  6:05 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 [this message]
2020-10-20 12:57   ` Jon Ringle
2020-10-21  7:27     ` Ladislav Michl
2020-10-28  7:28       ` Michael Olbrich
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=20201020060458.GA68883@lenoch \
    --to=ladis@linux-mips.org \
    --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