</sect1>
+<sect1>
+ <title>IDEALX Management Console</title>
+
+ <para>
+ IMC (the IDEALX Mamagement Console) is a tool that can be used as the basis for a comprehensive
+ web-based management interface for UNIX and Linux systems.
+ </para>
+
+ <para>
+ The Samba toolset is the first console developped for IMC. It offers a simple and ergonomic
+ interface for managing a Samba domain controler. The goal is to give Linux administrators who
+ need to manage production Samba servers an effective, intuitive and consistent management
+ experience. An IMC screenshot of the user management tool is shown in <link linkend="imcidealx"/>.
+ </para>
+
+ <figure id="imcidealx">
+ <title>The IMC Samba User Account Screen</title>
+ <imagefile scale="40">imc-usermanager2</imagefile>
+ </figure>
+
+ <para>
+ IMC is built on a set of Perl modules. Most modules are standard CPAN modules. Some are bundled with IMC,
+ but will soon to be hosted on the CPAN independently, like Struts4P, a port of Struts to the Perl language.
+ </para>
+
+ <para>
+ For further information regarding IMC refer to the web <ulink url="http://imc.sourceforge.net/">site.</ulink>
+ Prebuilt RPM packages are also <ulink url="http://imc.sourceforge.net/download.html">available.</ulink>
+ </para>
+
+</sect1>
+
<sect1 id="ch12-SUIDSGID">
<title>Effect of Setting File and Directory SUID/SGID Permissions Explained</title>
<note><para>
The following information applies to Samba-3.0.20 when used with the Idealx smbldap-tools
-scripts version 0.9.0. If using a different version of Samba or of the smbldap-tools tarball,
+scripts version 0.9.1. If using a different version of Samba or of the smbldap-tools tarball,
please verify that the versions you are about to use are matching. The smbldap-tools package
uses counter-entries in the LDAP directory to avoid duplication of the UIDs and GIDs that are
issued for POSIX accounts. The LDAP rdn under which this information is stored are called
LDAP configuration scripts. The use of these scripts will help avoid the necessity
to create custom scripts. It is easy to download them from the Idealx
<ulink url="http://samba.idealx.org/index.en.html">Web site</ulink>. The tarball may
- be directly <ulink url="http://samba.idealx.org/dist/smbldap-tools-0.9.0.tgz">downloaded</ulink>
+ be directly <ulink url="http://samba.idealx.org/dist/smbldap-tools-0.9.1.tgz">downloaded</ulink>
from this site also. Alternatively, you may obtain the
- <ulink url="http://samba.idealx.org/dist/smbldap-tools-0.9.0-1.src.rpm">smbldap-tools-0.9.0-1.src.rpm</ulink>
+ <ulink url="http://samba.idealx.org/dist/smbldap-tools-0.9.1-1.src.rpm">smbldap-tools-0.9.1-1.src.rpm</ulink>
file that may be used to build an installable RPM package for your Linux system.
</para>
Copy all the <filename>smbldap-*</filename> and the <filename>configure.pl</filename> files into the
<filename>/opt/IDEALX/sbin</filename> directory, as shown here:
<screen>
-&rootprompt; cd smbldap-tools-0.9.0/
+&rootprompt; cd smbldap-tools-0.9.1/
&rootprompt; cp smbldap-* configure.pl *pm /opt/IDEALX/sbin/
&rootprompt; cp smbldap*conf /etc/smbldap-tools/
&rootprompt; chmod 750 /opt/IDEALX/sbin/smbldap-*
<para>
In the event that you have elected to use the RPM package provided by Idealx, download the
- source RPM <filename>smbldap-tools-0.9.0-1.src.rpm</filename>, then follow this procedure:
+ source RPM <filename>smbldap-tools-0.9.1-1.src.rpm</filename>, then follow this procedure:
</para>
<procedure>
<step><para>
Install the source RPM that has been downloaded as follows:
<screen>
-&rootprompt; rpm -i smbldap-tools-0.9.0-1.src.rpm
+&rootprompt; rpm -i smbldap-tools-0.9.1-1.src.rpm
</screen>
</para></step>
<step><para>
Install the binary package by executing:
<screen>
-&rootprompt; rpm -Uvh ../RPMS/noarch/smbldap-tools-0.9.0-1.noarch.rpm
+&rootprompt; rpm -Uvh ../RPMS/noarch/smbldap-tools-0.9.1-1.noarch.rpm
</screen>
</para></step>
The interactive use of this script for the PDC is demonstrated here:
<screen>
&rootprompt; /opt/IDEALX/sbin/configure.pl
+merlin:/opt/IDEALX/sbin # ./configure.pl
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
smbldap-tools script configuration
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Looking for configuration files...
Samba Config File Location [/etc/samba/smb.conf] >
-smbldap Config file Location (global parameters)
- [/etc/opt/IDEALX/smbldap-tools/smbldap.conf] >
+smbldap-tools configuration file Location (global parameters)
+ [/etc/opt/IDEALX/smbldap-tools/smbldap.conf] >
smbldap Config file Location (bind parameters)
- [/etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf] >
+ [/etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf] >
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Let's start configuring the smbldap-tools scripts ...
. workgroup name: name of the domain Samba act as a PDC
workgroup name [MEGANET2] >
-. netbios name: netbios name of the samba controller
+. netbios name: netbios name of the samba controler
netbios name [MASSIVE] >
-. logon drive: local path to which the home directory will
- be connected (for NT Workstations). Ex: 'H:'
+. logon drive: local path to which the home directory
+ will be connected (for NT Workstations). Ex: 'H:'
logon drive [H:] >
. logon home: home directory location (for Win95/98 or NT Workstation).
(use %U as username) Ex:'\\MASSIVE\%U'
logon home (press the "." character if you don't want homeDirectory)
- [\\MASSIVE\%U] > \\%L\%U
+ [\\MASSIVE\%U] >
. logon path: directory where roaming profiles are stored.
- Ex:'\\MASSIVE\profiles\%U'
+ Ex:'\\MASSIVE\profiles\%U'
logon path (press the "." character if you don't want roaming profile)
- [\\%L\profiles\%U] >
+ [\\%L\profiles\%U] >
. home directory prefix (use %U as username) [/home/%U] > /data/users/%U
. default users' homeDirectory mode [700] >
. default user netlogon script (use %U as username) [scripts\logon.bat] >
default password validation time (time in days) [45] > 900
-. ldap suffix [dc=terpstra-world,dc=org] >
+. ldap suffix [dc=abmas,dc=biz] >
. ldap group suffix [ou=Groups] >
. ldap user suffix [ou=People,ou=Users] >
. ldap machine suffix [ou=Computers,ou=Users] >
. sambaUnixIdPooldn: object where you want to store the next uidNumber
and gidNumber available for new users and groups
sambaUnixIdPooldn object (relative to ${suffix})
- [sambaDomainName=MEGANET2] >
-. ldap master server: IP adress or DNS name of the
- master (writable) ldap server
- ldap master server [merlin.terpstra-world.org] >
+ [sambaDomainName=MEGANET2] >
+. ldap master server: IP adress or DNS name of the master
+ (writable) ldap server
+ ldap master server [massive.abmas.biz] >
. ldap master port [389] >
-. ldap master bind dn [cn=Manager,dc=terpstra-world,dc=org] >
+. ldap master bind dn [cn=Manager,dc=abmas,dc=biz] >
. ldap master bind password [] >
. ldap slave server: IP adress or DNS name of the slave ldap server:
- can also be the master one
- ldap slave server [merlin.terpstra-world.org] >
+ can also be the master one
+ ldap slave server [massive.abmas.biz] >
. ldap slave port [389] >
-. ldap slave bind dn [cn=Manager,dc=terpstra-world,dc=org] >
+. ldap slave bind dn [cn=Manager,dc=abmas,dc=biz] >
. ldap slave bind password [] >
. ldap tls support (1/0) [0] >
. SID for domain MEGANET2: SID of the domain
- (can be obtained with 'net getlocalsid MASSIVE')
- SID for domain MEGANET2 [S-1-5-21-3504140859-1010554828-2431957765] >
+ (can be obtained with 'net getlocalsid MASSIVE')
+ SID for domain MEGANET2 [S-1-5-21-3504140859-1010554828-2431957765]] >
. unix password encryption: encryption used for unix passwords
unix password encryption (CRYPT, MD5, SMD5, SSHA, SHA) [SSHA] > MD5
. default user gidNumber [513] >
. default computer gidNumber [515] >
. default login shell [/bin/bash] >
-. default domain name to append to mail adress [] > terpstra-world.org
+. default skeleton directory [/etc/skel] >
+. default domain name to append to mail adress [] > abmas.biz
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
backup old configuration files:
/etc/opt/IDEALX/smbldap-tools/smbldap.conf->
- /etc/opt/IDEALX/smbldap-tools/smbldap.conf.old
+ /etc/opt/IDEALX/smbldap-tools/smbldap.conf.old
/etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf->
- /etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf.old
+ /etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf.old
writing new configuration file:
/etc/opt/IDEALX/smbldap-tools/smbldap.conf done.
/etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf done.
INTIFB="eth2"
/sbin/depmod -a
-/sbin/modprobe -i ip_tables
-/sbin/modprobe -i ip_conntrack
-/sbin/modprobe -i ip_conntrack_ftp
-/sbin/modprobe -i iptable_nat
-/sbin/modprobe -i ip_nat_ftp
+/sbin/modprobe ip_tables
+/sbin/modprobe ip_conntrack
+/sbin/modprobe ip_conntrack_ftp
+/sbin/modprobe iptable_nat
+/sbin/modprobe ip_nat_ftp
$IPTABLES -P INPUT DROP
$IPTABLES -F INPUT
$IPTABLES -P OUTPUT ACCEPT
<chapter id="simple">
<title>No-Frills Samba Servers</title>
-<?latex \pagenumbering{arabic} ?>
-
<para>
This is the start of the real journey toward the successful deployment of Samba. For some this chapter
is the end of the road because their needs will have been adequately met. For others, this chapter is
192.168.1.1 server
</screen>
-<?latex \newpage ?>
-
</para></step>
<step><para>
<imagefile scale="80">Charity-Network</imagefile>
</figure>
-<?latex \newpage ?>
-
<procedure>
<title>Samba Server Configuration</title>
</tgroup>
</table>
-<?latex \newpage ?>
-
<procedure>
<title>Migration from Windows NT4 Workstation System to Samba-3</title>
--- /dev/null
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
+
+<chapter lang="en-US">
+<title>Samba Support</title>
+
+<para>
+One of the most difficult to answer questions in the information technology industry is, <quote>What is
+support?</quote>. That question often irritates some folks, as much as common answers may annoy others.
+</para>
+
+<para>
+The most aggravating situation pertaining to support is typified when, as a Linux user, a call is made to
+an Internet service provider who, instead of listening to the problem to find a solution, blandly replies:
+<quote>Oh, Linux? We do not support Linux!</quote>. It has happened to me, and similar situations happen
+through-out the IT industry. Answers like that are designed to inform us that there are some customers
+that a business just does not want to deal with, and well may we feel the anguish of the rejection that
+is dished out.
+</para>
+
+<para>
+One way to consider support is to view it as consisting of the right answer, in the right place,
+at the right time, no matter the situation. Support is all that it takes to take away pain, disruption,
+inconvenience, loss of productivity, disorientation, uncertainty, and real or perceived risk.
+</para>
+
+<para>
+One of the forces that has become a driving force for the adoption of open source software is the fact that
+many IT businesses have provided services that have perhaps failed to deliver what the customer expected, or
+that have been found wanting for other reasons.
+</para>
+
+<para>
+In recognition of the need for needs satisfaction as the primary experience an information technology user or
+consumer expects, the information provided in this chapter may help someone to avoid an unpleasant experience
+in respect of problem resolution.
+</para>
+
+<para>
+In the open source software arena there are two support options: free support and paid-for, or commercial,
+support.
+</para>
+
+ <sect1>
+ <title>Free Support</title>
+
+ <para>
+ Free support may be obtained from friends, colleagues, user groups, mailing lists, and interactive help
+ facilities such as chat rooms such as the Internet relay chat (IRC) channels that provide user
+ supported mutual assistance.
+ </para>
+
+ <para>
+ The Samba project maintains a mailing list that is commonly used to discuss solutions to Samba
+ deployments. Information regarding subscription to the Samba mailing list can be found on the
+ Samba <ulink url="https://lists.samba.org/mailman/">web</ulink> site. The public mailing list
+ that can be used to obtain free, user contributed, support is called the <literal>samba</literal>
+ list. The email address for this list is at <literal>mail:samba@samba.org</literal>.
+ </para>
+
+ <para>
+ Information regarding the Samba IRC channels may be found on the Samba <ulink
+ url="http://www.samba.org/samba.irc.html">IRC</ulink> web page.
+ </para>
+
+ <para>
+ As a general rule, it is considered poor net behavior to contact a Samba Team member directly
+ for free support. Most active members of the Samba Team work exceptionally long hours to assist
+ users who have demonstrated a qualified problem. Some team members may respond to direct email
+ or telephone contact, with requests for assistance, by requesting payment. A few of the Samba
+ Team members actually provide professional paid-for Samba support and it is therefore wise
+ to show appropriate discretion and reservation in all direct contact.
+ </para>
+
+ <para>
+ When you stumble across a Samba bug, often the quickest way to get it resolved is by posting
+ a bug <ulink url="https://bugzilla.samba.org/">report</ulink>. All such reports are mailed to
+ the responsible code maintainer for action. The better the report, and the more serious it is,
+ the sooner it will be dealt with. On the other hand, if the responsible person can not duplicate
+ the reported bug it is likely to be rejected. It is up to you to provide sufficient information
+ that will permit the problem to be reproduced.
+ </para>
+
+ <para>
+ We all recognize that sometimes free support does not provide the answer that is sought within
+ the time-frame required. At other times the problem is elusive and you may lack the experience
+ necessary to isolate the problem and thus to resolve it. This is a situation where is may be
+ prudent to purchase paid-for support.
+ </para>
+
+ </sect1>
+
+ <sect1>
+ <title>Commercial Support</title>
+
+ <para>
+ There are six basic support oriented services that are most commonly sought by Samba sites:
+ </para>
+
+ <itemizedlist>
+ <listitem><para>Assistance with network design</para></listitem>
+ <listitem><para>Staff Training</para></listitem>
+ <listitem><para>Assistance with Samba network deployment and installation</para></listitem>
+ <listitem><para>Priority telephone or email Samba configuration assistance</para></listitem>
+ <listitem><para>Trouble-shooting and diagnostic assistance</para></listitem>
+ <listitem><para>Provision of quality assured ready-to-install Samba binary packages</para></listitem>
+ </itemizedlist>
+
+ <para>
+ Information regarding companies that provide professional Samba support can be obtained by performing
+ a Google search, as well as by reference to the Samba
+ <ulink url="http://www.samba.org/samba/support.html">Support</ulink> web page. Companies who notify
+ the Samba Team that they provide commercial support are given a free listing that is sorted by the country
+ of origin. Multiple listings are permitted, however no guarantee is offered. It is left to you to qualify a
+ support provider and to satisfy yourself that both the company and its staff are able to deliver what is
+ required of them. </para>
+
+ <para>
+ In deference to the policy within the Samba Team to treat all commercial support providers equally
+ and to show no preference, Samba Team members who provide commercial support are lumped in with
+ everyone else. You are encouraged to obtain the services needed from a company in your local area.
+ The open source movement is pro-community, so do what you can to help a local business to prosper.
+ </para>
+
+ <para>
+ Open source software support can be found in any quality, at any price and in any place you can
+ to obtain it. Over 180 companies around the world provide Samba support, there is no excuse for
+ suffering in the mistaken belief that Samba is unsupported software &smbmdash; it is supported.
+ </para>
+
+ </sect1>
+
+</chapter>
<para>
<emphasis>Samba-3 by Example</emphasis> would not have been written except
- as a result of feedback provided by reviewers of the book <emphasis>The
- Official Samba-3 HOWTO and Reference Guide.</emphasis> I hope this book
- more than answers the challenge and fills the void that was brought to
- my attention.
+ as a result of feedback provided by reviewers and readers of the book <emphasis>The
+ Official Samba-3 HOWTO and Reference Guide.</emphasis> This second edition
+ was made possible by generous feedback from Samba users. I hope this book
+ more than answers the challenge and needs of many more networks that are
+ languishing for a better networking solution.
</para>
<para>
<para>
My heartfelt thanks go out also to a small set of reviewers (alphabetically
listed) who gave substantial feedback and significant suggestions for improvement:
- Roland Gruber, Luke Howard, Jon Johnston, Alan Munter, Tarjei Huse, Mike MacIsaac,
- Scott Mann, Ed Riddle, Santos Soler, Mark Taylor, and Jérôme Tournier.
+ Tony Earnshaw, William Enestvedt, Eric Hines, Roland Gruber, Gavin Henry,
+ Steven Henry, Luke Howard, Jon Johnston, Alan Munter, Tarjei Huse, Mike MacIsaac,
+ Scott Mann, Ed Riddle, Geoff Scott, Santos Soler, Misty Stanley-Jones, Mark Taylor,
+ and Jérôme Tournier.
</para>
<para>
<para>
Particular mention is due to Lyndell, Amos and Melissa who gave me the
- latitude necessary to spend nearly a entire year writing Samba documentation.
+ latitude necessary to spend nearly a entire year writing Samba documentation,
+ and then gave more so this second edition could be created.
</para>
</preface>
<varlistentry>
<term>Chapter 9 &smbmdash; Migrating NT4 Domain to Samba-3</term><listitem>
<para>
- Another six months have <?latex \linebreak ?>
- passed. Abmas has acquired yet another company. You will find a
+ Another six months have passed. Abmas has acquired yet another company. You will find a
way to migrate all users off the old network onto the existing network without loss
of passwords and will effect the change-over during one weekend. May the force (and caffeine) be with
you, may you keep your back to the wind and may the sun shine on your face.
<authorgroup>\r
<author>&person.jht;</author>\r
</authorgroup>\r
- <pubdate>April 12, 2005</pubdate>\r
+ <pubdate>June, 2005</pubdate>\r
</bookinfo>\r
<?latex \clearpage ?>\r
<?latex \setcounter{page}{5} ?>\r
\r
<para>\r
The examples have been tested with Red Hat Fedora Core 2, Novell SUSE Linux Professional\r
-9.2 and Novell SUSE Linux Enterprise Server (SLES) 9. The principals of implementation\r
+9.3 and Novell SUSE Linux Enterprise Server (SLES) 9. The principals of implementation\r
apply to all Linux and UNIX systems in general, though some system files and tools will \r
be different and the location of some Samba file locations will be different since these \r
are determined by the person who packages Samba for each platform.\r
</para>\r
\r
+<para>\r
+If you are deploying Samba is a mission-critical environment, or if you simply want\r
+to save time and get your Samba network operational with minimal fuss, there is the\r
+option to purchase commercial, professional, Samba support. Information regarding\r
+commercial support options may be obtained from the commercial\r
+<ulink url="http://www.samba.org/samba/support/">support</ulink> pages from \r
+the Samba web site.\r
+</para>\r
+\r
</partintro>\r
<xi:include href="SBE-SimpleOfficeServer.xml"/>\r
<xi:include href="SBE-TheSmallOffice.xml"/>\r
<xi:include href="SBE-KerberosFastStart.xml"/>\r
<xi:include href="SBE-DomainAppsSupport.xml"/>\r
<xi:include href="SBE-HighAvailability.xml"/>\r
+ <xi:include href="SBE-Support.xml"/>\r
<xi:include href="SBE-Appendix1.xml"/>\r
<xi:include href="SBE-Appendix2.xml"/>\r
<xi:include href="http://www.gnu.org/licenses/gpl.xml"/>\r
git.samba.org / tprouty / samba.git / commitdiff
