Re: [Samba] Proper way to upgrade from rc1?
Do let us know if you have any remaining issues. Andrew Bartlett It look like everything works ok. Will see dns in few days. GPO, login scripts work, so useres don't even notice change! Good work! Szymon -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] logon Samba workstation domain with Active Directory trustdom account issue
Hi, I made a mistake, we have Samba 3.5.3. Can somebody help ? Regards, Romain 2012/12/13 Romain gro...@gmail.com Hello samba list, I'm close to be able to make this work but I just need a bit help. Here is the situation: - Windows 2008 R2 x64 Domain Controller: domain ES01 - Samba 3.4.3 Domain Controller:domain ES02 - Windows Seven Workstation (SSO4): on domain ES02 - Window Xp Workstation (SSO2): on domain ES01 We put a both side trust relationship and seems to work regarding command net rpc trustdom list. *[root@localhost ~]# net rpc trustdom list* *Enter root's password:* *Trusted domains list:* * * *ES01S-1-5-21-1816646249-803782145-3669927669* * * *Trusting domains list:* * * *ES01S-1-5-21-1816646249-803782145-3669927669* Now, here is the issue: We can logon domain ES01 with Windows account from Windows Xp Workstation (normal use) We can logon domain ES01 with Samba account from Windows Xp Workstation (that's outgoing trust relationship's work) We can logon domain ES02 with samba account (pretty normal use) *We CAN'T logon domain ES02 with Windows Account (and unfortunatly, that's what we need to go further)* I join you all my configuration files and SS4 workstation log while I try to log with tata account from ES01 windows domain. As you can see in smb.conf, we tried some custom tricks to make winbind working... Hope you will give us a fresh idea that we didn't think about. Regards, Romain -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] smbclient 3.5.6 potential bug: 100-character filenames not extracted properly from tar
On Fri, Dec 07, 2012 at 08:57:24PM +, Bjoren Davis wrote: Hello Samba folks, I have come across a problem with smbclient 3.5.6 when I use the tar 'x' feature. Pathnames that work out to be 100 characters long are extracted incorrectly: bash-3.2$ tar tvf ugh.tar -rw-r--r-- bdavis/Domain Users 137 2012-12-07 13:36:40 a50characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABCD/a49characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABC -rw-r--r-- bdavis/Domain Users 138 2012-12-07 13:37:11 a50characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABCD/a50characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABCD bash-3.2$ smbclient --version Version 3.5.6 bash-3.2$ smbclient //XXX/Temp30Day -U XX/bdavis Enter XX/bdavis's password: Domain=[XXX] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2] smb: \ cd bdavis smb: \bdavis\ tar x ugh.tar restore tar file \bdavis\a50characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABCD\a49characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABC644 of size 137 bytes restore tar file \bdavis\a50characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABCD\a50characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABCD of size 138 bytes tar: restored 2 files and directories smb: \bdavis\ cd a50characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABCD\ smb: \bdavis\a50characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABCD\ dir . D0 Fri Dec 7 13:44:34 2012 .. D0 Fri Dec 7 13:44:34 2012 a49characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABC644 137 Fri Dec 7 13:36:40 2012 a50characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABCD 138 Fri Dec 7 13:37:11 2012 35000 blocks of size 4194304. 10651 blocks available smb: \bdavis\a50characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABCD\ exit As you can see, the file with the 100 character pathname is extracted with its octal permissions concatenated to the name. I'm attaching the tar file that I used. I don't know if this problem is fixed in a newer release of smbclient. Please let me know if there's more information you need. Thanks. Please create a bug at bugzilla.samba.org and upload this information and tar file as an attachment to the bug report. Thanks ! Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba Client -- Server Timeout
Hi Folk, I am writing a Samba VFS module. The VFS CLOSE operation takes a longer time, much greater than 20s, to return. Looks this will cause Samba client server communication timeout. And Samba will load a new module, which is not what I want. I want Samba to wait, until VFS CLOSE operation finishes what it should do. I don't want Samba to load a new module. Can anyone tell me how/where to change Samba source code to realize this? Many thanks Eric -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Client -- Server Timeout
On Fri, Dec 14, 2012 at 06:36:58PM +0800, Eric Liu wrote: I am writing a Samba VFS module. The VFS CLOSE operation takes a longer time, much greater than 20s, to return. Looks this will cause Samba client server communication timeout. And Samba will load a new module, which is not what I want. I want Samba to wait, until VFS CLOSE operation finishes what it should do. I don't want Samba to load a new module. Can anyone tell me how/where to change Samba source code to realize this? VFS_CLOSE taking more than 20 seconds is nothing Samba is prepared for at the moment. Very likely it's the client that ran into a timeout and opened a new connection. Can the CLOSE operation you are writing fail at all? If not, can you defer the long-running operations to a forked process and return quickly to the main smbd, faking success? This would be a quick workaround. The real solution would be to make CLOSE asynchronous, see smbd/aio.c for read and write operations. With best regards, Volker Lendecke -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kont...@sernet.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Client -- Server Timeout
Hi Folk, Note, I am using Samba 3.5.10. I have tried to change source3\libsmb\clientgen.c line 591. But it does not work. cli-timeout = 2 * 360; /* was 2, Timeout in in milliseconds. */ Thanks Eric On Fri, Dec 14, 2012 at 6:36 PM, Eric Liu eric@uniquesoft.com wrote: Hi Folk, I am writing a Samba VFS module. The VFS CLOSE operation takes a longer time, much greater than 20s, to return. Looks this will cause Samba client server communication timeout. And Samba will load a new module, which is not what I want. I want Samba to wait, until VFS CLOSE operation finishes what it should do. I don't want Samba to load a new module. Can anyone tell me how/where to change Samba source code to realize this? Many thanks Eric -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Client -- Server Timeout
On Fri, Dec 14, 2012 at 06:44:56PM +0800, Eric Liu wrote: Hi Folk, Note, I am using Samba 3.5.10. I have tried to change source3\libsmb\clientgen.c line 591. But it does not work. cli-timeout = 2 * 360; /* was 2, Timeout in in milliseconds. */ clientgen.c is a client piece. VFS CLOSE is server side. There is something I am missing in this picture... Can you describe a bit more closely what you are doing? Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kont...@sernet.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Client -- Server Timeout
Volker, To be honest, I don't really know clientgen.c. I just see there is a 2ms there. And I try it and see if I am lucky. Obviously, I am not. My issue is still server side. In case that VFS_CLOSE operation takes longer time than 20s, Samba server shall loads a new module. I don't want that happens. As you have mentioned, probably the client side ran into timeout and opened a new connection. To prevent this happening, I would think the quick workaround here would be to increase the timeout value at the client side. But I don't know how to do it. Thanks Eric On Fri, Dec 14, 2012 at 7:10 PM, Volker Lendecke volker.lende...@sernet.dewrote: On Fri, Dec 14, 2012 at 06:44:56PM +0800, Eric Liu wrote: Hi Folk, Note, I am using Samba 3.5.10. I have tried to change source3\libsmb\clientgen.c line 591. But it does not work. cli-timeout = 2 * 360; /* was 2, Timeout in in milliseconds. */ clientgen.c is a client piece. VFS CLOSE is server side. There is something I am missing in this picture... Can you describe a bit more closely what you are doing? Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kont...@sernet.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Migrate to samba 4 in ( relatively ) complex openLDAP environment
On Thu, 2012-12-13 at 16:54 +0100, andreas wrote: Hello, we, a public hospital, would like to migrate to samba4 from our samba3.x environment. According to the documentation samba4 does use a internal ldap server. We use openLDAP as directory for samba horde Oracle name resolution zope user authentication, Checkpoint Firewall authentication (only few users ), squid proxy authentication, logon authentication to our linux servers, logon authentication to our enterasys switches via freeradius This will be a long process, and one that will probably benefit from the extension of some of our scripts, or the writing of additional scripts. You can of course continue using the 'classic' domain you already have with Samba 4.0, but without the AD features, while you prepare the upgrade. Specifically, the 'samba-tool domain classicupgrade' tool does not currently pick up the additional attributes, and doesn't know how to import the additional schema that may be required in any case. You will have to convert the schema to AD format, load it and then add the attributes back on to the users/groups/hosts. Other attributes don't make sense in an AD environment, where things like the shadowExpires attributes are instead handled by Samba's internal account expiry code. I would like to work with you, not only if you do manage to improve our scripts, but also to share your experiences so that others in a similarly complex situation can get some guideance. I'm sorry this isn't as simple as we would prefer, but I'm sure we can work something out. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] DNS Replication
On Thu, 2012-12-13 at 06:47 -0700, Zane Zakraisek wrote: I created a test domain on a Samba 4.0.0 machine, and added a Server 2008 R2 server. I joined it as a domain controller and DNS server. I've noticed that records that I create on one server aren't being replicated to the other. I experienced this with some of the Betas and Release Candidates too, but I thought it was fixed. Why isn't DNS replication working? Thanks Samba team We need to look into this more, but this is why this has a specific note in the WHATSNEW. For some reason, getting this partition registered correctly for replication seems to be more difficult than for the main partitions. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Client -- Server Timeout
On Fri, Dec 14, 2012 at 07:40:06PM +0800, Eric Liu wrote: To be honest, I don't really know clientgen.c. I just see there is a 2ms there. And I try it and see if I am lucky. Obviously, I am not. My issue is still server side. In case that VFS_CLOSE operation takes longer time than 20s, Samba server shall loads a new module. I don't want that happens. As you have mentioned, probably the client side ran into timeout and opened a new connection. To prevent this happening, I would think the quick workaround here would be to increase the timeout value at the client side. But I don't know how to do it. In case you are serving Windows clients, there is no really good way to increase those timeouts. See a recent discussion on samba-techni...@samba.org. In case you are serving Linux clients, you might have a chance by tweaking the cifs.ko module. SMB clients are just not happy with individual operations taking long. SMB is a lot less forgiving than NFS for example is. With best regards, Volker Lendecke -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kont...@sernet.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Difference between real and reported disk usage
Berni CED ced at bernispa.com writes: strict allocate = yes I've retried commenting out this line and repeating the entire copy with robocopy: now the disk usage corresponds to the one reported by Windows and by du -s -h --apparent-size. Are there any technical reason for that? Should i file a bug? I have an ext4 filesystem and from the smb.conf man page strict allocate = yes looks like a recommended setup. Cesare. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Difference between real and reported disk usage
Berni CED ced at bernispa.com writes: Berni CED ced at bernispa.com writes: strict allocate = yes I've retried commenting out this line and repeating the entire copy with robocopy: now the disk usage corresponds to the one reported by Windows and by du -s -h --apparent-size. To summarize, in my case strict allocate = yes has caused samba server to use 123 GB do store 45 GB of effective data. That is there is a lot more wasted space (78 GB) than data (45 GB)! Cesare. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Difference between real and reported disk usage
Dear Cesare, On 12/14/2012 03:51 PM, Berni CED wrote: I've retried commenting out this line and repeating the entire copy with robocopy: now the disk usage corresponds to the one reported by Windows and by du -s -h --apparent-size. To summarize, in my case strict allocate = yes has caused samba server to use 123 GB do store 45 GB of effective data. That is there is a lot more wasted space (78 GB) than data (45 GB)! This is by design. With the strict allocate = yes Samba stops creating sparse files. If you copy a sparse file with a real size of e.g. 100MB and a reserved/allocated size of 1GB to a server with strict allocate = yes, the server writes 900MB trailing zeros to the file :-) Please refer to smb.conf(5) manual page and look for strict allocate. Best regards, Björn -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kont...@sernet.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba4 LDAP ACLs - access to POSIX attributes from a non-admin account
In our current testing environment, we are using nslcd to get user and group information from the Samba4 LDAP server, using the last part of objectSid as uidNumber. The configuration is designed to pull down unixHomeDirectory and loginShell if they exist, but they default to standard values if they do not. nslcd on each machine binds to LDAP using a dedicated user account, nslcd-service, and the entire setup works pretty well. But now we have run into a problem - although both POSIX attributes exists on a particular user (ismith in this case) they cannot be read by the machine using nslcd-service to bind to the LDAP directory. After further testing, we found that binding as Administrator makes the attributes show up - in fact adding nslcd-service to 'Domain Admins' group also lets it see those attributes. Unfortunately both of these options are a huge security risk - any server that becomes compromised can effectively take control of the Samba4 domain and server, and in turn take out the rest of the network. It seems strange that all normal attributes are perfectly readable by any user, while the manually added POSIX attributes are not. I do not know enough about AD configuration to figure out where the ACLs are stored for this, and documentation has been scarce to say the least. Thus I have come to this mailing list for guidance. An alternative strategy would be to enable anonymous binding on the LDAP server, but the (slightly less scarce) documentation shows that to do that requires each entry be specifically set to allow this, which seems to be more hassle than it is worth. Any help on this would also be greatly appreciated. Thanks, Rob -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] user can't access subdirectories on share using Win7
Hello, I have samba 3.5.6 PDC and BDC on debian squeeze with openldap backend and couple samba member servers based on samba 3.5.15 and 3.6.6 on solaris 11 delivering shares to windows and linux users. recently we moved from samba 3.0.24 on solaris to above verions and we stuck with a problem on windows 7 machines. on solaris zfs filsystem mounted with these settings: drwxrws--t 20 root dnateam 22 Dec 7 11:48 sample_tracking and exported with samba: [sample_tracking] path = /dataPool/samples/sample_tracking force group = dnateam force create mode = 0770 force directory mode = 0770 browsable = yes read only = yes veto oplock files = /*.mdb/*.MDB/ write list = @DIL_\informatics valid users = @DIL_\dnateam @DIL_\informatics in sample tracking directory there are subdirectories with files and projects ex. drwxrws--- 59 mattwinformatics 61 Dec 14 17:37 projects When I mount this share on windows XP or servr 2003 on my account groups wojciech informatics sample_management dnateam sampleinf I have access to sample tracking projects and all subdirectories but when I mount it on Win7 or server 2008 have an access to sample tracking (can create files directories) but can't enter projects directory. (access denied). when i add o+rx on projects problem moves one level deeper. I was checking logs while I try accessing projects no information appeared in logs (not event connections). logleve is 5. it looks like windows 7 gives access denied without connection to samba server. What might be a problem? win 7 security setting ? Win7 has all these setting: Network security: LAN Manager authentication level Send LM NTLM responses Minimum session security for NTLM SSP Disable Require 128-bit encryption thanks Wojciech -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Roaming Profiles - WinXP and Win7
Hello All, Today I was able to implement Samba4 as a DC with AD in a test environment. I eventually got it all working and was able to join the domain from two different virtual machines. I was also able to set up a roaming profile share and configure a user to utilize this share. My issue is that when I first logged into the domain after setting up the roaming profiles I did so from a Windows XP machine. the user's roaming directory was correctly created an all profile data stored. However, when I logged out of the Windows XP machine and logged back in from a Windows 7 machine another (totally separate) user profile directory was created with a .V2 appended to it. The two profiles do not talk to one another and exist on their own. In my opinion this cripples the roaming profile functionality unless your enter network is make up of computers using the same OS. Is this a bug, or is there a solution to this behavior. Thanks for any insight. -- Regards, Aaron J. Wood Vice President Chief of Operations Sun Tire Services, Inc. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba4 LDAP ACLs - access to POSIX attributes from a non-admin account
On the samba-technical mailing list there is this exact problem detailed, so your help is no longer needed to configure reading of unixHomeDirectory and loginShell by other users, but the question about anonymous access still stands - it would be much better for each client to have anonymous access to LDAP rather than needing the dedicated user, which brings with it security holes. On 14/12/12 18:03, Rob McCorkell wrote: In our current testing environment, we are using nslcd to get user and group information from the Samba4 LDAP server, using the last part of objectSid as uidNumber. The configuration is designed to pull down unixHomeDirectory and loginShell if they exist, but they default to standard values if they do not. nslcd on each machine binds to LDAP using a dedicated user account, nslcd-service, and the entire setup works pretty well. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Roaming Profiles - WinXP and Win7
On Fri, 14 Dec 2012, Aaron Wood wrote: In my opinion this cripples the roaming profile functionality unless your enter network is make up of computers using the same OS. Is this a bug, or is there a solution to this behavior. It's not a bug, and there is no solution, since it is designed that way. Windows XP and Windows 7 (and others) cannot share common profiles, even if you are fully Windows all the way. Steve -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Roaming Profiles - WinXP and Win7
(...) is there a solution to this behavior. Partial folder redirection? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Roaming Profiles - WinXP and Win7
On 14/12/12 04:29 PM, Aaron Wood wrote: Hello All, Today I was able to implement Samba4 as a DC with AD in a test environment. I eventually got it all working and was able to join the domain from two different virtual machines. I was also able to set up a roaming profile share and configure a user to utilize this share. My issue is that when I first logged into the domain after setting up the roaming profiles I did so from a Windows XP machine. the user's roaming directory was correctly created an all profile data stored. However, when I logged out of the Windows XP machine and logged back in from a Windows 7 machine another (totally separate) user profile directory was created with a .V2 appended to it. The two profiles do not talk to one another and exist on their own. In my opinion this cripples the roaming profile functionality unless your enter network is make up of computers using the same OS. Is this a bug, or is there a solution to this behavior. Thanks for any insight. You get the same problem in Linux - trying to share a home folder for an account where they are running different versions of the same window manager or different versions of Linux. The various resource files are not always compatible so you are out of luck trying to share everything. I wouldn't even try to get it to work. Just accept that Windows 7 profiles are different from Windows XP profiles. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Installing manpages
According to the Samba documentation, the manpages are supposed to be installed with Samba. Quote: docs/manpages: You don't need to worry about these yet; during the installation, the files will be installed so that you can use the man command to read them. But you can take a look in the directory to see which manpages are available. My problem: Samba4 on 64bit Fedora 17 will not install the manpages, other than a bare-bones samba page. Specifically, it will not install the smb.conf page. What I tried: I tried reinstalling Samba with the following commands: sudo yum reinstall samba4 sudo yum reinstall samba4-devel sudo yum reinstall samba4-common sudo yum reinstall samba4-libs No luck - man smb.conf still gave a No manual entry for smb.conf error. After googling some more, I found the make installman command. So I downloaded the source for Samba4, and ran ./configure, make, and then make installman. That returned the following error: No rule to make target `installman' Wow, this is a PITA. Googling for that error didn't reveal anything helpful. Next, I reinstalled from source (which I just finished compiling), thinking the manpages might be installed with a full, manual installation: sudo make install. Still no luck - man smb.conf still gives the same error. During my googling, I remember reading about pointing the man command to the location of the manpages. So, I used the following command to look for the man pages: locate smb|grep man Next, man man told me the location of the local man config file. I wasn't sure which PATH to use, so I added these to /etc/man_db.conf: MANPATH_MAP/bin/usr/local/samba/share/man MANPATH_MAP/usr/bin/usr/local/samba/share/man MANPATH_MAP/sbin/usr/local/samba/share/man That finally fixed my manpage problem. Why must the Samba man pages be so $#@%#! difficult to install? Every other Linux application that I have ever installed automatically installs the man pages. Why can't Samba do the same thing? PS: This email would be a lot easier to read if mailing lists supported code tags, or if Samba had a forum or bulletin board. :) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba4 Domain UP, but no roaming profiles
I've performed a *successful* domain migration from S3/LDAPSAM to S4.0.0. Yay! I can browse and connect to the server from a workstation [logged in as a local account]. DNS looks good. kinit klist work. I was able to *add* a workstation to the domain. But I can't get roaming profiles to work. On the server the roaming profile looks like - [profiles] path = /opt/s4/var/profiles read only = No profile acls = Yes writeable = yes create mask = 0600 directory mask = 0700 -- Adam Tauno Williams GPG D95ED383 Systems Administrator, Python Developer, LPI / NCLA -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Following symlinks
I'm struggling with following symlinks with samba on the recent versions. I cannot use mount -bind as I've seen others suggest. This is for my mythtv backend, so I'm using the rename script to create nice names for the recordings. Anyway, I can map the drive from Windows XP and Windows 7, and see symlinked files, but I cannot open or copy them as I used to be able to do. My system is opensuse 12.2. My smb.conf looks like: [global] unix extensions = no workgroup = WORKGROUP printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User include = /etc/samba/dhcp.conf logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: usershare allow guests = No wins server = wins support = No [homes] comment = Home Directories valid users = %S, %D%w%S browseable = No read only = Yes inherit acls = Yes follow symlinks = Yes wide links = Yes Thanks, James -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba_dnsupdate --verbose --all-names with internal DNS?
Using the internal / default DNS server should the command samba_dnsupdate --verbose --all-names work? Looking at the wiki this appears to be part of step#9, but I not sure the test shouldn't succeed. $ samba_dnsupdate --verbose --all-names ... ; TSIG error with server: tsig verify failure Failed nsupdate: 2 Calling nsupdate for SRV _gc._tcp.default-first-site-name._sites.micore.us barbel.micore.us 3268 Outgoing update query: ;; -HEADER- opcode: UPDATE, status: NOERROR, id: 0 ;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 ;; UPDATE SECTION: _gc._tcp.default-first-site-name._sites.micore.us. 900 IN SRV 0 100 3268 barbel.micore.us. ; TSIG error with server: tsig verify failure Failed nsupdate: 2 Failed update of 21 entries -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[SCM] Samba Shared Repository - branch v3-5-test updated
The branch, v3-5-test has been updated via 31292e6 WHATSNEW: Prepare release notes for Samba 3.5.20. from 06e3c65 Fix bug #9455 munmap called for an address location not mapped by samba. http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-5-test - Log - commit 31292e6fbedef78126435c92d6e687a4844847d9 Author: Karolin Seeger ksee...@samba.org Date: Fri Dec 14 10:12:34 2012 +0100 WHATSNEW: Prepare release notes for Samba 3.5.20. Karolin --- Summary of changes: WHATSNEW.txt | 17 - 1 files changed, 16 insertions(+), 1 deletions(-) Changeset truncated at 500 lines: diff --git a/WHATSNEW.txt b/WHATSNEW.txt index f0114d6..e2249fc 100644 --- a/WHATSNEW.txt +++ b/WHATSNEW.txt @@ -8,12 +8,27 @@ This is the latest stable release of Samba 3.5. Major enhancements in Samba 3.5.20 include: -o +o Fix segfaults in log level = 10 on Solaris (bug #9390). +o Apply ACL masks correctly when setting ACLs (bug #9236). + Changes since 3.5.19: - o Jeremy Allison j...@samba.org +* BUG 7781: Samba transforms ShareName to lowercase (sharename) when adding + new share via MMC. +* BUG 9236: Apply ACL masks correctly when setting ACLs. +* BUG 9455: munmap called for an address location not mapped by Samba. + + +o Björn Baumbach b...@sernet.de +* BUG 9345: Fix usage of smbconfoption tag. + + +o Stefan Metzmacher me...@samba.org +* BUG 9390: Fix segfaults in log level = 10 on Solaris. +* BUG 9402: Fix dns updates against BIND9 (used in a Samba4 domain). ## -- Samba Shared Repository
