docs/htmldocs/Portability.html

   1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 37. Portability</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="Appendixes.html" title="Part VI. Appendixes"><link rel="previous" href="compiling.html" title="Chapter 36. How to Compile Samba"><link rel="next" href="Other-Clients.html" title="Chapter 38. Samba and Other CIFS Clients"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 37. Portability</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="compiling.html">Prev</a> </td><th width="60%" align="center">Part VI. Appendixes</th><td width="20%" align="right"> <a accesskey="n" href="Other-Clients.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Portability"></a>Chapter 37. Portability</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="Portability.html#id2974513">HPUX</a></dt><dt><a href="Portability.html#id2974600">SCO UNIX</a></dt><dt><a href="Portability.html#id2974655">DNIX</a></dt><dt><a href="Portability.html#id2974825">Red Hat Linux</a></dt><dt><a href="Portability.html#id2974869">AIX</a></dt><dd><dl><dt><a href="Portability.html#id2974876">Sequential Read Ahead</a></dt></dl></dd><dt><a href="Portability.html#id2974902">Solaris</a></dt><dd><dl><dt><a href="Portability.html#id2974909">Locking Improvements</a></dt><dt><a href="Portability.html#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></div><p>Samba works on a wide range of platforms but the interface all the
   2 platforms provide is not always compatible. This chapter contains
   3 platform-specific information about compiling and using Samba.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2974513"></a>HPUX</h2></div></div><div></div></div><p>
   4 HP's implementation of supplementary groups is non-standard (for
   5 historical reasons). There are two group files, <tt class="filename">/etc/group</tt> and
   6 <tt class="filename">/etc/logingroup</tt>; the system maps UIDs to numbers using the former, but
   7 initgroups() reads the latter. Most system admins who know the ropes
   8 symlink <tt class="filename">/etc/group</tt> to <tt class="filename">/etc/logingroup</tt>
   9 (hard link does not work for reasons too obtuse to go into here). initgroups() will complain if one of the
  10 groups you're in in <tt class="filename">/etc/logingroup</tt> has what it considers to be an invalid
  11 ID, which means outside the range <tt class="constant">[0..UID_MAX]</tt>, where <tt class="constant">UID_MAX</tt> is (I think)
  12 60000 currently on HP-UX. This precludes -2 and 65534, the usual <tt class="constant">nobody</tt>
  13 GIDs.
  14 </p><p>
  15 If you encounter this problem, make sure the programs that are failing
  16 to initgroups() are run as users, not in any groups with GIDs outside the
  17 allowed range.
  18 </p><p>This is documented in the HP manual pages under setgroups(2) and passwd(4).
  19 </p><p>
  20 On HP-UX you must use gcc or the HP ANSI compiler. The free compiler
  21 that comes with HP-UX is not ANSI compliant and cannot compile Samba.
  22 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2974600"></a>SCO UNIX</h2></div></div><div></div></div><p>
  23 If you run an old version of SCO UNIX, you may need to get important
  24 TCP/IP patches for Samba to work correctly. Without the patch, you may
  25 encounter corrupt data transfers using Samba.
  26 </p><p>
  27 The patch you need is UOD385 Connection Drivers SLS. It is available from
  28 SCO (<ulink url="ftp://ftp.sco.com/">ftp.sco.com</ulink>, directory SLS,
  29 files uod385a.Z and uod385a.ltr.Z).
  30 </p><p>
  31 The information provided here refers to an old version of SCO UNIX. If you require
  32 binaries for more recent SCO UNIX products, please contact SCO to obtain packages that are
  33 ready to install. You should also verify with SCO that your platform is up-to-date for the
  34 binary packages you will install. This is important if you wish to avoid data corruption
  35 problems with your installation. To build Samba for SCO UNIX products  may
  36 require significant patching of Samba source code. It is much easier to obtain binary
  37 packages directly from SCO.
  38 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2974655"></a>DNIX</h2></div></div><div></div></div><p>
  39 DNIX has a problem with seteuid() and setegid(). These routines are
  40 needed for Samba to work correctly, but they were left out of the DNIX
  41 C library for some reason.
  42 </p><p>
  43 For this reason Samba by default defines the macro NO_EID in the DNIX
  44 section of includes.h. This works around the problem in a limited way,
  45 but it is far from ideal, and some things still will not work right.
  46 </p><p>
  47 To fix the problem properly, you need to assemble the following two
  48 functions and then either add them to your C library or link them into
  49 Samba. Put the following in the file <tt class="filename">setegid.s</tt>:
  50 </p><pre class="programlisting">
  51         .globl  _setegid
  52 _setegid:
  53         moveq   #47,d0
  54         movl    #100,a0
  55         moveq   #1,d1
  56         movl    4(sp),a1
  57         trap    #9
  58         bccs    1$
  59         jmp     cerror
  60 1$:
  61         clrl    d0
  62         rts
  63 </pre><p>
  64 Put this in the file <tt class="filename">seteuid.s</tt>:
  65 </p><pre class="programlisting">
  66         .globl  _seteuid
  67 _seteuid:
  68         moveq   #47,d0
  69         movl    #100,a0
  70         moveq   #0,d1
  71         movl    4(sp),a1
  72         trap    #9
  73         bccs    1$
  74         jmp     cerror
  75 1$:
  76         clrl    d0
  77         rts
  78 </pre><p>
  79 After creating the above files, you then assemble them using
  80 </p><pre class="screen">
  81 <tt class="prompt">$ </tt><b class="userinput"><tt>as seteuid.s</tt></b>
  82 <tt class="prompt">$ </tt><b class="userinput"><tt>as setegid.s</tt></b>
  83 </pre><p>
  84 that should produce the files <tt class="filename">seteuid.o</tt> and
  85 <tt class="filename">setegid.o</tt>
  86 </p><p>
  87 Then you need to add these to the LIBSM line in the DNIX section of
  88 the Samba Makefile. Your LIBSM line will then look something like this:
  89 </p><pre class="programlisting">
  90 LIBSM = setegid.o seteuid.o -ln
  91 </pre><p>
  92 You should then remove the line:
  93 </p><pre class="programlisting">
  94 #define NO_EID
  95 </pre><p>from the DNIX section of <tt class="filename">includes.h</tt>.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2974825"></a>Red Hat Linux</h2></div></div><div></div></div><p>
  96 By default during installation, some versions of Red Hat Linux add an
  97 entry to <tt class="filename">/etc/hosts</tt> as follows:
  98 </p><pre class="programlisting">
  99         127.0.0.1 loopback "hostname"."domainname"
 100 </pre><p>
 101 </p><p>
 102 This causes Samba to loop back onto the loopback interface.
 103 The result is that Samba fails to communicate correctly with
 104 the world and therefore may fail to correctly negotiate who
 105 is the master browse list holder and who is the master browser.
 106 </p><p>
 107 Corrective Action: Delete the entry after the word "loopback"
 108 in the line starting 127.0.0.1.
 109 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2974869"></a>AIX</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2974876"></a>Sequential Read Ahead</h3></div></div><div></div></div><p>
 110 Disabling Sequential Read Ahead using <b class="userinput"><tt>vmtune -r 0</tt></b> improves
 111 Samba performance significantly.
 112 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2974902"></a>Solaris</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2974909"></a>Locking Improvements</h3></div></div><div></div></div><p>Some people have been experiencing problems with F_SETLKW64/fcntl
 113 when running Samba on Solaris. The built-in file locking mechanism was
 114 not scalable. Performance would degrade to the point where processes would
 115 get into loops of trying to lock a file. It would try a lock, then fail,
 116 then try again. The lock attempt was failing before the grant was
 117 occurring. So the visible manifestation of this would be a handful of
 118 processes stealing all of the CPU, and when they were trussed they would
 119 be stuck if F_SETLKW64 loops.
 120 </p><p>
 121 Sun released patches for Solaris 2.6, 8, and 9. The patch for Solaris 7
 122 has not been released yet.
 123 </p><p>
 124 The patch revision for 2.6 is 105181-34, for 8 is 108528-19 and for 9 is 112233-04.
 125 </p><p>
 126 After the install of these patches, it is recommended to reconfigure
 127 and rebuild Samba.
 128 </p><p>Thanks to Joe Meslovich for reporting this.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="winbind-solaris9"></a>Winbind on Solaris 9</h3></div></div><div></div></div><p>
 129 Nsswitch on Solaris 9 refuses to use the Winbind NSS module. This behavior
 130 is fixed by Sun in patch 113476-05, which as of March 2003, is not in any
 131 roll-up packages.
 132 </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="compiling.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Appendixes.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Other-Clients.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 36. How to Compile Samba </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 38. Samba and Other CIFS Clients</td></tr></table></div></body></html>