PDA

View Full Version : cannot get access to /home/myname/mp3



Kevin Davison
2004-04-12, 20:11
Thanks, S. Ben Melhuish. However, I'm still having the same problem. I'm
fairly familiar with 'nix owner and group permissions, but Slimserver just
doesn't want to recognize the directory no matter what permissions I give
it. I've chown'd the entire mp3 directory to slimserver:slimserver
recursively just to see if giving it full access to everything would work.
Negative. It was a good idea to suggest Slimserver wants write privs, but I
don't think it needs those, even though I did give grant that in the example
above. It takes my /home/kevin directory fine. I even did /home/rachel who
is another user just to test and it also took that fine, which is a dir that
doesn't even belong to the mp3 group. It's only when I go in three sub
directories /home/kevin/mp3 that I have issues. I created a new directory
called mp32 to test that and same thing. I'm thinking that I need to check
how slimserver is running. How do I run it as root? Maybe that is my
problem. Or, is there something in a configuration file I can change? This
was so easy before! Thanks again in advance if anyone has some ideas.

Kevin

-----Original Message-----
From: S. Ben Melhuish [mailto:sben (AT) pile (DOT) org]
Sent: Monday, April 12, 2004 8:53 PM
To: Kevin Davison
Subject: [slim] cannot get access to /home/myname/mp3

On Apr 12, 2004, at 4:17 PM, Kevin Davison wrote:

> I get: drwxr-xr-x 143 kevin mp3 4096 Apr 11 18:27 /home/kevin/mp3
>
> Does this mean anything to you? ^^^

By the way, I don't know how comfortable you are with Unix security,
but I didn't see a response to this part of the message, so here's the
quick Unix security tutorial:

drwxr-xr-x 143 kevin mp3 4096 Apr 11 18:27 /home/kevin/mp3
1(2)(3)(4) (5) (6) (7) (8 ) ( 9 ) ( 10 )

1: This indicates that you're looking at a directory.
2: This indicates that the owner (see 6) has read, write, and execute
permissions. (I think directories need to have execute permissions if
you want someone to read them, but I'm not sure about this part, I just
treat it as voodoo.)
3: This indicates that the group (see 7) has read and execute
permissions.
4: This indicates that everyone else has read and execute permissions.
5: I have no idea what this is.
6: The user 'kevin' is the owner.
7: 'mp3' is the group.
8: This directory entry takes up 4KB. (The *contents* of the
directory may be much larger, but all the bookkeeping about what the
directory contains, etc., take up 4096 bytes.)
9: This directory was last modified at this time. (Probably when you
last added a file or changed ownership.)
10: This is the full path to the directory.

2 and 6, together, imply that 'kevin' has full access to the directory.

3, 4, and 7, together, imply that everyone else has read-only access to
the directory.

Security doesn't "inherit", so subdirectories can have entirely
different permissions. You can use the -R (I think) flag on chown and
chmod (the commands which change ownership and permissions,
respectively) to recursively change the directory and all its contents.

As someone suggested, the slimserver wants write permissions, and
doesn't seem to have them.

As far as the chmod command that someone else suggested: Each
permission has a number associated with it; r is 1, w is 2, x is 4.
`chmod 777 [filename]` changes the permissions to "everyone has
read/write/execute access". The directory you listed above has 755
permissions, which is more normal. 775 would be 'kevin' and 'mp3' have
full rights, everyone else has read-only, which is probably close to
what you want for the slimserver.

Hope that helps.

-- S. Ben Melhuish

Pat Farrell
2004-04-12, 20:43
<warning: unix/linux specific stuff follows>

At 11:11 PM 4/12/2004, Kevin Davison wrote:
>Thanks, S. Ben Melhuish. However, I'm still having the same problem. I'm
>fairly familiar with 'nix owner and group permissions, but Slimserver just
>doesn't want to recognize the directory no matter what permissions I give
>it.

If you fire the slimserver up with an explicit log file and lots of verbosity
turned on, you should be able to see what it is whining about , or not finding.

> I'm thinking that I need to check how slimserver is running. How do I
> run it as root? Maybe that is my problem. Or, is there something in a
> configuration file I can change?

How do you start it? the /etc/rc.d/init.d/slimserver script
really wants to be started while you are root, either su
or do a
su -c /etc/rc.d/init.d/slimserver start

or run it by hand, go to the /usr/local/slimserver directory
and run the perl script manually.
you probably should try --d_stdio --d_source . --logfile foo.log

The basic config for the slimserver is specified in
/etc/slimserver.conf

Control for the daemon startup and stop is in
/etc/sysconfig/slimserver

Be careful, is there is no /etc/slimserver.conf, the server will write one
to ~ and call it ~.slimserver.conf which will not show up when you do
a casual ls command due to the leading dot

Try it with a small music library, just a few songs.
Sometimes it can take so long to scan a large library that
I get tired of waiting.

Pat