On Fri, Mar 22, 2019 at 06:46:21AM +0200, Mantas Mikulėnas wrote:
> Masking *is* local configuration. It's there so that the admin could
> simulate deleting a unit from /usr, which is considered more-or-less
> read-only; same idea as overriding /usr units in general.
>
> When you've created your
Masking *is* local configuration. It's there so that the admin could
simulate deleting a unit from /usr, which is considered more-or-less
read-only; same idea as overriding /usr units in general.
When you've created your own unit in /etc, there's no point in masking it
if you can just move the
On Fri, Mar 22, 2019 at 07:06:30AM +0300, Andrei Borzenkov wrote:
> 22.03.2019 6:50, Vito Caputo пишет:
> > On Thu, Mar 21, 2019 at 08:49:03PM -0700, Vito Caputo wrote:
> >> I have a local system unit file at /etc/systemd/system/foo.conf, which I
> >> need to mask.
> >
> > Correction:
22.03.2019 6:50, Vito Caputo пишет:
> On Thu, Mar 21, 2019 at 08:49:03PM -0700, Vito Caputo wrote:
>> I have a local system unit file at /etc/systemd/system/foo.conf, which I
>> need to mask.
>
> Correction: /etc/systemd/system/foo.service
>
>>
>> However, when I try to mask it systemctl
On Thu, Mar 21, 2019 at 08:49:03PM -0700, Vito Caputo wrote:
> I have a local system unit file at /etc/systemd/system/foo.conf, which I
> need to mask.
Correction: /etc/systemd/system/foo.service
>
> However, when I try to mask it systemctl complains:
>
> # systemctl --version
> systemd
I have a local system unit file at /etc/systemd/system/foo.conf, which I
need to mask.
However, when I try to mask it systemctl complains:
# systemctl --version
systemd 241 (241.7-2-arch)
+PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ
Hi,
Problem Summary (which I forgot to put in the bug):
/etc/crypttab configured to use /dev/urandom to generate a new key
each boot for encrypted device to be used as swap. The dmcrypt device
is successfully created, and mkswap succeeds, but somewhere just
before (?) swapon the job gets stuck
Hello!
I've come to really love using the sd-bus and sd-event APIs for lightweight
D-Bus access and event loops, and I'm sure I'm not the only one. The amount
of bindings to other languages for stuff like sd-bus. However, this
unfortunately doesn't work in a Flatpak environment, and building the
dear devel
I have a service which fails "Dependency failed for Pacemaker High
Availability Cluster Manager" but that dependency is up & okey(corosync)
(cannot say why pacemaker's systemctl thinks that some dep failed)
So I thought I'd help pacemaker.service by adding:
[Service]
Back then, this is something we have tried and it works. Not with bind
mount though. We also have SD-card as primary storage. As soon as the
storage service mounted the SD-Card, we have created a symbolink link
under /var/log to the persistent and triggered journald flush. It
worked just fine!
On
10 matches
Mail list logo
