From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 1/2] systemd: install_alternative_tree /lib/systemd/system/
Date: Wed, 1 Oct 2014 15:12:47 +0200 [thread overview]
Message-ID: <20141001131247.GJ16481@pengutronix.de> (raw)
In-Reply-To: <CAMwGMjwEXidPo51ceCtHzGVOMFtCfKEooHxAgm9H4NpneiNnRw@mail.gmail.com>
On Wed, Oct 01, 2014 at 08:06:42AM -0400, Jon Ringle wrote:
> On Tue, Sep 30, 2014 at 4:12 AM, Michael Olbrich <m.olbrich@pengutronix.de>
> wrote:
>
> > On Tue, Sep 30, 2014 at 12:18:43AM -0400, jon@ringle.org wrote:
> > > From: Jon Ringle <jringle@gridpoint.com>
> > >
> > > This allows platform specific customizations to /lib/systemd/system/ to
> > > be installed on the target
> > >
> > > Signed-off-by: Jon Ringle <jringle@gridpoint.com>
> > > ---
> > > rules/systemd.make | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/rules/systemd.make b/rules/systemd.make
> > > index ff3d606..51ffcac 100644
> > > --- a/rules/systemd.make
> > > +++ b/rules/systemd.make
> > > @@ -303,7 +303,7 @@ ifdef PTXCONF_SYSTEMD_NETWORK
> > > endif
> > >
> > > # # units
> > > - @$(call install_tree, systemd, 0, 0, -, /lib/systemd/system/)
> > > + @$(call install_alternative_tree, systemd, 0, 0,
> > /lib/systemd/system/)
> >
> > Are you sure, this is what you want? install_alternative_tree replaces the
> > entire tree, not individual files. You can overwrite individual files by
> > placing your copy in /etc/systemd/system/.
> >
> >
> Normally, systemd enable/disable will create/remove a symlink from
> /etc/systemd/system/ to the corresponding file in /lib/systemd/system/. If
> I put a real file in /etc/systemd/system/, how will systemd handle
> enable/disable of a service?
enable/disable creates links in /etc/systemd/system/*.wants/, so that will
not clash. Only mask/unmask creates symlinks (to /dev/null) in
/etc/systemd/system/. But in my experience masking core systemd units
is rarely needed.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-10-01 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 4:18 jon
2014-09-30 4:18 ` [ptxdist] [PATCH 2/2] systemd: PTXCONF_SYSTEMD_COREDUMP jon
2014-09-30 8:20 ` Michael Olbrich
2014-09-30 8:12 ` [ptxdist] [PATCH 1/2] systemd: install_alternative_tree /lib/systemd/system/ Michael Olbrich
2014-10-01 12:06 ` Jon Ringle
2014-10-01 13:12 ` Michael Olbrich [this message]
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=20141001131247.GJ16481@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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