Carlos E. R. said the following on 06/08/2011 10:54 AM:
On 2011-06-08 15:24, Anton Aylward wrote:
The automation process needs access but that doesn't mean the relevant directories have to be universal rw.
Windows normally expects RW. If the application they use allows editing the mp3 metadata, it needs RW and will check for it (ie, try to open files RW). Or, it needs RW for the auxiliary files where the other info they need for the station.
Yes, but WHAT rw? Samba doesn't demand the "other" rw bits to be set. Don't forget: Linux system permissions take precedence over Samba permissions. If I have a file -rw------- 1 anton anton 2106714 Nov 18 2009 bookmarks.html then what? I can also use the "read list", "valid users", "admin users" and "invalid users" The first is good- sets READ ONLY. I can also use both userid and group, so I can set a user to be read only if he's not in a specific group. Which gets back to what I was saying earlier. It helps to know a bit about sets when setting up groups. For example, -rw-rw---- 1 anton anton 2106714 Nov 18 2009 bookmarks.html is very different from -rw-rw---- 1 anton users 2106714 Nov 18 2009 bookmarks.html in the second case valid users = .... @users will grant permission, whereas in the first it won't. Of course you still need the username mapping of the Windows login "Joe Sixpack" to the Linux ID "sixpackj" and the entry in /etc/groups I've seen many sites where access control is ignored and "guest" is used and files are rw-rw-rw-. The root cause of this is laziness mixed with frustration. If that's the case then there's no further point in discussing this. -- "We stand behind all of our products, except for the manure spreader." -- Corporate motto of an equipment manufacturer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org