Any suggestions? Improve this question. Jack H Jack H 71 1 1 silver badge 12 12 bronze badges. Compile it on your own. You complain about Debian testing, while using Samba 4?!
That sounds odd as the website of Samba states: "Samba 4 is currently not yet in a state where it can replace existing production deployments. I was not complaining, I was wanting to keep experimental software to a minimum. I do however require the GPO functionality of Samba4. Add a comment. Active Oldest Votes. Or just do it manually.
Improve this answer. Add only a deb-src line not a deb line for testing or unstable to sources. Why is that better? Since packages from testing are far more likely to be buggy, and testing gets no security support, the fewer packages installed from testing the better.
Only if it works with the old version of the libs If it doesn't, then the Build-Depends: of the package are mis-declared. In the case when one is backporting and not all the Build-Depends are satisfiable in stable, one can often just first backport those. Because this share is writable, the default umask will apply. I like to override this because I want ensure that new files are owned by the group smbmedia and the user should be set to the user who created the file for record keeping.
Set the sticky bit to ensure new directories keep the same ACLs which we'll set next. The group stick bit will therefore only work for new directories at 1 level below the base level of the share. This means that newly created directories at level 1 will have the ACLs applied minus the group sticky bit, so that level 2 directories will assume the primary group permissions of the user that created the new directory, and not necessarily the "shared" group permissions something like this.
There are two ways to deal with this: One way it to use something like inotify to watch for new directories and apply the group sticky bit on newly created directories recursively. Now you can be sure that new files will be created with the correct permissions so that they can be seen and changed by smb client users.
This will allow anyone in the smbmedia group to change files owned by other people, however. You can adjust the ACLs accordingly.
Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 7 years, 3 months ago. Active 9 months ago. Viewed k times. Setup is as follows: Server : Debian Wheezy sudo smbd --version gives me Version 3.
Client : Debian Testing Jessie Windows 7 2 different machines. My smb. Improve this question. Add a comment. Active Oldest Votes. OK, I have found an answer myself.
After that, I have added this user to the Samba registry or maybe created new identical one, don't care : smbpasswd -a jonnie It asked for password, I have entered the same as for the main system. Improve this answer. See your distributor's package or port system for a native install of samba on your system.
Nowadays, the Samba Team needs a dollar instead of pizza ;-. Samba 4. Download The Samba source code is distributed via https. The advantage of fetching via GIT is can update your sources at any time using a single command. See the Git instructions.
0コメント