On Thu, 16 Feb 2012 12:24:45 +0700 Pandu Poluan <pa...@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! -- Willie Matthews matthews.wil...@gmail.com
