On Thu, 2012-01-05 at 18:08 +0800, Mathieu Bridon wrote:
> The systemd.mount(5) manual says:
> If the mount point is not existing at time of mounting, it
> is created.
>
> That seems to work fine when I run manually:
[... snip ...]
> However, when the unit is run at boot-time (because it has b
mount command in the latest version of util-linux(2.21-rc1[1])
supports /etc/fstab.d; mount command reads /etc/fstab.d/*.fstab
files as if they are written in /etc/fstab.
The benefits of .d mechanism are explained in [2][3].
With this patch, systemd can handle /etc/fstab.d/*.fstab.
How to try it
Colin Guthrie wrote:
> However, if I do: "systemctl enable [email protected]" I get
> the
> same error as above.
>
>
> Do you agree that when calling this command it should work and enable
> things as needed? It would obviously mean supporting %i/%I in the
> [Install] section's Alias opti
Is there any reason that systemctl --quiet enable foo.service will print
out the ln -s command on stderr and ditto for disable and it's rm command?
I'd have thought a --quiet argument should suppress that? Also, it's not
really an error so not sure why it's on stderr.
If it were on stdout, I'd ha
Hi,
during the builds for Fedora/s390x I've found that systemd v38 fails to
build on big-endian platforms.
...
make[2]: Entering directory `/root/systemd'
CC src/journal/libsystemd_journal_la-sd-journal.lo
src/journal/sd-journal.c: In function 'init_location':
src/journal/sd-journal.c:69:22
Hi,
Previously I've asked why "systemctl enable dm.service" results in a
(cryptic) error:
Failed to issue method call: No such file or directory
While that is something I ultimately intend to fix (i.e. give a clearer
error message) this is the expected behaviour as dm.service is really an
alias
