On Thursday 06 May 2004 03:52 pm, frankieh wrote: > Flávio Henrique wrote: > >>Flávio Henrique wrote: > >> > hmmm.. so this msec "thing" break the shares because is too risk ? > >> > >>I'm right > >> > >>>? is that what your mean ?? > >> > >>It doesn't break the share, it has nothing to do with samba at all. > >>It seems the files that are writable and executable to everyone, and it > >>changes them to safer permissions. > > > > in fact, the permission still displayed like dwrxwrxwrx for my share... > > but the users can access it... > > > > even that, I need to give 'chmod 777 /share' again to work... > > yes, but are the files still 777 ???? > > > Flávio Henrique
My solution is to KILL G%^%$#$ msec. I HATE msec, because I know what permissions I want on my files and I don't want to be hand-held by any program. It is especially not necessary on a home network where everyone is (or should be) a trusted user. To kill msec so that it can't run, as root go to /usr/sbin and rename the msec executable to DISABLEmsec. Presto, no more permissions changes on shared folders. An added bonus is no more filling up of logs with msec messages. e.
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
