thanks for the help ... thanks to all now its working like it should... forget what I said in may last post the ask for a password I think was a windows bug the now is not having anymore.
Thanks =) On 6/20/07, Cary Robinson <[EMAIL PROTECTED]> wrote:
I'm no pro (by a long shot), But..... Have you looked into using the ACL commands for this ? Permissions can be specified using acl command setfacl for the right group/person. use getfacl to check the applied permissions. From my limited experimentation with these ACL commands, I would think you can accomplish the permissions you are after. Rgd's, Cary At 10:37 AM 6/20/2007, Maginot Junior wrote: >Hmm now its workin... BUT one more thing, and if I dont want to be prompted >for an user name ? >What I want to do is map the share with the foouser login and username info >and all other who try to view the share could do it at the most transparent >way, with no question for user and password... is that possible? > > >And thanks for the help, worked great =) > >On 6/20/07, Eric Boehm <[EMAIL PROTECTED]> wrote: >> >>On Wed, Jun 20, 2007 at 11:53:59AM -0300, Maginot Junior wrote: >> >>>>> "Maginot" == Maginot Junior <[EMAIL PROTECTED]> writes: >> >> Maginot> the problem is if I set the write list or valid users Im >> Maginot> only giving the permission to those in the list... and >> Maginot> the big problem is how to set all other users to be in >> Maginot> the read list ... I dont have group with all inside and >> Maginot> are not going to be any... I tryed with something like >> >> >>[memos] >> path = /home/memos >> write list = foouser >> read list = !foouser >> >>No, you should use >> >>[memos] >> path = /home/memos >> read only = yes >> write list = foouser >> >>This will make it read only except for anyone in the write list. From >>man smb.conf >> >> write list (S) >> This is a list of users that are given read-write >> access to a service. If the connecting user is in this >> list then they will be given write access, no matter >> what the read only option is set to. The list can >> include group names using the @group syntax. >> >> Note that if a user is in both the read list and the >> write list then they will be given write access. >> >> This parameter will not work with the security = share >> in Samba 3.0. This is by design. >> >> >>Note the first paragraph -- "If the connecting user is in this list >>then they will be given write access, no matter what the read only >>options is set to." >> >>-- >>Eric M. Boehm /"\ ASCII Ribbon Campaign >>[EMAIL PROTECTED] \ / No HTML or RTF in mail >> X No proprietary word-processing >>Respect Open Standards / \ files in mail > > > >-- >Maginot Júnior >"the game of life" >LPIC - CCNA - ¿Designer? >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/listinfo/samba > > > >-- >No virus found in this incoming message. >Checked by AVG. Version: 7.5.472 / Virus >Database: 269.9.1/854 - Release Date: 6/19/2007 1:12 PM -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
-- Maginot Júnior "the game of life" LPIC - CCNA - ¿Designer? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
