similar to: Samba and WINS

The shared mem size option is set to 102400 by default and change is discouraged: The man page (1.9.18p10) says: This parameter is only useful when Samba has been compiled with FAST_SHARE_MODES. It specifies the size of the shared memory (in bytes) to use between smbd processes. You should never change this parameter unless you have studied the source and know what you are doing.

We are moving from a PCNFS client to SMB client environment and hence moving from NFS for our Sun fileservers to Samba. I have seen figures indicating Samba is as good NT for SMB service. However what we are concerned with is: a) relative performance of Samba vs Sun's NFS b) loading on servers with lots of active connections (and hence lots of smbds). Do you need more memory than with

Our usage of Samba is being questioned with regards to being "non-standard" as against Windows NT servers. As the Samba Survey has been defunct for a while, I wonder if: a) there is any suitable advocacy document listing large and famous users of Samba? b) If not I would be happy to summarise responses from those prepared to go public. I am especially interested in Universities and

Environment: Solaris 2.5.1 Samba 1.9.18p3 We run samba from inetd (no special reason - just how its been done in the past). Then on one server we got masses of Samba daemons running (up to 40 as a time trying to run - load average 40+!), giving following complaints: Sep 28 14:39:06 zeus.brunel.ac.uk smbd[10728]: standard input is not a socket, a ssuming -D option Sep 28 14:39:06

I have just been upgrading my Samba servers from 1.9.18p10 to 2.0.6 So far as I can tell users have been happy (or at least not noticed!). Our clients are almost exclusively NT 4.0 (most at SP5). Our servers are Suns running Solaris 2.5.1 and 7. On upgrading 2 of our busier servers (for admin - home directories and NT binaries), I observed a considerable increase in server load. Home server

I realise that Samba is a voluntary effort and keeping Web Sites upto date may not be everyone's favourite occupation, but there appear to be a number of things missing or wrong: a) There is no contact info for the WebSite I could discern - hence posting here. b) There is still reference to samba-bugs@samba.org address - which I have been informed by it, is now dead. So may be this could be

On our most heavilly loaded Samba server (running 1.9.18p10 under Solaris 2.5.1) we have got occaisional meltdowns with load average rocketing to 100+. The evidence indicates lots of smbd processes running. Syslogs indicate lots of: Nov 12 12:48:35 zeus.brunel.ac.uk smbd[21572]: Failed to set socket option SO_KE EPALIVE Nov 12 12:48:35 zeus.brunel.ac.uk smbd[21572]: Failed to set socket

Nguyen Cao Dat asked about this: ERROR! Out of file structures - perhaps increase MAX_OPEN_FILES? As it happens I have started getting them too - on a PC Application server - the cause seems to be lots of files needed to be open to run applications - Lotus apps seems to be a particular culprit, but experiments indicate that even opening help on Microsoft Word opens 13 files! MAX_OPEN_FILES

[Apologies to sending to both samba & samba-technical lists - but I feel this is an issue to be aware of and an issue that may need fixing] This is what I have discovered with Samba 1.9.18p10 on Solaris 2.5.1: In contrast to smbd which checks its configuration files every minute or so, nmbd only does so on startup and on receipt of a HUP signal. This is not documented in the nmbd manual

Does anyone have any log analysis tools? I'm currently configured with "log file = /usr/local/samba/var/log.%m", which makes identifying issues with any one client easy, but doesn't provide me with an overall picture of what has been happening. What I'd like to be able to produce is a report showing, for a given unit time, the total number of clients that have connected,

Has anyone had any success in getting Samba to correctly restart logging to the log files with the default logrotate setup (or even a modified one) from RedHat? The default setup is to move the files to another location, create a new file for Samba to fill, then send the daemons a HUP signal. I've tried some of the options that can be used in the logrotate.d/samba file (nocreate and

I have set up a web page describing my Unix to SMB password synchronisiation which also has the source code to the C front end and expect script used. http://www.btinternet.com/~p.polkinghorne/samba/u2s/ Note this is a Solaris specific solution - but should be adaptable to other Unices. Hope this helps someone ... -- Peter Polkinghorne, IT Manager Kingsford Stacey Blackwell

Hi, I've install Samba on AIX 3.2.5 and I'd like to know if there are large companies using Samba ? What's the size of your company ? How many users ? Do you know a limit of Samba ? (performances) Thanks Vincent Ceriani

[The following is my understanding from doco and experiments - hosts Solaris 2.5.1 and Samba 1.9.18p3, client NT 4.0 - please re-use if wanted] Samba presents a DOS file permissions view to users. That is they can set the following attributes for files: Archive, Hidden and Readonly. As an ordinary user on NT 4.0 System attribute is not accessible. These attributes map as follows onto the

I can't answer any of this, but the following was taken from a thread on the "Novell Technology Transfer Partners List <NOVTTP@LISTSERV.SYR.EDU>" and passed over to me by my boss... Any comments/refutations/etc most definitely accepted... Please note that *I'm* the Senior Unix Systems Administrator at the University I work at, and have been moving us towards Samba since I

Best Regards, Mike Garver _________________________ Marketing Associate Deerfield.com http://www.deerfield.com/ sales@deerfield.com ---------------------------------------------------------------------- Please download and try our other exciting software products: ---------------------------------------------------------------------- WinGate - http://www.wingate.com/ FTP Voyager -

In investigating some performance issues (elderly server with just 10Mbps ethernet), I noticed that smbstatus reported hardly any open files with oplocks. In particular files opened with Office 2000 & XP stay un-oplocked. I have checked and testparm claims oplocks are enabled and manual says this is so by default. The clients are all Windows 2000 servers - so we have 1 samba connection with

Hello, Our university has a study in progress looking at using SAMBA to provide file/print sharing as an enterprise-wide solution. Does anyone know of an entity that uses SAMBA to support up to or more than 10 site locations, over 125 buildings, and supporting over 5000 workstations? -- Regards, /~\ The ASCII Richard Jackson \ / Ribbon Campaign Computer Systems Engineer,

I just thought I'd throw this out there because it doesn't seem normal to me. We have 2.0.5a on AIX 4.3.2. We initially tried to increase the shared mem size to 4MB. This would not happen until we rebooted AIX. Then smbstatus reported a 4MB shared mem size. Now we are trying to decrease it because we will only need about 2MB and it won't reduce. I suspect it will when we reboot

I have a samba 2.2.4 PDC which acts as the repository of roaming profiles. Just recently some of our users have experienced failure to load roaming profiles. The clients are on a pair of Windows 2000 terminal servers. The failure does not seem to be confined to one server and only affects some people. The error given takes place during the loading profile stage: Windows can not copy: \\Samba