From 3878085eca35d5c3b08761f61281de0b1b49ce2d Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 1 Jul 2003 22:58:52 +0000 Subject: regenerate docs (This used to be commit cc02d3bc170fe5c8c4474156edb6c83720a47aa0) --- docs/htmldocs/Portability.html | 31 +++++++++++++++---------------- 1 file changed, 15 insertions(+), 16 deletions(-) (limited to 'docs/htmldocs/Portability.html') diff --git a/docs/htmldocs/Portability.html b/docs/htmldocs/Portability.html index 0a9de2b4d1..bb2c20ac9f 100644 --- a/docs/htmldocs/Portability.html +++ b/docs/htmldocs/Portability.html @@ -1,7 +1,6 @@ - -Chapter 37. Portability

Chapter 37. Portability

Jelmer R. Vernooij

The Samba Team

Samba works on a wide range of platforms but the interface all the +Chapter 37. Portability

Chapter 37. Portability

Jelmer R. Vernooij

The Samba Team

Samba works on a wide range of platforms but the interface all the platforms provide is not always compatible. This chapter contains -platform-specific information about compiling and using samba.

HPUX

+platform-specific information about compiling and using samba.

HPUX

HP's implementation of supplementary groups is, er, non-standard (for hysterical reasons). There are two group files, /etc/group and /etc/logingroup; the system maps UIDs to numbers using the former, but @@ -18,10 +17,10 @@ to initgroups() be run as users not in any groups with GIDs outside the allowed range.

This is documented in the HP manual pages under setgroups(2) and passwd(4).

-On HPUX you must use gcc or the HP Ansi compiler. The free compiler -that comes with HP-UX is not Ansi compliant and cannot compile +On HPUX you must use gcc or the HP ANSI compiler. The free compiler +that comes with HP-UX is not ANSI compliant and cannot compile Samba. -

SCO Unix

+

SCO Unix

If you run an old version of SCO Unix then you may need to get important TCP/IP patches for Samba to work correctly. Without the patch, you may encounter corrupt data transfers using samba. @@ -29,7 +28,7 @@ encounter corrupt data transfers using samba. The patch you need is UOD385 Connection Drivers SLS. It is available from SCO (ftp.sco.com, directory SLS, files uod385a.Z and uod385a.ltr.Z). -

DNIX

+

DNIX

DNIX has a problem with seteuid() and setegid(). These routines are needed for Samba to work correctly, but they were left out of the DNIX C library for some reason. @@ -88,13 +87,13 @@ LIBSM = setegid.o seteuid.o -ln You should then remove the line:

 #define NO_EID
-

from the DNIX section of includes.h

RedHat Linux Rembrandt-II

+

from the DNIX section of includes.h

RedHat Linux Rembrandt-II

By default RedHat Rembrandt-II during installation adds an entry to /etc/hosts as follows: -

+

 	127.0.0.1 loopback "hostname"."domainname"
-
-

+

+

This causes Samba to loop back onto the loopback interface. The result is that Samba fails to communicate correctly with the world and therefor may fail to correctly negotiate who @@ -102,13 +101,13 @@ is the master browse list holder and who is the master browser.

Corrective Action: Delete the entry after the word loopback in the line starting 127.0.0.1 -

AIX

Sequential Read Ahead

+

AIX

Sequential Read Ahead

Disabling Sequential Read Ahead using vmtune -r 0 improves -samba performance significally. -

Solaris

Locking improvements

Some people have been experiencing problems with F_SETLKW64/fcntl -when running samba on solaris. The built in file locking mechanism was +Samba performance significantly. +

Solaris

Locking improvements

Some people have been experiencing problems with F_SETLKW64/fcntl +when running Samba on Solaris. The built in file locking mechanism was not scalable. Performance would degrade to the point where processes would -get into loops of trying to lock a file. It woul try a lock, then fail, +get into loops of trying to lock a file. It would try a lock, then fail, then try again. The lock attempt was failing before the grant was occurring. So the visible manifestation of this would be a handful of processes stealing all of the CPU, and when they were trussed they would -- cgit