[Samba] Samba 3.0.37 Performance issue
Hi,
up until the summer we were running a very old version of Samba in a
zone on a Sun V890 running Solaris 10 in a cluster. As we we moving over
to a Windows 7 desktop in the summer I set up a new zone running Samba
3.0.37 that accesses the same filesystem containing the users home
directories. This seemed to be working fairly reasonably until the start
of term since when we have been having severe performance issues when
using the new version and have had to revert back to the old version.
Apart from the version change the old version used the smbpasswd file
authentication method whereas the new version uses AD authentication,
although I can't see that this should cause a massive issue. I've had a
look at some config options (deadtime = 5, socket options = TCP_NODELAY
and change notify = no*) to see whether I can improve performance but so
far nothing seems to have helped. Are there likely to be any great
performance advantages in upgrading Samba to 3.5.8, or do I need to look
at further configuration tweaks. The trouble is that the only way I can
reliably test to see if anything works is to put it in to the live
environment and just monitor the system and switch back as soon as
problems start arising. Also as upgrading to 3.5.8 will involve
installing multiple patches on all 4 nodes in the cluster and so I'd
only want to go down that route if there is a definite (and
considerable) performance advantage of 3.5.8 over 3.0.37. Alternately is
there anything else I could look at in the configuration file to help
improve performance?
Martin Rootes.
(*) I tried "change notify = no" as in the Samba 2 config I'd used
"change notify timeout = 3000" to cure a performance issue, but Samba 3
doesn't have the "change notify timeout" option and so I thought I'd see
whether "change notify = no" would have a similar effect (it didn't).
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
[Samba] UID mapping
Hi, I'm trying to convert an old system on Solaris 10 that uses the smbpasswd file authentication method to a system that authenticates against Active Directory. I've managed to get winbind working but of course this just allocates UIDs as it sees fit whereas the smbpasswd file method used the UID from the /etc/passwd file. The user codes on the Solaris server match the user codes in AD but if I just switch over to winbind the UIDs will not match. If there were only a small number of users I could simply change the ownership of the users home directories to match the winbind allocated UID but unfortunately there are thousands of users and so this would be a mammoth task. I've has a look at various bits of documentation but can't get my head around the best strategy. Has anyone needed to do something similar and if so how did you go about it? Also the users' home directories are distributed around multiple directories and I would prefer to continue to use the home directory information from /etc/passwd as opposed to using "template homedir" (although I assume that I could leave the directories in place and just set up links to them). I've had also had a look at the PADL nss_ldap stuff but can't get it to compile, it seems to be looking for SASL, would the SASL version on the Sun Freeware site work? Martin. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba and ZFS
Hi, I've recently moved our student fileserver from a Solaris 10 server that was using UFS filesytems to a new Sun Cluster. As part of the move I decided to employ ZFS for the filesystem so that I could take advantage of some of ZFS's features. However, it now seems that windows does not report the amount of space that the user is actually using, or the amount of quota left, instead it reports the total amount of space in use and free on the total filesystem. I'm currently running and exceptionally old version of Samba (<3 !) and have been planning to upgrade to the latest version of 3 prior to the start of term. However, I'm concerned that this may be an inherant issue with Samba and ZFS. Will any of the latest versions of Samba correctly report a users usage and free space based on their quota or am I going to have to look at moving all the data back to UFS to get quota reporting working again? Martin. -- ======== Martin Rootes Learning and Information Technology Services Sheffield Hallam University -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
