From 99bde6889d3d8b7a9e950c86c30e82662e1dacdd Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Tue, 9 Sep 2003 02:58:53 +0000 Subject: syncing files from 3.0 into HEAD again (This used to be commit bca0bba209255d0effbae6a3d3b6d298f0952c3a) --- docs/docbook/projdoc/UNIX_INSTALL.xml | 158 ++++++++++++++-------------------- 1 file changed, 66 insertions(+), 92 deletions(-) (limited to 'docs/docbook/projdoc/UNIX_INSTALL.xml') diff --git a/docs/docbook/projdoc/UNIX_INSTALL.xml b/docs/docbook/projdoc/UNIX_INSTALL.xml index e919ff8c57..6a38e60c0e 100644 --- a/docs/docbook/projdoc/UNIX_INSTALL.xml +++ b/docs/docbook/projdoc/UNIX_INSTALL.xml @@ -15,12 +15,12 @@ Binary packages of samba are included in almost any Linux or - Unix distribution. There are also some packages available at + UNIX distribution. There are also some packages available at the samba homepage. - If you need to compile samba from source, check the - appropriate appendix chapter. + If you need to compile samba from source, check + the chapter about compiling samba from scratch. If you have already installed samba, or if your operating system was pre-installed with samba, then you may not need to bother with this @@ -55,39 +55,39 @@ - - [global] - workgroup = MYGROUP - - [homes] - guest ok = no - read only = no - + + Simplest possible smb.conf file +[global] +workgroup&example.workgroup; + +[homes] +guest okno +read onlyno + This will allow connections by anyone with an account on the server, using either - their login name or "homes" as the service name. + their login name or homes" as the service name. (Note that the workgroup that Samba must also be set.) - Make sure you put the smb.conf file in the same place - you specified in the Makefile (the default is to - look for it in /usr/local/samba/lib/). + Make sure you put the &smb.conf; file in the correct place + (usually in /etc/samba). For more information about security settings for the - [homes] share please refer to the chapter - Securing Samba. + [homes] share please refer to + "Securing Samba". Test your config file with <command>testparm</command> - It's important that you test the validity of your smb.conf + It's important that you test the validity of your &smb.conf; file using the &testparm; program. If testparm runs OK then it will list the loaded services. If not it will give an error message. @@ -115,7 +115,7 @@ To launch SWAT just run your favorite web browser and - point it at http://localhost:901/. Replace + point it at http://localhost:901/. Replace localhost with the name of the computer you are running samba on if you are running samba on a different computer than your browser. @@ -134,8 +134,9 @@ Try listing the shares available on your server - $ smbclient -L - yourhostname + +&prompt;smbclient -L yourhostname + You should get back a list of shares available on your server. If you don't then something is incorrectly setup. @@ -153,51 +154,55 @@ Try connecting with the unix client - $ smbclient - //yourhostname/aservice + + +&prompt;smbclient //yourhostname/aservice + Typically the yourhostname would be the name of the host where you installed &smbd;. The aservice is any service you have defined in the &smb.conf; - file. Try your user name if you just have a [homes] + file. Try your user name if you just have a [homes] section in &smb.conf;. For example if your unix host is bambi and your login name is fred you would type: - $ smbclient //bambi/fred - + +&prompt;smbclient //bambi/fred + - Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client - - Try mounting disks. eg: + Try connecting from another SMB client - C:\WINDOWS\> net use d: \\servername\service - + Try mounting disks. from a DOS, Windows or OS/2 client, eg: + + +&dosprompt;net use d: \\servername\service + Try printing. eg: - C:\WINDOWS\> net use lpt1: - \\servername\spoolservice + + +&dosprompt;net use lpt1: \\servername\spoolservice + - C:\WINDOWS\> print filename - + +&dosprompt;print filename + What If Things Don't Work? - Then you might read the file chapter - Diagnosis and the - FAQ. If you are still stuck then try to follow - the Analysing and Solving Problems chapter + Then you might read the file chapter diagnosis + and the FAQ. If you are still stuck then refer to "Analysing and solving problems". Samba has been successfully installed at thousands of sites worldwide, - so maybe someone else has hit your problem and has overcome it. + so maybe someone else has hit your problem and has overcome it. @@ -209,55 +214,7 @@ The following questions and issues get raised on the samba mailing list over and -Why are so many smbd processes eating memory? - - - -Site that is running Samba on an AIX box. They are sharing out about 2 terabytes using samba. -Samba was installed using smitty and the binaries. We seem to be experiencing a memory problem -with this box. When I do a svmon -Pu the monitoring program shows that &smbd; has several -processes of smbd running: - - - - - -Is samba suppose to start this many different smbd processes? Or does it run as one smbd process? Also -is it normal for it to be taking up this much memory? - - - - - -Inuse * 4096 = amount of memory being used by this process - - Pid Command Inuse Pin Pgsp Virtual 64-bit Mthrd - 20950 smbd 33098 1906 181 5017 N N - 22262 smbd 9104 1906 5410 - 21060 smbd 9048 1906 181 5479 N N - 25972 smbd 8678 1906 181 5109 N N - 24524 smbd 8674 1906 181 5105 N N - 19262 smbd 8582 1906 181 5013 N N - 20722 smbd 8572 1906 181 5003 N N - 21454 smbd 8572 1906 181 5003 N N - 28946 smbd 8567 1906 181 4996 N N - 24076 smbd 8566 1906 181 4996 N N - 20138 smbd 8566 1906 181 4996 N N - 17608 smbd 8565 1906 181 4996 N N - 21820 smbd 8565 1906 181 4996 N N - 26940 smbd 8565 1906 181 4996 N N - 19884 smbd 8565 1906 181 4996 N N - 9912 smbd 8565 1906 181 4996 N N - 25800 smbd 8564 1906 181 4995 N N - 20452 smbd 8564 1906 181 4995 N N - 18592 smbd 8562 1906 181 4993 N N - 28216 smbd 8521 1906 181 4954 N N - 19110 smbd 8404 1906 181 4862 N N - - Total memory used: 841,592,832 bytes - - - + Large number of smbd processes Samba consists on three core programs: @@ -285,10 +242,27 @@ run in "split mode" (in which case there will be two instances). - I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs - Your loopback device isn't working correctly. Make sure it's running. + "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" + Your loopback device isn't working correctly. Make sure it's configured properly. The loopback device is an internal (virtual) network device with + the ip address 127.0.0.1. Read your OS documentation for details + on how to configure the loopback on your system. + + "<errorname>The network name cannot be found</errorname>" + + + This error can be caused by one of these misconfigurations: + + + + You specified an nonexisting path for the share in &smb.conf; + The user you are trying to access the share with does not + have sufficient permissions to access the path for the share. Both read (r) and access (x) should be possible. + The share you are trying to access does not exist. + + + -- cgit