Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: All the syslogs
Date: Fri, 07 May 2010 12:59:58 +0200	[thread overview]
Message-ID: <4BE3F2AE.8060305@dresearch.de> (raw)
In-Reply-To: <4BE3C542.4070603@dresearch.de>

> OK, than i'll try to create an u-a setting for all the syslogs (btw: we
> have not three but four different ones, there's sysklogd too).
> 
> Has anyone combined update-alternatives and update-rc.d for initscripts
> before? I'm afraid there are some pitfalls in the naming of the initscript
> itself and the symlinks.

I made some first tests and they confirmed my fears. :(

The recipes look like this:

-------------------->snip<---------------------------
inherit autotools update-rc.d

do_install_append() {
        ...
        install -m 755 ${WORKDIR}/initscript ${D}/${sysconfdir}/init.d/syslog.${PN}
}

pkg_postinst_${PN} () {
    update-alternatives --install ${sysconfdir}/init.d/syslog syslog-init syslog.${PN} 300
}

pkg_prerm_${PN} () {
    update-alternatives --remove syslog-init syslog.${PN}
}

INITSCRIPT_NAME = "syslog"
-------------------->snip<---------------------------

When opkg installs the packages it wants to run update-rc.d *before*
update-alternatives. This results in an "file does not exist" error. :(

  Installing rsyslog (5.5.4-r1.0.5) to root...
  Installing busybox-syslog (1.13.2-r24.1.5) to root...
  Configuring rsyslog
  update-rc.d: /etc/init.d/syslog: file does not exist
  update-alternatives: Linking //etc/init.d/syslog to syslog.rsyslog

Any suggestions?

Regards,
Steffen

-- 
Steffen Sledz
DResearch Digital Media Systems GmbH
Otto-Schmirgal-Str.3, D-10319 Berlin, Germany
Tel: +49 (30) 515932237 mailto:sledz@DResearch.DE
Fax: +49 (30) 515932299 http://www.DResearch.DE
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 54412;
Ust.-IDNr. DE169013825; WEEE Reg.-Nr. DE 85995642




  reply	other threads:[~2010-05-07 11:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  6:04 All the syslogs Steffen Sledz
2010-05-06  6:13 ` Koen Kooi
2010-05-07  7:46   ` Steffen Sledz
2010-05-07 10:59     ` Steffen Sledz [this message]
2010-05-07 11:09       ` Martin Jansa
2010-05-07 13:02         ` Steffen Sledz
2010-05-07 13:08           ` Martin Jansa
2010-05-07 14:04             ` Steffen Sledz
2010-05-07 14:20               ` [PATCH] busybox/syslogs: use update-alternatives for syslog selection Steffen Sledz
2010-05-07 14:49                 ` Martin Jansa
2010-05-07 15:04                   ` Steffen Sledz
2010-05-10  8:30                     ` Martin Jansa
2010-05-07 14:58                 ` Martin Jansa
2010-05-07 15:08                   ` Steffen Sledz
2010-05-07 15:34                 ` [PATCH v2] " Steffen Sledz
2010-05-07 14:52               ` All the syslogs Martin Jansa
2010-05-12 12:10                 ` [PATCH v3] busybox/syslogs: use update-alternatives for syslog selection Steffen Sledz
2010-05-12 12:21                   ` Martin Jansa
2010-05-12 12:50                     ` [PATCH v4] " Steffen Sledz
2010-05-13 18:55                       ` Sledz, Steffen
2010-05-17 11:11                       ` Martin Jansa

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=4BE3F2AE.8060305@dresearch.de \
    --to=sledz@dresearch.de \
    --cc=openembedded-devel@lists.openembedded.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