From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RxvUo-0005ot-SJ for garchives@archives.gentoo.org; Thu, 16 Feb 2012 07:11:19 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3D3D6E0E36; Thu, 16 Feb 2012 07:11:00 +0000 (UTC) Received: from svr-us4.tirtonadi.com (svr-us4.tirtonadi.com [69.65.43.212]) by pigeon.gentoo.org (Postfix) with ESMTP id 67D11E0DC0 for ; Thu, 16 Feb 2012 07:09:59 +0000 (UTC) Received: from mail-lpp01m010-f53.google.com ([209.85.215.53]) by svr-us4.tirtonadi.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.69) (envelope-from ) id 1RxvTb-000aR7-R0 for gentoo-user@lists.gentoo.org; Thu, 16 Feb 2012 14:09:59 +0700 Received: by lahd3 with SMTP id d3so2289115lah.40 for ; Wed, 15 Feb 2012 23:09:55 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.112.48.193 with SMTP id o1mr455845lbn.1.1329376195222; Wed, 15 Feb 2012 23:09:55 -0800 (PST) Received: by 10.112.38.194 with HTTP; Wed, 15 Feb 2012 23:09:55 -0800 (PST) Received: by 10.112.38.194 with HTTP; Wed, 15 Feb 2012 23:09:55 -0800 (PST) In-Reply-To: <20120215225749.0e990290@mini> References: <20120215225749.0e990290@mini> Date: Thu, 16 Feb 2012 14:09:55 +0700 Message-ID: Subject: Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ? From: Pandu Poluan To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=bcaec553fdfae39d5604b90f839e X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - svr-us4.tirtonadi.com X-AntiAbuse: Original Domain - lists.gentoo.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - poluan.info X-Archives-Salt: a927d2bb-3cdf-4dd6-b943-2acae067029b X-Archives-Hash: 415af04895a2fe3aadbd4284293867b3 --bcaec553fdfae39d5604b90f839e Content-Type: text/plain; charset=UTF-8 On Feb 16, 2012 2:01 PM, "Willie Matthews" wrote: > > On Thu, 16 Feb 2012 12:24:45 +0700 > Pandu Poluan 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, --bcaec553fdfae39d5604b90f839e Content-Type: text/html; charset=UTF-8


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,

--bcaec553fdfae39d5604b90f839e--