On Feb 16, 2012 6:48 PM, "J. Roeleveld" <jo...@antarean.org> wrote: > > > On Thu, February 16, 2012 12:39 pm, Pandu Poluan wrote: > > On Feb 16, 2012 6:14 PM, "Florian Philipp" <li...@binarywings.net> wrote: > >> > >> Am 16.02.2012 11:12, schrieb Pandu Poluan: > >> > > >> > On Feb 16, 2012 3:33 PM, "J. Roeleveld" <jo...@antarean.org > >> > <mailto:jo...@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,
