Well, the subject says it all: I had masked a socket unit and the related non-socket-unit failed to start. Trying to see the definition of the unit with "systemctl cat" I only saw "# /dev/null". Is that intended? "systemctl show" still shows a lot of data... My idea was when "unmask" knows how to get the unit, why shouldn't "cat" be able to, too? (systemd-234-24.64.1.x86_64 of SLES15 SP2) Regards, Ulrich _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Is it intentional that "systemctl cat" outputs "# /dev/null" for a masked unit?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Is it intentional that "systemctl cat" outputs "# /dev/null" for a masked unit?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 02 Feb 2021 10:34:50 +0100
- Follow-Ups:
- Re: Is it intentional that "systemctl cat" outputs "# /dev/null" for a masked unit?
- From: Lennart Poettering
- Re: Is it intentional that "systemctl cat" outputs "# /dev/null" for a masked unit?
- Prev by Date: udev blkid check on mmcblk0boot0 and boot1
- Next by Date: Still confused with socket activation
- Previous by thread: udev blkid check on mmcblk0boot0 and boot1
- Next by thread: Re: Is it intentional that "systemctl cat" outputs "# /dev/null" for a masked unit?
- Index(es):
 |