On Fri, 30 Apr 2021 at 22:15, Michael Biebl wrote:
>
> Am Fr., 30. Apr. 2021 um 20:27 Uhr schrieb Rick Winscot
> :
>
> > At this point, flush is attempting to re-route /run/log/journal to
/var/log/journal ... and the /var partition is not yet mounted. Units
generated for fstab in /run/systemd/gene
On Wed, 2021-04-28 at 10:09 +1000, Erwin van Londen wrote:
>
> On Tue, 2021-04-27 at 16:41 -0400, Ewan D. Milne wrote:
> > On Tue, 2021-04-27 at 20:33 +, Martin Wilck wrote:
> > > On Tue, 2021-04-27 at 16:14 -0400, Ewan D. Milne wrote:
> > > > There's no way to do that, in principle. Because
--On Friday, April 30, 2021 11:39 AM -0400 Rick Winscot
wrote:
Early in the project it was decided to make the rootfs read-only... in an
effort to improve durability in environments where power fluctuations
might cause problems on the eMMC. At the same time, making logging (e.g.
/var) persiste
Am Fr., 30. Apr. 2021 um 20:27 Uhr schrieb Rick Winscot
:
> At this point, flush is attempting to re-route /run/log/journal to
> /var/log/journal ... and the /var partition is not yet mounted. Units
> generated for fstab in /run/systemd/generator that manage the mount have an
> After=local-fs-p
15:31:18 localhost systemd[1]: Dependency failed for Flush Journal to
Persistent Storage.
░░ Subject: A start job for unit systemd-journal-flush.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-jour
Am Fr., 30. Apr. 2021 um 19:42 Uhr schrieb Rick Winscot
:
>
> systemd 247
Ok, thanks
> /etc/systemd/journald.conf storage is persistent,
> systemd-journal-flush.service has RequiresMountsFor=/var/log/journal.
>
> Mounting /var on a separate read-write partition handles the persistent log
> requ
systemd 247
/etc/systemd/journald.conf storage is persistent,
systemd-journal-flush.service has RequiresMountsFor=/var/log/journal.
Mounting /var on a separate read-write partition handles the persistent log
requirement as well as offloading other read-write operations that can no
longer live on
Hi guys.
I'm do on my pretty vanilla, so I'd like to think, setup this:
-> $ systemd-run --machine=qemu-8-c8kubernode1 /bin/cat
/etc/centos-release
Failed to create bus connection: Input/output error
Someone would care to decipher that for me or/and shed bit
more light on possible troublesho
Am Freitag, dem 30.04.2021 um 10:39 -0400 schrieb Rick Winscot:
> My question for anyone on the list, is the method outlined below a
> reasonable solution to mounting /var early in the start-up cycle?
>
> Or... is there a better way? Some trimming
>
Hi Rick,
by definition if you need to mount /va
On Fri, 30 Apr 2021 at 16:45, Rick Winscot wrote:
>
> We have an embedded product that uses a minimal Linux distribution
generated via Buildroot.
>
> Early in the project it was decided to make the rootfs read-only... in an
effort to improve durability in environments where power fluctuations migh
What is the actual problem you have with a separate /var and systemd-journald?
For completeness sake, which systemd version do you have?
Am Fr., 30. Apr. 2021 um 16:39 Uhr schrieb Rick Winscot
:
>
> We have an embedded product that uses a minimal Linux distribution generated
> via Buildroot.
>
>
We have an embedded product that uses a minimal Linux distribution
generated via Buildroot.
Early in the project it was decided to make the rootfs read-only... in an
effort to improve durability in environments where power fluctuations might
cause problems on the eMMC. At the same time, making log
On Fr, 30.04.21 02:00, Pengpeng Sun (pengpe...@vmware.com) wrote:
> > > Here is where our code calls “/sbin/telinit 6” to reboot Linux.
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvmware%2Fopen-vm-tools%2Fblob%2Fmaster%2Fopen-vm-tools%2FlibDeployPkg%2Flinux
13 matches
Mail list logo
