From: Steffen Sledz <sledz@dresearch-fe.de>
To: "Kang Kai" <kai.kang@windriver.com>,
"Martin Jansa" <Martin.Jansa@gmail.com>,
"Chen Qi" <Qi.Chen@windriver.com>,
"Ross Burton" <ross.burton@intel.com>,
"Radu Moisan" <radu.moisan@intel.com>,
openembedded-core <openembedded-core@lists.openembedded.org>,
"Andreas Müller" <schnitzeltony@googlemail.com>,
"Khem Raj" <raj.khem@gmail.com>,
"Koen Kooi" <koen@dominion.thruhere.net>,
"Jonathan Liu" <net147@gmail.com>
Subject: systemd service vs. update-alternatives (was rsyslog: buggy systemd/ua handling?)
Date: Thu, 19 Nov 2015 15:34:12 +0100 [thread overview]
Message-ID: <564DDDE4.20002@dresearch-fe.de> (raw)
In-Reply-To: <564CA3F8.9020404@dresearch-fe.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 18.11.2015 17:14, Steffen Sledz wrote:
> On 17.11.2015 09:08, Steffen Sledz wrote:
>> On 16.11.2015 12:28, Steffen Sledz wrote:
>>> I'm not sure but i believe there's a bug in the systemd/ua-handling in meta-oe/recipes-extended/rsyslog/rsyslog_7.6.1.bb.
>>>
>>> In my opinion this code
>>>
>>> if bb.utils.contains('DISTRO_FEATURES', 'systemd', True, False, d): pn = d.getVar('PN', True) d.appendVar('ALTERNATIVE_%s' % (pn), ' syslog-service') d.setVarFlag('ALTERNATIVE_LINK_NAME', 'syslog-service', '%s/systemd/system/syslog.service' % (d.getVar('sysconfdir', True))) d.setVarFlag('ALTERNATIVE_TARGET', 'syslog-service', '%s/system/rsyslog.service' % (d.getVar('systemd_unitdir', True)))
>>>
>>> registers the systemd service file under the (ua-)name "syslog-service". So it should not be
>>>
>>> SYSTEMD_SERVICE_${PN} = "${BPN}.service"
>>>
>>> but
>>>
>>> SYSTEMD_SERVICE_${PN} = "syslog.service"
>>>
>>> Right?
>>
>> Hi experts! Is my assumption correct? If yes i would prepare patches for master, fido and jethro.
The problem seems to be much more complex then I thought before. :(
The systemd integration for busybox-syslog was introduced by commit cf3618f9a57e46fb78d5be35d473e2dd5290e961.
The do_install stage got among others this line:
ln -sf /dev/null ${D}${systemd_unitdir}/system/syslog.service
I believe this was made to avoid a package error like this:
ERROR: Function failed: SYSTEMD_SERVICE_busybox-syslog value syslog.service does not exist
But if another syslog alternative (rsyslog or syslog-ng) will do the same this leads to another error:
ERROR: The recipe busybox is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/home/sledz/work/hipos-dfe.fido/build-closed/tmp-glibc/sysroots/himx0294/lib/systemd/system/syslog.service
So what is th right way to bring a systemd service file and update-alternatives together???
- --
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBAgAGBQJWTd3kAAoJEIz5slJ1krPh0f4QAIoQcwiyYs1l1lCCFhg96xry
5wFMCFDdtCCPerpLBPHh0nLcqB5z0JKV9wCfuZu2QBZbh49s/0Qg4F09yN7qT2Bb
auP3yEVIZrekuVIpQYkXOTI5q+1DrC4QCGMFfm7XaJZiqdOBaP9t1xWMQxzA5W3M
OyQCH3JDABkD9UJQbsYLs1Qq6jm1rzbD1ZO5Uv0JvZaW+ZyHvDUHN7M+nlCxWFKE
HPTtri1trgg9iZYZgTG0y2WferO5Unug5TKrFMSLiKv8iwOGha2O45m9nsFWCzZL
vQ+6z1mnL9syVy6kmOakmc2Q+RnSC6Zx2Y3GbPuUMGtn4Y3neole6YaMJ0Yl+Uk7
nn49/f7qxAD6sYJu7YaD0oBbEj/ugKbtFzKcwWjAe365h21Cndt2NkhELr1xUk7/
owwVD60mmPHGCQ6ugT6wSnmLAVO4P5td5HLuDKWIDV2Smtm3XAQ2MQ52vFzr53sh
dyUq3e5J9zuDbYWmC5xRvv77H7R6eUCltkGNHg5JjkbqtUw4NQWteaHTUpM7KlI1
23w0nDU1xACpJDs+TgMzNyo7c+0b0g0SKjw07Qo7aIdNJuHoeik+hJIewMU7KDdl
BjHy1PIFqXdSPR3myMOMOXlDCYJLJSy19roOr067LSiwXSEwycj93AsqMNzaGSWS
8o0HjDbiMarMi2aXCyCH
=4bav
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-11-19 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 11:28 rsyslog: buggy systemd/ua handling? Steffen Sledz
2015-11-17 8:08 ` Steffen Sledz
[not found] ` <564CA3F8.9020404@dresearch-fe.de>
2015-11-19 14:34 ` Steffen Sledz [this message]
2015-11-20 9:06 ` systemd service vs. update-alternatives (was rsyslog: buggy systemd/ua handling?) ChenQi
2015-11-20 13:42 ` Steffen Sledz
2015-11-23 10:26 ` Steffen Sledz
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=564DDDE4.20002@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=Martin.Jansa@gmail.com \
--cc=Qi.Chen@windriver.com \
--cc=kai.kang@windriver.com \
--cc=koen@dominion.thruhere.net \
--cc=net147@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=radu.moisan@intel.com \
--cc=raj.khem@gmail.com \
--cc=ross.burton@intel.com \
--cc=schnitzeltony@googlemail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.