From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from mail-wm1-f67.google.com ([209.85.128.67])
 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 1kUa1O-0003JZ-ND
 for ptxdist@pengutronix.de; Mon, 19 Oct 2020 20:36:39 +0200
Received: by mail-wm1-f67.google.com with SMTP id k21so556342wmi.1
 for <ptxdist@pengutronix.de>; Mon, 19 Oct 2020 11:36:38 -0700 (PDT)
MIME-Version: 1.0
References: <CAMwGMjzH4-OxG0Hx4JqDv87hf_LT8OUH5j+oJSwxfWcAzVghxw@mail.gmail.com>
In-Reply-To: <CAMwGMjzH4-OxG0Hx4JqDv87hf_LT8OUH5j+oJSwxfWcAzVghxw@mail.gmail.com>
From: Jon Ringle <jon@ringle.org>
Date: Mon, 19 Oct 2020 14:36:26 -0400
Message-ID: <CAMwGMjwHYYAZoSiPU5nO9K78-JTksQ7cRcF1RA9i4acqh+kUgw@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 Mon, Oct 19, 2020 at 2:32 PM Jon Ringle <jon@ringle.org> wrote:
>
> I recently updated to ptxdist-2020.08.0 for running on our device that
correction. I meant ptxdist-2020.10.0

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

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