Chris,
Your e-mail was helpful to me, thank you.
With it, and another resource I was able to figure out our problem. I’ll put
out there, for posterity, that there is another factor that these play off of.
In Windows, you define whether or not a
share is writeable or not and it doesn’t just become the default, it becomes
the only option. With Samba, if a share is ‘writable = no’, that is only the
default behavior. You can modify it with ‘write list = ‘. So, in my example…
(or readonly = yes ? correct me if I’m wrong there.)
‘Maybe giving me an example would be
easier. Say I have 2 groups; ShareRW and ShareR. I want the people in ShareRW
to be able to browse, read, and write, and the people in ShareR to browse and
read only. What is/are the possible configuration(s) for that scenario?’
Valid users = @ShareRW @ShareR
Write list = @ShareRW
It looks like the ‘write list’ is only
valid if the writeable = no, and I bet the read list is only valid if writeable
= yes… its possible, too, that readonly=yes has different behavior than writeable=no.
Maybe someone can shed some light on
that?
Again, thanks!
Andy
From:
plug-bounces@lists.phillylinux.org [mailto:plug-bounces@lists.phillylinux.org] On Behalf Of W. Chris Shank
Sent: Tuesday, November 14, 2006
10:53 PM
To: Philadelphia Linux User's
Group Discussion List
Subject: [Check] - Re: [PLUG]
Samba 3 question - Email found in subject
-Valid Users/Groups
user that are allowed to connect to a particular service - Read or Write access
TBD by other settings
-Invalid
Users/Groups
users that
are never allowed to connect to a service 0 regardless of RW settings
-Possible Users/Groups
never heard
of this
-Read only
Users/Groups
can only
read - users here with no valid user listing are assumed valid
-Read/write
Users/Groups
same as
above but with read and write