Help! I'm running a trial with a spare 486/dx4 with only 16MB RAM and a 1GB HDD. I don't need speed - I need connectivity - nmbd starts ok but I just can't get smbd to start. No matter what I do It just won't go. The log seems to indicate it can't bind to the port - is it a memory issue? It wants to open 10000 files but can only open 1014. The swap file is 64MB, and it's set as a Gnome workstation cos it wouldn't do a server install and so I'm having to bodge around it. It's a connectivity trial with Windows 2000 and is very urgent. The final section of the log is shown below: [2000/09/06 15:09:47, 1] smbd/server.c:main(628) smbd version 2.0.5a started. Copyright Andrew Tridgell 1992-1998 [2000/09/06 15:10:04, 0] param/params.c:OpenConfFile(507) params.c:OpenConfFile() - Unable to open configuration file "/etc/smb.conf": Too many open files [2000/09/06 15:10:04, 0] param/loadparm.c:service_ok(1768) No path in service netlogon - using /tmp [2000/09/06 15:11:01, 1] smbd/files.c:file_init(216) file_init: Information only: requested 10000 open files, 1014 are available. [2000/09/06 15:11:01, 0] smbd/server.c:main(683) standard input is not a socket, assuming -D option [2000/09/06 15:11:02, 0] lib/util_sock.c:open_socket_in(886) bind failed on port 139 socket_addr=0.0.0.0 (Address already in use) Please can anyone help? If so can you e-mail me direct at: matthewh@fesa.co.uk Many thanks Matt Unless otherwise agreed expressly in writing by Fesa UK Limited, this communication should be treated as confidential and the information contained therein may not be used or disclosed except for the purpose for which it was sent. If you are not the intended recipient of this communication please contact the sender immediately. WARNING: Computer viruses can be transmitted by e-mail. The recipient should check this e-mail and any attachments for the presence of viruses. Fesa UK Limited accepts no liability for any damage caused by any virus transmitted by this e-mail. This e-mail and and attachments may not be copied and forwarded without the written consent of Fesa UK Limited . In the event of copying or forwarding, the recipient will be required to idemnify Fesa UK Limited against any claim for loss or damage caused by any virus or otherwise.
On Wed, 6 Sep 2000, Matthew Halliday wrote:> [2000/09/06 15:09:47, 1] smbd/server.c:main(628) > smbd version 2.0.5a started. > Copyright Andrew Tridgell 1992-1998You might want to try v2.0.7 (particularly since you mention Windows 2000, and 2.0.7 has W2K related bug fixes).> [2000/09/06 15:10:04, 0] param/params.c:OpenConfFile(507) > params.c:OpenConfFile() - Unable to open configuration file > "/etc/smb.conf": > Too many open filesEr - I don't know what is causing that, but I don't like the look of it ...> [2000/09/06 15:10:04, 0] param/loadparm.c:service_ok(1768) > No path in service netlogon - using /tmpSet "path = ..." to wherever your login scripts are stored in [netlogon] part of the smb.conf file.> [2000/09/06 15:11:01, 1] smbd/files.c:file_init(216) > file_init: Information only: requested 10000 open files, 1014 are > available.This is harmless (Samba asks for way more file-descriptors-per-process than it is ever going to get, just so that it can get as many as the OS is prepared to grant it). If the message annoys you, and you want to quell it, then you could set the global parameter "max open files 1000" in smb.conf.> [2000/09/06 15:11:01, 0] smbd/server.c:main(683) > standard input is not a socket, assuming -D option > [2000/09/06 15:11:02, 0] lib/util_sock.c:open_socket_in(886) > bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)This is confusing. Are you trying to start smbd as a standalone daemon, or out of inetd? Something is already using the network port that smbd wants to listen on. Make sure that there are no smbd processes already running. If you are trying to run a standalone daemon (using a startup script somewhere in /etc/rc.d for example), then check that there isn't a "netbios-ssn" service defined in /etc/inetd.conf. If you are trying to run samba out of inetd, check that there isn't a startup script somewhere that is running a standalone smbd (or attempting to!). Regards, -- Neil Hoggarth Departmental Computer Officer <neil.hoggarth@physiol.ox.ac.uk> Laboratory of Physiology http://www.physiol.ox.ac.uk/~njh/ University of Oxford, UK