Re: [Samba] Question on how to get Samba to use larger pread/write calls.
On 17 January 2011 08:14, Chris Duffy wrote: > We are testing Samba 3 (and 4) on Fedora Core 13, > 10Gbit connection with a Mac OS 10.6.4 system > as the client. We will be adding some Windows > machines sooner or later with 10Gbit interfaces. > > We are seeing 100-150MBytes/sec read or write > performance between the Mac and the FC13 system > over 10Gbit interface but it should be capable of > 400-500MBytes/sec. We have a local raid > on the FC13 system that runs 1GByte/sec locally > using an Areca 1880-ix-16 raid card (6Gbit version). > It has 16 fast Hitachi disks in a Raid5 format > using xfs filesystem. > > The problem here is that samba is poking the Areca > at 128KByte I/O's on preads and writes, i.e. > shown to us using strace on the smbd daemons > that are running. Using vmstat/iostat/sar utilities, > we see 100% utilization of the Areca card because the > average wait time is real high and the average > queue length to it is also high..too many > small I/O's. > This is not the case if I run "fio" or "dd" locally > to/from the Areca's raid using 1-4MByte I/O's. > I see fast I/O... > > I do not see any way to increase the size of Samba's > pread/write's in the smb.conf documentation. I > am sure it may be just a matter of getting the source > code and making some changes to allow larger > sized IO's butand of course I suppose Windows > clients may complain but > > I remember that back in the old Irix days with the > group of engineers in Australia I worked with, > we had Samba screaming fast but not sure if they > tweaked the version of Samba on Irix to do this. Hi Chris :) IIRC, we used a carefully tweaked read ahead module to make sure that I/Os were hitting the disks properly aligned and of reasonable size. http://www.samba.org/samba/docs/man/manpages-3/vfs_readahead.8.html > > Can you guys come up with a way for us to allow > the reads/writes to/from the disks to be tunable > up to say 4MB in size? > > Thx > chris duffy > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Connecting an iMac to os/2
On 11 January 2011 12:07, James Moe wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello, > I have an iMac v10.6. I'd like to get it to connect to an old os/2 > server, v4.5 fp3. > Using smbutils on the iMac: > > $ smbutil -v view //sma-server1.sma.com > smbutil: server connection failed: RPC struct is bad > > Can anyone suggest what changes may be made that will correct this > error? Is it even possible? I don't think that the Mac OS X client will support a server that old. You could file a bug at bugreporter.apple.com, but I'm pretty confident that's what they'll tell you. Sorry. > > - -- > James Moe > moe dot james at sohnen-moe dot com > 520.743.3936 > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.15 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk0suJ4ACgkQzTcr8Prq0ZPJ7wCeMTU56gbcigWb1gsjR57AxkGm > ycEAoLKKbbvi1plOlr/7EEHJV7KYg+79 > =ls/L > -END PGP SIGNATURE- > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] macmini samba
On 24 August 2010 15:09, larry wrote: > Hi, > > > > Did anyone know the samba daemon,config file and the installation path on > MAC OS 10.6? $ smbd -b Built by:r...@ghosttown.apple.com Built on:Thu May 6 17:48:29 PDT 2010 Built using: /usr/bin/cc Build host: Darwin ghosttown.apple.com 10.0 Darwin Kernel Version 10.0.0: Fri Jul 31 22:46:25 PDT 2009; root:xnu-1456.1.25~1/RELEASE_X86_64 x86_64 SRCDIR: /SourceCache/samba/samba-235.4/samba/source BUILDDIR:/var/tmp/samba/samba-235.4~1/x86_64 Paths: SBINDIR: /usr/sbin BINDIR: /usr/bin SWATDIR: /usr/swat CONFIGFILE: /private/etc/smb.conf LOGFILEBASE: /private/var/log/samba LMHOSTSFILE: /private/etc/lmhosts LIBDIR: /usr/lib/samba SHLIBEXT: dylib LOCKDIR: /private/var/samba PIDDIR: /private/var/run SMB_PASSWD_FILE: /private/var/db/samba/smbpasswd PRIVATE_DIR: /private/var/db/samba > > > > I have a problem that the windows users can only access shares on MAC by > computer name. > > > > But need input user name and password by IP address. > > > > > > > > Thanks > > > > Larry > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] mac client: folder copy problem
2009/12/16 Anton Starikov : > > On Dec 16, 2009, at 9:45 PM, James Peach wrote: > >> 2009/12/16 Anton Starikov : >>> One question. >>> >>> The fact that client ignore ACL capabilities of server, it is also normal >>> for current smbfs implementation? >> >> Even in 10.5, the smbfs client does not ignore the filesystem ACL >> support attribute. > > With unix extensions enabled? > > Then I don't understand. Where is the problem. > > On server side I see > > smbd_audit: antst|xxx|antst|sys_acl_get_file|ok|. > smbd_audit: antst|xxx|antst|sys_acl_get_file|ok|. > smbd_audit: antst|xxx|antst|sys_acl_get_entry|ok| > smbd_audit: antst|xxx|antst|sys_acl_free_acl|ok| > smbd_audit: antst|xxx|antst|sys_acl_free_acl|ok| > smbd_audit: antst|xxx|antst|get_nt_acl|ok|. > > > a file: > > # getfacl /home/antst/tt1 > getfacl: Removing leading '/' from absolute path names > # file: home/antst/tt1 > # owner: antst > # group: cmsusers > user::rw- > user:mohand:rwx > group::r-- > mask::rwx > other::--- > > And on client side: > > ls -le /tmp/qq1/tt1 > -rw-r- 1 antst cmsusers 0 Dec 16 20:19 /tmp/qq1/tt1 > > > And if I try to set ACL from OSX I get > $ chmod +a "mohand allow write" /tmp/qq1/tt1 > chmod: Failed to set ACL on file '/tmp/qq1/tt1': Operation not supported > > Looking into the source code of client (thanks for link) I see that > CIFS_UNIX_POSIX_ACLS_CAP is not referenced in the sources (except header > file, where it is defined). Although it can mean nothing and you can use > somewhere in the code just numerical value. It doesn't use unix ACLs, it uses SMB ACLs. -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] mac client: folder copy problem
2009/12/16 Anton Starikov : > One question. > > The fact that client ignore ACL capabilities of server, it is also normal for > current smbfs implementation? Even in 10.5, the smbfs client does not ignore the filesystem ACL support attribute. > > On Dec 16, 2009, at 9:28 PM, James Peach wrote: > >> 2009/12/16 Jeremy Allison : >>> On Wed, Dec 16, 2009 at 07:00:09PM +0100, Anton Starikov wrote: >>>> And although it creates directory, it doesn't copy contents, because it >>>> stops process of copying directory after this error. If I repeat filesync, >>>> the contents of directory will be copid (cause directory is already here). >>>> >>>> So, it looks exactly the same. >>>> If so, then problem in chflags(). >>>> I expect that samba on linux is compiled without support for chflags, >>>> obviously. >>>> >>>> I presume that settings "unix extensions = no" would probably fix this, >>>> but it has a drawback, because then you loose native unix things like >>>> symlinks etc. >>>> >>>> Which is, at least in our case is not possible, cause shares accessed by >>>> both, mac and linux clients over NFS (the same clients on different hosts) >>>> and symlinks are heavily used. >>>> >>>> I think, OSX client, when it sees that server supports "unix extensions", >>>> expects that on other side is OSX server with samba which supports chflags. >>>> >>>> So, if we don't discuss rewrite of OSX cifs FS, then only solution is to >>>> "emulate" chflags support on samba side (or convert flags to XFS/ETX3 >>>> attrs somehow) >>> >>> Hmmm. Looks like a client bug then, in that they don't cope with an >>> error on chflags set. What error is the Samba server returning here ? >>> >>> George, what errors can the MacOSX client cope with and continue ? >> >> FileSync wants to create accurate copies of files, including all their >> metadata. We just pass the error up the stack. The current code does >> not look too closely at the unix capabilities, we should be looking >> at the flags mask in the UNIX_INFO2 response and handling the case >> where the server doesn't understand any flags. >> >> Please file a bug at http://bugreporter.apple.com and attach the >> packet trace. This will help us to make a case to fix this in an >> update. >> >> -- >> James Peach | jor...@gmail.com > > -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] mac client: folder copy problem
2009/12/16 Anton Starikov : > > On Dec 16, 2009, at 7:08 PM, Jeremy Allison wrote: > >> On Wed, Dec 16, 2009 at 07:00:09PM +0100, Anton Starikov wrote: >>> And although it creates directory, it doesn't copy contents, because it >>> stops process of copying directory after this error. If I repeat filesync, >>> the contents of directory will be copid (cause directory is already here). >>> >>> So, it looks exactly the same. >>> If so, then problem in chflags(). >>> I expect that samba on linux is compiled without support for chflags, >>> obviously. >>> >>> I presume that settings "unix extensions = no" would probably fix this, but >>> it has a drawback, because then you loose native unix things like symlinks >>> etc. >>> >>> Which is, at least in our case is not possible, cause shares accessed by >>> both, mac and linux clients over NFS (the same clients on different hosts) >>> and symlinks are heavily used. >>> >>> I think, OSX client, when it sees that server supports "unix extensions", >>> expects that on other side is OSX server with samba which supports chflags. >>> >>> So, if we don't discuss rewrite of OSX cifs FS, then only solution is to >>> "emulate" chflags support on samba side (or convert flags to XFS/ETX3 attrs >>> somehow) >> >> Hmmm. Looks like a client bug then, in that they don't cope with an >> error on chflags set. What error is the Samba server returning here ? > > Of course it is client error. But it is much easy to add "dirty hack" to > samba on server that fooling around bunch of clients. > Does Apple opensource their implementation of smbfs? http://www.opensource.apple.com/source/smb/smb-348.7/ -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] mac client: folder copy problem
2009/12/16 Jeremy Allison : > On Wed, Dec 16, 2009 at 07:00:09PM +0100, Anton Starikov wrote: >> And although it creates directory, it doesn't copy contents, because it >> stops process of copying directory after this error. If I repeat filesync, >> the contents of directory will be copid (cause directory is already here). >> >> So, it looks exactly the same. >> If so, then problem in chflags(). >> I expect that samba on linux is compiled without support for chflags, >> obviously. >> >> I presume that settings "unix extensions = no" would probably fix this, but >> it has a drawback, because then you loose native unix things like symlinks >> etc. >> >> Which is, at least in our case is not possible, cause shares accessed by >> both, mac and linux clients over NFS (the same clients on different hosts) >> and symlinks are heavily used. >> >> I think, OSX client, when it sees that server supports "unix extensions", >> expects that on other side is OSX server with samba which supports chflags. >> >> So, if we don't discuss rewrite of OSX cifs FS, then only solution is to >> "emulate" chflags support on samba side (or convert flags to XFS/ETX3 attrs >> somehow) > > Hmmm. Looks like a client bug then, in that they don't cope with an > error on chflags set. What error is the Samba server returning here ? > > George, what errors can the MacOSX client cope with and continue ? FileSync wants to create accurate copies of files, including all their metadata. We just pass the error up the stack. The current code does not look too closely at the unix capabilities, we should be looking at the flags mask in the UNIX_INFO2 response and handling the case where the server doesn't understand any flags. Please file a bug at http://bugreporter.apple.com and attach the packet trace. This will help us to make a case to fix this in an update. -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Permission problem with mac os x client
2009/7/16 Udo Mueller : > Hi all, > > Server: Debian 5.0 with samba 3.2.5 > Client: Current Mac OS X > > Wanted: files with 0760, directories with 2770 > > Config: create mask = 760 > directory mask = 770 > force create mode = 760 > force directory mode = 2770 > > Problem: files created with 644 or 764 or 600 > directories created with 2700 or 0770 or 0700 > > My setup works just perfect with Windows Clients. > > Anyone knows why this doesnt work with mac os x? try "unix extensions = no" -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Time capsule and "bad smb"
2009/4/21 Pietro Battiston : > Il giorno lun, 16/02/2009 alle 23.03 -0800, Jeremy Allison ha scritto: >> On Mon, Feb 16, 2009 at 09:42:48PM -0800, James Peach wrote: >> > >> > Volker's suggestion is the best. >> > >> > Pietro should to <http://developer.apple.com/bugreporter/> and log a >> > bug against the TIme Capsule. It would be best to attach a packet >> > trace to the bug. Follow the instructions here: >> > >> > <http://wiki.samba.org/index.php/Capture_Packets> >> >> Boo, hiss, cop-out :-). >> >> > I'll try and dig up a time capsule to bring to Connectathon next week >> > if any of the Linux smbfs folks would like to test against it ... >> >> Sure, I'll be there and I'd love to take a look at it. >> Will there be any Time Capsule engineers there though >> if we do find bugs ? > > Did someone debug the problem? yes > The bug I filed (# 6598363) in the Apple bugtracker is just there, > alone, with apparently no care given to, since more than 2 months... Not everything that happens to a bug report is visible to the originator. When they ship a release that includes the fix, the bug should be sent back to you to verify. Sorry the process is so opaque. -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Re: samba Digest, Vol 76, Issue 10
2009/4/10 Alex Thurley : > Dear List, > > I wonder if somebody has a correctly working SMB service in Mac OS X Server > 10.5.x. I've got here lots of "This process has forked.." This is because a call to the Security framework touches a part of CoreFoundation that is unhappy that Samba forks without a subsequent exec. It's annoying but harmless. > and "Broken Pipe" > errors as described in this post: > http://www.afp548.com/forum/viewtopic.php?showtopic=22295 Not really enough info to say what is happening here. the broken pipe means that the client disconnected unexpectedly, but it's not clear why. As some of the posters in that thread note, there is a bug in the streams module where we return an error for reads after the end-of-file (we ought to succeed but return no data). > > Would be nice if a Samba-guru could point us to the right direction. Volker's suggestion to file a Radar with Apple is spot on. -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Time capsule and "bad smb"
2009/2/18 Pietro Battiston : > Il giorno lun, 16/02/2009 alle 21.42 -0800, James Peach ha scritto: > >> Pietro should to <http://developer.apple.com/bugreporter/> and log a >> bug against the TIme Capsule. It would be best to attach a packet >> trace to the bug. Follow the instructions here: >> >> <http://wiki.samba.org/index.php/Capture_Packets> > > To report a bug I had to give my home address among a lot of other > personal data. Apple will certainly send me home a flowers bouquet to > thank for my contribution. So nice. > > Anyway, done, Bug ID # 6598363. Cool! > > Thank you everyone for the help. Looks like the Time Capsule is sending an incorrect word count field in the logoff response. Thanks for taking the time to send a trace. -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba+acl problem on OSX
2009/2/17 Eero Volotinen : > I have problem using samba+acl (ext3+acl) on OSX client. > > Access rights works fine on Linux and Windows series, but OSX Leopard says > access denied to every directory that is using acl. > > Is OSX cifs client too stripped that it cannot use acl or is this OSX bug? > Is there any solution on OSX that can access samba+acl directories? The Mac OS X client looks at the posix mode bits to preflight access checks. you can disable this on the server side by setting "unix extensions = no" -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Time capsule and "bad smb"
2009/2/16 Jeremy Allison : > On Mon, Feb 16, 2009 at 09:42:48PM -0800, James Peach wrote: >> >> Volker's suggestion is the best. >> >> Pietro should to <http://developer.apple.com/bugreporter/> and log a >> bug against the TIme Capsule. It would be best to attach a packet >> trace to the bug. Follow the instructions here: >> >> <http://wiki.samba.org/index.php/Capture_Packets> > > Boo, hiss, cop-out :-). > >> I'll try and dig up a time capsule to bring to Connectathon next week >> if any of the Linux smbfs folks would like to test against it ... > > Sure, I'll be there and I'd love to take a look at it. > Will there be any Time Capsule engineers there though > if we do find bugs ? No, but if you do the testing, I'll write up the bugs for you -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Time capsule and "bad smb"
2009/2/16 Jeremy Allison : > On Mon, Feb 16, 2009 at 05:01:53PM +0100, Pietro Battiston wrote: >> Some update to the mail below: if I understand correctly, there are two >> different problems showing up: >> 1) mount.cifs and the Time Capsule (I have no idea on which front the >> problem is) don't seem to be able to handshake correctly if the share >> name contains whitespaces. I didn't notice at first glance, but then found >> some "no such share" errors in dmesg - not reported as output of the >> command. Then I tried to change the share name (on the Time Capsule, >> obviously) to a single word and reconnect, and it worked (almost, keep >> reading). >> 2) on some particular smb commands - please bear with me if what I say >> is somewhat imprecise - the Time Capsule sends back packets badly >> formatted (or that mount.cifs thinks are badly formatted). This happens, >> in particular: >> - for some packets that report an error, such as the "no such share" >> - for some packets during the unmount >> >> This is the reason why - as far as I can conjecture - though the >> handshaking failed because the name of the share could not be resolved, >> I didn't get a message about that: in the communication where the Time >> Capsule said "hey, I don't have that share!", some packet was reported >> as incorrect and dropped. >> >> Notice that now it does mount immediately, but when I unmount it takes >> almost a minute, and in dmesg I get: >> >> [341279.777815] Bad SMB: : dump of 48 bytes of data at 0xcc482e00 >> [341279.777836] 0027 424d53ff 0074 00018800 ' . . . � S M B >> t . . . . . . . >> [341279.777855] >> 2118 . . . . . . . . . . . . . . . ! >> [341279.777873] 0096 ff03 0f00 6401a8c0 . . . . . >> � . . . . . . � � . d >> >> Googling, I found a very similar problem: >> https://bugzilla.redhat.com/show_bug.cgi?id=191112 >> , in which case it was said to the reporter "the server is buggy, go >> tell to the producer". Now, before trying, probably in vain, to talk >> with some Apple guy, I'd like to know the opinion of someone slightly >> more expert than me (I have used smb/cifs 5-6 times in all my life), >> also because my "conjecture" doesn't explain everything... in >> particular it's a mistery for me the fact that one of the two sites I >> linked in the former email claimed to have mounted successfully a Time >> Capsule with a share name containing whitespaces. I'll try to contact >> the writer of that page (notice that before trying changing the share name, >> I had >> tried changing the Time Capsule firmware, installing all the 3 available >> versions with no luck, so the difference isn't there). >> >> In the meanwhile, any hint? I anyone connecting to a Time Capsule without >> problems? > > We have an Apple Samba Team member, James Peach. James, any ideas > on what is going wrong here ? Volker's suggestion is the best. Pietro should to <http://developer.apple.com/bugreporter/> and log a bug against the TIme Capsule. It would be best to attach a packet trace to the bug. Follow the instructions here: <http://wiki.samba.org/index.php/Capture_Packets> I'll try and dig up a time capsule to bring to Connectathon next week if any of the Linux smbfs folks would like to test against it ... -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] mac os 10.5.5 and symbolic link to www
2008/10/29 Marc Fromm <[EMAIL PROTECTED]>: >>(unix extensions = no) > My smb.conf does not contain unix extensions option. "unix extensions = yes" is the default that will be used if smb.conf does not specify otherwise > Is this a setting on the mac that I need to change? you need to change it on the server >> If you want the server to follow the symlink instead, you have to turn off >> unix extension support > I'm not sure about the above comment. On the server I can follow the symbolic > link to the > www directory, it only does not work when a Mac makes a samba connection and > on the > Mac I try to go to the www directory. Because the target of the symlink is a location on the server. When the Mac client tries to resolve the symlink, it will try to access the corresponding location on the client. If you turn the unix extensions support off, then the server will follow the symlink and the Mac will behave just like the Windows clients > > -Original Message- > From: James Peach [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 28, 2008 3:40 PM > To: Marc Fromm > Cc: samba@lists.samba.org > Subject: Re: [Samba] mac os 10.5.5 and symbolic link to www > > 2008/10/28 Marc Fromm <[EMAIL PROTECTED]>: >> We have a new server running Red Hat 5.2EL. >> Windows machines can samba to the linux server with no problems, including >> symbolic links to the www directory. >> Our Mac OS 10.5.5 machines have a problem with symbolic links to the www >> directory. >> On the Mac computers, the symbolic links show up as an alias that cannot be >> followed. >> These same MAC computers can samba to the www directory via a symbolic link >> on our Fedora Core 5 server. > > The Mac is almost certainly using the unix extensions to follow the > symlink on the client side. If you want the server to follow the > symlink instead, you have to turn off unix extension support (unix > extensions = no). > >> >> Since the www symbolic link works on a PC that sambas to the Red Hat server, >> is this strictly a problem on the macs or is there a setting I need to >> change in a conf file on the Red Hat server, since the same Macs can use the >> symbolic link to the www directory on the Fedora server? >> >> Thanks >> >> Marc >> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/listinfo/samba >> > > > > -- > James Peach | [EMAIL PROTECTED] > -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] mac os 10.5.5 and symbolic link to www
2008/10/28 Kyle <[EMAIL PROTECTED]>: > > Can some one clarify that statement a little more for the hard at learning > please? Do you mean the MAC is using the SAMBA symlink and attempting to > follow it to a location on its local disk? Yes. Because Windows clients do not understand the SMB protocol extension the Mac uses in this case, the server follows the symlink on their behalf (to a location on the server's disk). > > "The Mac is almost certainly using the unix extensions to follow the symlink > on the client side. If you want the server to follow the symlink instead, > you have to turn off unix extension support (unix extensions = no)." > > -------- > Kind Regards > > Kyle > > > > James Peach wrote: >> >> 2008/10/28 Marc Fromm <[EMAIL PROTECTED]>: >> >>> >>> We have a new server running Red Hat 5.2EL. >>> Windows machines can samba to the linux server with no problems, >>> including symbolic links to the www directory. >>> Our Mac OS 10.5.5 machines have a problem with symbolic links to the www >>> directory. >>> On the Mac computers, the symbolic links show up as an alias that cannot >>> be followed. >>> These same MAC computers can samba to the www directory via a symbolic >>> link on our Fedora Core 5 server. >>> >> >> The Mac is almost certainly using the unix extensions to follow the >> symlink on the client side. If you want the server to follow the >> symlink instead, you have to turn off unix extension support (unix >> extensions = no). >> >> >> > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba > -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Installing windows drivers into print$ on OS X 10.5 Leopard
2008/10/26 Chris <[EMAIL PROTECTED]>: > Has anyone had any success installing windows printer drivers onto a > leopard-hosted print$ share? > > If I use the Add Printer Wizard method, if copies the driver files to > \\SERVER\print$\W32X86 then fails with an "Operation cannot be completed." > > If I use the rpcclient method I get a WERR_INVALID_PARAM error. Using the > Adobe Generic PostScript driver as an example. > > osxserver:W32X86 root# ls -l > total 2832 > drwxrwxr-x 2 root domainadmins 68 Oct 25 23:16 0 > drwxrwxr-x 2 root domainadmins 68 Oct 25 23:16 2 > drwxrwxr-x 2 root domainadmins 68 Oct 26 00:00 3 > -rw-r--r-- 1 fred domainadmins 13492 Oct 26 01:43 DEFPRTR2.PPD > -rw-r--r-- 1 fred domainadmins 135248 Oct 26 01:43 PS5UI.DLL > -rw-r--r-- 1 fred domainadmins 26056 Oct 26 01:43 PSCRIPT.HLP > -rw-r--r-- 1 fred domainadmins 792644 Oct 26 01:43 PSCRIPT.NTF > -rw-r--r-- 1 fred domainadmins 470608 Oct 26 01:43 PSCRIPT5.DLL > > osxserver:W32X86 root# rpcclient localhost -d3 -Ufred%password -c 'adddriver > "Windows NT x86" > "genericps:PSCRIPT5.DLL:DEFPRTR2.PPD:PS5UI.DLL:PSCRIPT.HLP:NULL:RAW:PSCRIPT.NTF"' > added interface ip=192.168.223.13 bcast=192.168.223.255 nmask=255.255.255.0 > lp_load: refreshing parameters > Initialising global parameters > params.c:pm_process() - Processing configuration file > "/private/etc/smb.conf" > Processing section "[global]" > params.c:pm_process() - Processing configuration file "/var/db/smb.conf" > Processing section "[global]" > Processing section "[global]" > Connecting to host=localhost > Connecting to 127.0.0.1 at port 445 > Doing spnego session setup (blob length=126) > got OID=1 2 840 113554 1 2 2 > got OID=1 2 840 48018 1 2 2 > got OID=1 3 6 1 4 1 311 2 2 10 > got principal=cifs/[EMAIL PROTECTED] > Got challenge flags: > Got NTLMSSP neg_flags=0x40898215 > NTLMSSP: Set final flags: > Got NTLMSSP neg_flags=0x40088215 > NTLMSSP Sign/Seal - Initialising with flags: > Got NTLMSSP neg_flags=0x40088215 > rpc_pipe_bind: Remote machine localhost pipe \lsarpc fnum 0x7400 bind > request returned ok. > lsa_io_sec_qos: length c does not match size 8 > rpc_pipe_bind: Remote machine localhost pipe \spoolss fnum 0x7401 bind > request returned ok. > result was WERR_INVALID_PARAM I believe that this problem is because the Darwin VFS doesn't implement the read operation, only the pread operation. You should be able to work around this by temporarily commenting out the "vfs objects" line in /etc/smb.conf while you do the printer setup. > > > smb.log shows this: > osxserver (127.0.0.1) connect to service print$ initially as user fred > (uid=1025, gid=20) (pid 36350) > [2008/10/26 02:01:50, 2, pid=36350] > /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_file(391) > fred opened file W32X86/PSCRIPT5.DLL read=Yes write=No (numopen=1) > [2008/10/26 02:01:50, 2, pid=36350] > /SourceCache/samba/samba-187.8/samba/source/smbd/close.c:close_normal_file(399) > fred closed file W32X86/PSCRIPT5.DLL (numopen=0) NT_STATUS_OK > [2008/10/26 02:01:50, 1, pid=36350] > /SourceCache/samba/samba-187.8/samba/source/smbd/service.c:close_cnum(1284) > osxserver (127.0.0.1) closed connection to service print$ > > User fred is a member of Admins and Domain Admins and I have explicitly > added SePrintOperatorPrivilege to EXAMPLE\Domain Admins (it didn't help.) > > This used to work great on 10.4... > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba > -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] mac os 10.5.5 and symbolic link to www
2008/10/28 Marc Fromm <[EMAIL PROTECTED]>: > We have a new server running Red Hat 5.2EL. > Windows machines can samba to the linux server with no problems, including > symbolic links to the www directory. > Our Mac OS 10.5.5 machines have a problem with symbolic links to the www > directory. > On the Mac computers, the symbolic links show up as an alias that cannot be > followed. > These same MAC computers can samba to the www directory via a symbolic link > on our Fedora Core 5 server. The Mac is almost certainly using the unix extensions to follow the symlink on the client side. If you want the server to follow the symlink instead, you have to turn off unix extension support (unix extensions = no). > > Since the www symbolic link works on a PC that sambas to the Red Hat server, > is this strictly a problem on the macs or is there a setting I need to change > in a conf file on the Red Hat server, since the same Macs can use the > symbolic link to the www directory on the Fedora server? > > Thanks > > Marc > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba > -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbd
2008/10/23 vishesh <[EMAIL PROTECTED]>: > dear all > When samba running, i issued command to list process using ps -C smbd list > more than one process. > I have following queries regarding this > how one can determine how many smbd process run? > Is there any way to determine which smbd process link with which share > session? The smbstatus command will tell you this -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] strang locking behaviour with macosx clients
2008/9/30 Holger Hegmanns <[EMAIL PROTECTED]>: > On Mon, Sep 29, 2008 at 08:45:40PM -0700, James Peach wrote: >> 2008/9/29 Holger Hegmanns <[EMAIL PROTECTED]>: >> > The only debug information I have is the output of smbstatus. The column >> > "DenyMode" looks totally different if a mac or a windows client opens >> > the same file. >> > >> > A *windows* client opens a file: >> > [...] >> > Locked files: >> > Pid UidDenyMode Access R/WOplock >> > SharePath Name Time >> > -- >> > 19919501DENY_ALL 0x2019f RDWR >> > EXCLUSIVE+BATCH /data0/prod ~test~0kjyv(.idlk Tue Sep 30 00:50:24 2008 >> > 19919501DENY_WRITE 0x20089 RDONLY >> > EXCLUSIVE+BATCH /data0/prod test.indd Tue Sep 30 00:50:24 2008 >> > >> > A *mac* client opens a file: >> > [...] >> > Locked files: >> > Pid UidDenyMode Access R/WOplock >> > SharePath Name Time >> > -- >> > 19564501DENY_NONE 0x20007 RDWR NONE >> > /data0/prod ~test~0kjyv(.idlk Tue Sep 30 00:51:43 2008 >> > 19564501DENY_NONE 0x20001 RDONLY NONE >> > /data0/prod test.indd Tue Sep 30 00:51:43 2008 >> > >> > Believe it or not, but generally windows denies the opening of a file >> > that is already opened on a mac. >> >> It's the client's choice which kind of deny mode to use. If the OS X >> application is happy to use DENY_NONE, then presumably that's correct >> for that usage. There's no bug here and nothing you can do on the >> server to alter this behaviour. > > Thanks for your help, James. But who is responsible for the lock of this > file? The application (Indesign by the example above)? Only with the > existence of the .idlk file? The application is 100% responsible for locking. There's nothing in the protocol or the server that can override the application's choice of locking strategy. > Isn't it horrible? I guess that depends on your point of view :) > What's about that scenario: > The Mac opens the file and it takes some time to create the .idlk file. > Than there is no "lock" at all, not even an application based. If InDesign doesn't take a lock, then there's no lock. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] strang locking behaviour with macosx clients
2008/9/29 Holger Hegmanns <[EMAIL PROTECTED]>: > I'm running a samba pdc on my gentoo box in a mixed environment with a > couple of Windows XP clients and only a few MacOSX clients. The users > told me, the file locking across the platforms does not work properly > sometimes. > > I tried to google my problem, but without luck. I switched all the flags > related the lock mechanism of samba on and off, but the problem seems to > be solved yet. > > The only debug information I have is the output of smbstatus. The column > "DenyMode" looks totally different if a mac or a windows client opens > the same file. > > A *windows* client opens a file: > [...] > Locked files: > Pid UidDenyMode Access R/WOplock > SharePath Name Time > -- > 19919501DENY_ALL 0x2019f RDWR > EXCLUSIVE+BATCH /data0/prod ~test~0kjyv(.idlk Tue Sep 30 00:50:24 2008 > 19919501DENY_WRITE 0x20089 RDONLY > EXCLUSIVE+BATCH /data0/prod test.indd Tue Sep 30 00:50:24 2008 > > A *mac* client opens a file: > [...] > Locked files: > Pid UidDenyMode Access R/WOplock > SharePath Name Time > -- > 19564501DENY_NONE 0x20007 RDWR NONE > /data0/prod ~test~0kjyv(.idlk Tue Sep 30 00:51:43 2008 > 19564501DENY_NONE 0x20001 RDONLY NONE > /data0/prod test.indd Tue Sep 30 00:51:43 2008 > > Believe it or not, but generally windows denies the opening of a file > that is already opened on a mac. It's the client's choice which kind of deny mode to use. If the OS X application is happy to use DENY_NONE, then presumably that's correct for that usage. There's no bug here and nothing you can do on the server to alter this behaviour. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] OSX client, Linux server, permissions problem
2008/9/29 Brian Gregorcy <[EMAIL PROTECTED]>: >> You might be seeing the SMB unix extensions in action. In 10.5, the OS >> X SMB filesystem was taught to understand some SMB protocol extensions >> designed for unix system. what *might* be happening here is that the >> client is resetting the permissions after Samba applies the >> configuration mode masks. >> >> You should be able to verify this by packet sniffing or setting "unix >> extensions = no" on the server. >> > > That worked for me :) > > Thanks I have been looking for that for awhile now, is there any downside to > disabling unix extensions? The client will behave as though it is talking to a windows box, so unix modes will be best-effort and symlinks will be resolved on the server side rather than on the client side. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] OSX client, Linux server, permissions problem
2008/9/29 Brian Gregorcy <[EMAIL PROTECTED]>: > > > barsalou wrote: >> >> I've been using samba for some time and have always had a good experience. >> >> I decided to try and configure my home network to let all my computers >> talk to the samba share. >> >> I'm stuck on one part where my OSX client, when creating new >> files/directories, won't create them writeable by the group. >> >> I've tried what seems like every combination of directory mask, force >> directory mode, etc. but I'm unable to get the OSX client to create folders >> with 770 permissions on any newly created folders. >> >> What I'd like to do is find a way to "see" all the permission's that are >> getting applied to that directory when it is getting created. >> >> This isn't a production box, so I'm willing to try anything at the moment. >> >> The good news is that it does create new files and folders...just that >> other users can't modify them. >> >> I do have logging turned up, but do not know what I should be looking for. >> >> Scenario: >> >> Client - OSX 10.5 >> Server - Ubuntu 7.04, XFS mounted /home, Samba 3.026a >> >> >> Share section of smb.conf >> >> [shared] >> path = /home/shared >> available = yes >> browseable = yes >> writable = yes >> create mask = 02770 >> directory mask = 02770 >> force group = +shared >> >> >> Testparm results (shared section) >> [shared] >>path = /home/shared >>force group = +shared >>read only = No >> >> Hope I didn't forget anything. >> > > > > I know this doesn't help but we are seeing the same problem, I opened a bug > with apple but so far have not heard anything back. I also sent this email > to this list awhile back and did not get a response, the copy of the email I > sent is below. You might be seeing the SMB unix extensions in action. In 10.5, the OS X SMB filesystem was taught to understand some SMB protocol extensions designed for unix system. what *might* be happening here is that the client is resetting the permissions after Samba applies the configuration mode masks. You should be able to verify this by packet sniffing or setting "unix extensions = no" on the server. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] odd mac situation
2008/9/11 Mike Eggleston <[EMAIL PROTECTED]>: > Morning, > > This is somewhat off topic. I've not thought of a better place to ask > than here. > > I have a user on a Macbook (Mac OS X 10.5, Leopard) with Microsoft Office > 2008 for the mac and Parallels running an image of Microsoft Windows XP > Pro with Microsoft Office 2007. Inside Parallels and XP Pro the user can > open a spreadsheet shared from a Windows Server 2003 box, and yet the > user gets an error (read only, etc) when opening the same spreadsheet > shared from the same server on the pure mac side in Microsoft Office 2008. > > Any idea what might be going on. The user is using a domain account from > a samba PDC (ha, there's the samba reference) and I find no entries in > the Event Viewer on the Windows 2003 server. You should check that the Mac user is getting the authentication they expect. Maybe they accidentally got connected as the guest user? I expect that you could verify this from the Windows serve console. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] the field ttl in struct referral doesn't work
2008/8/31 dengke <[EMAIL PROTECTED]>: > > > > > In samba source code, the file "source\include\msdfs.h" defines a struct named > referral.In this struct, there is a field named ttl which is used to decide > how long > should client cache referral, and this field uses constant > REFERRAL_TTL(#define > REFERRAL_TTL 600) as default.My problem is when i set REFERRAL_TTL to be > 10, it doesn't work. I used this a couple of years ago with Win2K clients and it worked fine. What makes you think it's not working? -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] nmbd Hogging CPU on Mac OSX (10.5.4)
2008/8/21 Mark Jackson <[EMAIL PROTECTED]>: > Hi All, > > Firstly, I know this is a MacOS X issue and not sure if you guys can help, > but I'm really hoping you can since I don't appear to be getting any joy > elsewhere. > > Running OSX 10.5.4 and recently (last week) nmbd is hogging the CPU. I know > this is a part of the Samba server on OSX, hence the post to this mail-list. > > When I disconnect from the network, nmbd goes away and doesn't hog the CPU. > Reconnect, within a minute it comes back. Happens on both Wired and Wireless > connections. I don't have filesharing enabled within OSX. > > Checked the logs in /var/logs/samba/log.nmbd and the last entries are below. > > My Mac is on my corporate network which is 99% Windows, if that matters...? > > Any thoughts or comments appreciated as this is getting quite frustrating > now. > > Thanks, > Mark > > [2008/08/21 09:09:28, 0, pid=118] > /SourceCache/samba/samba-187.4/samba/source/lib/util_tdb.c:tdb_log(662) > tdb(/private/var/samba/gencache.tdb): tdb_rec_read bad magic 0xd9fee666 at > offset=2592 > [2008/08/21 09:09:33, 0, pid=118] > /SourceCache/samba/samba-187.4/samba/source/lib/util_tdb.c:tdb_log(662) > tdb(/private/var/samba/gencache.tdb): tdb_rec_read bad magic 0xd9fee666 at > offset=2592 > [2008/08/21 09:09:33, 0, pid=118] > /SourceCache/samba/samba-187.4/samba/source/lib/util_tdb.c:tdb_log(662) > tdb(/private/var/samba/gencache.tdb): tdb_rec_read bad magic 0xd9fee666 at > offset=2592 > [2008/08/21 09:09:33, 0, pid=118] > /SourceCache/samba/samba-187.4/samba/source/lib/util_tdb.c:tdb_log(662) > tdb(/private/var/samba/gencache.tdb): tdb_rec_read bad magic 0xd9fee666 at > offset=2592 > [2008/08/21 09:09:34, 0, pid=118] > /SourceCache/samba/samba-187.4/samba/source/nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351) > find_domain_master_name_query_fail: > Unable to find the Domain Master Browser name WORKGROUP<1b> for the > workgroup WORKGROUP. > Unable to sync browse lists in this workgroup. > [2008/08/21 09:09:34, 0, pid=118] > /SourceCache/samba/samba-187.4/samba/source/nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351) > find_domain_master_name_query_fail: > Unable to find the Domain Master Browser name WORKGROUP<1b> for the > workgroup WORKGROUP. > Unable to sync browse lists in this workgroup. > [2008/08/21 09:24:43, 0, pid=118] > /SourceCache/samba/samba-187.4/samba/source/nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351) > find_domain_master_name_query_fail: > Unable to find the Domain Master Browser name WORKGROUP<1b> for the > workgroup WORKGROUP. > Unable to sync browse lists in this workgroup. > [2008/08/21 09:24:43, 0, pid=118] > /SourceCache/samba/samba-187.4/samba/source/nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351) > find_domain_master_name_query_fail: > Unable to find the Domain Master Browser name WORKGROUP<1b> for the > workgroup WORKGROUP. > Unable to sync browse lists in this workgroup. > [2008/08/21 09:29:54, 0, pid=118] > /SourceCache/samba/samba-187.4/samba/source/lib/util_tdb.c:tdb_log(662) > tdb(/private/var/samba/gencache.tdb): remove_from_freelist: not on list at > off=8736 > [2008/08/21 09:29:54, 0, pid=118] > /SourceCache/samba/samba-187.4/samba/source/lib/util_tdb.c:tdb_log(662) > tdb(/private/var/samba/gencache.tdb): tdb_free: left free failed at 8736 gencache.tdb is corrupt, delete /var/samba/gencache.tdb. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Leopard Macs using Kerberos: Failed to parse negTokenTarg
O - Simple Protected Negotiation)
>SPNEGO
>negTokenInit
>mechTypes: 1 item
>Item: 1.2.840.48018.1.2.2 (MS KRB5 - Microsoft
> K5)
>mechToken: 6082090306092A864886F71201020201006E82...
>krb5_blob: 6082090306092A864886F71201020201006E82...
>KRB5 OID: 1.2.840.113554.1.2.2 (KRB5 - Kerberos
> 5)
>krb5_tok_id: KRB5_AP_REQ (0x0001)
>Kerberos AP-REQ
>Pvno: 5
>MSG Type: AP-REQ (14)
>Padding: 0
>APOptions:
>Ticket
>Tkt-vno: 5
>Realm: SU.WIN.STANFORD.EDU
>Server Name (Principal): cifs/sesfs.stanford.edu
>Name-type: Principal (1)
>Name: cifs
>Name: sesfs.stanford.edu
>enc-part rc4-hmac
>Encryption type: rc4-hmac (23)
>Kvno: 2
>enc-part: 24F85A3983BE0989B20CC51F...
>Authenticator des-cbc-md5
>Encryption type: des-cbc-md5 (3)
>Authenticator data: ADB975580F588B675C...
>Native OS: MacOSX
>Native LAN Manager: NETSMB
>
> Finally, here's the dump of the successful packet (Reassembled TCP (2431
> bytes)). As before, the security blob starts at byte 0x3f, but in this
> packet, at byte 0x62 (the 36th byte of the security blob), we have a byte of
> 0xa2, like the parser is expecting.
>
> 00 00 09 7b ff 53 4d 42 73 00 00 00 00 08 01 48 ...{.SMBs..H
> 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00
> 0020 00 00 01 00 0c ff 00 00 00 04 41 32 00 02 00 58 ..A2...X
> 0030 4b 00 00 32 09 00 00 00 00 4c 00 00 80 40 09 60 [EMAIL PROTECTED]
> 0040 82 09 2e 06 06 2b 06 01 05 05 02 a0 82 09 22 30 .+"0
> 0050 82 09 1e a0 0d 30 0b 06 09 2a 86 48 82 f7 12 01 .0...*.H
> 0060 02 02 a2 82 09 0b 04 82 09 07 60 82 09 03 06 09 ..`.
> 0070 2a 86 48 86 f7 12 01 02 02 01 00 6e 82 08 f2 30 *.Hn...0
> 0080 82 08 ee a0 03 02 01 05 a1 03 02 01 0e a2 07 03
> 0090 05 00 00 00 00 00 a3 82 08 46 61 82 08 42 30 82 .Fa..B0.
> 00a0 08 3e a0 03 02 01 05 a1 15 1b 13 53 55 2e 57 49 .>.SU.WI
> 00b0 4e 2e 53 54 41 4e 46 4f 52 44 2e 45 44 55 a2 25 N.STANFORD.EDU.%
> 00c0 30 23 a0 03 02 01 01 a1 1c 30 1a 1b 04 63 69 66 0#...0...cif
> 00d0 73 1b 12 73 65 73 66 73 2e 73 74 61 6e 66 6f 72 s..sesfs.stanfor
> 00e0 64 2e 65 64 75 a3 82 07 f7 30 82 07 f3 a0 03 02 d.edu0..
>
>
> I've posted the full text of the log files and packet displays on the web
> at:
>
>http://www.stanford.edu/~lanz/leopard-samba/
>
> Does this analysis look correct?
yes
> And if so, is this something that can be patched in Samba?
Fixed in Samba 3.2 ..
<http://git.samba.org/?p=samba.git;a=commit;h=59a2bcf30fef14ecc826271862b645dd3a61cb48>
--
James Peach | [EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks OS X
2008/7/30 Aquaserver <[EMAIL PROTECTED]>: > Hello > I enable oplocks on samba server and testparm send me no error. > But when 2 users open the same file there is nothing like "File in Use" (i > have seen this on a forum). > All client use OS X, normally samba works fine on it. oplocks aren't locks in the sense of you have one and I don't get access. they are a permission to cache. If an application holds an oplock on a file, that will not prevent another application opening the same file. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [Slightly OT] Mac and Samba
2008/5/21 Rubin Bennett <[EMAIL PROTECTED]>: > Hello all... > I have a question that is outside the realm of my experience but that > has come up several times recently. > > I have a mixed network (some Macs, some PCs) that needs a server. I'm > going through the standard process of deciding between Samba and a > Windows domain controller, my strong preference being to install > Linux/Samba server. The Mac won't join to a Samba (NT4-style) domain, only to an Active Directory domain. > The sticking point seems to be that the Mac users > need to be able to run Access and Quickbooks, recent versions, neither > of which are ported to the Mac as I understand it. You could run these under Parallels or VMware Fusion. > > So my question is this: When faced with this situation, what do folks > out there do? Install a Terminal server of some flavor (out of reach > for this tiny non-profit)? Or is there some simple thing I could do > that would bridge the gap in a cost effective and reasonably easy to > administer way? > > Thanks very much in advance, > Rubin > -- > Rubin Bennett > RB Technologies > http://thatitguy.com > [EMAIL PROTECTED] > (802)223-4448 > > "They that can give up essential liberty to obtain a little > temporary security deserve neither liberty nor safety" > --Benjamin Franklin, Historical Review of Pennsylvania, 1759 > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba > -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Help: justification for Linux PDC vs Windows...
On 10/04/2008, JJB <[EMAIL PROTECTED]> wrote: [snip] > Thanks everyone who posted so far. While we are at it, is Apple's > OpenDirectory a rough equivalent of AD In some ways, yes. > or is OpenDirectory just > Samba/OpenLDAP compiled on OS X? No, it's a completely different beast. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] configure script not found in newly checked out source from SVN repository.
On 26/03/2008, Siju George <[EMAIL PROTECTED]> wrote: > Hi, > > I was following > > > http://wiki.samba.org/index.php/Samba4/HOWTO#Testing_Samba4_Active_Directory_in_Ubuntu_7.04_howto > > to put Samba 4 to test. > > I got this error. > > === > [EMAIL PROTECTED]:/var/Software/samba4/source$ sudo svn update > At revision 26701. Run ./autogen.sh at this point > [EMAIL PROTECTED]:/var/Software/samba4/source$ sudo ./configure > --prefix=/usr/local > sudo: ./configure: command not found Don't run configure under sudo. do the configure and make as yourself, then do "sudo make install" to install. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba 3.0.28 and dropboxes
On 20/12/2007, CJ Keist <[EMAIL PROTECTED]> wrote: > All, > I searched archives and found one related to our problem, with > subject "samba 3.0.26a and dropboxes", but there was no solution. So > posting this again for hopes of a fix. > > We have dropboxes where users can drop files in someone else's > dropbox folder. You have write permissions but not read for the folder. > In UNIX the dropbox permision is set as 2733. This all worked fine with > Samba 3.0.6a. But now have upgraded to Samba 3.0.28 and > they are no longer working. I think that's a Samba bug, There was a change in the directory handling code that started requiring the ability to read the directory. I have a patch for this somewhere - I'll try to dig it up in the new year. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Illegal Characters in filename
On 14/09/2007, Sean Dizazzo <[EMAIL PROTECTED]> wrote: > Hi all, > > We are sharing directories from Windows 2003 server to, among other > things, Mac computers. Most of the time the windows shares work > perfectly. However we are running into a problem with users entering > odd characters into file names on the Mac clients. What sort of characters? > The Mac clients see these files/folders perfectly fine, as samba on > the Mac allows for these odd characters. However, if someone tries to > access one of these files on a windows client, the operation errors > out. The errors range from "not sufficient permissions" to "the file > doesn't exist" Which windows clients? If the server is happy to accept file names with these characters in them, it's odd that clients would not also accept them. > For internal use, we can yell at the offenders to have them stop > adding odd characters to the names. This will work somewhat. But > some of these files and folders are created by external clients that > are much harder to yell at. > > Is there any way to either use the mac samba client to limit the > allowed characters, or to somehow force a filename change when an > illegal character is entered? Not to my knowledge. The Mac client is not Samba, so you might have better luck on a Mac-specific mailing list, eg: http://lists.apple.com/mailman/listinfo/macos-x-server/ make sure you note what Os the mac clients are running and whether the SMB client is the Apple one or the Thursby one -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and OSX 10.4
On 17/08/2007, Kevin McIntosh <[EMAIL PROTECTED]> wrote: > Is OSX 10.4.10 compatible with Samba's print server software? yes > My I.T. Dept > has had no luck in getting this to work. From what I've seen online, there > does seem to be issues, but Samba also seems to be fully supported by Apple > which doesn't make sense if it's not compatible. you might ask on one of the OS X Server lists: http://lists.apple.com/mailman/listinfo/macos-x-server/ you should also provide details on exactly what you tried and how it fails to work -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] remove group mappings manually?
On 16/08/07, Paddy O'Herlihy <[EMAIL PROTECTED]> wrote: > Hi, > > We have a os x server here with duplicate groupmappings unfortunately the > net groupmap functions are broken due to apple modifications. > > Can I manually delete the groupmapping from the database? > > I assumed the group mappings were stored in ldap but can't find any > reference there. The group_mapping tdb also seems empty so asides rom > looking at the source I am at a loss. The right way to manipulate group mappings on OS X server is to use Workgroup Manager. You can add SMBSID or SMBRID attributes to groups to force them to be mapped to particular absolute or domain-relative SIDs. -- James Peach | [EMAIL PROTECTED] -- 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 MacOSX and SAMBA
On 07/06/07, Dr.Peer-Joachim Koch <[EMAIL PROTECTED]> wrote: Hi, our Mac users have sometimes trouble with samba shares. Those users are not able for a certain time ( 0.5 -20 sec) to read or write to files. Some reported error messages like "read only file" or file not found. Windows users (XP) have some also slow access, but no further problems. Our file system is also used from or linux cluster (192CPU), but we are using a GFS to share the load. I'm not sure if the gfs or ldap or something else causes the delay in the file i/o. Error messages did not appear in the samba (normal) log. Any idea ? Not really. Do these problems reproduce with a local filesystem (eg. EXT3 or XFS)? If you could provide a packet trace of the OS X clients that might be helpful (maybe). -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] OSX losses link when samba is restarted
On 25/05/07, Alexander Lazarevich <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: >> We run Samba 3.0.24 on a FC5 and RHEL4-AS systems. Works great with windows >> clients, and OSX clients work great with it too except for one problem: >> >> Whenever I restart samba (with /etc/init.d/smb restart) any OSX client that >> has a samba share open will lose that connection, and so if a person had a >> file open and was editing, all changes made since the last save are lost. >> This of course does NOT happen with windows clients, they are smart enough >> to recognize the link is reconnected. But OSX losses the link completely, >> and the share has to be remounted, which is really silly. >> >> I'm not sure if there is some smb.conf setting that will fix this for OSX, >> and not screw things up for windows clients. Or maybe there is an OSX tweek >> to make on each client? I searched this list for OSX and found no similar >> problems. Arghgh. >> >> Anyone see this behavior and know of a fix. >> >> Our OSX clients are 10.4.9. >> >> Thanks in advance, >> >> Alex >> > This is normal behavior of OS X, I'm afraid. I would love to have a way > around it too. > > Andy Well shoot, okay so it's normal behavior, but isn't there some system setting that can be changed on the mac that changes the behavior? There must be some fix for this, I mean this is nuts if that's just the way it is and there really is no way around it. Unfortunately there is no fix in 10.4. You could file a bug with Apple, but I don't like your chances. Is there any documentation you can point me to that talks about this issue? there might be something on http://www.apple.com/support My boss uses OSX and I don't think he's going to be happy if I just say, " there is no way around it", and don't say nothing else. FWIW, the SMB client is noticeably improved in 10.5. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] strict allocate = no does not work
On 04/05/07, Markus Knapp <[EMAIL PROTECTED]> wrote: Hi! I've got Debian 4.0 on an NSLU2 with Samba. The system is on an USB-Stick, the Samba share is on an USB-Disk. If the filesystem some version of FAT? If so, FAT does not support holey files, so you will always get strict allocation. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Performance Problems in smbmount but not in smbclient
On 13/04/07, Rob Caskey <[EMAIL PROTECTED]> wrote: I have an OS X 10.4 Server machine that has abysmal performance when copying files to it over smbmount from a linux machine or through Finder on OS X but performs very well when copying files through smbclient from the same Linux and OS X machines. I have already tried the commonly suggested adjustment of net.inet.tcp.delayed_ack=0 and have not noticed a significant performance improvement. Through smbmount I am seeing about 2-3 megs up and 8 megs down, when I am in the upper 20s or lower 30s/sec with smbclient. What could account for this performance discrepancy? You are using 2 completely different SMB clients, which have different performance characteristics. Try using cifsfs on Linux - it's supported and reputed to have good performance. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Mac OSX Samba Q
On 03/04/07, Dawn & Marie Perry <[EMAIL PROTECTED]> wrote: Are Samba & Quark compatible? I haven't tested quark, but I don't know of any problems. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Resolution of Groups on Mac OS X 10.4.8...
On 12/03/07, Peter <[EMAIL PROTECTED]> wrote: Hi, my Problem: I tried to limit the disk usage for certain samba users by means of group quotas. But when looking at the disk free space from the client the quota is not honoured. So I wrote a little script trying to find out the quota left using the "dfree command" setting. So far everything is fine, but now, as soon as the script is called (I placed some debug output there) the groups, the user signing on via samba is member of, are not recognised. Calling "id" for this purpose, I got for my user a: uid=1001(a) gid=1099(dummy) groups=1099(dummy) but called from the commend line (after su s2) I got: uid=1001(a) gid=1099(dummy) groups=1099(dummy), 1098(tmp), 1002(x), 1001(y) So my questions are: How are those groups are resolved in Mac OS X? The standard unix group APIs call into libc, which eventually ends up in Directory Services and memberd. There are at least 2 layers of caching involved, so it is probably possible to see stale group membership information if you are unlucky. id(1) will only ever show you up to 15 supplementary groups. Also, Mac OS X supports nested groups, which can be surprising sometimes. You can check group memberships with dseditgroup(8): http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/dseditgroup.8.html Which mechanism is used by samba (the default installation provided by apple) to resolve this??? IIRC, Samba uses getgroups/setgroups on 10.4. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] MAC OSX-Users - samba PDC - passwd
On 19/02/07, Dr.Peer-Joachim Koch <[EMAIL PROTECTED]> wrote: Hi, we have just moved our old NT4 domain to some linux boxes running samba as a PDC. Everything is working well, but ... Setting passwords seems to be tricky. For Windows eyerything is working great. All passwords (unix,windows) are correctly set. For linux I've written a little wrapper to call smbpasswd and this is also working withou any problems. But what to do for MAC OSX users ? Any idea ? This isn't something I've ever needed to do, but there's likely to be a hint somewhere in the server documentation: http://www.apple.com/server/documentation/ Otherwise, you might ask on the os-x-server list (lists.apple.com) or macenterprise list at macenterprise.org. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: ClearCase Interop problem with recent Samba versions
On Feb 16, 2007, at 12:19 PM, Volker Lendecke wrote: On Fri, Feb 16, 2007 at 05:46:08PM +, Bill Marshall wrote: I think the Vmware Physical to Virtual converter http://www.vmware.com/products/converter/ also has problems with systems that claim to host msdfs. The wizard failed with a crazy error and there wasn't a hint until I did some network traces. Just thought if it was wise to enable dfs by default. It seems to cause quite difficult to track down grief in some situations. My experience is that "host msdfs" is OK since it just sets the capability bit. "msdfs root" can cause changes in client behaviour. We saw this in netbench testing ... I can probably dig up the traces if necessary. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Sniffer techniques
On 10/02/07, John Schmerold <[EMAIL PROTECTED]> wrote: As the group knows, I'm having compatibility issues with a critical database application. It's been wisely suggested that I monitor the line to see what's up. Problem is: I've never done this before & suspect others like me are not familiar with these techniques. I did find an old LinuxWorld article http://tinyurl.com/yrjurx however I help thinking there is more on the top. Anyone find one or more how-tos especially enlightning? There's some very brief info about packet sniffing here: http://wiki.samba.org/index.php/Capture_Packets -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Advertising Samba shares on the local network via mDNS
On 31/01/07, Rishi Srivatsavai <[EMAIL PROTECTED]> wrote: Hello All, I would like to add support for advertising Samba shares (browseable ones) on the local network using Multicast DNS. Multicast DNS allows applications to query/publish network services on the local link. I would appreciate if you could all please share your thoughts on whether such support would be welcome in Samba. If you know of existing efforts in Samba to include such support please let me know as well. On Mac OS X, the Samba service is already advertised over mDNS (by launchd). It would be useful to add the list of shares to the advertisement though. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Mac OS X and AD
On 20/01/07, David A. Toth <[EMAIL PROTECTED]> wrote: I have a question about integrating MAc OS X and Windows 2003 AD Domain. Getting the machine to join the doamin is easy. But when I try to map the home drives, I can see them but not access them. There was a note that implied this is due to sending encrypted vs non-encrypted with samba and that Win 2K3 server SP1 broke that. It says to disable kerberos authentication on the Windows side. Is that the case or is there a fix for Samba that re-enables this feature. Sorry I don't have the version of Samba it is using but just wondering if anyone on the list can point me in the right direction. Thanks! The best place to ask this sort of question is the macos-x-server list: http://lists.apple.com/mailman/listinfo/macos-x-server -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.10 - Invalid Value!!!
On 12/01/07, Volker Lendecke <[EMAIL PROTECTED]> wrote: On Thu, Jan 11, 2007 at 03:20:39PM -0800, Niatross wrote: > I have a Macintosh Xserve running OS 10.4.8 and it's running Samba 3.0.10. > Everytime a Windows XP workstation logs off the Macintosh Xserve server, the > following shows up in the log.smbd (located at var/log/samba): > > [2007/01/11 14:24:17, 0] pdb_ods.c:make_a_mod(2045) > make_a_mod: INVALID VALUE!!! pdb_ods.c is not in the original Samba sources, I would expect that this is a modification that Apple has made. You should contact your Apple support for help on this topic. See http://developer.apple.com/bugreporter/ for how to open an Apple bug. They'll probably ask for a packet trace of this. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP Clients kicked off Tiger Server - not consistent
On 20/12/06, Paul McGrath <[EMAIL PROTECTED]> wrote: Hi, I am running a Panther Server as a domain controller with a Mac Tiger Server (all latest patches) as the location of home folders and group shares. I have one group of users who keep losing connection to the server (both home and group folders). The can only reconnect to the server if they logoff the XP client and login again. I have loads of other XP users and Mac clients who do not have this problem. They are all using XPSP2. I've tried loads of server settings and some XP registry settings but it still happens. Some of these PCs where ghosted and I didn't change the SID so I am going to try that next. Any other You might have better luck asking the OS X server folk over at http://lists.apple.com/mailman/listinfo/macos-x-server -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Compilation error on Mac OS X 10.4.7
On 13/12/06, Olivier Meyer <[EMAIL PROTECTED]> wrote: Dear List: I am having difficulties compiling samba-3.0.23d on mac os x. Here is the output of 'uname -a': Darwin TI-15 8.7.0 Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC Power Macintosh powerpc The errors I get are: Compiling lib/system.c lib/system.c: In function 'sys_getxattr': lib/system.c:1420: error: too few arguments to function 'getxattr' lib/system.c: In function 'sys_fgetxattr': lib/system.c:1504: error: too few arguments to function 'fgetxattr' lib/system.c: In function 'sys_listxattr': lib/system.c:1705: error: too few arguments to function 'listxattr' lib/system.c: In function 'sys_flistxattr': lib/system.c:1741: error: too few arguments to function 'flistxattr' lib/system.c: In function 'sys_removexattr': lib/system.c:1759: error: too few arguments to function 'removexattr' lib/system.c: In function 'sys_fremovexattr': lib/system.c:1811: error: too few arguments to function 'fremovexattr' lib/system.c: In function 'sys_setxattr': lib/system.c:1842: error: too few arguments to function 'setxattr' lib/system.c: In function 'sys_fsetxattr': lib/system.c:1939: error: too few arguments to function 'fsetxattr' Since I am a C programmer, I looked at the prototype for getxattr. It is ssize_t getxattr(const char *path, const char *name, void *value, size_t size, u_int32_t position, int options); and in the lib/system.c, it is called as: return getxattr(path, name, value, size); I think that position and options can safely be set to zero, but could someone tell me if configure can be told to detect the prototype for getxattr, and add 0,0 to the argument list. This is fixed in the svn repository. To download and build this, see http://us2.samba.org/samba/devel/ -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Authenticating to a MacOS X server
On 12/12/06, Luke Sharkey <[EMAIL PROTECTED]> wrote: Hello I am currently testing Fedora Core 6 i386 on a moderately sized network (with the permission of the system administrator), with 150 or so computers, some running Mac OSX and others running NT 4.0. As to the storage of personal files and authentication, there is both a NT 4.0 server (for the NT 4.0 machines to authenticate to) and a Mac OSX server (for the Mac OS X machines to authenticate to). Having *never really done all that much networking before*, I am having problems detecting the Apple Mac servers. I am able to use konqueror to access smb:/ and browse the Windows server quite easily (even though I have not yet set up smb.conf; why is this, by the way?), and authenticating to the NT4.0 server, using the Samba-howto and winbind, would not prove too difficult, I think. However, the NT 4.0 server is due to be replaced some time this year, and so I would like to be able to authenticate to the OSX server instead. Nonetheless, though documentation for authenticating to Windows servers on the internet is excellent (samba howto, etc.) I can find very little about connecting to OSX networks. Can anyone tell me where I can find some documentation, etc., or give me a head start? At the moment, as I've already said, I don't even know how to detect the OS X server (it may be password protected, by the way). The OS X Server manuals are all online here: http://www.apple.com/support/manuals/macosxserver/ You probably should take a look at the Open Directory manual and the User Management manual at least. Secondly, seeing as OS X is unix and is distantly related to Linux, (I know this is a strange question to ask on a Samba mailing list) but is there anyway I could authenticate to the Apple server without using Samba? Yes. OS X Server supports lots of different authentication methods. See mnuals above. I would like to be able to have the /home partitions on the server, and I know Samba has problems with this due to the sockets that KDE / etc. uses Another good resource is the os-x-server mailing list: http://lists.apple.com/mailman/listinfo/macos-x-server -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] libdm.so.0 needed by smbd
On 07/12/06, Latrell Wang 王獻綱 <[EMAIL PROTECTED]> wrote: Hi all: I upgraded samba to 3.0.23d, and the compilation was successfully. However, when I want to start samba, it shows it can't find libdm.so.6. Is it related to openldap? No, it's for DMAPI, which is used to determine when files are offline (ie, the file data is stored on a tape somewhere, not on the local disk). How can I get the library? That depends on your platform. Since your Samba depends on libdm, then I assume that libdm is available for your platform. You'll need to figure out which package it is in and install that. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: help with samba
On Oct 29, 2006, at 5:49 PM, julio cruz wrote: Hi James: I hope you can give me a hand in diagnosing the problem with my samba. - I recently installed FC6 and installation worked fine - I installed Samba as well to talk with the other computer used by my kids - my computer can talk with their win XP and read/write files with no problem - their windows XP can "see" my computer [FC6] but cannot access [read/write] files and printer. Is there something I overlook? Maybe you didn't set up the right user accounts? Try working through this example: http://us2.samba.org/samba/docs/man/Samba-Guide/simple.html#AccountingOffice If this doesn't help, please post your smb.conf file and the recent entries from your log.smbd logfile. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] dmapi doesn't work on aix; possible fix included
On 29/10/06, J Raynor <[EMAIL PROTECTED]> wrote:
I'm running samba 3.0.23c on aix 5.3 TL4. I'm using Tivoli HSM 5.3.4.0
on a JFS2 filesystem. Samba compiled fine, and I set "dmapi support =
yes" in smb.conf, but samba wouldn't recognize offline files ("migrated
files" in tsm terminology). After setting a higher log level I think
I've tracked down the problem. The patch is at the bottom of this email.
The first problem is this snippet in dmapi_file_flags() in smbd/dmapi.c:
err = dm_path_to_handle(CONST_DISCARD(char *, path),
&dm_handle, &dm_handle_len);
if (err < 0) {
DEBUG(DMAPI_TRACE, ("dm_path_to_handle(%s): %s\n",
path, strerror(errno)));
if (errno != EPERM) {
return 0;
}
On AIX, dm_path_to_handle() is returning EACCES instead of EPERM, so it
hits the return 0. Is EPERM supposed to be the only allowed error, or
is this something that's likely implementation dependent?
This code was originally written for Linux and IRIX. IIRC in Linux there was
a problem where the process capabilities were reset across fork() because
Samba changes its effective user ID. So when we get a permission error
we go back and try to re-acquire our capabilities.
Changing the if-condition to (errno != EPERM && errno != EACCES) lets
things continue on. The rest of the problem in dmapi_file_flags() is
that things are running with the effective uid of the user, so dmapi
calls are failing. The posix capability DMAPI_ACCESS_CAPABILITY is
Note that DMAPI_ACCESS_CAPABILITY is not a real capability, it's just
a name for whatever capability set is needed to do DMAPI operations on
the current platform.
supposed to allow the functions to work, but to my knowledge AIX doesn't
have posix capabilties.
This is well beyond my knowledge of AIX. I used capabilities for this,
rather than
(un)become_root for performance reasons. If there's no other way to achieve the
functionality, then I guess this is fine.
I'd prefer a feature-based test for whether this is necessary, rather
than a platform-
based test. Something like
#if !defined(HAVE_POSIX_CAPABILITIES)
become_root();
#endif
I used become_root/unbecome_root around the dmapi calls, and this
appeared to get things to work. Samba's log messages are indicating
that files are offline, and Windows Explorer is picking up on this and
changing the file icons to indicate that the files are offline. However,
I don't know if my solution is entirely correct. Here's the patch:
*** dmapi.c.origSat Oct 28 02:33:13 2006
--- dmapi.c Sat Oct 28 11:12:54 2006
***
*** 246,252
DEBUG(DMAPI_TRACE, ("dm_path_to_handle(%s): %s\n",
path, strerror(errno)));
! if (errno != EPERM) {
return 0;
}
--- 246,252
DEBUG(DMAPI_TRACE, ("dm_path_to_handle(%s): %s\n",
path, strerror(errno)));
! if (errno != EPERM && errno != EACCES) {
return 0;
}
***
*** 259,266
--- 259,274
set_effective_capability(DMAPI_ACCESS_CAPABILITY);
+ #ifdef AIX
+ become_root();
+ #endif
+
err = dm_path_to_handle(CONST_DISCARD(char *, path),
&dm_handle, &dm_handle_len);
+
+ #ifdef AIX
+ unbecome_root();
+ #endif
if (err < 0) {
DEBUG(DMAPI_TRACE,
("retrying dm_path_to_handle(%s): %s\n",
***
*** 269,276
--- 277,293
}
}
+ #ifdef AIX
+ become_root();
+ #endif
+
err = dm_get_eventlist(dmapi_session, dm_handle, dm_handle_len,
DM_NO_TOKEN, DM_EVENT_MAX, &events, &nevents);
+
+ #ifdef AIX
+ unbecome_root();
+ #endif
+
if (err < 0) {
DEBUG(DMAPI_TRACE, ("dm_get_eventlist(%s): %s\n",
path, strerror(errno)));
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
--
James Peach | [EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: Re: [Samba] PLEASE HELP - MAC NEWBIE - MAC OS X 10.4.8 (Intel) compiling errors of Samba 3.0.23.c
On 24/10/06, Steven Thomas Smith <[EMAIL PROTECTED]> wrote: Hi, I'm a newbie having the same problems as reported at http://www.mail-archive.com/samba@lists.samba.org/msg78809.html. I'm writing to ask if these bug fixes have been implemented yet, and how to download if they have! The changes are in the svn repository but not yet in any released Samba version. I'm used to downloading tarballs, but have no idea how to navigate through subversion http://viewcvs.samba.org/cgi-bin/viewcvs.cgi/. You can get the bleeding edge source via anonymous rsync: rsync --recursive rsync://rsync.samba.org/ftp/unpacked/samba . -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: Re: [Samba] PLEASE HELP - MAC NEWBIE - MAC OS X 10.4.8 (Intel) - Bus Error
On 12/10/06, Dan <[EMAIL PROTECTED]> wrote: Here is what I got: (gdb) run -U administrator%"MYPASS" -I 10.1.0.11 -L 10.2.0.9 Starting program: /usr/bin/smbclient -U administrator%"MYPASS" -I 10.1.0.11 -L 10.2.0.9 Reading symbols for shared libraries . done Domain=[MY_DOMAIN] OS=[Unix] Server=[Samba 3.0.23c] Sharename Type Comment - --- Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x 0x000a11fd in rpccli_srvsvc_NetShareEnum () ooh! null pointer dereference! Can you please open a bug at bugzilla.samba.org? Assign it to [EMAIL PROTECTED] and hopefully I'll be able to do something about it in the next few days. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: Re: [Samba] PLEASE HELP - MAC NEWBIE - MAC OS X 10.4.8 (Intel) - Bus Error
On 12/10/06, Dan <[EMAIL PROTECTED]> wrote: Unfortunately I can not find a core file any where on the system. There is a directory /private/var/log/cores with smbd and nmbd folders but all are empty. Any thing else I can do to get the core file or needed info? try running smbclient under gdb gdb /path/to/smbclient (gdb) run -with -whatever -args -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: Re: [Samba] PLEASE HELP - MAC NEWBIE - MAC OS X 10.4.8 (Intel) - Bus Error
On 11/10/06, Dan <[EMAIL PROTECTED]> wrote: I was able to get things to compile but with warnings of "unrecognized option '--pie'". Add --disable-pie to your configure line. Unfortunately configure tests generally can't detect warnings, so -pie gets enabled when it probably shouldn't be. When I run things I still can not login to shares and when I run smbclient I get a "Bus Error". Could this be related to the compile warnings? Maybe a gcc thing? I don't see any glibc files on the system. Any help is greatly appreciated. Here is the output from the smbclient: This smells like a bug. When this happens, smbclient should drop a core file in /cores. It will be called /cores/core.$pid. Can you use gdb to get a stack trace of where it crashes? -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: Re: [Samba] PLEASE HELP - MAC NEWBIE - MAC OS X 10.4.8 (Intel) compiling errors of Samba 3.0.23.c - FIXED
On 11/10/06, Dan <[EMAIL PROTECTED]> wrote: I figured out what I was doing wrong. Obviously the old configure file will not work. I ran the make-tarball.sh script to reproduce the configure and everything builds fine. yep :) I usually do a ./autogen.sh && ./configure --foo -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] PLEASE HELP - MAC NEWBIE - MAC OS X 10.4.8 (Intel) compiling errors of Samba 3.0.23.c
On 11/10/06, Dan <[EMAIL PROTECTED]> wrote: Hello, I am trying to compile the latest samba 3.0.23c on MAC Intel OS X 10.4.8 and I am getting errors with the krb5 stuff. I have searched the net and found other people with the same error but didn't see any solution. Has anyone successfully compiled it on 10.4.8 Intel? Any help would be greatly appreciated as I am new to the mac platform but have lots of linux experience. The errors are below: Compiling libsmb/clikrb5.c libsmb/clikrb5.c: In function 'krb5_locate_kdc': libsmb/clikrb5.c:378: error: 'krb5_krbhst_handle' undeclared (first use in this function) libsmb/clikrb5.c:378: error: (Each undeclared identifier is reported only once libsmb/clikrb5.c:378: error: for each function it appears in.) libsmb/clikrb5.c:378: error: parse error before 'hnd' libsmb/clikrb5.c:379: error: 'krb5_krbhst_info' undeclared (first use in this function) libsmb/clikrb5.c:379: error: 'hinfo' undeclared (first use in this function) libsmb/clikrb5.c:388: error: 'KRB5_KRBHST_KDC' undeclared (first use in this function) libsmb/clikrb5.c:388: error: 'hnd' undeclared (first use in this function) libsmb/clikrb5.c:917:2: error: #error UNKNOWN_KRB5_AP_REQ_FREE_FUNCTION libsmb/clikrb5.c:959:2: error: #error UNKOWN_KRB5_AP_REQ_DECODING_FUNCTION make: *** [libsmb/clikrb5.o] Error 1 metze just checked in a change to fix this. If you try the latest code from the subversion repository, it should build. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: Re: [Samba] smbd hanging on OS X 10.4.8
On 06/10/06, nicerobot <[EMAIL PROTECTED]> wrote: Right, -i was intentional so that I can watch what it's doing from the command-line, so that I can see the messages as a smbclient attempts to connect. But it is actually hanging before it ever gets to a point in the initialization that it will be capable of responding to connection requests so I'll never see any debugging messages beyond the point where it hangs. Can you ktrace the process whilst it is hung? Is it making any system calls? -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbd hanging on OS X 10.4.8
On 05/10/06, nicerobot <[EMAIL PROTECTED]> wrote: Hi, If process all my mounts prior to the "..." bit below. It looks as if it's hanging while processing some printer config. On that assumption Can you please describe exactly what problem is occurring and the steps that you take to trigger it? and since I don't and never have had any printers attached, I've commented out the '[printers]' section from smb.conf. No section contains a 'printable = yes'. I've tried with all sections containing 'printable = no'. The '[global]' section includes 'load printers = no'. Still it hangs. Any clue or tips on things to try are greatly appreciated. Apple hasn't been able to reproduce the problem and haven't been able to come up with any recommendations that I haven't already tried. Thanks $ smbd -V Version 3.0.10 $ smbd -i -d 100 -s /etc/smb.conf ... lp_servicenumber: couldn't find printers lp_file_list_changed() file /etc/smb.conf -> /etc/smb.conf last mod_time: Mon Oct 2 13:46:25 2006 added interface ip=192.168.1.20 bcast=192.168.1.255 nmask=255.255.255.0 Netbios name list:- my_netbios_names[0]="DODO" loaded services fcntl_lock 6 8 0 1 3 fcntl_lock: Lock call successful Registered MSG_REQ_POOL_USAGE Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED Opening cache file at /private/var/samba/gencache.tdb namecache_enable: enabling netbios namecache, timeout 30 seconds reghook_cache_add: Adding key [/HKLM/SYSTEM/CurrentControlSet/Control/Print] sorted_tree_add: Enter sorted_tree_find_child: Did not find [HKLM] sorted_tree_birth_child: First child of node [NULL]! [HKLM] sorted_tree_find_child: Did not find [SYSTEM] sorted_tree_birth_child: First child of node [HKLM]! [SYSTEM] sorted_tree_find_child: Did not find [CurrentControlSet] sorted_tree_birth_child: First child of node [SYSTEM]! [CurrentControlSet] sorted_tree_find_child: Did not find [Control] sorted_tree_birth_child: First child of node [CurrentControlSet]! [Control] sorted_tree_find_child: Did not find [Print] sorted_tree_birth_child: First child of node [Control]! [Print] sorted_tree_add: Successfully added node [HKLM/SYSTEM/CurrentControlSet/Control/Print] to tree sorted_tree_add: Exit reghook_dump_cache: Starting cache dump now... ROOT/: [HKLM] (NULL) ROOT/HKLM/: [SYSTEM] (NULL) ROOT/HKLM/SYSTEM/: [CurrentControlSet] (NULL) ROOT/HKLM/SYSTEM/CurrentControlSet/: [Control] (NULL) ROOT/HKLM/SYSTEM/CurrentControlSet/Control/: [Print] (data) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] hello and question on Mac OS X Server use of Samba
On 25/09/06, Jaime Magiera <[EMAIL PROTECTED]> wrote: Hi, I'm new to the list (and samba). It's a great technology and I look forward to learning more about it. I have an OS X Server that utilizes the built-in Samba to allow for Windows client connectivity. The OSXS gets the majority of its users from an LDAP server elsewhere on the campus. On OSXS, it's expected that the Windows users will be local or that the server will be a KDC or that the server will be bound to an AD. Regrettably, my server is not bound not an AD, nor is it a Kerberos KDC for the University and the users are not local but from the campus-wide LDAP server. The only option I can think of for Windows clients to use Samba is to re-kerberize the Samba service itself to the University KDC. I can get the keytabs. However, I've been told by folks on other lists that there on some tweaks on OSXS that make Samba configuration a little different. You can definitely configure Samba to talk to the campus-wide LDAP server to resolve user names. Check the official howto and the "by example" books on samba.org. Does anyone here have experience (re)kerberizing Samba on an OSX Server? Or any suggestions how I could solve this conundrum I'm in? Or, if I'm misunderstanding something about how Samba works? AFAIK, windows clients will only do Kerberos authentication to AD member servers. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Linux Samba to Mac OSX: resource fork lock problems?
On 22/09/06, William Yang <[EMAIL PROTECTED]> wrote: I am seeking a better workaround than I currently have for the problem. Using OS X 10.3.x and 10.4.x (and possibly other versions) as workstations, and Gentoo Linux (kernel 2.6.16) with Samba 3.0.22, I have the following sequence of events. The symptom is most prevalent when dealing with multi MB files: 1. Resource fork (._ file) gets locked 2. File associated with resource fork also gets locked. 3. File gets unlocked 4. Resource fork never gets unlocked. Because the resource fork never gets unlocked, this causes problems with migration of data off the Mac to the server and occasionally results in a file being deleted unexpectedly. Can you please confirm that this behaviour is present in the most recent 10.4 update? If it is, could you please get a network trace of this behaviour and file a bug with Apple? I'm not too familiar with tcpdump syntax, but it would be best to capture entire packets (-s 0) in both directions (do you need to "in.pcap port 139" as well?). See http://developer.apple.com/bugreporter/ for how to file an Apple bug. thanks, -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] fam error
On 09/09/06, Willy Offermans <[EMAIL PROTECTED]> wrote: On Mon, Sep 04, 2006 at 10:27:35PM +1000, James Peach wrote: > On 04/09/06, Willy Offermans <[EMAIL PROTECTED]> wrote: > >Dear Samba Friends, > > > >I got the following error again and again: > > > > > >. > >Sep 4 10:58:18 sun smbd[94479]: [2006/09/04 10:58:18, 0] > >smbd/notify_fam.c:fam_check_reconnect(136) > >Sep 4 10:58:18 sun smbd[94479]: failed to connect to FAM service > >Sep 4 10:58:23 sun smbd[94479]: [2006/09/04 10:58:23, 0] > >smbd/notify_fam.c:fam_check_reconnect(136) > >Sep 4 10:58:23 sun smbd[94479]: failed to connect to FAM service > >Sep 4 10:58:24 sun smbd[94479]: [2006/09/04 10:58:24, 0] > >smbd/notify_fam.c:fam_check_reconnect(136) > >Sep 4 10:58:24 sun smbd[94479]: failed to connect to FAM service > >Sep 4 10:58:25 sun smbd[94479]: [2006/09/04 10:58:25, 0] > >smbd/notify_fam.c:fam_check_reconnect(136) > >Sep 4 10:58:25 sun smbd[94479]: failed to connect to FAM service > >Sep 4 10:58:25 sun smbd[94479]: [2006/09/04 10:58:25, 0] > >smbd/notify_fam.c:fam_check_reconnect(136) > >Sep 4 10:58:25 sun smbd[94479]: failed to connect to FAM service > >Sep 4 11:23:22 sun smbd[94479]: [2006/09/04 11:23:22, 0] > >smbd/notify_fam.c:fam_check_reconnect(136) > >Sep 4 11:23:22 sun smbd[94479]: failed to connect to FAM service > >. > > > > > >I'm using samba-3.0.23b,1 on FreeBSD 6.1 > > I've only ever tested the FAM support on IRIX. smbd will automatically > attempt to use FAM if it appears to be available, but it shouldn't > > >I did not specify anything with respect to fam in my > >/usr/local/etc/smb.conf file. > > > >I have only noticed that a new directory has been created in /tmp/ > > > >drwx-- 2 root wheel 512 Sep 4 08:45 /tmp/fam-root/ > > > >This directory is empty and updated once and a while. I mean the > >directory is recreated at a later time. Attributes and owner do not > >change. > > > >In the clients log files I find the following: > > > > > > > >[2006/09/04 11:36:41, 0] smbd/notify_fam.c:fam_check_reconnect(136) > > failed to connect to FAM service > > Socket directory /tmp/fam-root has different owner > > Failed to remove unsafe path /tmp/fam-root > >... > > > > > >It seems that the client tries to access /tmp/fam-root but has not the > >right user priviliges. > > > >Can someone help me out and explain what is going on? How can I solve > >the problem? > > You can disable FAM support by setting "fam change notify = no" in > smb.conf. This > will get rid of the messages, but obviously you won't get FAM support. > I'd have to dig > into the FAM implementation on FreeBSD to be more helpful, and I won't > be able to > do that for a couple of weeks. > > -- > James Peach | [EMAIL PROTECTED] Well, since the error message is only annoying and __not__ critical at the moment, I will just be patient then. Yes, FAM can be disabled without losing any functionality. It is merely a performance optimisation. I do not know how fam is implemented into samba and if calling the fam function in FreeBSD needs special considerations. I expected that the samba developer, responsible for the fam implementation, would have a look. I do not know if I reach that person via this mailing list. Yes, that's me. I just don't have the facility to do anything about this for couple of weeks. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] fam error
On 04/09/06, Willy Offermans <[EMAIL PROTECTED]> wrote: Dear Samba Friends, I got the following error again and again: . Sep 4 10:58:18 sun smbd[94479]: [2006/09/04 10:58:18, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:18 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:23 sun smbd[94479]: [2006/09/04 10:58:23, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:23 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:24 sun smbd[94479]: [2006/09/04 10:58:24, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:24 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:25 sun smbd[94479]: [2006/09/04 10:58:25, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:25 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:25 sun smbd[94479]: [2006/09/04 10:58:25, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:25 sun smbd[94479]: failed to connect to FAM service Sep 4 11:23:22 sun smbd[94479]: [2006/09/04 11:23:22, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 11:23:22 sun smbd[94479]: failed to connect to FAM service . I'm using samba-3.0.23b,1 on FreeBSD 6.1 I've only ever tested the FAM support on IRIX. smbd will automatically attempt to use FAM if it appears to be available, but it shouldn't I did not specify anything with respect to fam in my /usr/local/etc/smb.conf file. I have only noticed that a new directory has been created in /tmp/ drwx-- 2 root wheel 512 Sep 4 08:45 /tmp/fam-root/ This directory is empty and updated once and a while. I mean the directory is recreated at a later time. Attributes and owner do not change. In the clients log files I find the following: [2006/09/04 11:36:41, 0] smbd/notify_fam.c:fam_check_reconnect(136) failed to connect to FAM service Socket directory /tmp/fam-root has different owner Failed to remove unsafe path /tmp/fam-root ... It seems that the client tries to access /tmp/fam-root but has not the right user priviliges. Can someone help me out and explain what is going on? How can I solve the problem? You can disable FAM support by setting "fam change notify = no" in smb.conf. This will get rid of the messages, but obviously you won't get FAM support. I'd have to dig into the FAM implementation on FreeBSD to be more helpful, and I won't be able to do that for a couple of weeks. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] 3.0.23rc1 - Failed to setup RT_SIGNAL_NOTIFY handler
On Mon, 2006-05-29 at 09:34 +1000, James Peach wrote: > On Mon, 2006-05-29 at 08:47 +1000, James Peach wrote: > > On 5/29/06, Volker Lendecke <[EMAIL PROTECTED]> wrote: > > > On Sun, May 28, 2006 at 08:34:57PM +0200, Thomas Bork wrote: > > > > Please accept this patch for configure.in, removing the function > > > > introduced in 15508 (Use clock_gettime for profiling timestamps if it is > > > > available. Use the fastest clock available on uniprocessors.): > > > > > > Hmmm. Fully removing it might not be really the right thing. > > > It might however be good to only link in -lrt (and thus the > > > depending pthreads) if --with-profiling-data=yes. > > > > > > James, what do you think? > > > > Yeh, that seems like the right thing to do. > > OK, now I've *actually* thought about this we can't just detect > clock_gettime if profiling is enabled, because on Linux, that would let > the user fall into a situation where they had profiling but broken > oplocks. We should never allow oplocks to be broken. > > Unfortunately, I think that this means that we need a new configure > macro to test whether linking with librt implicitly links libpthread. If > it does, we can disable clock_gettime without disabling > --with-profiling-data. This was way more horrible than I expected, but the attached patch implements the checks I describe above. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] 3.0.23rc1 - Failed to setup RT_SIGNAL_NOTIFY handler
On Mon, 2006-05-29 at 08:47 +1000, James Peach wrote: > On 5/29/06, Volker Lendecke <[EMAIL PROTECTED]> wrote: > > On Sun, May 28, 2006 at 08:34:57PM +0200, Thomas Bork wrote: > > > Please accept this patch for configure.in, removing the function > > > introduced in 15508 (Use clock_gettime for profiling timestamps if it is > > > available. Use the fastest clock available on uniprocessors.): > > > > Hmmm. Fully removing it might not be really the right thing. > > It might however be good to only link in -lrt (and thus the > > depending pthreads) if --with-profiling-data=yes. > > > > James, what do you think? > > Yeh, that seems like the right thing to do. OK, now I've *actually* thought about this we can't just detect clock_gettime if profiling is enabled, because on Linux, that would let the user fall into a situation where they had profiling but broken oplocks. We should never allow oplocks to be broken. Unfortunately, I think that this means that we need a new configure macro to test whether linking with librt implicitly links libpthread. If it does, we can disable clock_gettime without disabling --with-profiling-data. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] 3.0.23rc1 - Failed to setup RT_SIGNAL_NOTIFY handler
On 5/29/06, Volker Lendecke <[EMAIL PROTECTED]> wrote: On Sun, May 28, 2006 at 08:34:57PM +0200, Thomas Bork wrote: > Please accept this patch for configure.in, removing the function > introduced in 15508 (Use clock_gettime for profiling timestamps if it is > available. Use the fastest clock available on uniprocessors.): Hmmm. Fully removing it might not be really the right thing. It might however be good to only link in -lrt (and thus the depending pthreads) if --with-profiling-data=yes. James, what do you think? Yeh, that seems like the right thing to do. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can one set limits on new core dump?
On Tue, 16 May 2006 08:27 am, James Peach wrote: [snip] > I could certainly add a "enable core files" knob to smb.conf. I'd prefer > it to be on by default. something like this -- James Peach | [EMAIL PROTECTED] | SGI Australian Software Group I don't speak for SGI. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can one set limits on new core dump?
On Mon, 15 May 2006 09:40 pm, Doug VanLeuven wrote: > James Peach wrote: > > On Sat, 13 May 2006 12:16 am, Gerald (Jerry) Carter wrote: > >> James, > >> > >> This was your change right ? > > > > Yup. It's deliberately not configurable so that we can always get > > *something* that might help with fault diagnosis. > > > > Is there a chance for some kind of compromise? Of course. > winbindd cranked out hundreds of core dumps in less time than > it took to get a cup of coffee. Do you have some core-naming facility that renames the core files something other than "core"? I'm trying to understand why you ended up with more that one core file > My vmware machines all died for lack of temporary file space. > Ultimately, it required a reboot to get back to normal > because a lot of daemons require var space. > > If it's repeatable, the common process is to re-enable core > dumps and run a monitored test. Unfortunately not all problems are easily repeatable, and not all sites have people with the time and expertise to be able to do this sort of testing. > Barring a compromise, I'll have to investigate and probably > recommend hard limits be inherited in the startup files. > Otherwise, run the risk of having samba take down the entire > machine for the benefit of the developers on a Murphey. > The way I've done it for 30 years is limit core dumps for > normal day to day, re-enable it during problem determination. I could certainly add a "enable core files" knob to smb.conf. I'd prefer it to be on by default. -- James Peach | [EMAIL PROTECTED] | SGI Australian Software Group I don't speak for SGI. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can one set limits on new core dump?
On Sat, 13 May 2006 12:16 am, Gerald (Jerry) Carter wrote: > James, > > This was your change right ? Yup. It's deliberately not configurable so that we can always get *something* that might help with fault diagnosis. > Doug, I'm more interested in why winbindd is seg > faulting in the SAMBA_3_0 tree. Can you give me more > details? Agreed. Please let's get a backtrace at least: gdb `which winbindd` /path/to/core/file (gdb) where (quit) > Doug VanLeuven wrote: > > Sorry Jeff, been there, done that, if you'd read the whole post. > > > > > > Jeff Saxton wrote: > >> man ulimit > >> hint: ulimit -c This probably won't work because in fault.c we explicitly set the core size to 16MiM (IIRC). > >> > >> Doug VanLeuven wrote: > >>> Hi all, > >>> Is there anyway to limit the new core dumping panics? > >>> Can't find anything on it. (If I'd only looked in that ...) > >>> Was my mistake, but winbindd filled up an entire volume > >>> and froze out every process writing to that drive. You should only get 1 core file per daemon unless you have some system-specific core file naming facility enabled. If winbind is dumping core often it should always be in LOGBASE/cores/winbindd/core. > >>> I started it from a shell and my soft limit is > >>> already zero. (ulimit -S -c 0) > > ^^ > >>> > >>> FC4 2.6.16-1.2069 smp, gcc 4.0.2-8 > >>> samba 3.0.23pre2-SVN-build-15162 > >>> > >>> Regards, Doug > >>> > >> > > > > -- James Peach | [EMAIL PROTECTED] | SGI Australian Software Group I don't speak for SGI. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Performance issue on AIX when deleting files in a directory with a large number of files
On 5/12/06, Jeremy Allison <[EMAIL PROTECTED]> wrote: On Fri, May 12, 2006 at 12:50:37AM +1000, James Peach wrote: > On 5/11/06, Jeremy Allison <[EMAIL PROTECTED]> wrote: > >On Wed, May 10, 2006 at 12:29:53PM -0400, Claus Lund wrote: > >> > >> Well, then Windows Explorer is braindamaged as well (which is a claim I > >> won't contest ;) )... because it's slow deleting files right through > >> Explorer as well. > > > >Yep - I completely agree Explorer is braindamaged. That's probably > >the worst of the lot :-). > > > >> Well, it looks like a Samba problem to me (or maybe a compiler/compiler > >> optimization problem?). I'm trying to get Samba compiled using IBM's XLC > >> instead of GCC in the hopes that XLC might produce faster running > >binaries > >> ... but unfortunately that seems like a somewhat involved task (Samba > >> doesn't compile cleanly out of the box with XLC). > > > >If it only happens on AIX, it's not a Samba code logic problem, that's > >what I mean. I doubt modifying compiler flags will do anything about > >actions taking seconds to resolve - that's almost certainly a system > >problem (ie. JFS on AIX). > > sounds like samba is recreating the directory hash for change notifies It only does that every 30 seconds or so - so I don't think that is the problem (although turning if off might prove me wrong). IIRC, after each delete, the change notify fires and the client then reapplies it causing the hash to be recreated. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Performance issue on AIX when deleting files in a directory with a large number of files
On 5/11/06, Jeremy Allison <[EMAIL PROTECTED]> wrote: On Wed, May 10, 2006 at 12:29:53PM -0400, Claus Lund wrote: > > Well, then Windows Explorer is braindamaged as well (which is a claim I > won't contest ;) )... because it's slow deleting files right through > Explorer as well. Yep - I completely agree Explorer is braindamaged. That's probably the worst of the lot :-). > Well, it looks like a Samba problem to me (or maybe a compiler/compiler > optimization problem?). I'm trying to get Samba compiled using IBM's XLC > instead of GCC in the hopes that XLC might produce faster running binaries > ... but unfortunately that seems like a somewhat involved task (Samba > doesn't compile cleanly out of the box with XLC). If it only happens on AIX, it's not a Samba code logic problem, that's what I mean. I doubt modifying compiler flags will do anything about actions taking seconds to resolve - that's almost certainly a system problem (ie. JFS on AIX). sounds like samba is recreating the directory hash for change notifies -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] performance regression between 30.14a and 3.0.20
On 4/27/06, Jeremy Allison <[EMAIL PROTECTED]> wrote: > On Wed, Apr 26, 2006 at 01:20:23PM -0400, Greg Dickie wrote: > > OK all my gobbledy-gook stats aside. sorry for being incoherent. > > > > Stracing reveals that files after 3.0.20b are opened with O_SYNC. Could > > that be the source of the problems? I'll try and find that and test it > > when I get home but the question is is it necessary? > > Greg - I LOVE YOU :-). That's almost certainly the problem. > Back in the Win9x protocols days (the openX style of calls) > we had the problem that Windows clients were setting the > "sync this data" flag for almost every open - completely > unneccessary. For 3.0.20x we changed to the NTcreateX > style of open, and mapped the create option FILE_WRITE_THROUGH > to the O_SYNC. I bet the Windows redirector in W2K, XP and W2K3 > is just as dim, and is adding that on almost every open (I'm > on a plane right now so can't get to my vmware sessions > easily to check). xdd explicitly sets this flag when it calls CreateFile. Testing with a different windows dd program gives more expected results. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] performance regression between 30.14a and 3.0.20
On 4/27/06, Greg Dickie <[EMAIL PROTECTED]> wrote: > OK all my gobbledy-gook stats aside. sorry for being incoherent. > > Stracing reveals that files after 3.0.20b are opened with O_SYNC. Could > that be the source of the problems? I'll try and find that and test it > when I get home but the question is is it necessary? O_SYNC is not a good option to use if you want good write performance on XFS. It's what you use to when you really want your data safe and don't care about throughput. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: quota on xfs on lvm doesn't work(?)
On 4/24/06, Christoph Peus <[EMAIL PROTECTED]> wrote: > James Peach wrote: > > > There's a couple of more obvious ways that trying to get quota information > > can fail. > > > > The first is in the XFS check. This requires either that the caller be > > root or that either > > > > 1. the caller is checking a user quota and the caller's effective > >UID is the same as the UID for the user quota of interest > > > > or 2. the caller is interested in a group quota and is a member of > > of the group of interest > > > > Now, I would expect that if this check failed on the on a LVM device, > > it would also fail on a regular block device, given that the samba > > configuration is consistent. You can test this by adding "debug pid = > > yes" to smb.conf and checking the log messages to see whether smbd would > > pass the above checks. > > > > The other early check is done by the selinux code. This checks the > > "quotaget" capability (is this the right terminology?). I think this is > > more interesting, because I'm guessing that selinux could be configured > > to allow quotaget on one block device but not on another ... > > > > Am I on the right track? > > Hmmm... does it matter that selinux support isn't activated in my kernel? probably :) > But to make it short: it turns out now that the problem disappears, when > I use the "real" device of the logical volume (/dev/mapper/export-lvol0) > in the mount command instead of the symbolic link /dev/export/lvol0 -> > /dev/mapper/export-lvol0 yay! nice work! > :-) > > Is this a bug or a feature? Looks like a bug to me... sure smells like a bug (somewhere) to me ... -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: TDB locking overhead and performance...
On Sun, 2006-04-23 at 13:22 +0100, Daniel J Blueman wrote: > > > As a test, I changed the opening of the locking.tdb and brlock.tdb > > > files to use the TDB_INTERNAL flag, avoiding use of the fcntl(F_SETLK) > > > syscall for locking individual database records. Performance was a lot > > > snappier, with quite a bit less system time used. > > > > > > What is the scope of implementing shared memory TDBs, where locking > > > could be done simply on structures? > > > > How would you implement cross-process locking without > > any syscalls? Maybe Linux has some fancy stuff here, but for > > most unixes we need to coordinate the mmap'ed area for the > > tdbs fcntl locks. > > Locking via a 'volatile int count' in a shared file-backed or > anonymous mapping, or via sys V shm is what I had in mind. See tdb/spinlock.[ch] in the Samba source. > This would be quite clean to implement, but I just can't find any > user-space atomic operations exported by glibc. There are clever > tricks to use the kernel ones in /usr/include/asm/atomic.h, but that > is an ugly hack. > > Any ideas? Very recent gcc does have atomic op builtins, though I'm not sure how many platforms they are implemented for: http://gcc.gnu.org/onlinedocs/gcc/Atomic-Builtins.html -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: quota on xfs on lvm doesn't work(?)
On 4/21/06, Christoph Peus <[EMAIL PROTECTED]> wrote: > Sorry for the double posting. > > > munmap(0xb7998000, 4096)= 0 > > quotactl(Q_XGETQUOTA|GRPQUOTA, "/dev/export/lvol0", 4000, 0xbfdab390) = > > -1 EACCES (Permission denied) > > Perhaps I should add this: > > testdc ~ # ls -al /dev/export/lvol0 > lrwxrwxrwx 1 root root 24 Apr 21 2006 /dev/export/lvol0 -> > /dev/mapper/export-lvol0 > testdc ~ # ls -al /dev/mapper/export-lvol0 > brw-rw-rw- 1 root disk 254, 0 Apr 21 2006 /dev/mapper/export-lvol0 > ^^ > This was originally 600... So, you are right .. WXFS quotas are independent of the underlying block device. You also correctly anticipated that I'd ask what the device permissions are, and they look fine, though I would have expected brw-r--r--. There's a couple of more obvious ways that trying to get quota information can fail. The first is in the XFS check. This requires either that the caller be root or that either 1. the caller is checking a user quota and the caller's effective UID is the same as the UID for the user quota of interest or 2. the caller is interested in a group quota and is a member of of the group of interest Now, I would expect that if this check failed on the on a LVM device, it would also fail on a regular block device, given that the samba configuration is consistent. You can test this by adding "debug pid = yes" to smb.conf and checking the log messages to see whether smbd would pass the above checks. The other early check is done by the selinux code. This checks the "quotaget" capability (is this the right terminology?). I think this is more interesting, because I'm guessing that selinux could be configured to allow quotaget on one block device but not on another ... Am I on the right track? -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] quota on xfs on lvm doesn't work(?)
On 4/21/06, James Peach <[EMAIL PROTECTED]> wrote:
> On 4/20/06, Christoph Peus <[EMAIL PROTECTED]> wrote:
> > Hi James,
> >
> > thanks for your reply.
> >
> > > XFS quotas should work just fine on LVM. To narrow down what is
> > happening,
> > > can you please strace an xfs_quota command on the filesystem? Something
> > > like this should be sufficient:
> > >
> > > strace /usr/sbin/xfs_quota -c quota /mnt/tmp
> >
> > I should mention that quota does indeed work in general - I can not use
> > more space than is allowed by the hard limit, and the usage and remaining
> > free space is correctly displayed by 'quota' and 'quot'. The only thing
> > which doesn't work with LVM is the reporting of free space via samba. But
> > perhaps you can see something strange in this output:
> > (Thanks for your support!)
> >
> > testdc / # strace xfs_quota -c quota /mnt/tmp
> > execve("/bin/xfs_quota", ["xfs_quota", "-c", "quota", "/mnt/tmp"], [/* 27
> > vars */]) = 0
> > uname({sys="Linux", node="testdc", ...}) = 0
> > brk(0) = 0x8929000
> > access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
> > directory)
> > open("/etc/ld.so.cache", O_RDONLY) = 3
> > fstat64(3, {st_mode=S_IFREG|0644, st_size=19381, ...}) = 0
> > mmap2(NULL, 19381, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7fbd000
> > close(3)= 0
> > open("/lib/libc.so.6", O_RDONLY)= 3
> > read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\271U\1"..., 512)
> > = 512
> > fstat64(3, {st_mode=S_IFREG|0755, st_size=1199644, ...}) = 0
> > mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
> > = 0xb7fbc000
> > mmap2(NULL, 1113396, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0)
> > = 0xb7eac000
> > mprotect(0xb7fb5000, 27956, PROT_NONE) = 0
> > mmap2(0xb7fb6000, 16384, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x109) = 0xb7fb6000
> > mmap2(0xb7fba000, 7476, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7fba000
> > close(3)= 0
> > mprotect(0xb7fb6000, 4096, PROT_READ) = 0
> > mprotect(0xb7fd7000, 4096, PROT_READ) = 0
> > munmap(0xb7fbd000, 19381) = 0
> > open("/dev/urandom", O_RDONLY) = 3
> > read(3, "z\177#\245", 4)= 4
> > close(3)= 0
> > brk(0) = 0x8929000
> > brk(0x894a000) = 0x894a000
> > open("/usr/lib/locale/locale-archive", O_RDONLY|O_LARGEFILE) = 3
> > fstat64(3, {st_mode=S_IFREG|0644, st_size=1378768, ...}) = 0
> > mmap2(NULL, 1378768, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7d5b000
> > close(3)= 0
> > access("/proc/self/mounts", R_OK) = 0
> > open("/proc/self/mounts", O_RDONLY) = 3
> > fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
> > mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
> > = 0xb7fc1000
> > read(3, "rootfs / rootfs rw 0 0\n/dev/root"..., 1024) = 373
> > stat64("/mnt/tmp", {st_mode=S_IFDIR|0777, st_size=17, ...}) = 0
> > read(3, "", 1024) = 0
> > close(3)= 0
> > munmap(0xb7fc1000, 4096)= 0
> > open("/etc/projects", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or
> > directory)
> > getuid32() = 0
> > socket(PF_FILE, SOCK_STREAM, 0) = 3
> > fcntl64(3, F_GETFL) = 0x2 (flags O_RDWR)
> > fcntl64(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0
> > connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1
> > ENOENT (No such file or directory)
> > close(3)= 0
> > socket(PF_FILE, SOCK_STREAM, 0) = 3
> > fcntl64(3, F_GETFL) = 0x2 (flags O_RDWR)
> > fcntl64(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0
> > connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1
> > ENOENT (No such file or directory)
> > close(3)= 0
> > open("/etc/nsswitch.conf", O_RDONLY)= 3
> > fstat64(3, {st_mode=S_IFREG|0644, st_size=499, ...}) = 0
> > mmap2(NULL, 4096, PROT_READ|PROT_WR
Re: [Samba] quota on xfs on lvm doesn't work(?)
E, 3, 0) = 0xb7fbd000
> close(3)= 0
> open("/lib/libnss_files.so.2", O_RDONLY) = 3
> read(3, "[EMAIL PROTECTED]"...,
> 512) = 512
> fstat64(3, {st_mode=S_IFREG|0755, st_size=35744, ...}) = 0
> mmap2(NULL, 37512, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
> 0xb7d51000
> mmap2(0xb7d59000, 8192, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x7) = 0xb7d59000
> close(3)= 0
> munmap(0xb7fbd000, 19381) = 0
> open("/etc/passwd", O_RDONLY) = 3
> fcntl64(3, F_GETFD) = 0
> fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
> fstat64(3, {st_mode=S_IFREG|0644, st_size=1850, ...}) = 0
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
> = 0xb7fc1000
> read(3, "root:x:0:0:root:/root:/bin/bash\n"..., 4096) = 1850
> close(3)= 0
> munmap(0xb7fc1000, 4096)= 0
> quotactl(0x5807 /* Q_??? */|USRQUOTA, "/dev/export/lvol0", 0, NULL) = 0
> quotactl(Q_XGETQUOTA|USRQUOTA, "/dev/export/lvol0", 0, 0xbf8d4710) = 0
> exit_group(0) = ?
>
>
> Regards
> Christoph
>
--
James Peach | [EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Big performance difference between smbclient put/get
On 4/13/06, Henrik Zagerholm <[EMAIL PROTECTED]> wrote: > Hi list, > > I'm using Samba 3.0.21 on a FC4 box. > > When copying files using smbclient I get huge speed differences > between put and get commands. > > smb: \> put backup.tar > putting file backup.tar as \backup.tar (543.0 kb/s) (average 543.0 kb/s) > smb: \> get backup.tar > getting file \backup.tar of size 31549440 as backup.tar (7681.4 kb/s) > (average 7681.4 kb/s) > smb: \> put backup.tar > putting file backup.tar as \backup.tar (512.5 kb/s) (average 527.3 kb/s) > smb: \> > > > Get => 7681.4 kb/s > Put => 530 kb/s > > Any reason why? Could be anything. In general, there is no reason to expect reads and writes to achieve thta same bandwidth, and a mixed read/write workload will be different again. The reasons for this particular result could be in smbclient or they could be in the I/O stack on the server or the client. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA install on IRIX 6.5
On 3/31/06, McDougald, James D. (Contr) <[EMAIL PROTECTED]> wrote: > > > >> You should remove your symlink and install the openldap subsystem > from the CD 3. You will need at least openldap.sw.lib32 and > openldap.sw.hdr. > > Thanks, that fixed it. > The SGI is running 3.0.21c with ADS > now if I only had permissions to: net ads join > > grin > > I am trying to compile now on a SUN_SPARC_5.10 box and I am getting > similar errors :( this OpenLDAP is being difficult. > > ./configure --with-acl-support --with-quotas --with-included-popt > --localstatedir=/var/lib/samba --with-piddir=/var/run > --with-logfilebase=/var/log/samba -with-privatedir=/usr/local/etc/samba > --with-configdir=/usr/local/etc/samba --with-ldap=yes --with-ads=yes > > checking for LDAP support... yes > checking ldap.h usability... yes > checking ldap.h presence... yes > checking for ldap.h... yes > checking lber.h usability... yes > checking lber.h presence... yes > checking for lber.h... yes > checking for ber_scanf in -llber... no > checking for ldap_init in -lldap... yes > checking for ldap_set_rebind_proc... yes > checking whether ldap_set_rebind_proc takes 3 arguments... 3 > checking whether LDAP support is used... yes > checking for Active Directory and krb5 support... yes > checking for ldap_initialize... no > configure: error: Active Directory Support requires ldap_initialize > > > Any thoughts on this one? Sorry, no. I have a vague idea that there have been others having fun with the Solaris LDAP libraries. There might be something useful in the list archves. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA install on IRIX 6.5
On 3/28/06, McDougald, James D. (Contr) <[EMAIL PROTECTED]> wrote: > I am Running IRIX 6.5.28 and I am still having this problem. I just can > not get ADS support in Samba to compile. I have Kerberos and ldap and I > can even use kinit to authenticate against the ads server in the Windows > domain, but the Samba install chokes and says libldap is required for > ads support. I am at a loss. This does not make sense unless the > configure script can not follow symlinks as the ldap libs live in > /usr/freeware/lib32 and I have them symlinked to /usr/lib. The latest version of fw_openldap I can see in Freeware is 2.1.21. IRIX 6.5.28 ships with openldap 2.2.23. This does include the development headers. You should remove your symlink and install the openldap subsystem from the CD 3. You will need at least openldap.sw.lib32 and openldap.sw.hdr. > Anyone running samba 3.0 or higher for IRIX 6.5.28 willing to share > built binaries? > > As an asides, I can build samba 3.0.21c for this host with no issues as > a normal NT domain member without ADS. > > Thank You > > J. Darrin McDougald > > -Original Message- > From: Jason Mader [mailto:[EMAIL PROTECTED] > Sent: Friday, March 24, 2006 10:30 AM > To: samba@lists.samba.org > Cc: McDougald, James D. (Contr) > Subject: Re: [Samba] SAMBA install on IRIX 6.5 > > On Fri, 24 Mar 2006, James Peach wrote: > > > Use IRIX 6.5.22 or later. From 6.5.22 onwards, kerberos, openldap and > > openssl were bundled with the base OS. I've never attempted to build > > against the Freeware versions. > > Irix doesn't bundle Kerberos headers, won't that be a problem? I'm asking about this ... -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA install on IRIX 6.5
On 3/24/06, McDougald, James D. (Contr) <[EMAIL PROTECTED]> wrote: > I am having problems with Samba on IRIX 6.5 authenticating via Active > Directory. Installing the tardist of 3.0.21c did not give me > kerberos/ldap/adc capabilities even though Kerberos and LDAP were > prereq's. With OpenLDAP and Kerberos5 installed, my configure fails. I > am trying this: > > ./configure --libdir=/usr/lib --includedir=/usr/include > --prefix=/usr/samba --with-ldap --with-ads --with-krb5=/usr/local > --with-quotas --with-acl-support > > checking for LDAP support... yes > checking ldap.h usability... yes > checking ldap.h presence... yes > checking for ldap.h... yes > checking lber.h usability... yes > checking lber.h presence... yes > checking for lber.h... yes > checking for ber_scanf in -llber... no > checking for ldap_init in -lldap... no > checking for ldap_set_rebind_proc... no > checking whether ldap_set_rebind_proc takes 3 arguments... 3 > configure: error: libldap is needed for LDAP support > > mma-riss01 53# ls -la /usr/include/*ldap* > -rw-r--r--1 root sys39901 Mar 23 07:13 > /usr/include/ldap.h > -rw-r--r--1 root sys 9136 Mar 23 07:13 > /usr/include/ldap_cdefs.h > -rw-r--r--1 root sys 2056 Mar 23 07:13 > /usr/include/ldap_features.h > -rw-r--r--1 root sys 9462 Mar 23 07:13 > /usr/include/ldap_schema.h > -rw-r--r--1 root sys 3549 Mar 23 07:13 > /usr/include/ldap_utf8.h > > > mma-riss01 54# ls -la /usr/lib/*ldap* > lrwxr-xr-x1 root sys 29 Mar 23 09:15 > /usr/lib/libldap.a -> /usr/freeware/lib32/libldap.a > lrwxr-xr-x1 root sys 30 Mar 23 09:15 > /usr/lib/libldap.so -> /usr/freeware/lib32/libldap.so > lrwxr-xr-x1 root sys 32 Mar 23 09:15 > /usr/lib/libldap.so.3 -> /usr/freeware/lib32/libldap.so.3 > lrwxr-xr-x1 root sys 31 Mar 23 09:15 > /usr/lib/libldap_r.a -> /usr/freeware/lib32/libldap_r.a > lrwxr-xr-x1 root sys 32 Mar 23 09:15 > /usr/lib/libldap_r.so -> /usr/freeware/lib32/libldap_r.so > lrwxr-xr-x1 root sys 34 Mar 23 09:15 > /usr/lib/libldap_r.so.3 -> /usr/freeware/lib32/libldap_r.so.3 > > And I even tried to use the environment variable : > LD_LIBRARY=/usr/lib:/usr/include > > Any Suggestions? Use IRIX 6.5.22 or later. From 6.5.22 onwards, kerberos, openldap and openssl were bundled with the base OS. I've never attempted to build against the Freeware versions. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Directory Renaming problem Samba 2.2 on IRIX
On 3/9/06, James Tullett <[EMAIL PROTECTED]> wrote: > Hi: > > I have an old Indy that currently runs Samba 2.x on a Windows 2000/2003 > Active > Directory Network. It uses DOMAIN security, and the Domain Controllers > for > password service. > > Unfortunately, creating directories under Windows is problematic. When > I create > a directory under Windows, it cannot be renamed from Windows' default > name > "New Folder", "New Folder (2)" etc. Under UNIX, folders may be renamed > by their owners, or members of their group owners. > > Does this problem exist for Samba 3.x installations on IRIX 6.x using > Win2k/Win2k3 Domain Controllers and AD? This particular use case works fine in Samba 3, and I'd definitely recommend you upgrade since the 2.x series is now unsupported. However, the problem might be specific to your environment, so there's no guarantee that merely upgrading will help. > (quick listing of the existing setup follows) > > The current settings for one of the important shares is > > [media] > comment = > path = /path-to-samba-share > write list = @publish > read only = No > create mask = 0775 > force directory mode = 2775 > > The publish group is a UNIX group that contains all the User IDs that > are > permitted write access to the share. They can freely write files onto > the > share, but it is currently impossible to rename folders on the share, > nor indeed any share on the machine. > (setup listing ends) Sounds like some kind of permissions problem. This might mean that samba isn't running as the user you think it is at the time it does the rename. Take a par trace of the relevent smbd process to see exactly what is happenning to cause the error. Use par -p -i -sSS. > I checked the SGI site, but was unable to locate any binary packages > later than samba 2.2; the IRIX folder at samba.org is depressingly > empty. Samba 3 is supported on IRIX, 6.5.x in particular. There's no binary inst images on samba.org though, so you'll have to build from source. If you have an SGI support contract ask your support contact about getting a current copy of Samba for IRIX. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] lilesystem size limit samba on 64bit 2.6 kernel vs. clients win2k/winxp ?
On 2/14/06, Michael Will <[EMAIL PROTECTED]> wrote: > I had an incredibly hard time finding any documentation on filesystem size > limits for samba on 64bit linux with 2.6 kernel exporting to 32bit windows > 2003 > and windows-xp by googling. > > The closest I could get to was that cifs filesystem size correlates to ntfs > filesystem size and therefore there would be a 64TB limit. Are there > additional > limits within the software stack that I should be aware of? Possibly. I've exported a virtual 1PB filesystem to windows clients and they appeared to handle it ok. > We are considering exporting a 40TB xfs filesystem striped over 20 2TB luns > on a > fibre channel SAN via LVM2 on SLES9-SP3, and will be falling back to 16TB > filesystems if necessary. Anything below that would be cumbersome because of > the > amount of mountpoints. XFS will handle this just fine. Be aware that xfs_repair may take a fair amount of time and memory on very large filesystems. IIRC there was some scaling work done recently, but I'm not sure if it made SP3. > Can the 32bit windows clients keep up with that size as long as the files on > the > filesystem are not larger than 4GB? I've never seen modern windows clients have problems with large files of filesystems. I don't expect you will have problems. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Who or what is IP client 0.0.0.0?
On 1/15/06, taso <[EMAIL PROTECTED]> wrote: > Samba 3.0.21a > > Getting a fair bit of activity logged from IP 0.0.0.0 > What does it mean? > > [2006/01/14 13:42:23, 0] lib/util_sock.c:get_peer_addr(1222) >getpeername failed. Error was Transport endpoint is not connected > [2006/01/14 13:42:23, 0] lib/access.c:check_access(328) > [2006/01/14 13:42:23, 0] lib/util_sock.c:get_peer_addr(1222) >getpeername failed. Error was Transport endpoint is not connected >Denied connection from (0.0.0.0) > [2006/01/14 13:42:23, 1] smbd/process.c:process_smb(1187) > [2006/01/14 13:42:23, 0] lib/util_sock.c:get_peer_addr(1222) >getpeername failed. Error was Transport endpoint is not connected >Connection denied from 0.0.0.0 > [2006/01/14 13:42:23, 0] lib/util_sock.c:write_data(554) >write_data: write failure in writing to client 0.0.0.0. Error Connection > reset by peer > [2006/01/14 13:42:23, 0] lib/util_sock.c:send_smb(762) >Error writing 5 bytes to client. -1. (Connection reset by peer) > [2006/01/14 13:54:23, 0] lib/util_sock.c:get_peer_addr(1222) 0.0.0.0 is not the address of any client. This log snippet shows that smbd is calling the getpeername function to retrieve the IP address of the client. This fails because the client has already disconnected (this is what "transport endpoint is not connected" means). So, you have one or more clients on your network that disconnects from the server unexpectedly. You might be able to track them down by increasing the log level. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: what's the best filesystem
On 10/6/05, Sean W <[EMAIL PROTECTED]> wrote: > Actually, I am setting up an Ubuntu 5.04 box tomorrow as a Samba server > (right after I figure out how to disable the raid controller). Do you > suggest xfs? I've been reading this thread and people seem positive on > it, but are there negatives as well? I've never done any IO testing on Ubuntu, so all I can say about it is that I run it and it works. I don't know what its behaviour will be like under load. That is likely to vary between distros as much as between filesystems. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] what's the best filesystem
On 10/6/05, Eric A. Hall <[EMAIL PROTECTED]> wrote: > > On 10/4/2005 7:17 PM, mourik jan c heupink wrote: > > > I like xfs, specially with quota. (and using acl's here as well) > > > > with xfs you never have to run the check_quota (or whatever the command > > is...) This makes a rebooting after a crash *much* faster. > > that was one of the things I liked about, and replaying the journal was > nice too. > > one of the problems I had a couple of years back was that it wasn't > bootable (had to boot a mini-kernel off a fat partition, then load the xfs > modules). they've fixed that buy now I assume. That might depend on yr distro. I've used XFS root partitions on Ubuntu 5.04, SLES9 and OpenSUSE without any problems. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Samba install w/FC#3
On Wed, 2005-09-14 at 12:09 -0600, dave croden wrote: > downloaded samba i386,common, & client rpm's. Samba can't find the > common and client files, but the system says they are already > installed.Any suggestions.Should I upgrade to FC#4 and download the 3 > files for FC4 and try it? I don't run FC, but someone on the list might know something ... -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] max concurrent CIFS connections
On 9/8/05, John H Terpstra <[EMAIL PROTECTED]> wrote: > On Wednesday 07 September 2005 16:18, Gerald (Jerry) Carter wrote: > > Jeremy Allison wrote: > > | On Wed, Sep 07, 2005 at 09:22:31PM +0200, Pseudomizer wrote: > > |>I need some help please. I have been told from an administrator that > > |> Samba does only support up to 3.000 concurrent CIFS connections and each > > |> connections reserve 5MB of memory. > > | > > | This is incorrect and way too high. It depends on how active each > > | connection is. On the HP PSA (Print Server Appliance) I believe it's > > | a much smaller number (I'm sure Jerry can give more accurate figures). > > | Of course that's for printing only. Depends what the users are doing. > > > > My rule of thumb is 2Mb per smbd. With that man connections > > I'd go for a maybe an 8 way SMP box? But to be honest, I've > > never done a server that lareg in production myself. And I > > don't sysadmin anymore as a general rule. > > Samba does not scale linearly without bounds. Nothing does! > > The real bottle-neck needs to be identified. > > In a site that has heavy network usage, 30-40 concurrent users (all writing to > disk at the same time) can choke up a server in an amazing way. In this > situation, adding memory and/or CPUs achieves very little. > > Look at it this way: > > If the disk I/O architecture is provided by a controller that permits a > sustained write rate of 300 Mbytes/sec (an amazingly fast RAID controller > that can nearly saturate a whole PCI-X 133MHz 64-bit bus), the I/O limit is > easily reached with 3 gigabit network cards that are appropriately > configured. Anything more than 4 CPUs will hardly help over-all performance. > From past benchmarking work, as well as from practical field experience, the > benefit of adding memory under such load conditions in excess of 4GB is > marginal to say the least. > > On the other hand, if over-all network traffic is light, adding memory and > CPU's will make all clients more responsive. But adding memory and/or CPUs > does nothing to eliminate a disk I/O limitation. > > My rule of thumb is 3.5 MBytes per concurrently writing Windows client, plus > about 2 MB per additional client. This means that active clients will be > served from physical memoery and passive clients will most likely be in swap. Let's assume 7000 users, say each user has their own smbd daemon (ie. no connection multiplexing) and each smbd has 2MiB RSS. That's ~13GiB (worst case) for starters, but let's say that only 1000 users have a connection at any one time, which gives us more like 2GiB for smbd process memory requirements. Let's say that each user has a working set of 10MiB and that they need 512MiB/s of bandwidth (on average). So your bandwith requirement is ~500 MiB/sec, so you need to be driving 5 gig-e NICs at line rate, which will cost you about 5 CPUs (depending on a lot of stuff). The I/O rate you need from your storage will depend on how much RAM you stick in the server. With the assumptions above, if you stick 15 - 20 GiB of RAM in and the working set is pretty stable, you'll hardly ever need to do IO. Otherwise, you'll need at least enough I/O capacity to drive the network (~500MiB/s). -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Compiling VFS Support
On 8/26/05, Bill Ries <[EMAIL PROTECTED]> wrote: > Hello > > I'm trying to compile and install Samba with VFS support. I believe I have it > compiled and installed correctly, but I had to remove the RPM install to get > it to start via /etc/rc.d/init.d/smb which I customized to start the compiled > version of Samba. However, I'm getting the following error when starting > Samba. > > [2005/08/25 09:36:51, 0] smbd/server.c:main(839) > standard input is not a socket, assuming -D option This message is not related to VFS support. It just means that smbd is running in daemon mode even though you didn't specify the -D flag. Normally you would use -D when invoking smbd from an init script. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] configure options for 3.x -still experimental?
On 8/5/05, Moondance Foxmarnick <[EMAIL PROTECTED]> wrote: > Hello. I am trying to set up SAMBA 3.x on FC4. SAMBA will be PDC with no > other server. I work at a K-12 school, so unless I want 20 episodes of > "Family Guy" in a student's folder, I need to set quotas. > I've been looking around for 2 days and I'm stumped. > I found something called smbcquotas, but it seems to apply to a mixed NT > server environment. > I heard rumors of configure options --with-quotas, but couldn't find any > documentation in my Terpstra/Vernooij book. Finally I found a reference > to it my "Using SAMBA" book - it says it is experimental! Is that still > true? AFAIK, the quotas work. > Does no-one use quotas? Or is it a blindingly simple Linux thing that I > don't know about? I found un-answered posts through-out the Internet on > disk-quotas. What do other people do? You'll need to enable quotas in your underlying filesytem. Samba will then be able to query them. Most filesystems have quota support these days. I'm most familiar with XFS, in which case you need to enable quota support in your kernel and mount the filesytem with the "quota" option (see mount(8) for details). -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba client (NetApp->Solaris mount)
On 7/14/05, Paul Gienger <[EMAIL PROTECTED]> wrote: > > We want to make use of the samba client to securely mount FS on our Linux > > and Unix Solaris computers from the central file server (NetApp). > > > > I am new to samba and trying to have some feel whether it is possible and > > what kind of issues we can expect to face in this project. > > Linux will be able to mount your smb fileshares into the filesystem just > fine, though you may want to stick to the mount -t cifs rather than mount -t > smbfs. Either way these kernel modules aren't maintained here, they are > part of the kernel. > > That should lead to the rest of your UNIX network. I can speak for Solaris > and say that there is no support for mounting smb shares built in. AIX, > HP-UX, VMS, IRIX, whatever else, I have no idea about, but they are probably > in the same boat. IIRC, sharity runs on most unixes and will gives you a local SMB filesystem. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.14a problem: not able to see all files in a directory
On 7/14/05, Knut Hellebø <[EMAIL PROTECTED]> wrote: > Not much luck with this one, so I'm reposting hoping for some help... > > Samba 3.0.14a, running on Solaris 8 or Sgi IRIX 6.5.27. > > Scenario: > > 1. User has a symlink on his homeshare to a directory, let's call it > dir1, which is automounted to the samba server (tried both Solaris samba > server and Sgi, same result). I don't know about solaris, but there's a good change that on IRIX this is due to you using version 1 naming on your XFS filesystem. If you run xfs_growfs -n /mountpoint, the output will tell you which naming version is in use. Version 2 naming has been the default since 6.5.4. Unless you need to use the filesystem on a really ancient IRIX version, I strongly recommend you move to version 2 naming. Unfortunately, this is a dump and restore task. If you can't change the filesystem, Jeremy did change the directory code to handle this, but iirc it was checked in after 3.0.14a released. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] xfs filesystem corruption
On 7/13/05, mourik jan c heupink <[EMAIL PROTECTED]> wrote: > dear list. > > I was just wondering, is there anyone here using sles9 with xfs in an lvm? > > We had severe filesystem corruption on a server today, and only two > things were changed: I updated via yast online update (lot's of updates, > strange enough, including an lvm update) and I had to replace a drive in > my hardware 6 disk raid array. (IBM 5i, raid 5) > > Now I was wondering what caused the corruption: the lvm updates, or the > disk change... (or even something else..?) therefore I'm asking here... > > Anyone having xfs/lvm problems/corruption after the updates? This could be a lot of things. If you lost a disk, it might be possible for the volume rebuild to fail. Losing a drive at the same time as an LVM update sounds a little fishy, but I don't have any experience with LVM. You might try asking the XFS folks on [EMAIL PROTECTED] Someone there will probably have some experience with the XFS/LVM combination. You'll need to provide the output of xfs_growfs -n for the filesystem in question, as well as the LVM config details and all the package version numbers (ie. for the original LVM package and the one you updated to). -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: missing directory entries on irix
On 4/20/05, Cale Fairchild <[EMAIL PROTECTED]> wrote: > Thanks for the patch, unfortunately when I installed it I had a lot more > files missing from the directory listing and I have not taken much time to > look at why. But it certainly is the cast that off_t on the IRIX box is 8 > bytes > in the current OS, however the compilers seem to convert the long values > properly so long as overflow does not occur. > > Thanks to your suggestion on looking at the 'xfs_growfs -n' output I think > that > I have finally tracked down the problem with the missing file. In IRIX systems > that have version 1 naming the last entry in that directory listing has a > dirent->d_off value of -1 if you treat it as a long. On systems with version 2 > naming the value is not set to -1. In samba 3.0.11 there was no apparent test > of the dirent->d_off field, but in 3.0.12 it performs a telldir after reading > the last name and returns NULL if the offset it -1. Nice work! I'm away from the lab this week, but I'll have a patch for you early next week. Thanks for digging into this. -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] File listing problems in 3.0.13
On 4/16/05, Cale Fairchild <[EMAIL PROTECTED]> wrote: > Thanks for another quick response, I have done some poking in the code and > found that the cause of the problem for the missing file is that in the > function get_lanman2_dir_entry in trans2.c, dname returns false on the last > entry of the directory. I also noticed that where changes in the assignment of > dname between 11 and 12 > > < trans2.c.3.0.11 > > trans2.c.3.0.12 > --- > < prev_dirpos = TellDir(conn->dirptr); > < dname = ReadDirName(conn->dirptr); > --- > > long curr_dirpos = prev_dirpos = dptr_TellDir(conn->dirptr); > > dname = dptr_ReadDirName(conn->dirptr,&curr_dirpos,&sbuf); > > if (!dname) > return(False) > > I am going to try and track it down further but I am wondering if this > triggers any thoughts. > > Another thing that I notice in the code is that I get messages such as: > > get_lanman2_dir_entry:readdir on dirptr 0x10425968 now at offset -183597246 > > in the logs, the offset grows through the positive numbers and then it prints > negative from high to low (long int overflow) yet the files seem to be shown. > However the last entry printed is very close to -1 again (possible overflow of > unsigned long?) > > Sorry to bother you about this again but I don't really know how to approach > SGI with this since I don't know how to describe the problem to them so that > they understand it and I get differing results with the same OS and the same > compilers. What do you do to get the differing results? -- James Peach | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: [BUG] iconv detection in 3.0.5rc1
On Sun, Jul 11, 2004 at 01:33:39PM -0400, Jason Mader wrote: > I've found that the inner loop for iconv detection in a lib32 > subdirectory of the LOOK_DIR path doesn't work right. Here are the > problems I've noticed, > > 1) configure only tested lib32 on the first directory, /usr, this is > because ICONV_FOUND was set to "yes" on the try of /usr/local/lib and > never reset (if it should be) to "no" because all the conversion tests > were failures. I've found that by moving, > ICONV_FOUND="no" > inside the for loop, > for i in $LOOK_DIRS ; do > > permits configure to actually find the good installation of libiconv on > my system under /opt/lib32. > > 2) I've also noticed that on the second iteration of that loop to try > the lib32 directory that LDFLAGS is set to "-L/usr/lib -L/usr/lib32" > when it should probably only be "-L/usr/lib32". This is probably a > sign that other variables are not being restored to their saved values. Hi Jason, The patch at http://marc.theaimsgroup.com/?l=samba-technical&m=108293814431661&w=2 still applies to the 3.0.5 configure.in. IIRC this was ok for your environment when you tested it previously. -- James Peach | [EMAIL PROTECTED] | SGI Australian Software Group I don't speak for SGI. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
