Re: [Samba] Os X and Win clients to SMB 3.0.10 server - how to hide ._ files from win clients only
On Mar 3, 2005, at 7:29 PM, David Bowsky wrote: Could anyone point me to some information regarding managing these files in a Windows/OS X environment? Is there some way to base veto's on user or group IDs? For example, could I generate a group for my mac users and then veto ._files for everyone except that group? You can include a modified smb.conf file from within the standard file to customize the behavior for different clients. Look at the man page for smb.conf in the section on Explanation of each parameter for the parameter config file (listed alphabetically). Also look at the beginning of that man page (it's about 100 pages long!) under Variable Substitutions to get an idea of the sorts of things you can use to differentiate between clients. For example, one of the variables is %a, which is supposed to expand to the architecture of the remote machine. I assume this would be Samba for a MacOS X machine (based on what it says in the man page) and something else for a windows client. The way it works is that if the name of a config file is given, but the file doesn't exist, it's ignored. Otherwise, the new file is loaded in place of the original. So you could try something like adding a line: config file = /path/to/file/smb.conf.%a to your [global] section. Have the standard config file set up for the windows machines (with the veto to hide the ._files). Then make a new config file that is otherwise the same except without the veto for the MacOS X users and name it smb.conf.Samba. That way, any client that looks like Samba OS type will get the modified config file and all others will get the original. It sounds like %a may not be the most reliable of the variables, but of any OS type, one running samba should certainly be correctly detected! In any case, once you see all of the variables that can be used to control this, your head will start to spin with the possibilities. -- Patrick D. McSwiggen[EMAIL PROTECTED] Mathematical Sciences513-556-4080 University of Cincinnati 513-556-3417 FAX -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Fwd: Re: [Samba] force create mode]
On Jan 11, 2005, at 4:13 AM, Patrick DUBAU wrote: Thanks Bart for your answer. I did what you say force create mode = 0770 (default creat mask = 0744) but the files that are created are still with the rights rwx rwx r-- Strange ! Bart Hendrix a écrit : Hi Patrick, Try to use the following in your smb.conf. force create mode = 0770 Greetz Bart - Original Message - From: Patrick DUBAU [EMAIL PROTECTED] To: samba@lists.samba.org Sent: Monday, January 10, 2005 5:30 PM Subject: Re: [Samba] force create mode This is an update. I found for question 2. Just putforce group = group name or set the setgid bit on the root directory of the share But i still can't solve my first problem. What do i have to do so that each file that a user creates has the following rights rwx rwx --- ? Were is the trick ? i read about force mask , creat mask ... in man smb.conf but i really don't understand create mask *removes* permissions. force create mode *adds* them. To quote from the man page for smb.conf This parameter [create mask] may be thought of as a bit-wise MASK for the UNIX modes of a file. Any bit *not* set here will be *removed* from the modes set on a file when it is created. So if you don't want the o+r bit set use: create mask 0770 If you now want to force ug+rwx permissions for all files, *also* use: force create mode 0770 Another way of thinking about these is that create mask sets an upper bound on the permissions for the file and force create mode sets a lower bound, and the actual permissions are in between. (Except that force create mode is applied second, so if it is more permissive than the create mask, force create mode will override create mask.) Note that neither of these apply to directories. The analogous parameters there are directory mask and force directory mode. -- Patrick D. McSwiggen[EMAIL PROTECTED] Mathematical Sciences513-556-4080 University of Cincinnati 513-556-3417 FAX -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Fwd: Re: [Samba] force create mode]
On Jan 11, 2005, at 2:51 PM, Patrick McSwiggen wrote: So if you don't want the o+r bit set use: create mask 0770 If you now want to force ug+rwx permissions for all files, *also* use: force create mode 0770 and I also left off the equal signs--make these: create mask = 0770 force create mode = 0770 -- Patrick D. McSwiggen[EMAIL PROTECTED] Mathematical Sciences513-556-4080 University of Cincinnati 513-556-3417 FAX -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Fwd: Re: [Samba] force create mode]
On Jan 11, 2005, at 2:51 PM, Patrick McSwiggen wrote: So if you don't want the o+r bit set use: create mask 0770 If you now want to force ug+rwx permissions for all files, *also* use: force create mode 0770 and I also left off the equal signs--make these: create mask = 0770 force create mode = 0770 -- Patrick D. McSwiggen[EMAIL PROTECTED] Mathematical Sciences513-556-4080 University of Cincinnati 513-556-3417 FAX -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problem with include=smb.%U.conf
On Nov 14, 2004, at 9:28 PM, [EMAIL PROTECTED] wrote: In Windows, User 1 will see the shares listed in /etc/samba/smb.User1.conf. User 2 will not see those shares (unless they are listed in User 2's directory file as well, which in my case never happens). In Mac OS X (10.3.4, 10.3.5, and 10.3.6) as well as in various Linux distributions like Mandrake 10 and 10.1 and the latest Debian, if I log in as User 1, I cannot see the shares that correspond to User 1. The only shares I can see through the Mac Finder or through the Mac Connect to Server or through the Linux Smb4k or LinNeighborhood are those defined in the general /etc/samba/smb.conf file. I don't know how Windows does this, but I know initially MacOS X does not transmit a username. When using the Connect to Server, have you tried clicking on Authenticate? Only then does it tell the server who you are and for me the available shares get updated. However, I only have the standard [Homes] section plus shares that are available to everybody. So before Authenticate I see only the common shares. After Authenticate I get my own home directory added to the list. In linux have you tried the smbclient, supplying a username and password, to see if you see everything you are supposed to? -- Patrick D. McSwiggen[EMAIL PROTECTED] Mathematical Sciences513-556-4080 University of Cincinnati 513-556-3417 FAX -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Second Copy 2000 problem
On Sep 14, 2004, at 8:46 PM, Matthew Western, IT Support, Lonsdale wrote: Basically we have a share called data.When trying to access the share from second copy the log says can't see service 'dat'. Bizzaire Did you try duplicating the share but this time calling it [dat] (make it browseable = no) and see if that fools it into working? -- Patrick D. McSwiggen[EMAIL PROTECTED] Mathematical Sciences513-556-4080 University of Cincinnati 513-556-3417 FAX -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
