Re: Root remaining read-only after boot, no obvious reason why

• Subject: Re: Root remaining read-only after boot, no obvious reason why
• From: Dave Re <Dave.Re@xxxxxxxxxxxxx>
• Date: Tue, 16 May 2023 17:26:00 +0000
• Accept-language: en-US
• Cc: "systemd-devel@xxxxxxxxxxxxxxxxxxxxx" <systemd-devel@xxxxxxxxxxxxxxxxxxxxx>
• In-reply-to: <ZGOup9X7DDypxEQ+@kawka3.in.waw.pl>
• Msip_labels:
• References: <CY4PR03MB3141F7CDA1F876B5D2700ECFF7789@CY4PR03MB3141.namprd03.prod.outlook.com> <ZGMnR918ooGcR7GW@kawka3.in.waw.pl> <CY4PR03MB31411D8B075F0EFD89D9FA66F7799@CY4PR03MB3141.namprd03.prod.outlook.com> <ZGOup9X7DDypxEQ+@kawka3.in.waw.pl>

Hmm, so we stopped enabling systemd-remount-fs.service in this way back in 2018 (https://github.com/systemd/systemd/commit/9b69569d2c). At this point, that's ancient history for us ;) We're unfortunately stuck to the RHEL 8 choice for systemd, yeah... ancient for sure. One step I haven't taken is turning on debug level logging in systemd - not sure what to expect (or not expect) out of it, but I guess that's my next step. I'd welcome any pointers to debugging resources, etc, but realize this is an older version of systemd. Dave Re​ Manager, DevOps Engineering www.imprivata.com 20 CityPoint, 6th Floor ​480 Totten Pond Road ​Waltham, MA  02451 The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.  [ImprivataV12018]

• Follow-Ups:
  • Re: Root remaining read-only after boot, no obvious reason why
    • From: Brian Reichert
  • Re: Root remaining read-only after boot, no obvious reason why
    • From: Zbigniew Jędrzejewski-Szmek

• References:
  • Root remaining read-only after boot, no obvious reason why
    • From: Dave Re
  • Re: Root remaining read-only after boot, no obvious reason why
    • From: Zbigniew Jędrzejewski-Szmek
  • Re: Root remaining read-only after boot, no obvious reason why
    • From: Dave Re
  • Re: Root remaining read-only after boot, no obvious reason why
    • From: Zbigniew Jędrzejewski-Szmek

• Prev by Date: Re: idle home NFS gets unmounted although user is still logged in
• Next by Date: Re: Root remaining read-only after boot, no obvious reason why
• Previous by thread: Re: Root remaining read-only after boot, no obvious reason why
• Next by thread: Re: Root remaining read-only after boot, no obvious reason why
• Index(es):
  • Date
  • Thread