> Flávio Henrique wrote:
>
> > Hi guys!
> >
> > I made some shares here through samba 2.2.8 and put the permissions in
> > this share like this: 'chmod -R 777 /share', to make sure that all users
> > will open...
> >
> > and everything goes fine...
> >
> > but after some time, nobody can access the share...
> > so, I open the log in /var/log/samba/log.user, i.e., and I can see the
> > problem: "Can't chage the directory to /share (Permission denied)"
> >
> > but the permission is 777, like I said before...
> >
> > the share only works again if I type 'chmod -R 777 /share'  again...
> >
> > this is the only reason that I can not change definitely my server...
> >
> > plz, someone have a hint for this ??
> >
> > thanx
> >
> > Flávio Henrique
> >
> >
>
> It sounds like you have msec running along behind you cleaning up the
> permissions..

I can't understand this... what's 'msec' ??

>
> 777 is a dangerous permission and you shouldn't be suing it..

Yes, I know, but I use this just to see if the share it will be done...

>
> You are better off telling samba to use one user for all users.. and
> then set the files to 600
> in the shares., (and change their owner and group to the owner and group
> that you have just set the share up to use.)
>
>
> Try something like this for a share:
>
> [myshare]
>    comment = a test share
>    path = /home/allusers
>    force user = franki
>    force group = franki
>    public = no
>    writable = yes
>    printable = no
>
>

But do your think this have relations with why my share is losting after
some time?

for explanation, I use my linux as a single machine in my network (without
domain, just a workgroup)

thanx Flávio Henrique

> Thats much better security then using open permissions..
>
>
> -- 
> rgds
>
>
> Frank Hauptle (aka Franki)
>
>


____________________________________________________
Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com
____________________________________________________

Reply via email to