public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Non-opnerc init scripts
Date: Mon, 21 May 2018 16:11:05 -0400	[thread overview]
Message-ID: <CAGfcS_=mk+0SS22kqzyP9QVLN7YN408XAq+7j6NmwjtFvBH3pQ@mail.gmail.com> (raw)
In-Reply-To: <20180521194307.qqz4luwnjmzjsbhc@matica.foolinux.mooo.com>

On Mon, May 21, 2018 at 3:43 PM Ian Zimmerman <itz@very.loosely.org> wrote:

> openrc scripts have their own "API".  Converting a straight sysvinit
> script into an openrc one takes some work.  Look at some existing
> openrc script to see the kind of work that is needed.


Unless the upstream script does quite a bit you're usually better off
starting with a generic OpenRC init.d script and just tweaking it vs trying
to convert a non-openrc script into an openrc one.

Another option is to just create an openrc script wrapper that just calls
the upstream one, which is installed elsewhere.

Ideally though you want to get pid files and such to show up in the right
place.  However, if this is for oss I'm not sure you're even launching any
daemons vs just setting mixer levels and such.  If you aren't actually
leaving any processes running calling the upstream script from a wrapper
should be pretty harmless.  I haven't used openrc since it got cgroup
support but I suspect it is better about cleaning up orphans these days as
well.

-- 
Rich


      reply	other threads:[~2018-05-21 20:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 18:22 [gentoo-user] Non-opnerc init scripts Klaus Ethgen
2018-05-21 19:43 ` [gentoo-user] " Ian Zimmerman
2018-05-21 20:11   ` Rich Freeman [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='CAGfcS_=mk+0SS22kqzyP9QVLN7YN408XAq+7j6NmwjtFvBH3pQ@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-user@lists.gentoo.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