From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?
Date: Thu, 16 Feb 2012 14:09:55 +0700 [thread overview]
Message-ID: <CAA2qdGUfAu2jG42Hr1LJB453ma-vxv5DwMV_CY2HfY-VEL=rXA@mail.gmail.com> (raw)
In-Reply-To: <20120215225749.0e990290@mini>
[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]
On Feb 16, 2012 2:01 PM, "Willie Matthews" <matthews.willie@gmail.com>
wrote:
>
> On Thu, 16 Feb 2012 12:24:45 +0700
> Pandu Poluan <pandu@poluan.info> wrote:
>
> > I am wondering if any of you had experienced the same difficulty as
> > me:
> >
> > A couple of days ago, I upgraded openrc from (whatever version it was
> > previously) to 0.9.8.4.
> >
> > One of the scripts in /etc/init.d was a symlink
> > to /opt/some/package/path
> >
> > (To be precise, /etc/init.d/gatewall ->
> > /opt/wallmator/initscripts/gentoo/gatewall.init)
> >
> > ((wallmator is a "Firewall Automator" script I'm developing))
> >
> > This morning, I rebooted. Upon time to execute the "gatewall" script,
> > it complained that some settings (set through /etc/conf.d/gatewall are
> > not set). I double-checked the settings it complained; yep, they are
> > there in /etc/conf.d/gatewall.
> >
> > I tried `/etc/init.d/gatewall start`, no luck. It still complains of
> > some vital non-optional settings not being set.
> >
> > So, I replaced the symlink:
> >
> > cd /etc/init.d
> > mv gatewall gatewall.old
> > cp /opt/wallmator/initscripts/gentoo/gatewall.init gatewall
> >
> > And tried again `/etc/init.d/gatewall start` ... it worked!!
> >
> > So I tried `shutdown -r now` ... there's joy in Mudville! The
> > "gatewall" initscript now properly reads the settings in
> > /etc/conf.d/gatewall.
> >
> > My question is: Is there a change of behavior in how openrc executes a
> > script in /etc/init.d/ when said script is a symlink instead of a
> > 'normal' file?
> >
> > PS: For this particular system, everything under / except /boot
> > resides in the same filesystem.
> >
> > PPS: For the contents of the "gatewall" initscript, see
> >
https://bitbucket.org/pepoluan/wallmator/src/edae2e294d07/initscript/gentoo/gatewall.init
> >
> > Rgds,
>
> I didn't have that problem and upgraded yesterday!
>
Hmmm... strange... I can still work around the problem, though. Just
manually source the relevant file in /etc/conf.d.
Thanks for the info.
Rgds,
[-- Attachment #2: Type: text/html, Size: 2837 bytes --]
next prev parent reply other threads:[~2012-02-16 7:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 5:24 [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ? Pandu Poluan
2012-02-16 6:57 ` Willie Matthews
2012-02-16 7:09 ` Pandu Poluan [this message]
2012-02-16 8:34 ` J. Roeleveld
2012-02-16 10:12 ` Pandu Poluan
2012-02-16 11:11 ` Florian Philipp
2012-02-16 11:39 ` Pandu Poluan
2012-02-16 11:51 ` J. Roeleveld
2012-02-16 12:32 ` Pandu Poluan
2012-02-16 11:57 ` Neil Bothwick
2012-02-16 12:35 ` Pandu Poluan
2012-02-16 13:38 ` Neil Bothwick
2012-02-16 16:14 ` Pandu Poluan
2012-02-16 20:31 ` Neil Bothwick
2012-03-18 22:14 ` William Hubbs
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='CAA2qdGUfAu2jG42Hr1LJB453ma-vxv5DwMV_CY2HfY-VEL=rXA@mail.gmail.com' \
--to=pandu@poluan.info \
--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