From cad70ca6eda6498db9acdae97fade2c615c3ce5b Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Thu, 28 Aug 2003 22:13:10 +0000 Subject: Regenerate docs (This used to be commit b78c6ee1d155f255d329899c237281c7cf662260) --- docs/faq/FAQ-ClientApp.html | 17 ++++++++-------- docs/faq/FAQ-Install.html | 23 ++++++++++----------- docs/faq/FAQ-errors.html | 29 +++++++++++++-------------- docs/faq/FAQ-features.html | 49 ++++++++++++++++++++++----------------------- docs/faq/FAQ-general.html | 27 ++++++++++++------------- docs/faq/samba-faq.html | 4 ++-- 6 files changed, 72 insertions(+), 77 deletions(-) (limited to 'docs/faq') diff --git a/docs/faq/FAQ-ClientApp.html b/docs/faq/FAQ-ClientApp.html index 351e88acfa..3193311d1f 100644 --- a/docs/faq/FAQ-ClientApp.html +++ b/docs/faq/FAQ-ClientApp.html @@ -1,5 +1,4 @@ - -Chapter 3. Specific client application problems

Chapter 3. Specific client application problems

MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"

+Chapter 3. Specific client application problems

Chapter 3. Specific client application problems

MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"

When installing MS Office on a Samba drive for which you have admin user permissions, ie. admin users = username, you will find the setup program unable to complete the installation. @@ -9,9 +8,9 @@ permissions The problem is that MS Office Setup checks that a file is rdonly by trying to open it for writing.

Admin users can always open a file for writing, as they run as root. -You just have to install as a non-admin user and then use "chown -R" +You just have to install as a non-admin user and then use "chown -R" to fix the owner. -

How to use a Samba share as an administrative share for MS Office, etc.

+

How to use a Samba share as an administrative share for MS Office, etc.

Microsoft Office products can be installed as an administrative installation from which the application can either be run off the administratively installed product that resides on a shared resource, or from which that product can be @@ -37,7 +36,7 @@ set the following parameters on the share containing it: [MSOP95] path = /where_you_put_it comment = Your comment - volume = "The_CD_ROM_Label" + volume = "The_CD_ROM_Label" read only = yes available = yes share modes = no @@ -45,8 +44,8 @@ set the following parameters on the share containing it: browseable = yes public = yes

  • Now you are ready to run the setup program from the Microsoft Windows -workstation as follows: \\"Server_Name"\MSOP95\msoffice\setup -

  • Microsoft Access database opening errors

    +workstation as follows: \\"Server_Name"\MSOP95\msoffice\setup +

    Microsoft Access database opening errors

    Here are some notes on running MS-Access on a Samba drive from Stefan Kjellberg -

    Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.
    Make sure that you open the database as 'shared' and to 'lock modified records'
    Of course locking must be enabled for the particular share (smb.conf)
    -
    +

    Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.
    Make sure that you open the database as 'shared' and to 'lock modified records'
    Of course locking must be enabled for the particular share (smb.conf)

    +

    diff --git a/docs/faq/FAQ-Install.html b/docs/faq/FAQ-Install.html index 94a80b3953..fc5b1e9812 100644 --- a/docs/faq/FAQ-Install.html +++ b/docs/faq/FAQ-Install.html @@ -1,5 +1,4 @@ - -Chapter 2. Compiling and installing Samba on a Unix host

    Chapter 2. Compiling and installing Samba on a Unix host

    My client reports "cannot locate specified share name" or similar

    +Chapter 2. Compiling and installing Samba on a Unix host

    Chapter 2. Compiling and installing Samba on a Unix host

    My client reports "cannot locate specified share name" or similar

    This message indicates that your client CAN locate the specified server, which is a good start, but that it cannot find a service of the name you gave. @@ -8,7 +7,7 @@ The first step is to check the exact name of the service you are trying to connect to (consult your system administrator). Assuming it exists and you specified it correctly (read your client's docs on how to specify a service name correctly), read on: -

    Many clients cannot accept or use service names longer than eight characters.
    Many clients cannot accept or use service names containing spaces.
    Some servers (not Samba though) are case sensitive with service names.
    Some clients force service names into upper case.

    Why are my file's timestamps off by an hour, or by a few hours?

    +

    Many clients cannot accept or use service names longer than eight characters.
    Many clients cannot accept or use service names containing spaces.
    Some servers (not Samba though) are case sensitive with service names.
    Some clients force service names into upper case.

    Why are my file's timestamps off by an hour, or by a few hours?

    This is from Paul Eggert eggert@twinsun.com.

    Most likely it's a problem with your time zone settings. @@ -16,12 +15,12 @@ Most likely it's a problem with your time zone settings. Internally, Samba maintains time in traditional Unix format, namely, the number of seconds since 1970-01-01 00:00:00 Universal Time (or ``GMT''), not counting leap seconds. -

    +

    On the server side, Samba uses the Unix TZ variable to convert internal timestamps to and from local time. So on the server side, there are two things to get right. -
    The Unix system clock must have the correct Universal time. Use the shell command "sh -c 'TZ=UTC0 date'" to check this.
    The TZ environment variable must be set on the server before Samba is invoked. The details of this depend on the server OS, but typically you must edit a file whose name is /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.
    -

    TZ must have the correct value.

    +

    The Unix system clock must have the correct Universal time. Use the shell command "sh -c 'TZ=UTC0 date'" to check this.
    The TZ environment variable must be set on the server before Samba is invoked. The details of this depend on the server OS, but typically you must edit a file whose name is /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.

    +

    TZ must have the correct value.

    If possible, use geographical time zone settings (e.g. TZ='America/Los_Angeles' or perhaps TZ=':US/Pacific'). These are supported by most @@ -30,16 +29,16 @@ more accurate for historical timestamps. If your operating system has out-of-date tables, you should be able to update them from the public domain time zone tables at ftp://elsie.nci.nih.gov/pub/. -

    If your system does not support geographical timezone +

    If your system does not support geographical timezone settings, you must use a Posix-style TZ strings, e.g. TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time. Posix TZ strings can take the following form (with optional items in brackets): -

    +

     	StdOffset[Dst[Offset],Date/Time,Date/Time]
    -
    +

    where: -
    `Std' is the standard time designation (e.g. `PST').
    `Offset' is the number of hours behind UTC (e.g. `8'). +

    `Std' is the standard time designation (e.g. `PST').
    `Offset' is the number of hours behind UTC (e.g. `8'). Prepend a `-' if you are ahead of UTC, and append `:30' if you are at a half-hour offset. Omit all the remaining items if you do not use @@ -53,8 +52,8 @@ time starts and ends. The format for a date is of the nth week of the mth month, where week 5 means the last such day in the month. The format for a time is [h]h[:mm[:ss]], using a 24-hour clock. -
    -

    +

    +

    Other Posix string formats are allowed but you don't want to know about them.

    On the client side, you must make sure that your client's clock and diff --git a/docs/faq/FAQ-errors.html b/docs/faq/FAQ-errors.html index 5f9a5f54b4..ed896b9805 100644 --- a/docs/faq/FAQ-errors.html +++ b/docs/faq/FAQ-errors.html @@ -1,35 +1,34 @@ - -Chapter 4. Common errors

    Chapter 4. Common errors

    Not listening for calling name

    -
    +Chapter 4. Common errors

    Chapter 4. Common errors

    Not listening for calling name

    +

     Session request failed (131,129) with myname=HOBBES destname=CALVIN
     Not listening for calling name
    -
    -

    +

    +

    If you get this when talking to a Samba box then it means that your -global "hosts allow" or "hosts deny" settings are causing the Samba +global "hosts allow" or "hosts deny" settings are causing the Samba server to refuse the connection.

    -Look carefully at your "hosts allow" and "hosts deny" lines in the +Look carefully at your "hosts allow" and "hosts deny" lines in the global section of smb.conf.

    It can also be a problem with reverse DNS lookups not functioning correctly, leading to the remote host identity not being able to be confirmed, but that is less likely. -

    System Error 1240

    +

    System Error 1240

    System error 1240 means that the client is refusing to talk to a non-encrypting server. Microsoft changed WinNT in service pack 3 to refuse to connect to servers that do not support SMB password encryption. -

    There are two main solutions: -
    enable SMB password encryption in Samba. See the encryption part of +

    There are two main solutions: +

    enable SMB password encryption in Samba. See the encryption part of the samba HOWTO Collection
    disable this behaviour in NT. See the section about -Windows NT in the chapter "Portability" of the samba HOWTO collection -
    -

    smbclient ignores -N !

    +Windows NT in the chapter "Portability" of the samba HOWTO collection +

    +

    smbclient ignores -N !

    When getting the list of shares available on a host using the command smbclient -N -L the program always prompts for the password if the server is a Samba server. -It also ignores the "-N" argument when querying some (but not all) of our +It also ignores the "-N" argument when querying some (but not all) of our NT servers.

    @@ -43,7 +42,7 @@ This will set both the username and password to null, which is an anonymous login for SMB. Using -N would only set the password to null, and this is not accepted as an anonymous login for most SMB servers. -

    The data on the CD-Drive I've shared seems to be corrupted!

    +

    The data on the CD-Drive I've shared seems to be corrupted!

    Some OSes (notably Linux) default to auto detection of file type on cdroms and do cr/lf translation. This is a very bad idea when use with Samba. It causes all sorts of stuff ups. diff --git a/docs/faq/FAQ-features.html b/docs/faq/FAQ-features.html index 29e2b1d2a3..8eb7d94bab 100644 --- a/docs/faq/FAQ-features.html +++ b/docs/faq/FAQ-features.html @@ -1,41 +1,40 @@ - -Chapter 5. Features

    Chapter 5. Features

    How can I use samba as a fax server?

    Contributor: Gerhard Zuber

    Requirements: -
    UNIX box (Linux preferred) with SAMBA and a faxmodem
    ghostscript package
    mgetty+sendfax package
    pbm package (portable bitmap tools)
    -

    First, install and configure the required packages. Be sure to read the mgetty+sendfax -manual carefully.

    Tools for printing faxes

    Your incomed faxes are in: +Chapter 5. Features

    Chapter 5. Features

    How can I use samba as a fax server?

    Contributor: Gerhard Zuber

    Requirements: +

    UNIX box (Linux preferred) with SAMBA and a faxmodem
    ghostscript package
    mgetty+sendfax package
    pbm package (portable bitmap tools)

    +

    First, install and configure the required packages. Be sure to read the mgetty+sendfax +manual carefully.

    Tools for printing faxes

    Your incomed faxes are in: /var/spool/fax/incoming. Print it with:

     for i in *
     do
     g3cat $i | g3tolj | lpr -P hp
     done
    -
    -

    +

    +

    g3cat is in the tools-section, g3tolj is in the contrib-section for printing to HP lasers.

    If you want to produce files for displaying and printing with Windows, use some tools from the pbm-package like the following command: g3cat $i | g3topbm - | ppmtopcx - >$i.pcx and view it with your favourite Windows tool (maybe paintbrush) -

    Making the fax-server

    fetch the file mgetty+sendfax/frontends/winword/faxfilter and place it in /usr/local/etc/mgetty+sendfax/(replace /usr/local/ with whatever place you installed mgetty+sendfax)

    prepare your faxspool file as mentioned in this file +

    Making the fax-server

    fetch the file mgetty+sendfax/frontends/winword/faxfilter and place it in /usr/local/etc/mgetty+sendfax/(replace /usr/local/ with whatever place you installed mgetty+sendfax)

    prepare your faxspool file as mentioned in this file edit fax/faxspool.in and reinstall or change the final /usr/local/bin/faxspool too.

    -if [ "$user" = "root" -o "$user" = "fax" -o \
    -     "$user" = "lp" -o "$user" = "daemon" -o "$user" = "bin" ]
    +if [ "$user" = "root" -o "$user" = "fax" -o \
    +     "$user" = "lp" -o "$user" = "daemon" -o "$user" = "bin" ]
     

    find the first line and change it to the second.

    make sure you have pbmtext (from the pbm-package). This is needed for creating the small header line on each page. -

    Prepare your faxheader /usr/local/etc/mgetty+sendfax/faxheader

    +

    Prepare your faxheader /usr/local/etc/mgetty+sendfax/faxheader

    Edit your /etc/printcap file: -

    +

     # FAX 
     lp3|fax:\
             :lp=/dev/null:\
             :sd=/usr/spool/lp3:\
             :if=/usr/local/etc/mgetty+sendfax/faxfilter:sh:sf:mx#0:\
             :lf=/usr/spool/lp3/fax-log:
    -

    Now, edit your smb.conf so you have a smb based printer named "fax"

    Installing the client drivers

    -Now you have a printer called "fax" which can be used via +

    Now, edit your smb.conf so you have a smb based printer named "fax"

    Installing the client drivers

    +Now you have a printer called "fax" which can be used via TCP/IP-printing (lpd-system) or via SAMBA (windows printing).

    On every system you are able to produce postscript-files you @@ -45,7 +44,7 @@ On Windows 3.1 95 and NT:

    Install a printer wich produces postscript output, e.g. apple laserwriter -

    Connect the "fax" to your printer.

    +

    Connect the "fax" to your printer.

    Now write your first fax. Use your favourite wordprocessor, write, winword, notepad or whatever you want, and start with the headerpage. @@ -55,17 +54,17 @@ your address, your phone/fax-number.

    It carries also the recipient, his address and his *** fax number ***. Now here is the trick: -

    +

    Use the text: -

    +

     Fax-Nr: 123456789
    -
    +

    as the recipients fax-number. Make sure this text does not occur in regular text ! Make sure this text is not broken by formatting information, e.g. format it as a single entity. (Windows Write and Win95 Wordpad are functional, maybe newer versions of Winword are breaking formatting information). -

    +

    The trick is that postscript output is human readable and the faxfilter program scans the text for this pattern and uses the found number as the fax-destination-number. @@ -73,7 +72,7 @@ uses the found number as the fax-destination-number. Now print your fax through the fax-printer and it will be queued for later transmission. Use faxrunq for sending the queue out. -

    Example smb.conf

    +

    Example smb.conf

     [global]
      printcap name = /etc/printcap
      print command = /usr/bin/lpr -r -P %p %s
    @@ -89,7 +88,7 @@ queue out.
         create mode = 0700
         browseable = yes
         guest ok = no
    -

    Samba doesn't work well together with DHCP!

    +

    Samba doesn't work well together with DHCP!

    We wish to help those folks who wish to use the ISC DHCP Server and provide sample configuration settings. Most operating systems today come ship with the ISC DHCP Server. ISC DHCP is available from: @@ -142,14 +141,14 @@ applied to the resulting DHCP offered settings UNLESS the DHCP server also sets a NetBIOS Scope. It may therefore be prudent to forcibly apply a NULL NetBIOS Scope from your DHCP server. The can be done in the dhcpd.conf file with the parameter: -option netbios-scope ""; +option netbios-scope "";

    While it is true that the Microsoft DHCP server that comes with Windows NT Server provides only a sub-set of rfc1533 functionality this is hardly an issue in those sites that already have a large investment and commitment to Unix systems and technologies. The current state of the art of the DHCP Server specification in covered in rfc2132. -

    How can I assign NetBIOS names to clients with DHCP?

    +

    How can I assign NetBIOS names to clients with DHCP?

    SMB network clients need to be configured so that all standard TCP/IP name to address resolution works correctly. Once this has been achieved the SMB environment provides additional tools and services that act as helper agents in @@ -164,13 +163,13 @@ This can be done, but needs a few NT registry hacks and you need to be able to speak UNICODE, which is of course no problem for a True Wizzard(tm) :) Instructions on how to do this (including a small util for less capable Wizzards) can be found at -

    http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html

    How do I convert between unix and dos text formats?

    +

    http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html

    How do I convert between unix and dos text formats?

    Jim barry has written an excellent drag-and-drop cr/lf converter for windows. Just drag your file onto the icon and it converts the file.

    The utilities unix2dos and dos2unix(in the mtools package) should do the job under unix. -

    Does samba have wins replication support?

    +

    Does samba have wins replication support?

    At the time of writing there is currently being worked on a wins replication implementation(wrepld).

    diff --git a/docs/faq/FAQ-general.html b/docs/faq/FAQ-general.html index a0b477eabb..311368c2a9 100644 --- a/docs/faq/FAQ-general.html +++ b/docs/faq/FAQ-general.html @@ -1,30 +1,29 @@ - -Chapter 1. General Information

    Chapter 1. General Information

    What do the version numbers mean?

    +Chapter 1. General Information

    Chapter 1. General Information

    What do the version numbers mean?

    It is not recommended that you run a version of Samba with the word -"alpha" in its name unless you know what you are doing and are willing +"alpha" in its name unless you know what you are doing and are willing to do some debugging. Many, many people just get the latest recommended stable release version and are happy. If you are brave, by all means take the plunge and help with the testing and development - but don't install it on your departmental server. Samba is typically very stable and safe, and this is mostly due to the policy of many public releases. -

    +

    How the scheme works: -
    When major changes are made the version number is increased. For +

    When major changes are made the version number is increased. For example, the transition from 1.9.15 to 1.9.16. However, this version number will not appear immediately and people should continue to use 1.9.15 for production systems (see next point.)
    Just after major changes are made the software is considered unstable, and a series of alpha releases are distributed, for example 1.9.16alpha1. These are for testing by those who know what they are -doing. The "alpha" in the filename will hopefully scare off those who +doing. The "alpha" in the filename will hopefully scare off those who are just looking for the latest version to install.
    When the release manager, currently Jerry, thinks that the alphas have stabilised to the point where he would recommend new users install it, he renames it to the -same version number without the alpha, for example 1.9.16.
    Inevitably bugs are found in the "stable" releases and minor patch -levels are released which give us the pXX series, for example 1.9.16p2.
    - +same version number without the alpha, for example 1.9.16.
    Inevitably bugs are found in the "stable" releases and minor patch +levels are released which give us the pXX series, for example 1.9.16p2.

    +

    So the progression goes: -

    +

     1.9.15p7	(production)
     1.9.15p8	(production)
     1.9.16alpha1	(test sites only)
    @@ -32,17 +31,17 @@ So the progression goes:
     1.9.16alpha20	(test sites only)
     1.9.16		(production)
     1.9.16p1	(production)
    -
    -

    +

    +

    The above system means that whenever someone looks at the samba ftp site they will be able to grab the highest numbered release without an alpha in the name and be sure of getting the current recommended version. -

    What platforms are supported?

    +

    What platforms are supported?

    Many different platforms have run Samba successfully. The platforms most widely used and thus best tested are Linux and SunOS.

    At time of writing, there is support (or has been support for in earlier versions): -

    A/UX 3.0
    AIX
    Altos Series 386/1000
    Amiga
    Apollo Domain/OS sr10.3
    BSDI
    B.O.S. (Bull Operating System)
    Cray, Unicos 8.0
    Convex
    DGUX.
    DNIX.
    FreeBSD
    HP-UX
    Intergraph.
    Linux with/without shadow passwords and quota
    LYNX 2.3.0
    MachTen (a unix like system for Macintoshes)
    Motorola 88xxx/9xx range of machines
    NetBSD
    NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).
    OS/2 using EMX 0.9b
    OSF1
    QNX 4.22
    RiscIX.
    RISCOs 5.0B
    SEQUENT.
    SCO (including: 3.2v2, European dist., OpenServer 5)
    SGI.
    SMP_DC.OSx v1.1-94c079 on Pyramid S series
    SONY NEWS, NEWS-OS (4.2.x and 6.1.x)
    SUNOS 4
    SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')
    Sunsoft ISC SVR3V4
    SVR4
    System V with some berkely extensions (Motorola 88k R32V3.2).
    ULTRIX.
    UNIXWARE
    UXP/DS

    How do I subscribe to the Samba Mailing Lists?

    +

    A/UX 3.0
    AIX
    Altos Series 386/1000
    Amiga
    Apollo Domain/OS sr10.3
    BSDI
    B.O.S. (Bull Operating System)
    Cray, Unicos 8.0
    Convex
    DGUX.
    DNIX.
    FreeBSD
    HP-UX
    Intergraph.
    Linux with/without shadow passwords and quota
    LYNX 2.3.0
    MachTen (a unix like system for Macintoshes)
    Motorola 88xxx/9xx range of machines
    NetBSD
    NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).
    OS/2 using EMX 0.9b
    OSF1
    QNX 4.22
    RiscIX.
    RISCOs 5.0B
    SEQUENT.
    SCO (including: 3.2v2, European dist., OpenServer 5)
    SGI.
    SMP_DC.OSx v1.1-94c079 on Pyramid S series
    SONY NEWS, NEWS-OS (4.2.x and 6.1.x)
    SUNOS 4
    SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')
    Sunsoft ISC SVR3V4
    SVR4
    System V with some berkely extensions (Motorola 88k R32V3.2).
    ULTRIX.
    UNIXWARE
    UXP/DS

    How do I subscribe to the Samba Mailing Lists?

    Look at the samba mailing list page

    diff --git a/docs/faq/samba-faq.html b/docs/faq/samba-faq.html index 9912a4982e..c33143e747 100644 --- a/docs/faq/samba-faq.html +++ b/docs/faq/samba-faq.html @@ -1,4 +1,4 @@ -Samba FAQ

    Samba FAQ

    Samba Team

    October 2002


    Dedication

    +Samba FAQ

    +

    -- cgit