[gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[Pandu Poluan]

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,
-- 
FdS Pandu E Poluan
~ IT Optimizer ~

 • LOPSA Member #15248
 • Blog : http://pepoluan.tumblr.com
 • Linked-In : http://id.linkedin.com/in/pepoluan

Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[Willie Matthews]

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!

-- 

Willie Matthews
matthews.willie@gmail.com

Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[Pandu Poluan]

[-- 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 --]

Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[J. Roeleveld]

On Thu, February 16, 2012 6:24 am, 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,
> --
> FdS Pandu E Poluan
> ~ IT Optimizer ~
>
>  • LOPSA Member #15248
>  • Blog : http://pepoluan.tumblr.com
>  • Linked-In : http://id.linkedin.com/in/pepoluan
>

Pandu,

I haven't checked the source yet, but I'm wondering if the scripts are
looking for the "conf.d" file in the location:
" ../conf.d " (based from the actual location of the init-script)

Can you try the following:
# mkdir -p /opt/wallmator/initscripts/conf.d
# ln -s /etc/init.d/gatewall /opt/wallmator/initscripts/conf.d/gatewall

and then recreate the original link for the init-script.

-- 
Joost

Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[Pandu Poluan]

[-- Attachment #1: Type: text/plain, Size: 2727 bytes --]

On Feb 16, 2012 3:33 PM, "J. Roeleveld" <joost@antarean.org> wrote:
>
>
> On Thu, February 16, 2012 6:24 am, 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,
> > --
> > FdS Pandu E Poluan
> > ~ IT Optimizer ~
> >
> >  • LOPSA Member #15248
> >  • Blog : http://pepoluan.tumblr.com
> >  • Linked-In : http://id.linkedin.com/in/pepoluan
> >
>
> Pandu,
>
> I haven't checked the source yet, but I'm wondering if the scripts are
> looking for the "conf.d" file in the location:
> " ../conf.d " (based from the actual location of the init-script)
>
> Can you try the following:
> # mkdir -p /opt/wallmator/initscripts/conf.d
> # ln -s /etc/init.d/gatewall /opt/wallmator/initscripts/conf.d/gatewall
>
> and then recreate the original link for the init-script.
>

IIRC, it's the responsibility of runscript to source the relevant config
file in /etc/conf.d, and not the initscript's.

If you peruse the code, you can see that I relied on that feature; there is
no source-ing of any file in /etc/conf.d

Rgds,

[-- Attachment #2: Type: text/html, Size: 3728 bytes --]

Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[Florian Philipp]

[-- Attachment #1: Type: text/plain, Size: 3049 bytes --]

Am 16.02.2012 11:12, schrieb Pandu Poluan:
> 
> On Feb 16, 2012 3:33 PM, "J. Roeleveld" <joost@antarean.org
> <mailto:joost@antarean.org>> wrote:
>>
>>
>> On Thu, February 16, 2012 6:24 am, 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,
>> > --
>> > FdS Pandu E Poluan
>> > ~ IT Optimizer ~
>> >
>> >  • LOPSA Member #15248
>> >  • Blog : http://pepoluan.tumblr.com
>> >  • Linked-In : http://id.linkedin.com/in/pepoluan
>> >
>>
>> Pandu,
>>
>> I haven't checked the source yet, but I'm wondering if the scripts are
>> looking for the "conf.d" file in the location:
>> " ../conf.d " (based from the actual location of the init-script)
>>
>> Can you try the following:
>> # mkdir -p /opt/wallmator/initscripts/conf.d
>> # ln -s /etc/init.d/gatewall /opt/wallmator/initscripts/conf.d/gatewall
>>
>> and then recreate the original link for the init-script.
>>
> 
> IIRC, it's the responsibility of runscript to source the relevant config
> file in /etc/conf.d, and not the initscript's.
> 
> If you peruse the code, you can see that I relied on that feature; there
> is no source-ing of any file in /etc/conf.d
> 
> Rgds,
> 

Yes, but maybe runscript resolves the real file location and then
sources the conf file relative to that location.

Regards,
Florian Philipp


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[Pandu Poluan]

[-- Attachment #1: Type: text/plain, Size: 3379 bytes --]

On Feb 16, 2012 6:14 PM, "Florian Philipp" <lists@binarywings.net> wrote:
>
> Am 16.02.2012 11:12, schrieb Pandu Poluan:
> >
> > On Feb 16, 2012 3:33 PM, "J. Roeleveld" <joost@antarean.org
> > <mailto:joost@antarean.org>> wrote:
> >>
> >>
> >> On Thu, February 16, 2012 6:24 am, 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,
> >> > --
> >> > FdS Pandu E Poluan
> >> > ~ IT Optimizer ~
> >> >
> >> >  • LOPSA Member #15248
> >> >  • Blog : http://pepoluan.tumblr.com
> >> >  • Linked-In : http://id.linkedin.com/in/pepoluan
> >> >
> >>
> >> Pandu,
> >>
> >> I haven't checked the source yet, but I'm wondering if the scripts are
> >> looking for the "conf.d" file in the location:
> >> " ../conf.d " (based from the actual location of the init-script)
> >>
> >> Can you try the following:
> >> # mkdir -p /opt/wallmator/initscripts/conf.d
> >> # ln -s /etc/init.d/gatewall /opt/wallmator/initscripts/conf.d/gatewall
> >>
> >> and then recreate the original link for the init-script.
> >>
> >
> > IIRC, it's the responsibility of runscript to source the relevant config
> > file in /etc/conf.d, and not the initscript's.
> >
> > If you peruse the code, you can see that I relied on that feature; there
> > is no source-ing of any file in /etc/conf.d
> >
> > Rgds,
> >
>
> Yes, but maybe runscript resolves the real file location and then
> sources the conf file relative to that location.
>

Most likely. Didn't use to be like that, though.

Oh well, I'll just add an explicit source then.

Rgds,

[-- Attachment #2: Type: text/html, Size: 5076 bytes --]

Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[J. Roeleveld]

On Thu, February 16, 2012 12:39 pm, Pandu Poluan wrote:
> On Feb 16, 2012 6:14 PM, "Florian Philipp" <lists@binarywings.net> wrote:
>>
>> Am 16.02.2012 11:12, schrieb Pandu Poluan:
>> >
>> > On Feb 16, 2012 3:33 PM, "J. Roeleveld" <joost@antarean.org
>> > <mailto:joost@antarean.org>> wrote:

<SNIP>

>> >>
>> >> Pandu,
>> >>
>> >> I haven't checked the source yet, but I'm wondering if the scripts
>> are
>> >> looking for the "conf.d" file in the location:
>> >> " ../conf.d " (based from the actual location of the init-script)
>> >>
>> >> Can you try the following:
>> >> # mkdir -p /opt/wallmator/initscripts/conf.d
>> >> # ln -s /etc/init.d/gatewall
>> /opt/wallmator/initscripts/conf.d/gatewall
>> >>
>> >> and then recreate the original link for the init-script.
>> >>
>> >
>> > IIRC, it's the responsibility of runscript to source the relevant
>> config
>> > file in /etc/conf.d, and not the initscript's.
>> >
>> > If you peruse the code, you can see that I relied on that feature;
>> there
>> > is no source-ing of any file in /etc/conf.d
>> >
>> > Rgds,
>> >
>>
>> Yes, but maybe runscript resolves the real file location and then
>> sources the conf file relative to that location.
>>
>
> Most likely. Didn't use to be like that, though.
>
> Oh well, I'll just add an explicit source then.
>
> Rgds,
>

Did those little commands work then? I didn't test them myself.

--
Joost


-- 
Joost

Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[Pandu Poluan]

[-- Attachment #1: Type: text/plain, Size: 1680 bytes --]

On Feb 16, 2012 6:48 PM, "J. Roeleveld" <joost@antarean.org> wrote:
>
>
> On Thu, February 16, 2012 12:39 pm, Pandu Poluan wrote:
> > On Feb 16, 2012 6:14 PM, "Florian Philipp" <lists@binarywings.net>
wrote:
> >>
> >> Am 16.02.2012 11:12, schrieb Pandu Poluan:
> >> >
> >> > On Feb 16, 2012 3:33 PM, "J. Roeleveld" <joost@antarean.org
> >> > <mailto:joost@antarean.org>> wrote:
>
> <SNIP>
>
> >> >>
> >> >> Pandu,
> >> >>
> >> >> I haven't checked the source yet, but I'm wondering if the scripts
> >> are
> >> >> looking for the "conf.d" file in the location:
> >> >> " ../conf.d " (based from the actual location of the init-script)
> >> >>
> >> >> Can you try the following:
> >> >> # mkdir -p /opt/wallmator/initscripts/conf.d
> >> >> # ln -s /etc/init.d/gatewall
> >> /opt/wallmator/initscripts/conf.d/gatewall
> >> >>
> >> >> and then recreate the original link for the init-script.
> >> >>
> >> >
> >> > IIRC, it's the responsibility of runscript to source the relevant
> >> config
> >> > file in /etc/conf.d, and not the initscript's.
> >> >
> >> > If you peruse the code, you can see that I relied on that feature;
> >> there
> >> > is no source-ing of any file in /etc/conf.d
> >> >
> >> > Rgds,
> >> >
> >>
> >> Yes, but maybe runscript resolves the real file location and then
> >> sources the conf file relative to that location.
> >>
> >
> > Most likely. Didn't use to be like that, though.
> >
> > Oh well, I'll just add an explicit source then.
> >
> > Rgds,
> >
>
> Did those little commands work then? I didn't test them myself.
>

Neither have I, actually. Already on my way home when you suggested the
commands.

Will try them tomorrow and report here.

Rgds,

[-- Attachment #2: Type: text/html, Size: 2701 bytes --]

Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 250 bytes --]

On Thu, 16 Feb 2012 18:39:16 +0700, Pandu Poluan wrote:

> Oh well, I'll just add an explicit source then.

Or use a hardlink instead of a symlink.


-- 
Neil Bothwick

If you think the problem is bad now, just wait until we've solved it.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[Pandu Poluan]

[-- Attachment #1: Type: text/plain, Size: 458 bytes --]

On Feb 16, 2012 7:00 PM, "Neil Bothwick" <neil@digimed.co.uk> wrote:
>
> On Thu, 16 Feb 2012 18:39:16 +0700, Pandu Poluan wrote:
>
> > Oh well, I'll just add an explicit source then.
>
> Or use a hardlink instead of a symlink.
>
>

I tend to stay away from hardlinks; ls IIRC can't differentiate between
hardlinks and normal files. Thus, there's a possibility that I forgot and
accidentally change the one in /opt, which then get pushed to bitbucket.

Rgds,

[-- Attachment #2: Type: text/html, Size: 617 bytes --]

Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]

On Thu, 16 Feb 2012 19:35:50 +0700, Pandu Poluan wrote:

> > Or use a hardlink instead of a symlink.

> I tend to stay away from hardlinks; ls IIRC can't differentiate between
> hardlinks and normal files.

There is no difference. A normal file entry in a directory is still a
hardlink, what we generally call hardlinks are just additional copies,
it's all the same file.

> Thus, there's a possibility that I forgot
> and accidentally change the one in /opt, which then get pushed to
> bitbucket.

It doesn't matter where you change it when there's only one file. It
means you can put the file where openrc seems to want it and keep it in
your separate directory as you want.

However, if symlinks have stopped working, there was either a conscious
design decision or you've found a new bug.


-- 
Neil Bothwick

Despite the cost of living it remains popular.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[Pandu Poluan]

[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]

On Feb 16, 2012 8:41 PM, "Neil Bothwick" <neil@digimed.co.uk> wrote:
>
> On Thu, 16 Feb 2012 19:35:50 +0700, Pandu Poluan wrote:
>
> > > Or use a hardlink instead of a symlink.
>
> > I tend to stay away from hardlinks; ls IIRC can't differentiate between
> > hardlinks and normal files.
>
> There is no difference. A normal file entry in a directory is still a
> hardlink, what we generally call hardlinks are just additional copies,
> it's all the same file.
>
> > Thus, there's a possibility that I forgot
> > and accidentally change the one in /opt, which then get pushed to
> > bitbucket.
>
> It doesn't matter where you change it when there's only one file. It
> means you can put the file where openrc seems to want it and keep it in
> your separate directory as you want.
>

What I meant was, I rely on ls to remind me (or other sysadmins) that the
file is special and should not be edited willy-nilly.

That's because the wallmator package is still under development, and it's
synchronized between firewalls using mercurial.

I don't want a well-meaning but misguided minion to 'taint' the mercurial
repo.

> However, if symlinks have stopped working, there was either a conscious
> design decision or you've found a new bug.
>
>

Do you think I should bring this question to -dev, or file a bug?

Rgds,

[-- Attachment #2: Type: text/html, Size: 1654 bytes --]

Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 672 bytes --]

On Thu, 16 Feb 2012 23:14:19 +0700, Pandu Poluan wrote:

> What I meant was, I rely on ls to remind me (or other sysadmins) that
> the file is special and should not be edited willy-nilly.

> I don't want a well-meaning but misguided minion to 'taint' the
> mercurial repo.

Makes sense.

> > However, if symlinks have stopped working, there was either a
> > conscious design decision or you've found a new bug.

> Do you think I should bring this question to -dev, or file a bug?

I'd file a bug, then progress can be tracked. If it is a design decision,
the bug will be closed soon enough.


-- 
Neil Bothwick

In space, no one can hear you fart.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Can no longer use symlinks in /etc/init.d with openrc-0.9.8.4 ?

[William Hubbs]

[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]

On Thu, Feb 16, 2012 at 08:31:21PM +0000, Neil Bothwick wrote:
> On Thu, 16 Feb 2012 23:14:19 +0700, Pandu Poluan wrote:
> 
> > What I meant was, I rely on ls to remind me (or other sysadmins) that
> > the file is special and should not be edited willy-nilly.
> 
> > I don't want a well-meaning but misguided minion to 'taint' the
> > mercurial repo.
> 
> Makes sense.
> 
> > > However, if symlinks have stopped working, there was either a
> > > conscious design decision or you've found a new bug.
> 
> > Do you think I should bring this question to -dev, or file a bug?
> 
> I'd file a bug, then progress can be tracked. If it is a design decision,
> the bug will be closed soon enough.

All,

actually this is an issue which whas been around since the beginning of
openrc. We thought we had a fix, but the fix caused several regressions
and was reverted:

https://bugs.gentoo.org/show_bug.cgi?id=350910.

If you read that bug, the issue is pretty complex, because it relates to
the location and name of the conf.d file as well as the settings of
some of  openrc's environment variables.

I haven't looked at this issue in a while, but I can say that the fix is
far from trivial.

William

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]