I'm still a bit confused on your problem. I had several Samba problems in
the same configuration area as well and unintentionally became quite
knowledgable at the million ways NOT to configure Samba. Perhaps you could
provide a 'ls -l' of the dir itself plus its contents.
Here is an example of a locked-down directory on my system that is used for
development. It was the best I could do with the notoriously poor security
in Windows. I could have used masks of 0660 as well but most Windows boxes
seem intent on declaring everything executable (and this directory is not
accessed in Linux normally).
[SI]
comment = Source Integrity
browseable = yes
path = /data/SI
public = no
guest only = no
writable = yes
only user = no
write list = mzaleski, apalande, kboyd2, kvangord, jchen42
force user = mzaleski
force group = VDOuser
create mask = 0770
directory mask = 0770
force create mask = 0770
force directory mask = 0770
oplocks = True
> -----Original Message-----
> From: Leopold Palomo [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 29, 2000 5:50 PM
> To: [EMAIL PROTECTED]
> Cc: Bill Shirley
> Subject: Re: [expert] Strange problem with the users with Samba
>
>
> Bill Shirley ha escrit:
>
> > You sure didn't provide much information!
> >
> > Send a:
> > cat /etc/smb.conf
>
> All right, I'm sorry. I all the time complain about the
> people that don't
> send information and I do the same.
>
> [docutech]
> path = /home/users/docutech/fitxers-docutech
> valid users = produ
> admin users = produ
> write list = produ
> force user = docutech
> force group = users
> read only = No
>
> Any ideas??
>
> Thanks a lot for the interest.
>
> Best regards,
>
> Leo
>
