From: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
To: development@lists.ipfire.org
Subject: Re: [systemd-devel] Make systemctl is-enabled work for templated units
Date: Tue, 21 May 2013 15:30:08 +0200 [thread overview]
Message-ID: <20130521133008.GQ3394@in.waw.pl> (raw)
In-Reply-To: <1368971148.1836.45.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
On Sun, May 19, 2013 at 03:45:48PM +0200, Michael Tremer wrote:
> Hello guys,
>
> in this mail, you will find a patch which resolves the problem, that
> 'systemctl is-enabled' does not work for templated units.
Applied!
> See also https://bugs.freedesktop.org/show_bug.cgi?id=55318 for
> reference.
>
> Without this patch, systemctl is-enabled something(a)abc.service
> returned "No such file or directory", because it was checked
> if /usr/lib/systemd/system/something(a)abc.service, etc. existed,
> which is obviously not the case.
Actually, we can mask instance units, so "obviously" is not true.
And we can also "concretize" instance units by adding a normal
unit file for the instance. I tweaked your patch to just
ignore ENOENT for instance units, but perform the checks.
> If systemctl is-enabled is called for templated units, this
> check should be omitted and it should be searched for symlinks
> in the /etc paths right away.
Actually links can appear not just in /etc, so this part of the
description is misleading.
> I would like to request that this is merged to the systemd git tree.
This is implied :)
Zbyszek
next prev parent reply other threads:[~2013-05-21 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 13:45 Michael Tremer
2013-05-21 13:30 ` Zbigniew Jędrzejewski-Szmek [this message]
2013-05-21 13:47 ` [systemd-devel] " Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130521133008.GQ3394@in.waw.pl \
--to=zbyszek@in.waw.pl \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox