From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wr1-f53.google.com ([209.85.221.53]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kUZxt-0002mu-A6 for ptxdist@pengutronix.de; Mon, 19 Oct 2020 20:33:02 +0200 Received: by mail-wr1-f53.google.com with SMTP id e17so778676wru.12 for ; Mon, 19 Oct 2020 11:33:01 -0700 (PDT) MIME-Version: 1.0 From: Jon Ringle Date: Mon, 19 Oct 2020 14:32:49 -0400 Message-ID: Subject: [ptxdist] systemctl daemon-reload fails List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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" To: ptxdist@pengutronix.de I recently updated to ptxdist-2020.08.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. Thanks -Jon _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de