Lots of points, I'll try to address them all but I'm sure I'll miss some
so don't worry about more messages.

But first some questions:
Q. Are you logged in as root or as a specific user id when running
slimserver with the problem 

Q. What is the owner (user & group) and permissions (owner, group and
world) of /usr /usr/local at startup, before and after you make the
"wrx" permissions change.  Next time - try changing to "r", then "rw"
then "rwx" - which ones work ?

I think some of the problem relates to user id and permissions so
details & specifics are v. important.  When slimserver starts - it
loads modules on the search path. The "x" of the permissions enables
directory searching.

Regarding your question about running slimserver and not returning to
user.  If the "--daemon" command line option is NOT used, Slimserver
will runs as an ordinary process and stay attached to the shell. All
log/debug message as well as being sent to log file are also sent to
STDERR which is the terminal.  If you use "--daemon" on the command
line, then log output will only appear in the log file.

When slimserver starts - it tries to open with write access two files -
the preferences and log files.  If the existing log & pref files owner
or permissions are not "right" - slimserver startup will be affected. 
What are the user id and permission of the preference and log file at
startup before running Slimserver.  What are their owner & permissions
after a successful start of slimserver ?

When starting slimserver during these test, to get better info about
startup progress, use --d_start, --d_server and --d_plugins


-- 
bpa
------------------------------------------------------------------------
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread: http://forums.slimdevices.com/showthread.php?t=36596

_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/unix

Reply via email to