After I wrote the above I got curious as to where that "~" was coming
from. It appears to be coming from the default cache setting that is
determined in Prefs.pm. It concatenates $ENV{'HOME'} and "Cache" to
come up with a default value, and then does some checks to see if it
exists, and if not, whether the parent is writeable. If the parent
isn't writeable, it undef's the variable.
So it appeared to me that it wasn't properly picking up the value of
the HOME variable. I created a simple two-line Perl script to
determine what $ENV{'HOME'} evaluates to when invoked through the
"startproc" command used on SuSE (the second line spits out the output
of the "id" command for reference). Here's the output:
Code:
--------------------
dominion:~ # /tmp/test.pl
HOME = /root
User = uid=0(root) gid=0(root) groups=0(root)
dominion:~ # startproc -u slimserver /tmp/test.pl
HOME = /root
User = uid=1008(slimserver) gid=1002(slimserver)
groups=14(uucp),16(dialout),17(audio),33(video),1002(slimserver)
--------------------
So, for some reason it's not picking up the right HOME variable when
invoked through startproc. Of course, I'm using an ancient version of
SuSE (9.1 Professional) with Perl 5.8.3. I'm in the process of
building a new server and will put openSuSE 10.2 on it. I'll watch to
see if it makes a difference.
--
AubreyCTurnerJr
------------------------------------------------------------------------
AubreyCTurnerJr's Profile: http://forums.slimdevices.com/member.php?userid=9795
View this thread: http://forums.slimdevices.com/showthread.php?t=32200
_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
