Re: [Samba] Samba 64 bit compilation
It is for Solaris 9 and 10 Sparc machines. Thanks, Prabu -Original Message- From: Gaiseric Vandal [mailto:gaiseric.van...@gmail.com] Sent: Thursday, June 14, 2012 2:49 AM To: Murugan, Prabu; Samba Subject: Re: Samba 64 bit compilation Which platform? If on Solaris 10 sparc, GCC (either from Sun or sunfreeware.com) should be 64-bit by default. GCC from Sunfreeware for Solaris 10 x86 will compile 32-bit by default. For Solaris, you are better off using Sun Studio and Dmake. Actually, you are better off just using the compiled version from Oracle/Sun. On 06/13/12 02:08, prabu.muru...@emc.com wrote: Hi, Have tried to compile samba 64 bit. By default it is compiling 32 bit. Google doesn't give much info about it. Please share your experience on 64bit samba. Thanks, Prabu -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba 3.6.3 on Ubuntu Server 12.04 Server Problem (Urgent)
I upgraded a machine that had been configured as a PDC running Ubuntu Server
11.04 (and whatever version of Samba was default in July 2011) to the new
Ubuntu 12.04 Server LTS, which has Samba 3.6.3 (I did a fresh install). I
restored the existing samba configuration file (smb.conf), and re-created the
user accounts (both adduser and smbpasswd). The PDC serves roaming profiles to
user on Windows 7 Professional and Windows XP Professional computers.
I then removed each computer from the domain (changed to workgroup WORKGROUP)
and then re-added three computers to the domain. Each initially worked,
connecting to the domain, and downloading the user's roaming profile. I was
able to logon and logoff successfully a few times, then started getting the
following error: There are currently no logon servers available to service the
logon request..
When that error appeared the first time, I was able to reboot the client (Win7)
machine, and then logon to the domain successfully once, and then the error
message would reappear at the next attempt to logon (a few minutes later).
This worked two or three times, and has since failed - I get the same error
message no matter what now.
I am still able to ping and SSH into the PDC, so connectivity is still there,
just not when I try to use it as a PDC!
Does anyone know if there is anything in Samba 3.6.3 that has changed that
would cause this strange behavior?
(Attached is my smb.conf file the samba log from one of the affected
machines.)
Thanks in advance for any help that you can provide! I have to have this
server back up and running by Monday morning, even if it means rolling back and
re-installing Ubuntu Server 11.04.
Greg
Here is my smb.conf file (minus the comment section at the top):
#=== Global Settings ===
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
# enabled on 23 July 2011 by Greg
workgroup = LAKEPSYCH
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no
# enabled on 23 July 2011 by Greg
wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
Networking
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes
Debugging/Accounting
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Cap the size of the individual log files (in KiB).
max log size = 1000
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
### Authentication ###
# security = user is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
security = user
# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
# changed on 23 July 2011 by Greg
passdb backend = tdbsam
# passdb backend = smbpwdbsam
# Changed from yes to no on 16 Jun 2012 by Greg
obey pam restrictions = no
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the
[Samba] Samba Platform Support Clarification
Good evening. I'm seeking to verify the feasibility of using Samba as a file and print server running under the Linux operating system (Red Hat or SUSE), itself running under the System z Virtual Machine (z/VM). The documentation I've seen seems to indicate that Samba runs under Linux, but virtually all the specifics seem to speak in terms of UNIX. So I'd appreciate it for my peace of mind if you could please confirm whether (1) Samba runs under Linux, and even more specifically if possible, (2) whether Samba runs under Linux running under z/VM on System z. Thank you for any clarification you can provide. . Regards Dave Moss Senior Certified Executive Systems Architect Open Group Distinguished Certified IT Architect System z Client Architect IBM Corporation 6710 Rockledge Drive Bethesda, Maryland 20817 US Federal (301) 803-62208-262-6220 Cell Phone 703 268 0402 mo...@us.ibm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba4 Multi-Master replication
Thanks for the info, I did not try this setup yet. Anyway, Would you guys recommend a replication setup for production yet? The samba internal dns implementation being still work in progresss? I really wonder if I should just set up a single DC for starters and wait until the whole DNS will be part of samba. This Domain will only cater to about 100-150 clients and one DC should be easily able to deal with this workload?! A second DC would certainly a good idea, but i really wonder if it's worth the hassle right now. I can just take daily snapshots of a single DC and roll back if anything goes terribly wrong. Thanks for your input! -morten On 06/13/2012 09:00 AM, Daniel Müller wrote: You always need to have two Samba4/dns and the entries of both dns in your clients network settings too. --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprüngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von Gémes Géza Gesendet: Dienstag, 12. Juni 2012 19:19 An: samba@lists.samba.org Betreff: Re: [Samba] Samba4 Multi-Master replication On 2012-06-12 12:16, Morten Kramer wrote: Hi guys, I'm trying to get the Samba4 multi-master replication to work. I set up the primary domain controller using this howto (under CentOS 6.2 x64): http://wiki.samba.org/index.php/Samba4/HOWTO I installed bind 9.8.3 and enabled encrypted dns updates. I set up another VM with the same CentOS version and oriented myself on this howto: http://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC to join the second DC into the domain. I edited /etc/resolv.conf and set the nameserver to the IP of the primary DC (bind dns server). Basic replication seems to work (not doing the rsync for sysvol yet). However, when i take the primary DC offline (bind keeps running), I can't use any of the .msc domain admin tools anymore. I always get an error message, telling me that there is no RPC server available. When i run gpmc.msc i can choose the DC i want to work on and I can see the secondary one, but it will come back with the RPC error. I had Wireshark running on one of the Windows7 clients. It seems like it tries to talk to the 2nd DC (DCERPC packets). But i'm not an expert in packet analysis, could somebody give me a hint what to look for here? User authentication does still work and Kerberos tickets are generated by the 2nd DC. I can find this in the log: ../source4/dsdb/kcc/kcc_topology.c:1402: failed to find nCName attribute of object CN=ac7bf69c-9458-4205-acba-6fe172412d1b,CN=Partitions,CN=Configuration ,DC=aeriatest2,DC=dc,DC=loc ../source4/dsdb/kcc/kcc_topology.c:3158: failed to color vertices: NT_STATUS_INTERNAL_DB_CORRUPTION ../source4/dsdb/kcc/kcc_topology.c:3415: failed to create connections: NT_STATUS_INTERNAL_DB_CORRUPTION ... Warning: 60 extra bytes in incoming RPC request ../source4/rpc_server/drsuapi/dcesrv_drsuapi.c:74: doing DsBind with system_session Do i need to configure something extra, so the secondary DC will be able to act as an RPC server? Thanks, freezer Hi, With your setup DNS is the single point of failure, because with the (default) DLZ setup bind9 is able to serve DNS records only when samba4 is running on that box. My recommendation would be to try to set up DNS on the second DC too. Regards. Geza -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Platform Support Clarification
David, Samba indeed can be used on a wide range of operating systems to provide file and print interoperability with Microsoft Windows platforms. The Samba source code can be compiled to run on many operating system platforms. In the past is has been built and run on Linux, UNIX (all flavors), VME, VMS, MVE, etc. Samba is included with nearly all Linux distributions whether used natively or in virtual machines. You should be able to obtain Samba binaries (RPM packages) for your z/VM -baed Red Hat Linux system. If not, you may have to build them on your platform. - John T. On 06/15/2012 04:04 PM, David Moss wrote: Good evening. I'm seeking to verify the feasibility of using Samba as a file and print server running under the Linux operating system (Red Hat or SUSE), itself running under the System z Virtual Machine (z/VM). The documentation I've seen seems to indicate that Samba runs under Linux, but virtually all the specifics seem to speak in terms of UNIX. So I'd appreciate it for my peace of mind if you could please confirm whether (1) Samba runs under Linux, and even more specifically if possible, (2) whether Samba runs under Linux running under z/VM on System z. Thank you for any clarification you can provide. . Regards Dave Moss Senior Certified Executive Systems Architect Open Group Distinguished Certified IT Architect System z Client Architect IBM Corporation 6710 Rockledge Drive Bethesda, Maryland 20817 US Federal (301) 803-62208-262-6220 Cell Phone 703 268 0402 mo...@us.ibm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Two attempts required to join domain
bump I'd prefer to not have to put machine accounts into the People OU for all the obvious reasons, but I may be forced to in order to have the end-user (e.g. our customer) experience to be a smooth one. Any idea on what might cause the behavior I am seeing described on the 13th below? Thanks for any help! -- Bill Arlofski Reverse Polarity, LLC On 06/13/12 18:55, Bill Arlofski wrote: Hi Everyone. I have run across an issue that is driving me crazy. This is a new deployment of Samba v3.6.5 with openldap v2.4.30 and smbldap-tools v0.9.8 When trying to join the domain, on the first attempt the machine account is properly created in the correct ou - e.g. ou=Computers,dc=domain,dc=local But the failed to join domain pop-up with reason of The user name could not be found is displayed (which really means the machine name was not found in LDAP) and of course the machine is not yet a domain member. However, a 2nd attempt to join the domain with the same credentials, immediately after the failure results in a Welcome to the X domain and the machine is now a domain member. Setting the openldap slapd loglevel to 416 to show the queries during this process reveals the following: On 1st join attempt Samba searches the whole directory from dc=domain,dc=local with a scope of 2 (sub) for uid=MyMachine, objectClass=sambaSamAccount. It of course does not find it, so the smbldap-useradd script is called and the machine account is properly added to ou=Computers. Then Samba immediately searches _ONLY_ ou=People,dc=domain,dc=local for the newly created machine account and of course does not find it. And the failed to join domain pop-up is displayed on the WinXP machine. On the second join attempt, Samba _ONLY_ searches ou=Computers,dc=domain,dc=local, which is where it SHOULD search for machines as defined everywhere in my configs and it finds the machine and the machine successfully joins the domain. If I set all configs - samba, smbldap etc to be such that computers are in the People organizational unit, then joining the domain works on the first try, every time. Also, if I un-join the domain, but leave the machine account in LDAP in ou=Computers and then re-join the domain, this always works on first try too since Samba's initial scope 2 sub search of the directory starting at the top will find the machine account under ou=Computers. Can someone offer guidance as to why during the new machine creation process (joining a domain) Samba does not look for the machine in the defined machines ou but always in the People ou? Thank you in advance for any help on this! -- Bill Arlofski Reverse Polarity, LLC -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Platform Support Clarification
On Fri, Jun 15, 2012 at 5:04 PM, David Moss mo...@us.ibm.com wrote: Good evening. I'm seeking to verify the feasibility of using Samba as a file and print server running under the Linux operating system (Red Hat or SUSE), itself running under the System z Virtual Machine (z/VM). The documentation I've seen seems to indicate that Samba runs under Linux, but virtually all the specifics seem to speak in terms of UNIX. So I'd I'm afraid many people don't like to deal with the distnction. I know people who've tried to say they're the same and ignored the legal registration of the UNIX trademark with the Open Source Institute, and the specific API's necessary to be trademarked UNIX by that group. appreciate it for my peace of mind if you could please confirm whether (1) Samba runs under Linux, and even more specifically if possible, (2) whether Samba runs under Linux running under z/VM on System z. Thank you for any clarification you can provide. . Under Linux *absolutely*. t's the primary underlying kernel used to support Samba servers, and is a core feature of almost all Linux distributions. I highly recommend it over Windows servers for filesystems due to superior stability, performance, and the usually simpler backup and access management. (The built-in Windows permission system is too complex to manage in real life, the simpler POSIX used by by most Linux and UNIX filesystems is lightweight enough to manage.) z/VM. that's another story. I assume you mean Linux *guests* under the z/VM virtualization technology, *which is not itself Linux or a trademarked UNIX!!* The filesystems z/VM supports, either as a guest or a server, are whatever IBM built into that technology. You'd really have to ask IBM: for their list of supported technologies. But the guests running in z/VM should be just fine: I've used very sophisticated Samba servers and clients under VMWare, VirtualBox, Xen, and KVM, and don't see any likely problems for you unless you decide to use some really, really funky filesystems in your guest environments. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Two attempts required to join domain
You could put the machines in a sub container under people- , or have people and computers as subs under user accounts- that way samba can search the entire accounts or people subtree BUT you can restrict other LDAP services that use people to not be recursive. -Original Message- From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On Behalf Of Bill Arlofski Sent: Sunday, June 17, 2012 4:16 PM To: samba@lists.samba.org Subject: Re: [Samba] Two attempts required to join domain bump I'd prefer to not have to put machine accounts into the People OU for all the obvious reasons, but I may be forced to in order to have the end-user (e.g. our customer) experience to be a smooth one. Any idea on what might cause the behavior I am seeing described on the 13th below? Thanks for any help! -- Bill Arlofski Reverse Polarity, LLC On 06/13/12 18:55, Bill Arlofski wrote: Hi Everyone. I have run across an issue that is driving me crazy. This is a new deployment of Samba v3.6.5 with openldap v2.4.30 and smbldap-tools v0.9.8 When trying to join the domain, on the first attempt the machine account is properly created in the correct ou - e.g. ou=Computers,dc=domain,dc=local But the failed to join domain pop-up with reason of The user name could not be found is displayed (which really means the machine name was not found in LDAP) and of course the machine is not yet a domain member. However, a 2nd attempt to join the domain with the same credentials, immediately after the failure results in a Welcome to the X domain and the machine is now a domain member. Setting the openldap slapd loglevel to 416 to show the queries during this process reveals the following: On 1st join attempt Samba searches the whole directory from dc=domain,dc=local with a scope of 2 (sub) for uid=MyMachine, objectClass=sambaSamAccount. It of course does not find it, so the smbldap-useradd script is called and the machine account is properly added to ou=Computers. Then Samba immediately searches _ONLY_ ou=People,dc=domain,dc=local for the newly created machine account and of course does not find it. And the failed to join domain pop-up is displayed on the WinXP machine. On the second join attempt, Samba _ONLY_ searches ou=Computers,dc=domain,dc=local, which is where it SHOULD search for machines as defined everywhere in my configs and it finds the machine and the machine successfully joins the domain. If I set all configs - samba, smbldap etc to be such that computers are in the People organizational unit, then joining the domain works on the first try, every time. Also, if I un-join the domain, but leave the machine account in LDAP in ou=Computers and then re-join the domain, this always works on first try too since Samba's initial scope 2 sub search of the directory starting at the top will find the machine account under ou=Computers. Can someone offer guidance as to why during the new machine creation process (joining a domain) Samba does not look for the machine in the defined machines ou but always in the People ou? Thank you in advance for any help on this! -- Bill Arlofski Reverse Polarity, LLC -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Two attempts required to join domain
On Wed, 13 Jun 2012, Bill Arlofski wrote: Can someone offer guidance as to why during the new machine creation process (joining a domain) Samba does not look for the machine in the defined machines ou but always in the People ou? In /etc/ldap.conf you probably need something like: nss_base_passwd ou=People,dc=domain,dc=org?one nss_base_passwd ou=Computers,dc=domain,dc=org?one Steve -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Two attempts required to join domain
On 06/17/12 17:16, Gaiseric Vandal wrote: You could put the machines in a sub container under people- , or have people and computers as subs under user accounts- that way samba can search the entire accounts or people subtree BUT you can restrict other LDAP services that use people to not be recursive. Thanks for that idea, and I think that may be the way I have to go... Just wonder why I am having such a unique issue when everything else works fine. :) -- Bill Arlofski Reverse Polarity, LLC -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Two attempts required to join domain
On 06/17/12 18:03, Steve Thompson wrote: On Wed, 13 Jun 2012, Bill Arlofski wrote: Can someone offer guidance as to why during the new machine creation process (joining a domain) Samba does not look for the machine in the defined machines ou but always in the People ou? In /etc/ldap.conf you probably need something like: nss_base_passwd ou=People,dc=domain,dc=org?one nss_base_passwd ou=Computers,dc=domain,dc=org?one Steve Hi Steve... Thanks for that idea. I had the first one of course and had assumed that in that file it was a one, and only one setting e.g. didn't know you could stack those and all would be used. I tried adding the second line and now the symptom has changed. Instead of the The user name could not be found error on 1st join attempt, I am now seeing a rather bizarre: A device attached to the system is not functioning The machine account is however created in the Computers OU by the smbldap-useradd script and on an immediate 2nd join attempt I get Welcome the the domain X I can get some debug logs from both samba and slapd if that would help. Thanks for the reply. -- Bill Arlofski Reverse Polarity, LLC -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba 3.6.6 error loading shared libraries
Hello, I have compiled Samba 3.6.6 from the git branch 3-6-stable for my Ubuntu 10.04 system. Configure and make completed successfully though I get the error: error while loading shared libraries: libwbclient.so.0: cannot open shared object fie: No such file or directory This seems like a missing file, though I updated my Debian packages according to the dependencies before compiling. Also, would it be wise to use another branch? -- 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 master updated
The branch, master has been updated
via ede2fa8 heimdal:lib/wind: include stdlib.h at the end
from 326d174 heimdal:lib/wind: make sure errorlist_table.c includes
config.h as first header
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit ede2fa8e6925cd9f88d762049a4c65c4e130c2da
Author: Stefan Metzmacher me...@samba.org
Date: Sun Jun 17 14:18:49 2012 +0200
heimdal:lib/wind: include stdlib.h at the end
This makes sure config.h gets includes first.
This should fix the build on AIX.
metze
Autobuild-User(master): Stefan Metzmacher me...@samba.org
Autobuild-Date(master): Sun Jun 17 16:16:24 CEST 2012 on sn-devel-104
---
Summary of changes:
source4/heimdal/lib/wind/gen-bidi.py |2 +-
source4/heimdal/lib/wind/gen-combining.py |2 +-
source4/heimdal/lib/wind/gen-normalize.py |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
Changeset truncated at 500 lines:
diff --git a/source4/heimdal/lib/wind/gen-bidi.py
b/source4/heimdal/lib/wind/gen-bidi.py
index 70abb1e..21839c2 100644
--- a/source4/heimdal/lib/wind/gen-bidi.py
+++ b/source4/heimdal/lib/wind/gen-bidi.py
@@ -70,8 +70,8 @@ extern const size_t _wind_l_table_size;
bidi_c.file.write(
'''
-#include stdlib.h
#include bidi_table.h
+#include stdlib.h
''')
diff --git a/source4/heimdal/lib/wind/gen-combining.py
b/source4/heimdal/lib/wind/gen-combining.py
index cc692fd..86cbc6d 100644
--- a/source4/heimdal/lib/wind/gen-combining.py
+++ b/source4/heimdal/lib/wind/gen-combining.py
@@ -73,8 +73,8 @@ extern const size_t _wind_combining_table_size;
combining_c.file.write(
'''
-#include stdlib.h
#include combining_table.h
+#include stdlib.h
const struct translation _wind_combining_table[] = {
''')
diff --git a/source4/heimdal/lib/wind/gen-normalize.py
b/source4/heimdal/lib/wind/gen-normalize.py
index c076088..9b3553c 100644
--- a/source4/heimdal/lib/wind/gen-normalize.py
+++ b/source4/heimdal/lib/wind/gen-normalize.py
@@ -97,8 +97,8 @@ extern const unsigned short _wind_canon_next_table[];
normalize_c.file.write(
'''
-#include stdlib.h
#include normalize_table.h
+#include stdlib.h
const struct translation _wind_normalize_table[] = {
''')
--
Samba Shared Repository
[SCM] Samba Shared Repository - branch v3-6-test updated
The branch, v3-6-test has been updated via fc42ea0 s3:smbd: use fsp_persistent_id() as persistent_file_id part for SMB2 (bug #8995) via cb5a0b1 s3:smbd: add a fsp_persistent_id() function via 8c11594 s3:smbd: try to make fsp-fh-gen_id as globally unique as possible via a411223 Revert s3:smbd: set req-smb2req-compat_chain_fsp in file_fsp() via 9980779 s3:smb2_ioctl: make use of file_fsp_smb2() via f3049c6 s3:smb2_lock: make use of file_fsp_smb2() via b7da435 s3:smb2_write: make use of file_fsp_smb2() via 770ea1c s3:smb2_read: make use of file_fsp_smb2() via 742dd9d s3:smb2_notify: make use of file_fsp_smb2() via d4b4cc3 3:smb2_setinfo: make use of file_fsp_smb2() via e49840f s3:smb2_getinfo: make use of file_fsp_smb2() via 45d6159 s3:smb2_find: make use of file_fsp_smb2() via 416bb94 s3:smb2_break: make use of file_fsp_smb2() via feed8c0 s3:smb2_close: make use of file_fsp_smb2() via 3ade960 s3:smb2_flush: make use of file_fsp_smb2() via 6334f80 s3:smbd: add file_fsp_smb2() via 46d293d s3:smb2_write: pass fsp-fnum to init_strict_lock_struct() via 0afc959 s3:smb2_read: pass fsp-fnum to init_strict_lock_struct() via c47b3ff s3:smb2_lock: use fsp-fnum as locking context via 09dde2e s3:smb2_lock: use smb2req-compat_chain_fsp instead of looking it up again via 6ed9df5 s3:smbd: set req-smb2req-compat_chain_fsp in file_fsp() from 0ace3ca Part 2 of fix for bug #8998 - Notify code can miss a ChDir. http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-6-test - Log - commit fc42ea02c7af66ddf5af61d444fdfe5e348d05e2 Author: Stefan Metzmacher me...@samba.org Date: Wed Jun 13 12:13:01 2012 +0200 s3:smbd: use fsp_persistent_id() as persistent_file_id part for SMB2 (bug #8995) It seems to be important to have unique persistent file ids, because windows clients seem to index files by server_guid + persistent_file_id. Which may break, if we just have a 16-bit range per connection and the client connects multiple times. Based on code from Ira Cooper. Use fsp-fh-gen_id as the persistent fileid in SMB2. metze Autobuild-User(master): Stefan Metzmacher me...@samba.org Autobuild-Date(master): Thu Jun 14 22:04:13 CEST 2012 on sn-devel-104 Signed-off-by: Jeremy Allison j...@samba.org commit cb5a0b1bc311667818ab45bb1837dc67a241a379 Author: Stefan Metzmacher me...@samba.org Date: Thu Jun 14 10:32:43 2012 +0200 s3:smbd: add a fsp_persistent_id() function This calculates a 64-bit value that most likely uniquely identifies the files_struct globally to the server. * 32-bit random gen_id * 16-bit truncated open_time * 16-bit fnum (valatile_id) Based on code from Ira Cooper. Use fsp-fh-gen_id as the persistent fileid in SMB2. Pair-Programmed-With: Michael Adam ob...@samba.org metze Signed-off-by: Jeremy Allison j...@samba.org commit 8c1159461a0c5a948cd04cdf969e54e1fa83387e Author: Stefan Metzmacher me...@samba.org Date: Wed Jun 13 12:11:51 2012 +0200 s3:smbd: try to make fsp-fh-gen_id as globally unique as possible This makes sure the value is never 0, it's between 1 and UINT32_MAX. While fsp-fh-gen_id is 'unsigned long' currently (which might by 8 bytes), there's some oplock code which truncates it to uint32_t (using IVAL()). Which means we could reuse fsp-fh-gen_id as persistent file id until we have a final fix, which uses database. See bug #8995 for more details. Based on code from Ira Cooper. Ensure fsp-fh-gen_id starts from a random point. We will use this as the SMB2 persistent_id. metze Signed-off-by: Jeremy Allison j...@samba.org commit a41122337cb72fdc3f16d77396a3e68bf53c1c03 Author: Stefan Metzmacher me...@samba.org Date: Sat Jun 9 11:11:26 2012 +0200 Revert s3:smbd: set req-smb2req-compat_chain_fsp in file_fsp() This reverts commit c2716a7d5ccf78f9716b703c22e6cf4d4f179656. This is not needed anymore, as we have file_fsp_smb2() now. metze Autobuild-User(master): Stefan Metzmacher me...@samba.org Autobuild-Date(master): Sun Jun 10 18:04:21 CEST 2012 on sn-devel-104 Signed-off-by: Jeremy Allison j...@samba.org commit 99807792d743b7f258f0d433689b6231b260bddf Author: Stefan Metzmacher me...@samba.org Date: Fri Jun 15 13:42:27 2012 -0700 s3:smb2_ioctl: make use of file_fsp_smb2() metze Signed-off-by: Jeremy Allison j...@samba.org commit f3049c6cafc252a19db84636765674300ff4162b Author: Stefan Metzmacher me...@samba.org Date: Fri Jun 8 11:57:21 2012 +0200 s3:smb2_lock: make use of file_fsp_smb2() metze Signed-off-by: Jeremy Allison j...@samba.org commit
[SCM] Samba Shared Repository - branch v3-5-test updated
The branch, v3-5-test has been updated
via dfa5366 Fix for bug #8998 - Notify code can miss a ChDir.
from c615d8e Fix bug #8994 - winbind normalize names.
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-5-test
- Log -
commit dfa5366a6ee418d6292c1832520c0c1bd974af49
Author: Volker Lendecke volker.lende...@sernet.de
Date: Thu Jun 14 12:07:33 2012 -0700
Fix for bug #8998 - Notify code can miss a ChDir.
---
Summary of changes:
source3/smbd/notify.c | 55
1 files changed, 41 insertions(+), 14 deletions(-)
Changeset truncated at 500 lines:
diff --git a/source3/smbd/notify.c b/source3/smbd/notify.c
index a53f3fb..1f664d0 100644
--- a/source3/smbd/notify.c
+++ b/source3/smbd/notify.c
@@ -366,28 +366,55 @@ void
remove_pending_change_notify_requests_by_fid(files_struct *fsp,
}
}
-void notify_fname(connection_struct *conn, uint32 action, uint32 filter,
- const char *path)
+static void notify_parent_dir(connection_struct *conn,
+ uint32 action, uint32 filter,
+ const char *path)
{
- char *fullpath;
+ struct smb_filename smb_fname_parent;
char *parent;
const char *name;
+ char *oldwd;
- if (path[0] == '.' path[1] == '/') {
- path += 2;
+ if (!parent_dirname(talloc_tos(), path, parent, name)) {
+ DEBUG(1, (Can't get parent dirname, giving up\n));
+ return;
}
- if (parent_dirname(talloc_tos(), path, parent, name)) {
- struct smb_filename smb_fname_parent;
- ZERO_STRUCT(smb_fname_parent);
- smb_fname_parent.base_name = parent;
+ ZERO_STRUCT(smb_fname_parent);
+ smb_fname_parent.base_name = parent;
- if (SMB_VFS_STAT(conn, smb_fname_parent) != -1) {
- notify_onelevel(conn-notify_ctx, action, filter,
- SMB_VFS_FILE_ID_CREATE(conn, smb_fname_parent.st),
- name);
- }
+ oldwd = vfs_GetWd(parent, conn);
+ if (oldwd == NULL) {
+ DEBUG(1, (vfs_GetWd failed!\n));
+ goto done;
+ }
+ if (vfs_ChDir(conn, conn-connectpath) == -1) {
+ DEBUG(1, (Could not chdir to connect path!\n));
+ goto done;
+ }
+
+ if (SMB_VFS_STAT(conn, smb_fname_parent) == -1) {
+ goto chdir_done;
+ }
+
+ notify_onelevel(conn-notify_ctx, action, filter,
+ SMB_VFS_FILE_ID_CREATE(conn, smb_fname_parent.st),
+ name);
+chdir_done:
+ vfs_ChDir(conn, oldwd);
+done:
+ TALLOC_FREE(parent);
+}
+
+void notify_fname(connection_struct *conn, uint32 action, uint32 filter,
+ const char *path)
+{
+ char *fullpath = NULL;
+
+ if (path[0] == '.' path[1] == '/') {
+ path += 2;
}
+ notify_parent_dir(conn, action, filter, path);
fullpath = talloc_asprintf(talloc_tos(), %s/%s, conn-connectpath,
path);
--
Samba Shared Repository
