Michael Tarr
2004-12-10, 08:58
I have been trying to diagnose the fact that AlienBBC starts fine if
slimserver is started from my shell (tcsh fyi), but does not start up
correct if I startup slimserver via the prefpane or automatically at
boot.
Looking at shell script that is run - Start Slim Server.sh
it all appears okay, indeed, if I run the same command line from this
script manually all works. But not if it is sourced via prefpane or
boot. I am pretty sure it is a path and or search issue. In particular,
when I get the error, I don't see AlienBBC on the web page, but if I go
to the server plugins list, I see "Alien" which is the name of the
folder containing AlienBBC code. So I suspect somehow running under sh
rather than tcsh (or probably bash) causes a different behavior in how
the Plugins folder is parsed.
I am not clear if this is a problem with AlienBBC or something the Slim
people hadn't anticipated - that the plugins folder might contain
another folder full of code. And that under sh it works differently
than more advanced shells.
I don't think I can go beyond this.
FYI, I did try adding /usr/local/bin and /sw/bin to the path in
rc.common to see if it was a path problem in sh, but that didn't seem
to fix things
-m
slimserver is started from my shell (tcsh fyi), but does not start up
correct if I startup slimserver via the prefpane or automatically at
boot.
Looking at shell script that is run - Start Slim Server.sh
it all appears okay, indeed, if I run the same command line from this
script manually all works. But not if it is sourced via prefpane or
boot. I am pretty sure it is a path and or search issue. In particular,
when I get the error, I don't see AlienBBC on the web page, but if I go
to the server plugins list, I see "Alien" which is the name of the
folder containing AlienBBC code. So I suspect somehow running under sh
rather than tcsh (or probably bash) causes a different behavior in how
the Plugins folder is parsed.
I am not clear if this is a problem with AlienBBC or something the Slim
people hadn't anticipated - that the plugins folder might contain
another folder full of code. And that under sh it works differently
than more advanced shells.
I don't think I can go beyond this.
FYI, I did try adding /usr/local/bin and /sw/bin to the path in
rc.common to see if it was a path problem in sh, but that didn't seem
to fix things
-m