Re: [Samba] Samba with ADS on Sun Solaris System
On Mon, Jan 09, 2006 at 11:10:07AM -0600, Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adam D. Morley wrote: I would be surprised to see it, for a number of reasons: - Solaris doesn't have MIT/Heimdal Kerberos. It has SEAM, aka Sun Kerberos. I don't know if this matters, but ... - Solaris doesn't have OpenLDAP. It has Sun LDAP. I don't know if this matters, but ... The idea will be to package a statically linked version of smbd that includes the appropriate Kerb5 and OpenLDAP libs. Wow. Does this mean a new version would be released whenever there is a vulnerability in the kerb libs, openldap libs, or Samba? Or only for Samba? That seems like a lot of work for you/the rest of the Samba team. . . -- adam -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: CIFS + NFS'ing a single filesystem w/ locking
On Fri, Jan 06, 2006 at 06:24:22PM -0800, Adam D. Morley wrote: Hi, I have a Solaris 10 server exporting UFS directories using built-in NFS. I've built Samba 3.0.20b from OpenPKG (www.openpkg.org). I have a Solaris 10 (x86) client mounting the NFS share and opening OpenDocument files using StarOffice 8 (SO8, aka OO2.0). I also have a Windows 2003 Terminal Server mounting the Samba share and opening documents with SO8. This is a temporary development environment, so I can screw around with it. I have a similar, production environment using RHEL3 (clients) and Solaris 9 (server), with no Samba. Ie: I would like to export NFS shares as CIFS shares using Samba. But: I want file locking. [snip] I did some further testing. If a file is opened with StarOffice 8 on the console of a Linux machine (from an ext3 filesystem), thereby write-locking the file, Samba cannot read the file anymore, even though other clients logged into the machine can, albeit seeing the write lock properally. Here is smb.conf: [global] workgroup = test security = share [shared2] path = /shared2 read only = No guest ok = yes kernel oplocks = Yes locking = Yes oplocks = Yes level2 oplocks = No In what context does locking actually work with Samba? Is it only for clients reading through the CIFS filesystem, or is there some magic trick to make Samba see write locks from the UNIX side on the Windows side? I thought I read that one could export a directory with Samba and have it honor UNIX-side locks? What am I doing wrong? Thanks! -- adam -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba with ADS on Sun Solaris System
On Wed, Jan 04, 2006 at 05:28:13PM +0530, Venu Siddamshetty wrote: Hi, We are facing problems while configuring SAMBA ADS on Sun Solaris system. After installation and configuration we found that there is no ADS support on the version samba-3.0.21a-1-noads-sunos5.9-sparc.pkg.gz. Do you have any ADS support package for Sun Solaris 9. I would be surprised to see it, for a number of reasons: - Solaris doesn't have MIT/Heimdal Kerberos. It has SEAM, aka Sun Kerberos. I don't know if this matters, but ... - Solaris doesn't have OpenLDAP. It has Sun LDAP. I don't know if this matters, but ... This may have changed in 10, but as of the last time I looked at 9, it was still the Sun specialized versions (for good reasons, from what I've read) Take a look at www.openpkg.org, as it will (as of CVS/upcoming 2.6) build Samba (and MIT Kerberos/OpenLDAP/a bucket of other open source tools) for many platforms including Solaris. I currently use OpenPKG, and find it quite handy. -- adam -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] CIFS + NFS'ing a single filesystem w/ locking
Hi, I have a Solaris 10 server exporting UFS directories using built-in NFS. I've built Samba 3.0.20b from OpenPKG (www.openpkg.org). I have a Solaris 10 (x86) client mounting the NFS share and opening OpenDocument files using StarOffice 8 (SO8, aka OO2.0). I also have a Windows 2003 Terminal Server mounting the Samba share and opening documents with SO8. This is a temporary development environment, so I can screw around with it. I have a similar, production environment using RHEL3 (clients) and Solaris 9 (server), with no Samba. Ie: I would like to export NFS shares as CIFS shares using Samba. But: I want file locking. StarOffice 8/OO2.0 support file locking, whereby the first user to open a file will place a lock* on the file, and the other users will get a read-only file. This works fine with NFS nlockmgr (cross platform, linux/solaris). However, when I add Samba to the mix, it doesn't seem to see the locks. I am under the impression this is because Solaris does not support kernel oplocks. Here is my smb.conf: ---smb.conf--- [global] workgroup = test security = share [shared] path = /export/home/shared read only = No guest ok = yes locking = yes [I've tried leaving this out] kernel oplocks = yes [I've tried this as yes and left it out] oplocks = yes [I've tried not setting this, and diff combinations with locking] level2 oplocks = no [I've tried not setting this] ---smb.conf I also attempted to NFS mount the share from a RHEL3 box (which should support kernel oplocks) and then share it back out with Samba. Locks do not work here either (yes, I had anon and root properally set). I would think that the kernel oplock code in RHEL3's kernel would allow the locks to propegate down from Samba, and back out to the NFS server using lockd. It could also be that my understanding of what a lock is is not exactly correct. Ie: NFS lock != Samba lock. I have some indication of this based on the locking directory that exists for Samba, and the fact that lock on Windows is not implemented the same way as on UNIX. The specific symptoms of the lock not working are the following: - a file first opened on the solaris client will yield a file type selection box on the windows box (a sign that windows can't read the file, and a sign it is seeing some kind of lock) - a file first opened on the windows side, and then opened on the solaris client side will show read/write status on both clients - if the windows client then tries to save, it will get an I/O error (so it must be seeing some kind of lock...) - if the solaris client tries to save, it can save fine, not being informed that another user has the file open This is obviously somewhat problmatic! Am I totally missing something here, or does NFS/CIFS file locking simply not work? I seem to remember reading somewhere that NFS/CIFS from a Linux host works fine, and that NFS/CIFS on other systems won't work (save IRIX) because they don't have kernel oplock support for Samba. So: have I done something wrong, or is this the way things are? OR: Is it that the type of lock placed on the file when *nix OO2.0 opens a file is incompatible with the type of lock Samba thinks is ok wrt oplocks in the Samba code? *: It looks like lock type is a F_WRLCK on *nix, and a dwAccess |= GENERIC_WRITE for win32, based on my cursory, vastly under-knowledged reading of the OpenOffice 2.0 source code (sal/osl/unx/file.cxx and sal/osl/w32/file.cxx). Line 2450 in w32/file.cxx, line 548 in unx/file.cxx. Thanks a bunch! -- adam -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
