From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from mail-wr1-f66.google.com ([209.85.221.66])
 by metis.ext.pengutronix.de with esmtps
 (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92)
 (envelope-from <jonringle@gmail.com>) id 1kUrCt-0003Sp-DF
 for ptxdist@pengutronix.de; Tue, 20 Oct 2020 14:57:40 +0200
Received: by mail-wr1-f66.google.com with SMTP id h7so2015626wre.4
 for <ptxdist@pengutronix.de>; Tue, 20 Oct 2020 05:57:39 -0700 (PDT)
MIME-Version: 1.0
References: <CAMwGMjzH4-OxG0Hx4JqDv87hf_LT8OUH5j+oJSwxfWcAzVghxw@mail.gmail.com>
 <20201020060458.GA68883@lenoch>
In-Reply-To: <20201020060458.GA68883@lenoch>
From: Jon Ringle <jon@ringle.org>
Date: Tue, 20 Oct 2020 08:57:27 -0400
Message-ID: <CAMwGMjxwX-GxemmxwBueaNFBFBJgomxzq+ciMcmWBUiW5-HAqg@mail.gmail.com>
Subject: Re: [ptxdist] systemctl daemon-reload fails
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
 <mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/cgi-bin/mailman/private/ptxdist/>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
 <mailto:ptxdist-request@pengutronix.de?subject=subscribe>
Reply-To: ptxdist@pengutronix.de
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ptxdist-bounces@pengutronix.de
Sender: "ptxdist" <ptxdist-bounces@pengutronix.de>
To: ptxdist@pengutronix.de

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?

Our firmware update script calls `systemctl daemon-reload` after
installing an updated ipk package which then leads to failing to
restart our application service

-Jon

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