From ad00237aafd5f68c89df5da4bae7f98b95741200 Mon Sep 17 00:00:00 2001
From: cvs2svn Import User
Date: Tue, 1 Jul 1997 01:19:14 +0000
Subject: This commit was manufactured by cvs2svn to create tag
'pre_luke_stuffup_1'.
---
COPYING | 339 ---
README | 153 --
WHATSNEW.txt | 80 -
docs/INSTALL.txt | 342 ---
docs/MIRRORS | 33 -
docs/OS2.txt | 59 -
docs/README.OS2 | 87 -
docs/THANKS | 137 -
docs/Warp.txt | 103 -
docs/announce | 133 -
docs/faq/sambafaq-1.html | 392 ---
docs/faq/sambafaq-2.html | 239 --
docs/faq/sambafaq-3.html | 322 ---
docs/faq/sambafaq-4.html | 37 -
docs/faq/sambafaq-5.html | 30 -
docs/faq/sambafaq.html | 115 -
docs/faq/sambafaq.sgml | 789 ------
docs/faq/sambafaq.txt | 1122 --------
docs/history | 196 --
docs/htmldocs/wfw_slip.htm | 175 --
docs/manpages/nmbd.8 | 231 --
docs/manpages/samba.7 | 202 --
docs/manpages/smb.conf.5 | 3390 -----------------------
docs/manpages/smbclient.1 | 1204 --------
docs/manpages/smbd.8 | 418 ---
docs/manpages/smbrun.1 | 74 -
docs/manpages/smbstatus.1 | 70 -
docs/manpages/smbtar.1 | 178 --
docs/manpages/testparm.1 | 109 -
docs/manpages/testprns.1 | 112 -
docs/samba.faq | 900 ------
docs/samba.lsm | 26 -
docs/textdocs/Application_Serving.txt | 49 -
docs/textdocs/BROWSING.txt | 546 ----
docs/textdocs/BUGS.txt | 135 -
docs/textdocs/DIAGNOSIS.txt | 251 --
docs/textdocs/DNIX.txt | 69 -
docs/textdocs/DOMAIN.txt | 179 --
docs/textdocs/DOMAIN_CONTROL.txt | 90 -
docs/textdocs/ENCRYPTION.txt | 350 ---
docs/textdocs/Faxing.txt | 163 --
docs/textdocs/GOTCHAS.txt | 68 -
docs/textdocs/HINTS.txt | 209 --
docs/textdocs/INSTALL.sambatar | 33 -
docs/textdocs/NetBIOS.txt | 131 -
docs/textdocs/PROJECTS | 88 -
docs/textdocs/Passwords.txt | 46 -
docs/textdocs/Printing.txt | 93 -
docs/textdocs/README.DCEDFS | 78 -
docs/textdocs/README.jis | 149 -
docs/textdocs/README.sambatar | 23 -
docs/textdocs/SCO.txt | 19 -
docs/textdocs/SMBTAR.notes | 46 -
docs/textdocs/Speed.txt | 318 ---
docs/textdocs/Support.txt | 1388 ----------
docs/textdocs/Tracing.txt | 93 -
docs/textdocs/UNIX-SMB.txt | 231 --
docs/textdocs/WinNT.txt | 69 -
docs/textdocs/security_level.txt | 96 -
examples/README | 6 -
examples/dce-dfs/README | 4 -
examples/dce-dfs/smb.conf | 42 -
examples/misc/extra_smbstatus | 50 -
examples/misc/wall.perl | 69 -
examples/printer-accounting/README | 63 -
examples/printer-accounting/acct-all | 9 -
examples/printer-accounting/acct-sum | 29 -
examples/printer-accounting/hp5-redir | 43 -
examples/printer-accounting/lp-acct | 38 -
examples/printer-accounting/printcap | 22 -
examples/printing/smbprint | 77 -
examples/printing/smbprint.sysv | 52 -
examples/redhat/Instructions | 25 -
examples/redhat/makeldirs.sh | 10 -
examples/redhat/makerpms.sh | 10 -
examples/redhat/samba-axp.patch | 21 -
examples/redhat/samba-make.patch | 121 -
examples/redhat/samba.log | 17 -
examples/redhat/samba.spec | 154 --
examples/redhat/smb.conf | 196 --
examples/redhat/smb.init | 32 -
examples/redhat/smbprint | 77 -
examples/simple/README | 2 -
examples/simple/smb.conf | 167 --
examples/svr4-startup/README | 24 -
examples/svr4-startup/samba.server | 38 -
examples/thoralf/smb.conf | 152 -
examples/tridge/README | 8 -
examples/tridge/smb.conf | 101 -
examples/tridge/smb.conf.WinNT | 14 -
examples/tridge/smb.conf.fjall | 21 -
examples/tridge/smb.conf.lapland | 14 -
examples/tridge/smb.conf.vittjokk | 14 -
examples/validchars/msdos70.out | 257 --
examples/validchars/nwdos70.out | 257 --
examples/validchars/readme | 101 -
examples/validchars/validchr.c | 123 -
examples/validchars/validchr.com | Bin 9792 -> 0 bytes
source/.cvsignore | 12 -
source/Makefile.RPM | 663 -----
source/change-log | 1878 -------------
source/client/client.c | 4870 ---------------------------------
source/client/clientutil.c | 1027 -------
source/client/clitar.c | 1726 ------------
source/include/byteorder.h | 144 -
source/include/charset.h | 65 -
source/include/clitar.h | 17 -
source/include/includes.h | 1256 ---------
source/include/kanji.h | 130 -
source/include/local.h | 162 --
source/include/nameserv.h | 429 ---
source/include/trans2.h | 246 --
source/include/version.h | 1 -
source/include/vt_mode.h | 48 -
source/internals.doc | 212 --
source/lib/access.c | 289 --
source/lib/charcnv.c | 154 --
source/lib/charset.c | 283 --
source/lib/fault.c | 82 -
source/lib/getsmbpass.c | 165 --
source/lib/interface.c | 457 ----
source/lib/kanji.c | 894 ------
source/lib/md4.c | 299 --
source/lib/replace.c | 325 ---
source/lib/system.c | 394 ---
source/lib/time.c | 495 ----
source/lib/ufc.c | 782 ------
source/lib/username.c | 253 --
source/libsmb/namequery.c | 295 --
source/libsmb/nmblib.c | 731 -----
source/libsmb/smbencrypt.c | 196 --
source/locking/locking.c | 1247 ---------
source/locking/shmem.c | 844 ------
source/md4.h | 58 -
source/nameannounce.c | 563 ----
source/nameannounce.doc | 265 --
source/namebrowse.c | 246 --
source/namebrowse.doc | 149 -
source/nameconf.c | 350 ---
source/namedbname.c | 599 ----
source/namedbname.doc | 182 --
source/namedbresp.c | 164 --
source/namedbresp.doc | 100 -
source/namedbserver.c | 212 --
source/namedbsubnet.c | 346 ---
source/namedbwork.c | 243 --
source/nameelect.c | 850 ------
source/nameelect.doc | 256 --
source/namelogon.c | 145 -
source/namelogon.doc | 36 -
source/namepacket.c | 635 -----
source/namepacket.doc | 133 -
source/namequery.doc | 83 -
source/nameresp.c | 327 ---
source/nameresp.doc | 178 --
source/nameserv.c | 440 ---
source/nameserv.doc | 159 --
source/nameservreply.c | 641 -----
source/nameservreply.doc | 213 --
source/nameservresp.c | 917 -------
source/nameservresp.doc | 191 --
source/namework.c | 733 -----
source/namework.doc | 363 ---
source/nmbd/nmbd.c | 584 ----
source/nmbsync.c | 187 --
source/param/params.c | 326 ---
source/passdb/smbpass.c | 299 --
source/printing/pcap.c | 381 ---
source/printing/printing.c | 1082 --------
source/script/addtosmbpass | 74 -
source/script/installbin.sh | 44 -
source/script/installman.sh | 38 -
source/script/installscripts.sh | 43 -
source/script/mkproto.awk | 82 -
source/script/mksmbpasswd.sh | 6 -
source/script/revert.sh | 15 -
source/script/smbtar | 140 -
source/script/uninstallbin.sh | 43 -
source/script/uninstallman.sh | 31 -
source/script/uninstallscripts.sh | 37 -
source/script/updatesmbpasswd.sh | 14 -
source/smbd/chgpasswd.c | 379 ---
source/smbd/ipc.c | 3098 ---------------------
source/smbd/mangle.c | 660 -----
source/smbd/message.c | 201 --
source/smbd/password.c | 1572 -----------
source/smbd/pipes.c | 350 ---
source/smbd/predict.c | 145 -
source/smbd/quotas.c | 445 ---
source/smbd/reply.c | 3341 ----------------------
source/smbd/smbrun.c | 97 -
source/smbd/trans2.c | 1651 -----------
source/smbd/uid.c | 478 ----
source/smbd/vt_mode.c | 490 ----
source/utils/nmblookup.c | 209 --
source/utils/smbpasswd.c | 457 ----
source/utils/status.c | 512 ----
source/utils/testparm.c | 112 -
source/utils/testprns.c | 72 -
199 files changed, 67810 deletions(-)
delete mode 100644 COPYING
delete mode 100644 README
delete mode 100644 WHATSNEW.txt
delete mode 100644 docs/INSTALL.txt
delete mode 100644 docs/MIRRORS
delete mode 100644 docs/OS2.txt
delete mode 100644 docs/README.OS2
delete mode 100644 docs/THANKS
delete mode 100644 docs/Warp.txt
delete mode 100644 docs/announce
delete mode 100644 docs/faq/sambafaq-1.html
delete mode 100644 docs/faq/sambafaq-2.html
delete mode 100644 docs/faq/sambafaq-3.html
delete mode 100644 docs/faq/sambafaq-4.html
delete mode 100644 docs/faq/sambafaq-5.html
delete mode 100644 docs/faq/sambafaq.html
delete mode 100644 docs/faq/sambafaq.sgml
delete mode 100644 docs/faq/sambafaq.txt
delete mode 100644 docs/history
delete mode 100644 docs/htmldocs/wfw_slip.htm
delete mode 100644 docs/manpages/nmbd.8
delete mode 100644 docs/manpages/samba.7
delete mode 100644 docs/manpages/smb.conf.5
delete mode 100644 docs/manpages/smbclient.1
delete mode 100644 docs/manpages/smbd.8
delete mode 100644 docs/manpages/smbrun.1
delete mode 100644 docs/manpages/smbstatus.1
delete mode 100644 docs/manpages/smbtar.1
delete mode 100644 docs/manpages/testparm.1
delete mode 100644 docs/manpages/testprns.1
delete mode 100644 docs/samba.faq
delete mode 100644 docs/samba.lsm
delete mode 100644 docs/textdocs/Application_Serving.txt
delete mode 100644 docs/textdocs/BROWSING.txt
delete mode 100644 docs/textdocs/BUGS.txt
delete mode 100644 docs/textdocs/DIAGNOSIS.txt
delete mode 100644 docs/textdocs/DNIX.txt
delete mode 100644 docs/textdocs/DOMAIN.txt
delete mode 100644 docs/textdocs/DOMAIN_CONTROL.txt
delete mode 100644 docs/textdocs/ENCRYPTION.txt
delete mode 100644 docs/textdocs/Faxing.txt
delete mode 100644 docs/textdocs/GOTCHAS.txt
delete mode 100644 docs/textdocs/HINTS.txt
delete mode 100644 docs/textdocs/INSTALL.sambatar
delete mode 100644 docs/textdocs/NetBIOS.txt
delete mode 100644 docs/textdocs/PROJECTS
delete mode 100644 docs/textdocs/Passwords.txt
delete mode 100644 docs/textdocs/Printing.txt
delete mode 100644 docs/textdocs/README.DCEDFS
delete mode 100644 docs/textdocs/README.jis
delete mode 100644 docs/textdocs/README.sambatar
delete mode 100644 docs/textdocs/SCO.txt
delete mode 100644 docs/textdocs/SMBTAR.notes
delete mode 100644 docs/textdocs/Speed.txt
delete mode 100644 docs/textdocs/Support.txt
delete mode 100644 docs/textdocs/Tracing.txt
delete mode 100644 docs/textdocs/UNIX-SMB.txt
delete mode 100644 docs/textdocs/WinNT.txt
delete mode 100644 docs/textdocs/security_level.txt
delete mode 100644 examples/README
delete mode 100644 examples/dce-dfs/README
delete mode 100644 examples/dce-dfs/smb.conf
delete mode 100644 examples/misc/extra_smbstatus
delete mode 100644 examples/misc/wall.perl
delete mode 100644 examples/printer-accounting/README
delete mode 100644 examples/printer-accounting/acct-all
delete mode 100644 examples/printer-accounting/acct-sum
delete mode 100644 examples/printer-accounting/hp5-redir
delete mode 100644 examples/printer-accounting/lp-acct
delete mode 100644 examples/printer-accounting/printcap
delete mode 100755 examples/printing/smbprint
delete mode 100644 examples/printing/smbprint.sysv
delete mode 100644 examples/redhat/Instructions
delete mode 100755 examples/redhat/makeldirs.sh
delete mode 100755 examples/redhat/makerpms.sh
delete mode 100644 examples/redhat/samba-axp.patch
delete mode 100644 examples/redhat/samba-make.patch
delete mode 100644 examples/redhat/samba.log
delete mode 100644 examples/redhat/samba.spec
delete mode 100644 examples/redhat/smb.conf
delete mode 100755 examples/redhat/smb.init
delete mode 100755 examples/redhat/smbprint
delete mode 100644 examples/simple/README
delete mode 100644 examples/simple/smb.conf
delete mode 100644 examples/svr4-startup/README
delete mode 100755 examples/svr4-startup/samba.server
delete mode 100644 examples/thoralf/smb.conf
delete mode 100644 examples/tridge/README
delete mode 100644 examples/tridge/smb.conf
delete mode 100644 examples/tridge/smb.conf.WinNT
delete mode 100644 examples/tridge/smb.conf.fjall
delete mode 100644 examples/tridge/smb.conf.lapland
delete mode 100644 examples/tridge/smb.conf.vittjokk
delete mode 100644 examples/validchars/msdos70.out
delete mode 100644 examples/validchars/nwdos70.out
delete mode 100644 examples/validchars/readme
delete mode 100644 examples/validchars/validchr.c
delete mode 100644 examples/validchars/validchr.com
delete mode 100644 source/.cvsignore
delete mode 100644 source/Makefile.RPM
delete mode 100644 source/change-log
delete mode 100644 source/client/client.c
delete mode 100644 source/client/clientutil.c
delete mode 100644 source/client/clitar.c
delete mode 100644 source/include/byteorder.h
delete mode 100644 source/include/charset.h
delete mode 100644 source/include/clitar.h
delete mode 100644 source/include/includes.h
delete mode 100644 source/include/kanji.h
delete mode 100644 source/include/local.h
delete mode 100644 source/include/nameserv.h
delete mode 100644 source/include/trans2.h
delete mode 100644 source/include/version.h
delete mode 100644 source/include/vt_mode.h
delete mode 100644 source/internals.doc
delete mode 100644 source/lib/access.c
delete mode 100644 source/lib/charcnv.c
delete mode 100644 source/lib/charset.c
delete mode 100644 source/lib/fault.c
delete mode 100644 source/lib/getsmbpass.c
delete mode 100644 source/lib/interface.c
delete mode 100644 source/lib/kanji.c
delete mode 100644 source/lib/md4.c
delete mode 100644 source/lib/replace.c
delete mode 100644 source/lib/system.c
delete mode 100644 source/lib/time.c
delete mode 100644 source/lib/ufc.c
delete mode 100644 source/lib/username.c
delete mode 100644 source/libsmb/namequery.c
delete mode 100644 source/libsmb/nmblib.c
delete mode 100644 source/libsmb/smbencrypt.c
delete mode 100644 source/locking/locking.c
delete mode 100644 source/locking/shmem.c
delete mode 100644 source/md4.h
delete mode 100644 source/nameannounce.c
delete mode 100644 source/nameannounce.doc
delete mode 100644 source/namebrowse.c
delete mode 100644 source/namebrowse.doc
delete mode 100644 source/nameconf.c
delete mode 100644 source/namedbname.c
delete mode 100644 source/namedbname.doc
delete mode 100644 source/namedbresp.c
delete mode 100644 source/namedbresp.doc
delete mode 100644 source/namedbserver.c
delete mode 100644 source/namedbsubnet.c
delete mode 100644 source/namedbwork.c
delete mode 100644 source/nameelect.c
delete mode 100644 source/nameelect.doc
delete mode 100644 source/namelogon.c
delete mode 100644 source/namelogon.doc
delete mode 100644 source/namepacket.c
delete mode 100644 source/namepacket.doc
delete mode 100644 source/namequery.doc
delete mode 100644 source/nameresp.c
delete mode 100644 source/nameresp.doc
delete mode 100644 source/nameserv.c
delete mode 100644 source/nameserv.doc
delete mode 100644 source/nameservreply.c
delete mode 100644 source/nameservreply.doc
delete mode 100644 source/nameservresp.c
delete mode 100644 source/nameservresp.doc
delete mode 100644 source/namework.c
delete mode 100644 source/namework.doc
delete mode 100644 source/nmbd/nmbd.c
delete mode 100644 source/nmbsync.c
delete mode 100644 source/param/params.c
delete mode 100644 source/passdb/smbpass.c
delete mode 100644 source/printing/pcap.c
delete mode 100644 source/printing/printing.c
delete mode 100644 source/script/addtosmbpass
delete mode 100755 source/script/installbin.sh
delete mode 100755 source/script/installman.sh
delete mode 100755 source/script/installscripts.sh
delete mode 100644 source/script/mkproto.awk
delete mode 100755 source/script/mksmbpasswd.sh
delete mode 100755 source/script/revert.sh
delete mode 100644 source/script/smbtar
delete mode 100755 source/script/uninstallbin.sh
delete mode 100755 source/script/uninstallman.sh
delete mode 100755 source/script/uninstallscripts.sh
delete mode 100755 source/script/updatesmbpasswd.sh
delete mode 100644 source/smbd/chgpasswd.c
delete mode 100644 source/smbd/ipc.c
delete mode 100644 source/smbd/mangle.c
delete mode 100644 source/smbd/message.c
delete mode 100644 source/smbd/password.c
delete mode 100644 source/smbd/pipes.c
delete mode 100644 source/smbd/predict.c
delete mode 100644 source/smbd/quotas.c
delete mode 100644 source/smbd/reply.c
delete mode 100644 source/smbd/smbrun.c
delete mode 100644 source/smbd/trans2.c
delete mode 100644 source/smbd/uid.c
delete mode 100644 source/smbd/vt_mode.c
delete mode 100644 source/utils/nmblookup.c
delete mode 100644 source/utils/smbpasswd.c
delete mode 100644 source/utils/status.c
delete mode 100644 source/utils/testparm.c
delete mode 100644 source/utils/testprns.c
diff --git a/COPYING b/COPYING
deleted file mode 100644
index a43ea2126fb..00000000000
--- a/COPYING
+++ /dev/null
@@ -1,339 +0,0 @@
- GNU GENERAL PUBLIC LICENSE
- Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 675 Mass Ave, Cambridge, MA 02139, USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
- Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it. (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.) You can apply it to
-your programs, too.
-
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
-
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
- Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
- Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary. To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
- GNU GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
- 1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
- 2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
- a) You must cause the modified files to carry prominent notices
- stating that you changed the files and the date of any change.
-
- b) You must cause any work that you distribute or publish, that in
- whole or in part contains or is derived from the Program or any
- part thereof, to be licensed as a whole at no charge to all third
- parties under the terms of this License.
-
- c) If the modified program normally reads commands interactively
- when run, you must cause it, when started running for such
- interactive use in the most ordinary way, to print or display an
- announcement including an appropriate copyright notice and a
- notice that there is no warranty (or else, saying that you provide
- a warranty) and that users may redistribute the program under
- these conditions, and telling the user how to view a copy of this
- License. (Exception: if the Program itself is interactive but
- does not normally print such an announcement, your work based on
- the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
- 3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
- a) Accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of Sections
- 1 and 2 above on a medium customarily used for software interchange; or,
-
- b) Accompany it with a written offer, valid for at least three
- years, to give any third party, for a charge no more than your
- cost of physically performing source distribution, a complete
- machine-readable copy of the corresponding source code, to be
- distributed under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,
-
- c) Accompany it with the information you received as to the offer
- to distribute corresponding source code. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form with such
- an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
- 4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
- 5. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
- 7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all. For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
- 8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
-
- 9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
- 10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
- NO WARRANTY
-
- 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
- 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
- END OF TERMS AND CONDITIONS
-
- Appendix: How to Apply These Terms to Your New Programs
-
- If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
- To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-
- Copyright (C) 19yy
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
- Gnomovision version 69, Copyright (C) 19yy name of author
- Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License. Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. Here is a sample; alter the names:
-
- Yoyodyne, Inc., hereby disclaims all copyright interest in the program
- `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
- , 1 April 1989
- Ty Coon, President of Vice
-
-This General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library. If this is what you want to do, use the GNU Library General
-Public License instead of this License.
diff --git a/README b/README
deleted file mode 100644
index 9bc9953c265..00000000000
--- a/README
+++ /dev/null
@@ -1,153 +0,0 @@
-This is version 1.9.17 of Samba, the free SMB client and server for unix
-and other operating systems. Samba is maintained by the Samba Team,
-who support the original author, Andrew Tridgell.
-
->>>> Please read THE WHOLE of this file as it gives important information
->>>> about the configuration and use of Samba.
-
-This software is freely distributable under the GNU public license, a
-copy of which you should have received with this software (in a file
-called COPYING).
-
-WHAT IS SMB?
-============
-
-This is a big question.
-
-The very short answer is that it is the protocol by which a lot of
-PC-related machines share files and printers and other informatiuon
-such as lists of available files and printers. Operating systems that
-support this natively include Windows NT, OS/2, and Linux and add on
-packages that achieve the same thing are available for DOS, Windows,
-VMS, Unix of all kinds, MVS, and more. There is no reason why Apple
-Macs and indeed any Web browser should not be able to speak this
-protocol, and current development (in which the Samba team is heavily
-involved) is aimed at exactly that. Alternatives to SMB include
-Netware, NFS, Appletalk, Banyan Vines, Decnet etc; many of these have
-advantages but none are both public specifications and widely
-implemented in desktop machines by default.
-
-The Common Internet Filesystem is what the new SMB initiative is
-called. For details watch http://samba.anu.edu.au/cifs.
-
-WHAT CAN SAMBA DO?
-==================
-
-Here is a very short list of what samba includes, and what it does.
-
-- a SMB server, to provide Windows NT and LAN Manager-style file and print
- services to SMB clients such as Windows 95, Warp Server, smbfs and others.
-
-- a Netbios (rfc1001/1002) nameserver, which among other things gives
- browsing support. Samba can be the master browser on your LAN if you wish.
-
-- a ftp-like SMB client so you can access PC resources (disks and
-printers) from unix, Netware and other operating systems
-
-- a tar extension to the client for backing up PCs
-
-For a much better overview have a look at the web site at
-http://samba.canberra.edu.au/pub/samba, and browse the user survey.
-
-Related packages include:
-
-- smbfs, a linux-only filesystem allowing you to mount remote SMB
-filesystems from PCs on your linux box. This is included as standard with
-Linux 2.0 and later.
-
-- tcpdump-smb, a extension to tcpdump to allow you to investigate SMB
-networking problems over netbeui and tcp/ip.
-
-- smblib, a library of smb functions which are designed to make it
-easy to smb-ise any particular application. See
-ftp://samba.anu.edu.au/pub/samba/smblib.
-
-CONTRIBUTIONS
-=============
-
-If you want to contribute to the development of the software then
-please join the mailing list. The Samba team accepts patches
-(preferably in "diff -u" format, see docs/BUGS.txt for more details)
-and are always glad to receive feedback or suggestions to the address
-samba-bugs@samba.anu.edu.au.
-
-You could also send hardware/software/money/jewelry or pizza
-vouchers directly to Andrew. The pizza vouchers would be especially
-welcome, in fact there is a special field in the survey for people who
-have paid up their pizza :-)
-
-If you like a particular feature then look through the change-log and
-see who added it, then send them an email.
-
-Remember that free software of this kind lives or dies by the response
-we get. If noone tells us they like it then we'll probably move onto
-something else. However, as you can see from the user survey quite a lot of
-people do seem to like it at the moment :-)
-
-Andrew Tridgell
-Email: samba-bugs@samba.anu.edu.au
-
-3 Ballow Crescent
-Macgregor, A.C.T.
-2615 Australia
-
-Samba Team
-Email: samba-team@samba.anu.edu.au
-
-MORE INFO
-=========
-
-DOCUMENTATION
--------------
-
-There is quite a bit of documentation included with the package,
-including man pages, and lots of .txt files with hints and useful
-info. This is also available from the web page.
-
-FTP SITE
---------
-
-The main anonymous ftp distribution site for this software is
-samba.anu.edu.au in the directory pub/samba/.
-
-MAILING LIST
-------------
-
-There is a mailing list for discussion of Samba. To subscribe send
-mail to listproc@samba.anu.edu.au with a body of "subscribe samba Your Name"
-
-To send mail to everyone on the list mail to samba@listproc.anu.edu.au
-
-There is also an announcement mailing list where new versions are
-announced. To subscribe send mail to listproc@samba.anu.edu.au with a
-body of "subscribe samba-announce Your Name". All announcements also
-go to the samba list.
-
-
-NEWS GROUP
-----------
-
-You might also like to look at the usenet news group
-comp.protocols.smb as it often contains lots of useful info and is
-frequented by lots of Samba users. The newsgroup was initially setup
-by people on the Samba mailing list. It is not, however, exclusive to
-Samba, it is a forum for discussing the SMB protocol (which Samba
-implements). The samba list is gatewayed to this newsgroup.
-
-
-WEB SITE
---------
-
-A Samba WWW site has been setup with lots of useful info. Connect to:
-
-http://samba.canberra.edu.au/pub/samba/
-
-As well as general information and documentation, this also has searchable
-archives of the mailing list and a user survey that shows who else is using
-this package. Have you registered with the survey yet? :-)
-
-It is maintained by Paul Blackman (thanks Paul!). You can contact him
-at ictinus@lake.canberra.edu.au.
-
-
-
diff --git a/WHATSNEW.txt b/WHATSNEW.txt
deleted file mode 100644
index dd291c001f7..00000000000
--- a/WHATSNEW.txt
+++ /dev/null
@@ -1,80 +0,0 @@
- WHATS NEW IN 1.9.17alpha3 - June 6th 1997.
- ==========================================
-
-Improved browsing support.
---------------------------
-
-Samba now should support propagation of browse lists
-across subnets correctly. Look in the file docs/BROWSING.txt
-as it has been largely re-written to explain how to do this.
-
-*IMPORTANT* All Samba servers acting as local/domain master
-browsers must be running 1.9.17alpha3 (or later), in addition
-nmbd must be set up as the WINS server.
-
-Thanks to Silicon Graphics for allowing us to test the new
-code on their corporate network.
-
-
-Improved share mode handling
-----------------------------
-
-The handling of share modes has been completely rewritten.
-Samba can now run agressive PC Benchmarks (Ziff-Davis
-NetBench) correctly with many hundreds of concurrent PC's.
-The confidence level on share mode handling in Samba
-is now much higher than it was previously. PC database
-packages should be much safer when run against a
-Samba share. Thanks to Silicon Graphics for testing
-this code for us.
-
-If at all possible compile Samba to use the new share
-mode handling with shared memory (set the flags
-FAST_SHARE_MODES in the Makefile). This will be *much* faster
-than old file-based share modes. FAST_SHARE_MODES have
-been turned on by default on the following platforms in
-the Makefile :
-
- Linux
- Solaris
- BSDI
- IRIX 5.x.x
- FreeBSD
-
-Updated smb.conf documentation
-------------------------------
-All options are now documented we believe.
-
-Many small bugfixes and improvements
-------------------------------------
-From around the 'net around the world. Many
-thanks to everyone who contributed.
-
-Remaining known issues with cross-subnet browsing.
---------------------------------------------------
-When nmbd is acting as a WINS server it doesn't handle
-de-registering of members of a WORKGROUP<1e> name correctly.
-The first machine to de-register will remove the name. This
-should be fixed in a later release when group names are
-handled correctly in the WINS code.
-
-Propagation of servers between local master browsers and
-the domain master browser doesn't take into account the
-fact that only names seen by the local master browser on
-the local subnet should be propagated. This causes machines
-that have stopped serving to be propagated between browse
-masters. This issue will be fixed in the smbd code in a
-later release.
-
-Remember - this is new code so there may be
-bugs or problems.
-
-As always, all bugs are our responsibility -
-please report them to :
-
-samba-bugs@samba.anu.edu.au
-
-
-Regards,
-
- The Samba Team.
diff --git a/docs/INSTALL.txt b/docs/INSTALL.txt
deleted file mode 100644
index a97d5f26790..00000000000
--- a/docs/INSTALL.txt
+++ /dev/null
@@ -1,342 +0,0 @@
-Contributor: Andrew Tridgell
-Date: Unknown
-Status: Current
-
-Subject: HOW TO INSTALL AND TEST SAMBA
-===============================================================================
-
-
-STEP 0. Read the man pages. They contain lots of useful info that will
-help to get you started. If you don't know how to read man pages then
-try something like:
-
- nroff -man smbd.8 | more
-
-Unfortunately, having said this, the man pages are sadly out of date and
-really need more effort to maintain them. Other sources of information
-are pointed to by the Samba web site, http://samba.canberra.edu.au/pub/samba.
-
-STEP 1. Building the binaries
-
-To do this, first edit the file source/Makefile. You will find that
-the Makefile has an entry for most unixes and you need to uncomment
-the one that matches your operating system.
-
-You should also edit the section at the top of the Makefile which
-determines where things will be installed. You need to get this right
-before compilation as Samba needs to find some things at runtime
-(smbrun in particular). There are also settings for where you want
-your log files etc. Make sure you get these right, and that the
-directories exist.
-
-Then type "make". This will create the binaries.
-
-Once it's successfully compiled you can use "make install" to install
-the binaries and manual pages. You can separately install the binaries
-and/or man pages using "make installbin" and "make installman".
-
-Note that if you are upgrading for a previous version of Samba you
-might like to know that the old versions of the binaries will be
-renamed with a ".old" extension. You can go back to the previous
-version with "make revert" if you find this version a disaster!
-
-STEP 2. The all important step
-
-At this stage you must fetch yourself a coffee or other drink you find
-stimulating. Getting the rest of the install right can sometimes be
-tricky, so you will probably need it.
-
-If you have installed samba before then you can skip this step.
-
-STEP 3. Create the smb configuration file.
-
-There are sample configuration files in the examples subdirectory in
-the distribution. I suggest you read them carefully so you can see how
-the options go together in practice. See the man page for all the
-options.
-
-The simplest useful configuration file would be something like this:
-
- workgroup = MYGROUP
-
- [homes]
- guest ok = no
- read only = no
-
-which would allow connections by anyone with an account on the server,
-using either their login name or "homes" as the service name. (Note
-that I also set the workgroup that Samba is part of. See BROWSING.txt
-for defails)
-
-Note that "make install" will not install a smb.conf file. You need to
-create it yourself. You will also need to create the path you specify
-in the Makefile for the logs etc, such as /usr/local/samba.
-
-Make sure you put the smb.conf file in the same place you specified in
-the Makefile.
-
-STEP 4. Test your config file with testparm
-
-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.
-
-Make sure it runs OK and that the services look resonable before
-proceeding.
-
-STEP 5. Starting the smbd and nmbd.
-
-You must choose to start smbd and nmbd either as daemons or from
-inetd. Don't try to do both! Either you can put them in inetd.conf
-and have them started on demand by inetd, or you can start them as
-daemons either from the command line or in /etc/rc.local. See the man
-pages for details on the command line options.
-
-The main advantage of starting smbd and nmbd as a daemon is that they
-will respond slightly more quickly to an initial connection
-request. This is, however, unlilkely to be a problem.
-
-Step 5a. Starting from inetd.conf
-
-NOTE; The following will be different if you use NIS or NIS+ to
-distributed services maps.
-
-Look at your /etc/services. What is defined at port 139/tcp. If
-nothing is defined then add a line like this:
-
-netbios-ssn 139/tcp
-
-similarly for 137/udp you should have an entry like:
-
-netbios-ns 137/udp
-
-Next edit your /etc/inetd.conf and add two lines something like this:
-
-netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd
-netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd
-
-The exact syntax of /etc/inetd.conf varies between unixes. Look at the
-other entries in inetd.conf for a guide.
-
-NOTE: Some unixes already have entries like netbios_ns (note the
-underscore) in /etc/services. You must either edit /etc/services or
-/etc/inetd.conf to make them consistant.
-
-NOTE: On many systems you may need to use the "interfaces" option in
-smb.conf to specify the IP address and netmask of your interfaces. Run
-ifconfig as root if you don't know what the broadcast is for your
-net. nmbd tries to determine it at run time, but fails on some
-unixes. See the section on "testing nmbd" for a method of finding if
-you need to do this.
-
-!!!WARNING!!! Many unixes only accept around 5 parameters on the
-command line in inetd. This means you shouldn't use spaces between the
-options and arguments, or you should use a script, and start the
-script from inetd.
-
-Restart inetd, perhaps just send it a HUP. If you have installed an
-earlier version of nmbd then you may need to kill nmbd as well.
-
-Step 5b. Alternative: starting it as a daemon
-
-To start the server as a daemon you should create a script something
-like this one, perhaps calling it "startsmb"
-
-#!/bin/sh
-/usr/local/samba/bin/smbd -D
-/usr/local/samba/bin/nmbd -D
-
-then make it executable with "chmod +x startsmb"
-
-You can then run startsmb by hand or execute it from /etc/rc.local
-
-To kill it send a kill signal to the processes nmbd and smbd.
-
-NOTE: If you use the SVR4 style init system then you may like to look
-at the examples/svr4-startup script to make Samba fit into that system.
-
-
-STEP 7. Try listing the shares available on your server
-
-smbclient -L yourhostname
-
-Your should get back a list of shares available on your server. If you
-don't then something is incorrectly setup. Note that this method can
-also be used to see what shares are available on other LanManager
-clients (such as WfWg).
-
-If you choose user level security then you may find that Samba requests
-a password before it will list the shares. See the smbclient docs for
-details. (you can force it to list the shares without a password by
-adding the option -U% to the command line. This will not work with
-non-Samba servers)
-
-STEP 8. try connecting with the unix client. eg:
-
-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] section
-in smb.conf.
-
-For example if your unix host is bambi and your login name is fred you
-would type:
-
-smbclient '\\bambi\fred'
-
-NOTE: The number of slashes to use depends on the type of shell you
-use. You may need '\\\\bambi\\fred' with some shells.
-
-STEP 9. Try connecting from a dos/WfWg/Win95/NT/os-2 client. Try
-mounting disks. eg:
-
-net use d: \\servername\service
-
-Try printing. eg:
-
-net use lpt1: \\servername\spoolservice
-print filename
-
-Celebrate, or send me a bug report!
-
-WHAT IF IT DOESN'T WORK?
-========================
-
-If nothing works and you start to think "who wrote this pile of trash"
-then I suggest you do step 2 again (and again) till you calm down.
-
-Then you might read the file DIAGNOSIS.txt and the FAQ. If you are
-still stuck then try the mailing list or newsgroup (look in the README
-for details). Samba has been successfully installed at thousands of
-sites worldwide, so maybe someone else has hit your problem and has
-overcome it. You could also use the WWW site to scan back issues of
-the samba-digest.
-
-When you fix the problem PLEASE send me some updates to the
-documentation (or source code) so that the next person will find it
-easier.
-
-DIAGNOSING PROBLEMS
-===================
-
-If you have instalation problems then go to DIAGNOSIS.txt to try to
-find the problem.
-
-SCOPE IDs
-=========
-
-By default Samba uses a blank scope ID. This means all your windows
-boxes must also have a blank scope ID. If you really want to use a
-non-blank scope ID then you will need to use the -i option to
-nmbd, smbd, and smbclient. All your PCs will need to have the same
-setting for this to work. I do not recommend scope IDs.
-
-
-CHOOSING THE PROTOCOL LEVEL
-===========================
-
-The SMB protocol has many dialects. Currently Samba supports 5, called
-CORE, COREPLUS, LANMAN1, LANMAN2 and NT1.
-
-You can choose what maximum protocol to support in the smb.conf
-file. The default is NT1 and that is the best for the vast majority of
-sites.
-
-In older versions of Samba you may have found it necessary to use
-COREPLUS. The limitations that led to this have mostly been fixed. It
-is now less likely that you will want to use less than LANMAN1. The
-only remaining advantage of COREPLUS is that for some obscure reason
-WfWg preserves the case of passwords in this protocol, whereas under
-LANMAN1, LANMAN2 or NT1 it uppercases all passwords before sending them,
-forcing you to use the "password level=" option in some cases.
-
-The main advantage of LANMAN2 and NT1 is support for long filenames with some
-clients (eg: smbclient, Windows NT or Win95).
-
-See the smb.conf manual page for more details.
-
-Note: To support print queue reporting you may find that you have to
-use TCP/IP as the default protocol under WfWg. For some reason if you
-leave Netbeui as the default it may break the print queue reporting on
-some systems. It is presumably a WfWg bug.
-
-
-PRINTING FROM UNIX TO A CLIENT PC
-=================================
-
-To use a printer that is available via a smb-based server from a unix
-host you will need to compile the smbclient program. You then need to
-install the script "smbprint". Read the instruction in smbprint for
-more details.
-
-There is also a SYSV style script that does much the same thing called
-smbprint.sysv. It contains instructions.
-
-
-LOCKING
-=======
-
-One area which sometimes causes trouble is locking.
-
-There are two types of locking which need to be performed by a SMB
-server. The first is "record locking" which allows a client to lock a
-range of bytes in a open file. The second is the "deny modes" that are
-specified when a file is open.
-
-Samba supports "record locking" using the fcntl() unix system
-call. This is often implemented using rpc calls to a rpc.lockd process
-running on the system that owns the filesystem. Unfortunately many
-rpc.lockd implementations are very buggy, particularly when made to
-talk to versions from other vendors. It is not uncommon for the
-rpc.lockd to crash.
-
-There is also a problem translating the 32 bit lock requests generated
-by PC clients to 31 bit requests supported by most
-unixes. Unfortunately many PC applications (typically OLE2
-applications) use byte ranges with the top bit set as semaphore
-sets. Samba attempts translation to support these types of
-applications, and the translation has proved to be quite successful.
-
-Strictly a SMB server should check for locks before every read and
-write call on a file. Unfortunately with the way fcntl() works this
-can be slow and may overstress the rpc.lockd. It is also almost always
-unnecessary as clients are supposed to independently make locking
-calls before reads and writes anyway if locking is important to
-them. By default Samba only makes locking calls when explicitly asked
-to by a client, but if you set "strict locking = yes" then it will
-make lock checking calls on every read and write.
-
-You can also disable by range locking completely using "locking =
-no". This is useful for those shares that don't support locking or
-don't need it (such as cdroms). In this case Samba fakes the return
-codes of locking calls to tell clients that everything is OK.
-
-The second class of locking is the "deny modes". These are set by an
-application when it opens a file to determine what types of access
-should be allowed simultaneously with it's open. A client may ask for
-DENY_NONE, DENY_READ, DENY_WRITE or DENY_ALL. There are also special
-compatability modes called DENY_FCB and DENY_DOS.
-
-You can disable share modes using "share modes = no". This may be
-useful on a heavily loaded server as the share modes code is very
-slow. See also the FAST_SHARE_MODES option in the Makefile for a way
-to do full share modes very fast using shared memory (if your OS
-supports it).
-
-
-MAPPING USERNAMES
-=================
-
-If you have different usernames on the PCs and the unix server then
-take a look at the "username map" option. See the smb.conf man page
-for details.
-
-
-OTHER CHARACTER SETS
-====================
-
-If you have problems using filenames with accented characters in them
-(like the German, French or Scandinavian character sets) then I
-recommmend you look at the "valid chars" option in smb.conf and also
-take a look at the validchars package in the examples directory.
diff --git a/docs/MIRRORS b/docs/MIRRORS
deleted file mode 100644
index a055860e999..00000000000
--- a/docs/MIRRORS
+++ /dev/null
@@ -1,33 +0,0 @@
-The main Samba ftp site is samba.anu.edu.au in pub/samba/. Contact
-samba-bugs@samba.anu.edu.au for help with this site.
-
-Mirror sites include:
-
-ftp://nimbus.anu.edu.au/pub/tridge/samba
-ftp://sunsite.auc.dk/pub/unix/networking/samba/
-ftp://src.doc.ic.ac.uk/packages/samba/
-ftp://choc.satech.net.au/pub/samba/
-ftp://ftp.uni-trier.de/pub/unix/network/samba/
-ftp://sunsite.mff.cuni.cz/Net/Protocols/Samba/
-ftp://ring.aist.go.jp/archives/net/samba/
-ftp://ring.asahi-net.or.jp/archives/net/samba/
-ftp://ftp.cs.ucr.edu/pub/software/samba
-ftp://ftp.ua.pt/pub/misc/samba/
-ftp://sunsite.unc.edu/pub/Linux/system/Network/samba/
-
-There are several others. Give archie a try.
-
-SCO binaries available from:
-ftp://ftp.markv.com/pub/samba (built by lance@fox.com)
-
-AIX and DEC OSF/1 binaries are available from:
-ftp://151.99.220.5/pub/samba (built by davide.migliavacca@inferentia.inet.it)
-
-QNX binaries and source code:
-ftp://quics.qnx.com/usr/free/staging/samba
-
-Http sites include:
-
-http://samba.canberra.edu.au/pub/samba
-http://www.choc.satech.net.au/pub/samba/
-
diff --git a/docs/OS2.txt b/docs/OS2.txt
deleted file mode 100644
index d5703044a67..00000000000
--- a/docs/OS2.txt
+++ /dev/null
@@ -1,59 +0,0 @@
-Author: riiber@oslonett.no
-Date: Unknown
-Status: Unspecified Currency - feedback welcomed
-
-Subject: This describes how to use smbclient to connect to an OS/2 server.
- Knowing this allows you to use a OS/2 printer from unix.
-==============================================================================
-
-How to login to an OS/2 server
--------------------------------
-
-Sample setup for OS/2 server running LanMan 2.2:
-
- OS/2 Server Name : \\OBV11
- OS/2 User Account : ARNE
- OS/2 Password : xxx
- OS/2 shared service 1 : LASER02
- OS/2 Shared service 2 : PCPROGS
- Samba NetBIOS name : KLATREMUS
-
-First, the two servers were started with the commands
-smbd and nmbd -n KLATREMUS.
-
-Command to connect to a the shared printer LASER02 on the OS/2 server:
-
- smbclient '\\OBV11\LASER02' xxx -n ARNE -U ARNE -P
-
-and to connect to the shared drive 'PCPROGS':
-
- smbclient '\\OBV11\PCPROGS' xxx -n ARNE -U ARNE
-
-
-If login to the OS/2 server fails:
-----------------------------------
-
-The remarkable OS/2 server requires NetBIOS name to be equal to User name.
-This was the only combination of (NetBIOS name, User name) that allowed login.
-
-Password xxx must be in upper case, case in user name is unimportant.
-
-The OS/2 server responds with "Bad password - name/password pair"
-if the password is illegal (in lowercase, for example).
-
-If correct user name and password, but invalid NetBIOS name is given,
-it responds with "... SMBtcon failed. ERRDOS - 65".
-
-The OS/2 server can disable login from a list of workstations (PCs)
-corresponding to the NetBIOS name (-n option). I set it up to
-allow login from any workstation.
-
-
-
-(I experimented quite a lot with the -U and -n options, printed and browsed
-the MS SMB protocol docs and the RFC's, then read some comp.protocols.smb,
-got some tips, tried some "stupid" command line options,
-and at last I got it working!)
-
--Arne-
-
diff --git a/docs/README.OS2 b/docs/README.OS2
deleted file mode 100644
index ff98403d72b..00000000000
--- a/docs/README.OS2
+++ /dev/null
@@ -1,87 +0,0 @@
-Contributor: Jason Rumney .
-Date: 1995
-Status: Needs Updating - Old!
-
-Subject: IBM OS/2 Support
-=============================================================================
-
-
-Samba 1.9.15p8 for OS/2 : REQUIRES emx 0.9b.
-
-Please read the file README, which contains general information about
-the configuration and use of Samba.
-
-Notes specific to OS/2 port:
-============================
-
-Filenames have been shortened to 8.3 in case anyone is using FAT.
-Files affected are:
-smb.conf -> smb.cfg smbclient -> smbclnt.exe
-smbstatus -> smbstat.exe nmblookup -> nmblook.exe
-
-As I only use HPFS, I can't guarantee this will work on FAT systems,
-although I have tried to stick to 8.3 filenames. I have noticed some
-temporary files being created with long filenames by smbd when I tried
-printing (which does not work yet anyway). nmbd will not be able to
-create browse lists on FAT systems, as it uses temporary files with
-long file names.
-
-smb.cfg should be in the directory smbd is started from. The path to
-smb.cfg is a compile time option, so if you are compiling from source
-you can set this to an absolute path to remove this restriction.
-
-User home directories not supported. This doesn't make much sense on
-OS/2. I haven't actually disabled anything, so if you try setting
-this up, behaivour is undefined.
-
-Password support is incomplete (I have found a crypt() routine, but
-lack of passwd file support in the EMX libraries make support difficult
-without major changes).
-
-Printing does not appear to be working. OS/2's lpq gives output in a
-different format than the versions of lpq already supported by samba.
-This will be easy to accomodate, but there is not much point until I can
-get lpr working properly.
-
-
-
-Source is available from the Samba WWW site :
-
-http://samba.canberra.edu.au/pub/samba/
-
-EMX 0.9b is available from hobbes.nmsu.edu, ftp.cdrom.com, ftp.leo.org and
-other OS/2 FTP sites. emxrt.zip contains the required libraries.
-
-Bugs:
-=====
-
-Known problems:
-===============
-
-Printing does not work. I have tried using REXX scripts with path info
-built in, and watched the processes startup properly but nothing comes
-out of the printer (remote via lpr in this case).
-If you can get it going, please let me know how you did it.
-
-The output from OS/2's lpq.exe is not understood by smbd, so all querys
-about the print queue say it is empty. Printing doesn't work anyway,
-so I have not attempted to fix this yet.
-
-Temporary files are created with long filenames (when printing, and updating
-browse list)
-
-Bug reports for the OS/2 port should be sent to Jason Rumney .
-
-Change log:
-===========
-
-Changes from release 1 to release 2.
-
-nmblookup (nmblook.exe) is included, and works.
-
-An attempt at password support was made using the gnuufc crypt routines,
-but then I found that a lot of functions in the EMX libraries to do with
-passwd files don't actually do anything.
-
-Browse lists should now work if you use HPFS and set your lock directory
-to an absolute pathname.
diff --git a/docs/THANKS b/docs/THANKS
deleted file mode 100644
index 19c11dc432f..00000000000
--- a/docs/THANKS
+++ /dev/null
@@ -1,137 +0,0 @@
-=====================================================================
-This file is for thanks to individuals or organisations who have
-helped with the development of Samba, other than by coding or bug
-reports. Their contributions are gratefully acknowledged.
-
-Please refer to the manual pages and change-log for a list of those
-who have contributed in the form of patches, bug fixes or other
-direct changes to the package.
-
-Contributions of any kind are welcomed. If you want to help then
-please contact Andrew.Tridgell@anu.edu.au, or via normal mail at
-
- Andrew Tridgell
- 3 Ballow Crescent
- Macgregor, A.C.T
- 2615 Australia
-=====================================================================
-
-
-Lee Fisher (leefi@microsoft.com)
-Charles Fox (cfox@microsoft.com)
-Dan Perry (danp@exchnge.microsoft.com)
-Paul Leach (paulle@microsoft.com)
-Isaac Heizer (isaache@microsoft.com)
-
- These Microsoft people have been very helpful and supportive of
- the development of Samba over some years.
-
- Lee very kindly supplied me with a copy of the X/Open SMB
- specs. These have been invaluable in getting the details of the
- implementation right. They will become even more important as we move
- towards a Lanman 2.1 compliant server. Lee has provided very
- useful advice on several aspects of the server.
- Lee has also provided me with copies of Windows NTAS 3.1, Visual C
- and a developers CD-ROM. Being able to run NT at home is a
- great help.
-
- Charles has helped out in numerous ways with the provision of SMB
- specifications and helpful advice. He has been following the
- discussion of Samba on the mailing list and has stepped in
- regularly to clarify points and to offer help.
-
- Dan has put me in touch with NT developers to help sort out bugs and
- compatability issues. He has also supplied me with a copy of the
- NT browsing spec, which will help a lot in the development of the
- Samba browser code.
-
- Paul was responsible for Microsoft paying my flight to Seattle for the
- first CIFS conference (see http://samba.anu.edu.au/cifs) and has been
- generally helpful and cooperative as the SMB community moves towards
- an Internet-ready specification. Isaac has regularly provided help on
- the behaviour of NT networks.
-
-Bruce Perens (bruce@pixar.com)
-
- In appreciation of his effort on Samba we have sent Andrew copies of
- various Pixar computer-graphics software products. Pixar is best known
- for its "Renderman" product, the 3-D renderer used by ILM to make special
- effects for "Terminator II" and "Jurassic Park". We won the first Oscar
- given to a computer graphic animated feature for our short film "Tin Toy".
- Our retail products "Typestry" and "Showplace", incorporate the same
- renderer used on the films, and are available on Windows and the
- Macintosh.
-
-
-
-Henry Lee (hyl@microplex.co)
-
- Henry sent me a M202 ethernet print server, making my little lan
- one of the few home networks to have it's own print server!
-
- ``Microplex Systems Ltd. is a manufacturer of local and wide area
- network communications equipment based in beautiful Vancouver, British
- Columbia, Canada. Microplex's first products were synchronous wide
- area network devices used in the mainframe communication networks. In
- August 1991 Microplex introduced its first LAN product, the M200 print
- server, the first high performance print server under US$1,000.''
-
-
-Tom Haapanen (tomh@metrics.com)
-
- Tom sent me two 16 bit SMC ethernet cards to replace my ancient 8
- bit ones. The performance is much better!
-
- Software Metrics Inc. is a small custom software development and
- consulting firm located in Waterloo, Ontario, Canada. We work
- with a variety of environments (such as Windows, Windows NT and
- Unix), tools and application areas, and can provide assistance for
- development work ranging from a few days to to multiple man-year
- projects. You can find more information at http://www.metrics.com/.
-
-
-Steve Kennedy (steve@gbnet.net)
-
- Steve sent me 16Mb of ram so that I could install/test
- NT3.5. I previous had only 8Mb ram in my test machine, which
- wasn't enough to install a properly functioning copy of
- NTAS. Being able to directly test NT3.5 allowed me to solve
- several long standing NT<->Samba problems. Thanks Steve!
-
-John Terpstra (jht@aquasoft.com.au)
-
- Aquasoft are a specialist consulting company whose Samba-using
- customers span the world.
-
- Aquasoft have been avid supporters of the Samba project. As a
- token of appreciation Aquasoft have donated a 486DX2/66 PC with
- a 540MB EIDE drive and 20MB RAM.
-
- John has helped to isolate quite a few little glitches over time
- and has managed to implement some very interesting installations
- of Samba.
-
- The donation of the new PC will make it possible to more fully
- diagnose and observe the behaviour of Samba in conjuction with
- other SMB protocol utilising systems.
-
-
-Timothy F. Sipples (tsipple@vnet.IBM.COM)
-Steve Withers (swithers@vnet.IBM.COM)
-
- Tim and Steve from IBM organised a copy of the OS/2 developers
- connection CD set for me, and gave lots of help in getting
- OS/2 Warp installed. I hope this will allow me to finally fix
- up those annoying OS/2 related Samba bugs that I have been
- receiving reports of.
-
-Keith Wilkins (wilki1k@nectech.co.uk)
-
- Keith from NEC in England very generously supplied a PC to
- Luke Leighton to help with his nmbd development work. At the
- same time Keith offered to help me with some new hardware, and
- he sent me a pentium motherboard with 32MB of ram
- onboard. This was very helpful as it allowed me to upgrade
- my aging server to be a very powerful system. Thanks!
-
-
diff --git a/docs/Warp.txt b/docs/Warp.txt
deleted file mode 100644
index 8818443a484..00000000000
--- a/docs/Warp.txt
+++ /dev/null
@@ -1,103 +0,0 @@
-Contributor: Wade Maxfie
-Date: Unknown
-Status: Old
-
-Subject: Samba with OS/2 Warp.
-============================================================================
-
-Note that you may also find ftp://ftp.cdrom.com/pub/os2/new/os2net.faq
-useful.
-
-
-
- Can I use Samba with Warp?
-
- Yes. The MSClient software at ftp.microsoft.com in the Bussys
-(lanman os2 directory) will work, sort of. It is version 2.2c.
-
- First, uncloack os2ver. (attrib -h -r -s c:\os2ver). It is a
-text file. change netwksta.xxx to 20=netwksta.sys. Also add
-20=setup.exe. Another change will be needed, a .vdd file. I remember
-it came up during the installation as being a wrong version. I wrote
-the name down, changed os2ver to include it, and restarted the
-installation.
-
- Here is a copy of my os2ver
-
-setup.exe
-netbios.os2
-nwifs.ifs
-netwksta.sys
-nwreq.sys
-netbios.sys
-ipx.sys
-netvdd.sys
-
-Re-cloak os2ver. (attrib +h +r +s c:\os2ver)
-
-Run the installation from an OS/2 Box. Note that your mouse wont work,
-use the TAB key to move around, enter to select hilighted items.
-
-Here is a copy of my Config.sys file regarding the Laman entries.
-Note even though the version is 2.2c, it reports 2.2a in the text.
-
-REM ==== LANMAN 2.2a == DO NOT MODIFY BETWEEN THESE LINES == LANMAN 2.
-DEVICE=C:\LANMAN\DRIVERS\PROTMAN\PROTMAN.OS2 /i:C:\LANMAN
-DEVICE=C:\LANMAN\DRIVERS\ETHERNET\Ns2000\Ns2000.OS2
-RUN=C:\LANMAN\DRIVERS\PROTOCOL\tcpip\starttcp.exe
-RUN=C:\LANMAN\DRIVERS\PROTOCOL\tcpip\startnb.exe
-DEVICE=C:\LANMAN\DRIVERS\PROTOCOL\tcpip\tcpdrv.os2
-DEVICE=C:\LANMAN\DRIVERS\PROTOCOL\tcpip\nbdrv.os2
-DEVICE=C:\LANMAN\DRIVERS\PROTOCOL\tcpip\nmdrv.os2
-DEVICE=C:\LANMAN\arpa\sockdrv.os2
-DEVICE=C:\LANMAN\DRIVERS\PROTOCOL\NETBEUI\NETBEUI.OS2
-DEVICE=C:\LANMAN\NETPROG\RDRHELP.SYS
-IFS=C:\LANMAN\NETPROG\NETWKSTA.SYS /i:C:\LANMAN
-DEVICE=C:\LANMAN\NETPROG\NETVDD.SYS
-REM ==== LANMAN 2.2a == DO NOT MODIFY BETWEEN THESE LINES == LANMAN 2.
-
-
- If you have an NE2000 card, don't reboot, or you'll be sorry.
-enable the automatic backup mechanism for recovering old config.sys and
-other files in OS/2. It paid for itself during this installation nightm
-before I knew better!)
-
- Next, (or perhaps before this), if you have an NE2000 adaptor,
-get the ns2000 files from hobbes.nmsu.edu (in ns2000.zip). I manually
-patched protocol.ini to refer to that adaptor, and copied it into my
-c:\lanman directory. Note that I also modified the driver to be loaded
-in the config.sys to the ns2000.os2. It might install as an "other"
-adaptor.
-
- A command file "startup.cmd" is placed in c:\. This file is
-automatically run when OS/2 Warp starts.
-Here is a copy of my startup file. Note that Warp sometimes fails to
-login properly to the server. I solve this by checking for the
-existance of a file, and rerunning the loing if that file fails to
-exist.
-
-@REM ==== LANMAN 2.2a == DO NOT MODIFY BETWEEN THESE LINES == LANMAN
-NET START WORKSTATION
-:relogin
-NET LOGON maxfield mypassword /y
-rem net use f: \\packard90\d$
-rem net use g: \\linuxone\cdromsdir
-rem net use h: \\linuxone\public
-:doOver
-if not exist f:\wildcat\wildcat.exe goto relogin
-@REM ==== LANMAN 2.2a == DO NOT MODIFY BETWEEN THESE LINES == LANMAN
-exit
-
- Finally, the system expects to be on a domain with a domain
-server. BTW, TCP/IP and NetBeui allow simultaneous communication with
-Os/2 lanserver 4.0, and Samba. (Note: Lanserver 4.0 won't yet to
-TCP/IP. (Well,it might, but it crashes before I get to that point, so I
-havent' been able to enable it))
-
-I have not yet tried with only a SAMBA server on the domain.
-
- I would be glad to try to answer any questions at above e-mail
-address, if I can.
-
-wade
-
diff --git a/docs/announce b/docs/announce
deleted file mode 100644
index 18e34b68c2b..00000000000
--- a/docs/announce
+++ /dev/null
@@ -1,133 +0,0 @@
- Announcing Samba version 1.9
- ============================
-
-What is Samba?
---------------
-
-Samba is a SMB file server that runs on Unix and other operating systems.
-It allows these operating systems (currently Unix, Netware, OS/2 and
-AmigaDOS) to act as a file and print server for SMB clients. There are many
-Lan-Manager compatible clients such as LanManager for DOS, Windows for
-Workgroups, Windows NT, Windows 95, OS/2, Pathworks and many more.
-
-The package also includes a SMB client for accessing other SMB servers
-and a netbios nameserver for browsing support.
-
-What can it do for me?
-----------------------
-
-If you have any PCs running SMB clients, such as a PC running Windows
-for Workgroups, then you can mount file space or printers on a Samba
-host, so that directories, files and printers on the host are
-available on the PC.
-
-The client part of the package will also allow you to attach to other
-SMB-based servers (such as windows NT and windows for workgroups) so
-that you can copy files to and from your unix host. The client also
-allows you to access a SMB printer (such as one attached to an OS/2 or
-WfWg server) from Unix, using an entry in /etc/printcap, or by
-explicitly specifying the command used to print files.
-
-What are it's features?
-------------------------
-
-Samba supports many features that are not supported in other SMB
-implementations (all of which are commercial). Some of it's features
-include host as well as username/password security, a client,
-automatic home directory exporting, automatic printer exporting, dead
-connection timeouts, umask support, guest connections, name mangling
-and hidden and system attribute mapping. Look at the man pages
-included with the package for a full list of features.
-
-What's new since 1.8?
----------------------
-
-Lots of stuff. See the change log and man pages for details.
-
-Where can I get a client for my PC?
------------------------------------
-
-There is a free client for MS-DOS based PCs available from
-ftp.microsoft.com in the directory bussys/Clients/MSCLIENT/. Please
-read the licencing information before downloading. The built in
-Windows for Workgroups client is also very good.
-
-What network protocols are supported?
--------------------------------------
-
-Currently only TCP/IP is supported. There has been some discussion
-about ports to other protocols but nothing is yet available.
-
-There is a free TCP/IP implementation for Windows for Workgroups
-available from ftp.microsoft.com (it's small, fast and quite reliable).
-
-How much does it cost?
-----------------------
-
-Samba software is free software. It is available under the
-GNU Public licence in source code form at no cost. Please read the
-file COPYING that comes with the package for more information.
-
-What operating systems does it support?
----------------------------------------
-
-The code has been written to be as portable as possible. It has been
-"ported" to many unixes, which mostly required changing only a few
-lines of code. It has been run (to my knowledge) on at least these
-unixes:
-
-Linux, SunOS, Solaris, SVR4, Ultrix, OSF1, AIX, BSDI, NetBSD,
-Sequent, HP-UX, SGI, FreeBSD, NeXT, ISC, A/UX, SCO, Intergraph,
-Silicon Graphics Inc., Domain/OS and DGUX.
-
-Some of these have received more testing than others. If it doesn't
-work with your unix then it should be easy to fix. It has also been ported
-to Netware, OS/2 and the Amiga. A VMS port is available too. See the web site
-for more details.
-
-Who wrote it?
--------------
-
-Many people on the internet have contributed to the development of
-Samba. The maintainer and original author is Andrew Tridgell, but
-large parts of the package were contributed by several people from all
-over the world. Please look at the file `change-log' for information
-on who did what bits.
-
-Where can I get it?
--------------------
-
-The package is available via anonymous ftp from samba.anu.edu.au in
-the directory pub/samba/.
-
-What about SMBServer?
----------------------
-
-Samba used to be known as SMBServer, until it was pointed out that
-Syntax, who make a commercial Unix SMB based server, have trademarked
-that name. The name was then changed to Samba. Also, in 1992 a very
-early incarnation of Samba was distributed as nbserver.
-
-If you see any copies of nbserver or smbserver on ftp sites please let
-me or the ftp archive maintainer know, as I want to get them deleted.
-
-Where can I get more info?
----------------------------
-
-Please join the mailing list if you want to discuss the development or
-use of Samba. To join the mailing list send mail to
-listproc@listproc.anu.edu.au with a body of "subscribe samba Your
-Name".
-
-There is also an announcement mailing list for new version
-announcements. Subscribe as above but with "subscribe samba-announce
-Your Name".
-
-There is also often quite a bit of discussion about Samba on the
-newsgroup comp.protocols.smb.
-
-A WWW site with lots of Samba info can be found at
-http://samba.canberra.edu.au/pub/samba/
-
-The Samba Team (Contact: samba-bugs@samba.anu.edu.au)
-June 1996
diff --git a/docs/faq/sambafaq-1.html b/docs/faq/sambafaq-1.html
deleted file mode 100644
index 4b9e589e843..00000000000
--- a/docs/faq/sambafaq-1.html
+++ /dev/null
@@ -1,392 +0,0 @@
-
-
- Samba FAQ: General Information
-
-
-Previous
-Next
-Table of Contents
-
-
-
-
-Samba is a suite of programs which work together to allow clients to
-access to a server's filespace and printers via the SMB (Server
-Message Block) protocol. Initially written for Unix, Samba now also
-runs on Netware, OS/2 and VMS.
-
In practice, this means that you can redirect disks and printers to
-Unix disks and printers from Lan Manager clients, Windows for
-Workgroups 3.11 clients, Windows NT clients, Linux clients and OS/2
-clients. There is also a generic Unix client program supplied as part
-of the suite which allows Unix users to use an ftp-like interface to
-access filespace and printers on any other SMB servers. This gives the
-capability for these operating systems to behave much like a LAN
-Server or Windows NT Server machine, only with added functionality and
-flexibility designed to make life easier for administrators.
-
The components of the suite are (in summary):
-
-
-
smbd, the SMB server. This handles actual connections from clients, doing all the file, permission and username work
-
nmbd, the Netbios name server, which helps clients locate servers, doing the browsing work and managing domains as this capability is being built into Samba
-
smbclient, the Unix-hosted client program
-
smbrun, a little 'glue' program to help the server run external programs
-
testprns, a program to test server access to printers
-
testparms, a program to test the Samba configuration file for correctness
-
smb.conf, the Samba configuration file
-
smbprint, a sample script to allow a Unix host to use smbclient to print to an SMB server
-
Documentation! DON'T neglect to read it - you will save a great deal of time!
-
-
-
The suite is supplied with full source (of course!) and is GPLed.
-
The primary creator of the Samba suite is Andrew Tridgell. Later
-versions incorporate much effort by many net.helpers. The man pages
-and this FAQ were originally written by Karl Auer.
-
-
-The Samba suite is available via anonymous ftp from
-samba.anu.edu.au. The latest and greatest versions of the suite are in
-the directory:
-
/pub/samba/
-
Development (read "alpha") versions, which are NOT necessarily stable
-and which do NOT necessarily have accurate documentation, are
-available in the directory:
-
/pub/samba/alpha
-
Note that binaries are NOT included in any of the above. Samba is
-distributed ONLY in source form, though binaries may be available from
-other sites. Recent versions of some Linux distributions, for example,
-do contain Samba binaries for that platform.
-
-
-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
-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
-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
-are just looking for the latest version to install.
-
-
When Andrew 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.
-
-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.
-
-
-
Links to man pages and documentation, including this FAQ
-
A comprehensive survey of Samba users.
-
A searchable hypertext archive of the Samba mailing list.
-
Links to Samba source code, binaries, and mirrors of both.
-
-
-
The long list of topic documentation. These files can be found in the 'docs' directory of the Samba source, or at
-ftp://samba.anu.edu.au/pub/samba/docs/
-
-
-Obviously you should substitute YOUR first name for "Firstname" and
-YOUR last name for "Lastname"! Try not to send any signature stuff, it
-sometimes confuses the list processor.
-
The samba list is a digest list - every eight hours or so it
-regurgitates a single message containing all the messages that have
-been received by the list since the last time and sends a copy of this
-message to all subscribers.
-
If you stop being interested in Samba, please send another email to
-listproc@samba.anu.edu.au. Make sure the subject line is blank, and
-include the following two lines in the body of the message:
-
-
-unsubscribe samba
-unsubscribe samba-announce
-
-
-
-The From: line in your message MUST be the same address you used when
-you subscribed.
-
-
-
DO NOT post messages on mailing lists or in newsgroups until you have
-carried out the first three steps given here!
-
Firstly, see if there are any likely looking entries in this FAQ! If
-you have just installed Samba, have you run through the checklist in
-DIAGNOSIS.txt? It can save you a lot of time and effort.
-DIAGNOSIS.txt can also be found in the docs directory of the Samba distribution.
-
Secondly, read the man pages for smbd, nmbd and smb.conf, looking for
-topics that relate to what you are trying to do.
-
Thirdly, if there is no obvious solution to hand, try to get a look at
-the log files for smbd and/or nmbd for the period during which you
-were having problems. You may need to reconfigure the servers to
-provide more extensive debugging information - usually level 2 or
-level 3 provide ample debugging info. Inspect these logs closely,
-looking particularly for the string "Error:".
-
Fourthly, if you still haven't got anywhere, ask the mailing list or
-newsgroup. In general nobody minds answering questions provided you
-have followed the preceding steps. It might be a good idea to scan the
-archives of the mailing list, which are available through the Samba
-web site described in the previous
-section.
-
If you successfully solve a problem, please mail the FAQ maintainer a
-succinct description of the symptom, the problem and the solution, so
-I can incorporate it in the next version.
-
If you make changes to the source code, _please_ submit these patches
-so that everyone else gets the benefit of your work. This is one of
-the most important aspects to the maintainence of Samba. Send all
-patches to
-samba-bugs@samba.anu.edu.au. Do not send patches to Andrew Tridgell or any
-other individual, they may be lost if you do.
-
-
-Those who have registered in the Samba survey as "Pizza Factory" will
-already know this, but the rest may need some help. Andrew doesn't ask
-for payment, but he does appreciate it when people give him
-pizza. This calls for a little organisation when the pizza donor is
-twenty thousand kilometres away, but it has been done.
-
Method 1: Ring up your local branch of an international pizza chain
-and see if they honour their vouchers internationally. Pizza Hut do,
-which is how the entire Canberra Linux Users Group got to eat pizza
-one night, courtesy of someone in the US
-
Method 2: Ring up a local pizza shop in Canberra and quote a credit
-card number for a certain amount, and tell them that Andrew will be
-collecting it (don't forget to tell him.) One kind soul from Germany
-did this.
-
Method 3: Purchase a pizza voucher from your local pizza shop that has
-no international affiliations and send it to Andrew. It is completely
-useless but he can hang it on the wall next to the one he already has
-from Germany :-)
-
Method 4: Air freight him a pizza with your favourite regional
-flavours. It will probably get stuck in customs or torn apart by
-hungry sniffer dogs but it will have been a noble gesture.
-
-
-
-Previous
-Next
-Table of Contents
-
-
diff --git a/docs/faq/sambafaq-2.html b/docs/faq/sambafaq-2.html
deleted file mode 100644
index 38fec3d2c4b..00000000000
--- a/docs/faq/sambafaq-2.html
+++ /dev/null
@@ -1,239 +0,0 @@
-
-
- Samba FAQ: Compiling and installing Samba on a Unix host
-
-
-Previous
-Next
-Table of Contents
-
-
-
-
-See
-BROWSING.txt
-for more information on browsing. Browsing.txt can also be found
-in the docs directory of the Samba source.
-
If your GUI client does not permit you to select non-browsable
-servers, you may need to do so on the command line. For example, under
-Lan Manager you might connect to the above service as disk drive M:
-thusly:
-
-
- net use M: \\mary\fred
-
-
-
-The details of how to do this and the specific syntax varies from
-client to client - check your client's documentation.
-
-
-
-
-
-If you check what files are not showing up, you will note that they
-are files which contain upper case letters or which are otherwise not
-DOS-compatible (ie, they are not legal DOS filenames for some reason).
-
The Samba server can be configured either to ignore such files
-completely, or to present them to the client in "mangled" form. If you
-are not seeing the files at all, the Samba server has most likely been
-configured to ignore them. Consult the man page smb.conf(5) for
-details of how to change this - the parameter you need to set is
-"mangled names = yes".
-
-
-This indicates one of three things: You supplied an incorrect server
-name, the underlying TCP/IP layer is not working correctly, or the
-name you specified cannot be resolved.
-
After carefully checking that the name you typed is the name you
-should have typed, try doing things like pinging a host or telnetting
-to somewhere on your network to see if TCP/IP is functioning OK. If it
-is, the problem is most likely name resolution.
-
If your client has a facility to do so, hardcode a mapping between the
-hosts IP and the name you want to use. For example, with Man Manager
-or Windows for Workgroups you would put a suitable entry in the file
-LMHOSTS. If this works, the problem is in the communication between
-your client and the netbios name server. If it does not work, then
-there is something fundamental wrong with your naming and the solution
-is beyond the scope of this document.
-
If you do not have any server on your subnet supplying netbios name
-resolution, hardcoded mappings are your only option. If you DO have a
-netbios name server running (such as the Samba suite's nmbd program),
-the problem probably lies in the way it is set up. Refer to Section
-Two of this FAQ for more ideas.
-
By the way, remember to REMOVE the hardcoded mapping before further
-tests :-)
-
-
-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.
-
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 doco 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.
-
-
-Nothing is wrong - Samba does not implement the primary domain name
-controller stuff for several reasons, including the fact that the
-whole concept of a primary domain controller and "logging in to a
-network" doesn't fit well with clients possibly running on multiuser
-machines (such as users of smbclient under Unix). Having said that,
-several developers are working hard on building it in to the next
-major version of Samba. If you can contribute, send a message to
-samba-bugs@anu.edu.au !
-
Seeing this message should not affect your ability to mount redirected
-disks and printers, which is really what all this is about.
-
For many clients (including Windows for Workgroups and Lan Manager),
-setting the domain to STANDALONE at least gets rid of the message.
-
-
-Make sure that the specified print command for the service you are
-connecting to is correct and that it has a fully-qualified path (eg.,
-use "/usr/bin/lpr" rather than just "lpr").
-
Make sure that the spool directory specified for the service is
-writable by the user connected to the service. In particular the user
-"nobody" often has problems with printing, even if it worked with an
-earlier version of Samba. Try creating another guest user other than
-"nobody".
-
Make sure that the user specified in the service is permitted to use
-the printer.
-
Check the debug log produced by smbd. Search for the printer name and
-see if the log turns up any clues. Note that error messages to do with
-a service ipc$ are meaningless - they relate to the way the client
-attempts to retrieve status information when using the LANMAN1
-protocol.
-
If using WfWg then you need to set the default protocol to TCP/IP, not
-Netbeui. This is a WfWg bug.
-
If using the Lanman1 protocol (the default) then try switching to
-coreplus. Also not that print status error messages don't mean
-printing won't work. The print status is received by a different
-mechanism.
-
-
-There are numerous possible reasons for this, but one MAJOR
-possibility is that your software uses locking. Make sure you are
-using Samba 1.6.11 or later. It may also be possible to work around
-the problem by setting "locking=no" in the Samba configuration file
-for the service the software is installed on. This should be regarded
-as a strictly temporary solution.
-
In earlier Samba versions there were some difficulties with the very
-latest Microsoft products, particularly Excel 5 and Word for Windows
-6. These should have all been solved. If not then please let Andrew
-Tridgell know via email at
-samba-bugs@anu.edu.au.
-
-
-Your guest account is probably invalid for some reason. Samba uses the
-guest account for browsing in smbd. Check that your guest account is
-valid.
-
-
-This can have several causes. It might be because you are using a uid
-or gid of 65535 or -1. This is a VERY bad idea, and is a big security
-hole. Check carefully in your /etc/passwd file and make sure that no
-user has uid 65535 or -1. Especially check the "nobody" user, as many
-broken systems are shipped with nobody setup with a uid of 65535.
-
It might also mean that your OS has a trapdoor uid/gid system :-)
-
This means that once a process changes effective uid from root to
-another user it can't go back to root. Unfortunately Samba relies on
-being able to change effective uid from root to non-root and back
-again to implement its security policy. If your OS has a trapdoor uid
-system this won't work, and several things in Samba may break. Less
-things will break if you use user or server level security instead of
-the default share level security, but you may still strike
-problems.
-
The problems don't give rise to any security holes, so don't panic,
-but it does mean some of Samba's capabilities will be unavailable.
-In particular you will not be able to connect to the Samba server as
-two different uids at once. This may happen if you try to print as a
-"guest" while accessing a share as a normal user. It may also affect
-your ability to list the available shares as this is normally done as
-the guest user.
-
Complain to your OS vendor and ask them to fix their system.
-
Note: the reason why 65535 is a VERY bad choice of uid and gid is that
-it casts to -1 as a uid, and the setreuid() system call ignores (with
-no error) uid changes to -1. This means any daemon attempting to run
-as uid 65535 will actually run as root. This is not good!
-
-
-Yes! Thursby now have a CIFS Client / Server called DAVE - see
-http://www.thursby.com/.
-They test it against Windows 95, Windows NT and samba for compatibility issues.
-At the time of writing, DAVE was at version 1.0.1. The 1.0.0 to 1.0.1 update is available
-as a free download from the Thursby web site (the speed of finder copies has
-been greatly enhanced, and there are bug-fixes included).
-
Alternatives - There are two free implementations of AppleTalk for
-several kinds of UNIX machnes, and several more commercial ones.
-These products allow you to run file services and print services
-natively to Macintosh users, with no additional support required on
-the Macintosh. The two free omplementations are Netatalk,
-http://www.umich.edu/~rsug/netatalk/, and CAP,
-http://www.cs.mu.oz.au/appletalk/atalk.html. What Samba offers
-MS Windows users, these packages offer to Macs. For more info on
-these packages, Samba, and Linux (and other UNIX-based systems)
-see
-http://www.eats.com/linux_mac_win.html
-
-
-The following answer is provided by John E. Miller:
-
I'll assume that you're able to ping back and forth between the
-machines by IP address and name, and that you're using some security
-model where you're confident that you've got user IDs and passwords
-right. The logging options (-d3 or greater) can help a lot with that.
-DNS and WINS configuration can also impact connectivity as well.
-
Now, on to 'scope id's. Somewhere in your Win95 TCP/IP network
-configuration (I'm too much of an NT bigot to know where it's located
-in the Win95 setup, but I'll have to learn someday since I teach for a
-Microsoft Solution Provider Authorized Tech Education Center - what an
-acronym...) Note: It's under Control Panel | Network | TCP/IP | WINS
-Configuration there's a little text entry field called something like
-'Scope ID'.
-
This field essentially creates 'invisible' sub-workgroups on the same
-wire. Boxes can only see other boxes whose Scope IDs are set to the
-exact same value - it's sometimes used by OEMs to configure their
-boxes to browse only other boxes from the same vendor and, in most
-environments, this field should be left blank. If you, in fact, have
-something in this box that EXACT value (case-sensitive!) needs to be
-provided to smbclient and nmbd as the -i (lowercase) parameter. So, if
-your Scope ID is configured as the string 'SomeStr' in Win95 then
-you'd have to use smbclient -iSomeStr otherparms in connecting to
-it.
All of the above programs are applications that sit on an NT box and
-allow multiple users to access the NT GUI applications from remote
-workstations (often over X).
-
What has this got to do with Samba? The problem comes when these users
-use filemanager to mount shares from a Samba server. The most common
-symptom is that the first user to connect get correct file permissions
-and has a nice day, but subsequent connections get logged in as the
-same user as the first person to login. They find that they cannot
-access files in their own home directory, but that they can access
-files in the first users home directory (maybe not such a nice day
-after all?)
-
Why does this happen? The above products all share a common heritage
-(and code base I believe). They all open just a single TCP based SMB
-connection to the Samba server, and requests from all users are piped
-over this connection. This is unfortunate, but not fatal.
-
It means that if you run your Samba server in share level security
-(the default) then things will definately break as described
-above. The share level SMB security model has no provision for
-multiple user IDs on the one SMB connection. See
-security_level.txt in
-the docs for more info on share/user/server level security.
-
If you run in user or server level security then you have a chance,
-but only if you have a recent version of Samba (at least 1.9.15p6). In
-older versions bugs in Samba meant you still would have had problems.
-
If you have a trapdoor uid system in your OS then it will never work
-properly. Samba needs to be able to switch uids on the connection and
-it can't if your OS has a trapdoor uid system. You'll know this
-because Samba will note it in your logs.
-
Also note that you should not use the magic "homes" share name with
-products like these, as otherwise all users will end up with the same
-home directory. Use \\server\username instead.
-
-
-This info from Stefan Hergeth
-hergeth@f7axp1.informatik.fh-muenchen.de may be useful:
-
A network-printer (with ethernetcard) is connected to the NT-Clients
-via our UNIX-Fileserver (SAMBA-Server), like the configuration told by
-Matthew Harrell harrell@leech.nrl.navy.mil (see WinNT.txt)
-
-
If a user has choosen this printer as the default printer in his
-NT-Session and this printer is not connected to the network
-(e.g. switched off) than this user has a problem with the SAMBA-
-connection of his filesystems. It's very slow.
-
-
If the printer is connected to the network everything works fine.
-
-
When the smbd ist started with debug level 3, you can see that the
-NT spooling system try to connect to the printer many times. If the
-printer ist not connected to the network this request fails and the
-NT spooler is wasting a lot of time to connect to the printer service.
-This seems to be the reason for the slow network connection.
-
-
Maybe it's possible to change this behaviour by setting different
-printer properties in the Print-Manager-Menu of NT, but i didn't try it yet.
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.
-
-
If possible, use geographical time zone settings
-(e.g. TZ='America/Los_Angeles' or perhaps
-TZ=':US/Pacific'). These are supported by most
-popular Unix OSes, are easier to get right, and are
-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
-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').
-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
-daylight-saving time.
-
-
`Dst' is the daylight-saving time designation
-(e.g. `PDT').
-
-The optional second `Offset' is the number of
-hours that daylight-saving time is behind UTC.
-The default is 1 hour ahead of standard time.
-
-
`Date/Time,Date/Time' specify when daylight-saving
-time starts and ends. The format for a date is
-`Mm.n.d', which specifies the dth day (0 is Sunday)
-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 hh: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
-time zone is also set appropriately. [I don't know how to do this.]
-Samba traditionally has had many problems dealing with time zones, due
-to the bizarre ways that Microsoft network protocols handle time
-zones. A common symptom is for file timestamps to be off by an hour.
-To work around the problem, try disconnecting from your Samba server
-and then reconnecting to it; or upgrade your Samba server to
-1.9.16alpha10 or later.
-
-
-
-
-
-Question:
-On NT, I opened "Printer Manager" and "Connect to Printer".
-Enter "\\ptdi270\ps1" in the box of printer. I got the
-following error message:
-
-
- You do not have sufficient access to your machine
- to connect to the selected printer, since a driver
- needs to be installed locally.
-
-
-
-Answer:
-
In the more recent versions of Samba you can now set the "printer
-driver" in smb.conf. This tells the client what driver to use. For
-example:
-
-
- printer driver = HP LaserJet 4L
-
-
-
-with this, NT knows to use the right driver. You have to get this string
-exactly right.
-
To find the exact string to use, you need to get to the dialog box in
-your client where you select which printer driver to install. The
-correct strings for all the different printers are shown in a listbox
-in that dialog box.
-
You could also try setting the driver to NULL like this:
-
-
- printer driver = NULL
-
-
-
-this is effectively what older versions of Samba did, so if that
-worked for you then give it a go. If this does work then let us know via
-samba-bugs@anu.edu.au,
-and we'll make it the default. Currently the default is a 0 length
-string.
-
-
-
-
-
-As of SP3, Microsoft has decided that they will no longer default to
-passing clear text passwords over the network. To enable access to
-Samba shares from NT 4.0 SP3, you must do ONE of two things:
-
-
Set the Samba configuration option 'security = user' and implement all of the stuff detailed in
-ENCRYPTION.txt.
-
Follow Microsoft's directions for setting your NT box to allow plain text passwords. see
-Knowledge Base Article Q166730
-
-
-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.
-
To get around this problem, do the installation without admin user
-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"
-to fix the owner.
v 0.7, June '97
- This is the Frequently Asked Questions (FAQ) document for
-Samba, the free and very popular SMB server product. An SMB server
-allows file and printer connections from clients such as Windows,
-OS/2, Linux and others. Current to version 1.9.17. Please send any
-corrections to the author.
-
-
-
-
-Previous
-Next
-Table of Contents
-
-
diff --git a/docs/faq/sambafaq.sgml b/docs/faq/sambafaq.sgml
deleted file mode 100644
index df6dd346662..00000000000
--- a/docs/faq/sambafaq.sgml
+++ /dev/null
@@ -1,789 +0,0 @@
-
-
-
-
-
- Samba FAQ
-
-Paul Blackman, ictinus@lake.canberra.edu.au
-
-v 0.7, June '97
-
- This is the Frequently Asked Questions (FAQ) document for
-Samba, the free and very popular SMB server product. An SMB server
-allows file and printer connections from clients such as Windows,
-OS/2, Linux and others. Current to version 1.9.17. Please send any
-corrections to the author.
-
-
-
-
- General Information
diff --git a/docs/faq/sambafaq.txt b/docs/faq/sambafaq.txt
deleted file mode 100644
index 9324df3bdee..00000000000
--- a/docs/faq/sambafaq.txt
+++ /dev/null
@@ -1,1122 +0,0 @@
- Samba FAQ
- Paul Blackman, ictinus@lake.canberra.edu.au
- v 0.7, June '97
-
- This is the Frequently Asked Questions (FAQ) document for Samba, the
- free and very popular SMB server product. An SMB server allows file
- and printer connections from clients such as Windows, OS/2, Linux and
- others. Current to version 1.9.17. Please send any corrections to the
- author.
- ______________________________________________________________________
-
- Table of Contents:
-
- 1. General Information
-
- 1.1. What is Samba?
-
- 1.2. What is the current version of Samba?
-
- 1.3. Where can I get it?
-
- 1.4. What do the version numbers mean?
-
- 1.5. What platforms are supported?
-
- 1.6. How can I find out more about Samba?
-
- 1.7. How do I subscribe to the Samba Mailing Lists?
-
- 1.8. Something's gone wrong - what should I do?
-
- 1.9. Pizza supply details
-
- 2. Compiling and installing Samba on a Unix host
-
- 2.1. I can't see the Samba server in any browse lists!
-
- 2.2. Some files that I KNOW are on the server doesn't show up when
- I view the files from my client!
-
- 2.3. Some files on the server show up with really wierd filenames
- when I view the files from my client!
-
- 2.4. My client reports "cannot locate specified computer" or
- similar
-
- 2.5. My client reports "cannot locate specified share name" or
- similar
-
- 2.6. My client reports "cannot find domain controller", "cannot log
- on to the network" or similar
-
- 2.7. Printing doesn't work :-(
-
- 2.8. My programs install on the server OK, but refuse to work
- properly
-
- 2.9. My "server string" doesn't seem to be recognised
-
- 2.10. My client reports "This server is not configured to list
- shared resources"
-
- 2.11. Log message "you appear to have a trapdoor uid system"
-
- 3. Common client questions
-
- 3.1. Are there any Macintosh clients for Samba?
-
- 3.2. "Session request failed (131,130)" error
-
- 3.3. How do I synchronise my PC's clock with my Samba server?
-
- 3.4. Problems with WinDD, NTrigue, WinCenterPro etc
-
- 3.5. Problem with printers under NT
-
- 3.6. Why are my file's timestamps off by an hour, or by a few
- hours?
-
- 3.7. How do I set the printer driver name correctly?
-
- 3.8. I've applied NT 4.0 SP3, and now I can't access Samba shares,
- Why?
-
- 4. Specific client application problems
-
- 4.1. MS Office Setup reports "Cannot change properties of
- 'MSOFFICEUP.INI'"
-
- 5. Miscellaneous
-
- 5.1. Is Samba Year 2000 compliant?
- ______________________________________________________________________
-
- 1. General Information
-
-
-
- All about Samba - what it is, how to get it, related sources of
- information, how to understand the version numbering scheme, pizza
- details
-
-
- 1.1. What is Samba?
-
-
- Samba is a suite of programs which work together to allow clients to
- access to a server's filespace and printers via the SMB (Server
- Message Block) protocol. Initially written for Unix, Samba now also
- runs on Netware, OS/2 and VMS.
-
- In practice, this means that you can redirect disks and printers to
- Unix disks and printers from Lan Manager clients, Windows for
- Workgroups 3.11 clients, Windows NT clients, Linux clients and OS/2
- clients. There is also a generic Unix client program supplied as part
- of the suite which allows Unix users to use an ftp-like interface to
- access filespace and printers on any other SMB servers. This gives the
- capability for these operating systems to behave much like a LAN
- Server or Windows NT Server machine, only with added functionality and
- flexibility designed to make life easier for administrators.
-
- The components of the suite are (in summary):
-
-
- o smbd, the SMB server. This handles actual connections from clients,
- doing all the file, permission and username work
-
- o nmbd, the Netbios name server, which helps clients locate servers,
- doing the browsing work and managing domains as this capability is
- being built into Samba
-
-
- o smbclient, the Unix-hosted client program
-
- o smbrun, a little 'glue' program to help the server run external
- programs
-
- o testprns, a program to test server access to printers
-
- o testparms, a program to test the Samba configuration file for
- correctness
-
- o smb.conf, the Samba configuration file
-
- o smbprint, a sample script to allow a Unix host to use smbclient to
- print to an SMB server
-
- o Documentation! DON'T neglect to read it - you will save a great
- deal of time!
-
- The suite is supplied with full source (of course!) and is GPLed.
-
- The primary creator of the Samba suite is Andrew Tridgell. Later
- versions incorporate much effort by many net.helpers. The man pages
- and this FAQ were originally written by Karl Auer.
-
-
- 1.2. What is the current version of Samba?
-
-
- At time of writing, the current version was 1.9.17. If you want to be
- sure check the bottom of the change-log file.
-
-
- For more information see ``What do the version numbers mean?''
-
-
- 1.3. Where can I get it?
-
-
- The Samba suite is available via anonymous ftp from samba.anu.edu.au.
- The latest and greatest versions of the suite are in the directory:
-
- /pub/samba/
-
- Development (read "alpha") versions, which are NOT necessarily stable
- and which do NOT necessarily have accurate documentation, are
- available in the directory:
-
- /pub/samba/alpha
-
- Note that binaries are NOT included in any of the above. Samba is
- distributed ONLY in source form, though binaries may be available from
- other sites. Recent versions of some Linux distributions, for example,
- do contain Samba binaries for that platform.
-
-
- 1.4. 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
- 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:
-
- 1. 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.)
-
- 2. 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 are just looking for the latest version to install.
-
- 3. When Andrew 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.
-
- 4. 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)
- :
- 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 ver-
- sion.
-
-
- 1.5. 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, the Makefile claimed support for:
-
- o A/UX 3.0
-
- o AIX
-
- o Altos Series 386/1000
-
- o Amiga
-
- o Apollo Domain/OS sr10.3
-
- o BSDI
-
- o B.O.S. (Bull Operating System)
-
- o Cray, Unicos 8.0
-
- o Convex
-
- o DGUX.
-
- o DNIX.
-
- o FreeBSD
-
- o HP-UX
-
- o Intergraph.
-
- o Linux with/without shadow passwords and quota
-
- o LYNX 2.3.0
-
- o MachTen (a unix like system for Macintoshes)
-
- o Motorola 88xxx/9xx range of machines
-
- o NetBSD
-
- o NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for
- Mach).
-
- o OS/2 using EMX 0.9b
-
- o OSF1
-
- o QNX 4.22
-
- o RiscIX.
-
- o RISCOs 5.0B
-
- o SEQUENT.
-
- o SCO (including: 3.2v2, European dist., OpenServer 5)
-
- o SGI.
-
- o SMP_DC.OSx v1.1-94c079 on Pyramid S series
-
- o SONY NEWS, NEWS-OS (4.2.x and 6.1.x)
-
- o SUNOS 4
-
- o SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')
-
- o Sunsoft ISC SVR3V4
-
- o SVR4
-
- o System V with some berkely extensions (Motorola 88k R32V3.2).
-
- o ULTRIX.
-
- o UNIXWARE
-
- o UXP/DS
-
-
- 1.6. How can I find out more about Samba?
-
-
- There are a number of places to look for more information on Samba,
- including:
-
- o Two mailing lists devoted to discussion of Samba-related matters.
-
- o The newsgroup, comp.protocols.smb, which has a great deal of
- discussion on Samba.
-
- o The WWW site 'SAMBA Web Pages' at
- includes:
-
- o Links to man pages and documentation, including this FAQ
-
- o A comprehensive survey of Samba users.
-
- o A searchable hypertext archive of the Samba mailing list.
-
- o Links to Samba source code, binaries, and mirrors of both.
-
- o The long list of topic documentation. These files can be found in
- the 'docs' directory of the Samba source, or at
-
-
- o Application_Serving.txt
-
-
- o BROWSING.txt
-
- o BUGS.txt
-
- o DIAGNOSIS.txt
-
- o DNIX.txt
-
- o DOMAIN.txt
-
- o CONTROL.txt
-
-
- o ENCRYPTION.txt
-
-
- o Faxing.txt
-
- o GOTCHAS.txt
-
- o HINTS.txt
-
- o INSTALL.sambatar
-
-
- o INSTALL.txt
-
- o MIRRORS
-
- o NetBIOS.txt
-
- o OS2.txt
-
- o PROJECTS
-
- o Passwords.txt
-
- o Printing.txt
-
- o README.DCEDFS
-
- o README.OS2
-
- o README.jis
-
- o README.sambatar
-
-
- o SCO.txt
-
- o SMBTAR.notes
-
- o Speed.txt
-
- o Support.txt
-
- o THANKS
-
- o Tracing.txt
-
- o SMB.txt
-
- o Warp.txt
-
- o WinNT.txt
-
- o history
-
- o level.txt
-
-
- o slip.htm
-
-
- 1.7. How do I subscribe to the Samba Mailing Lists?
-
-
- Send email to listproc@samba.anu.edu.au. Make sure the subject line is
- blank, and include the following two lines in the body of the message:
-
-
- subscribe samba Firstname Lastname
- subscribe samba-announce Firstname Lastname
-
-
-
-
- Obviously you should substitute YOUR first name for "Firstname" and
- YOUR last name for "Lastname"! Try not to send any signature stuff, it
- sometimes confuses the list processor.
-
- The samba list is a digest list - every eight hours or so it
- regurgitates a single message containing all the messages that have
- been received by the list since the last time and sends a copy of this
- message to all subscribers.
-
- If you stop being interested in Samba, please send another email to
- listproc@samba.anu.edu.au. Make sure the subject line is blank, and
- include the following two lines in the body of the message:
-
-
- unsubscribe samba
- unsubscribe samba-announce
-
-
-
-
- The From: line in your message MUST be the same address you used when
- you subscribed.
-
-
- 1.8. Something's gone wrong - what should I do?
-
-
- # *** IMPORTANT! *** #
-
- DO NOT post messages on mailing lists or in newsgroups until you have
- carried out the first three steps given here!
-
- Firstly, see if there are any likely looking entries in this FAQ! If
- you have just installed Samba, have you run through the checklist in
- DIAGNOSIS.txt ? It can
- save you a lot of time and effort. DIAGNOSIS.txt can also be found in
- the docs directory of the Samba distribution.
-
- Secondly, read the man pages for smbd, nmbd and smb.conf, looking for
- topics that relate to what you are trying to do.
-
- Thirdly, if there is no obvious solution to hand, try to get a look at
- the log files for smbd and/or nmbd for the period during which you
- were having problems. You may need to reconfigure the servers to
- provide more extensive debugging information - usually level 2 or
- level 3 provide ample debugging info. Inspect these logs closely,
- looking particularly for the string "Error:".
-
- Fourthly, if you still haven't got anywhere, ask the mailing list or
- newsgroup. In general nobody minds answering questions provided you
- have followed the preceding steps. It might be a good idea to scan the
- archives of the mailing list, which are available through the Samba
- web site described in the previous section.
-
- If you successfully solve a problem, please mail the FAQ maintainer a
- succinct description of the symptom, the problem and the solution, so
- I can incorporate it in the next version.
-
- If you make changes to the source code, _please_ submit these patches
- so that everyone else gets the benefit of your work. This is one of
- the most important aspects to the maintainence of Samba. Send all
- patches to samba-bugs@samba.anu.edu.au. Do not send patches to Andrew
- Tridgell or any other individual, they may be lost if you do.
-
-
- 1.9. Pizza supply details
-
-
- Those who have registered in the Samba survey as "Pizza Factory" will
- already know this, but the rest may need some help. Andrew doesn't ask
- for payment, but he does appreciate it when people give him pizza.
- This calls for a little organisation when the pizza donor is twenty
- thousand kilometres away, but it has been done.
-
- Method 1: Ring up your local branch of an international pizza chain
- and see if they honour their vouchers internationally. Pizza Hut do,
- which is how the entire Canberra Linux Users Group got to eat pizza
- one night, courtesy of someone in the US
-
- Method 2: Ring up a local pizza shop in Canberra and quote a credit
- card number for a certain amount, and tell them that Andrew will be
- collecting it (don't forget to tell him.) One kind soul from Germany
- did this.
-
- Method 3: Purchase a pizza voucher from your local pizza shop that has
- no international affiliations and send it to Andrew. It is completely
- useless but he can hang it on the wall next to the one he already has
- from Germany :-)
-
-
- Method 4: Air freight him a pizza with your favourite regional
- flavours. It will probably get stuck in customs or torn apart by
- hungry sniffer dogs but it will have been a noble gesture.
-
-
- 2. Compiling and installing Samba on a Unix host
-
-
-
- 2.1. I can't see the Samba server in any browse lists!
-
-
- See BROWSING.txt for
- more information on browsing. Browsing.txt can also be found in the
- docs directory of the Samba source.
-
- If your GUI client does not permit you to select non-browsable
- servers, you may need to do so on the command line. For example, under
- Lan Manager you might connect to the above service as disk drive M:
- thusly:
-
-
- net use M: \\mary\fred
-
-
-
-
- The details of how to do this and the specific syntax varies from
- client to client - check your client's documentation.
-
-
- 2.2. Some files that I KNOW are on the server doesn't show up when I
- view the files from my client!
-
-
- See the next question.
-
- 2.3. Some files on the server show up with really wierd filenames
- when I view the files from my client!
-
-
- If you check what files are not showing up, you will note that they
- are files which contain upper case letters or which are otherwise not
- DOS-compatible (ie, they are not legal DOS filenames for some reason).
-
- The Samba server can be configured either to ignore such files
- completely, or to present them to the client in "mangled" form. If you
- are not seeing the files at all, the Samba server has most likely been
- configured to ignore them. Consult the man page smb.conf(5) for
- details of how to change this - the parameter you need to set is
- "mangled names = yes".
-
-
- 2.4. My client reports "cannot locate specified computer" or similar
-
-
- This indicates one of three things: You supplied an incorrect server
- name, the underlying TCP/IP layer is not working correctly, or the
- name you specified cannot be resolved.
-
- After carefully checking that the name you typed is the name you
- should have typed, try doing things like pinging a host or telnetting
- to somewhere on your network to see if TCP/IP is functioning OK. If it
- is, the problem is most likely name resolution.
-
-
- If your client has a facility to do so, hardcode a mapping between the
- hosts IP and the name you want to use. For example, with Man Manager
- or Windows for Workgroups you would put a suitable entry in the file
- LMHOSTS. If this works, the problem is in the communication between
- your client and the netbios name server. If it does not work, then
- there is something fundamental wrong with your naming and the solution
- is beyond the scope of this document.
-
- If you do not have any server on your subnet supplying netbios name
- resolution, hardcoded mappings are your only option. If you DO have a
- netbios name server running (such as the Samba suite's nmbd program),
- the problem probably lies in the way it is set up. Refer to Section
- Two of this FAQ for more ideas.
-
- By the way, remember to REMOVE the hardcoded mapping before further
- tests :-)
-
-
- 2.5. My client reports "cannot locate specified share name" or simi-
- lar
-
-
- 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.
-
- 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 doco on how
- to specify a service name correctly), read on:
-
-
- o Many clients cannot accept or use service names longer than eight
- characters.
-
- o Many clients cannot accept or use service names containing spaces.
-
- o Some servers (not Samba though) are case sensitive with service
- names.
-
- o Some clients force service names into upper case.
-
-
- 2.6. My client reports "cannot find domain controller", "cannot log
- on to the network" or similar
-
-
- Nothing is wrong - Samba does not implement the primary domain name
- controller stuff for several reasons, including the fact that the
- whole concept of a primary domain controller and "logging in to a
- network" doesn't fit well with clients possibly running on multiuser
- machines (such as users of smbclient under Unix). Having said that,
- several developers are working hard on building it in to the next
- major version of Samba. If you can contribute, send a message to
- samba-bugs@anu.edu.au !
-
- Seeing this message should not affect your ability to mount redirected
- disks and printers, which is really what all this is about.
-
- For many clients (including Windows for Workgroups and Lan Manager),
- setting the domain to STANDALONE at least gets rid of the message.
-
-
-
-
-
- 2.7. Printing doesn't work :-(
-
-
- Make sure that the specified print command for the service you are
- connecting to is correct and that it has a fully-qualified path (eg.,
- use "/usr/bin/lpr" rather than just "lpr").
-
- Make sure that the spool directory specified for the service is
- writable by the user connected to the service. In particular the user
- "nobody" often has problems with printing, even if it worked with an
- earlier version of Samba. Try creating another guest user other than
- "nobody".
-
- Make sure that the user specified in the service is permitted to use
- the printer.
-
- Check the debug log produced by smbd. Search for the printer name and
- see if the log turns up any clues. Note that error messages to do with
- a service ipc$ are meaningless - they relate to the way the client
- attempts to retrieve status information when using the LANMAN1
- protocol.
-
- If using WfWg then you need to set the default protocol to TCP/IP, not
- Netbeui. This is a WfWg bug.
-
- If using the Lanman1 protocol (the default) then try switching to
- coreplus. Also not that print status error messages don't mean
- printing won't work. The print status is received by a different
- mechanism.
-
-
- 2.8. My programs install on the server OK, but refuse to work prop-
- erly
-
-
- There are numerous possible reasons for this, but one MAJOR
- possibility is that your software uses locking. Make sure you are
- using Samba 1.6.11 or later. It may also be possible to work around
- the problem by setting "locking=no" in the Samba configuration file
- for the service the software is installed on. This should be regarded
- as a strictly temporary solution.
-
- In earlier Samba versions there were some difficulties with the very
- latest Microsoft products, particularly Excel 5 and Word for Windows
- 6. These should have all been solved. If not then please let Andrew
- Tridgell know via email at samba-bugs@anu.edu.au.
-
-
- 2.9. My "server string" doesn't seem to be recognised
-
-
- OR My client reports the default setting, eg. "Samba 1.9.15p4",
- instead of what I have changed it to in the smb.conf file.
-
- You need to use the -C option in nmbd. The "server string" affects
- what smbd puts out and -C affects what nmbd puts out.
-
- Current versions of Samba (1.9.16 +) have combined these options into
- the "server string" field of smb.conf, -C for nmbd is now obsolete.
-
-
- 2.10. My client reports "This server is not configured to list shared
- resources"
-
-
- Your guest account is probably invalid for some reason. Samba uses the
- guest account for browsing in smbd. Check that your guest account is
- valid.
-
- See also 'guest account' in smb.conf man page.
-
-
- 2.11. Log message "you appear to have a trapdoor uid system"
-
-
- This can have several causes. It might be because you are using a uid
- or gid of 65535 or -1. This is a VERY bad idea, and is a big security
- hole. Check carefully in your /etc/passwd file and make sure that no
- user has uid 65535 or -1. Especially check the "nobody" user, as many
- broken systems are shipped with nobody setup with a uid of 65535.
-
- It might also mean that your OS has a trapdoor uid/gid system :-)
-
- This means that once a process changes effective uid from root to
- another user it can't go back to root. Unfortunately Samba relies on
- being able to change effective uid from root to non-root and back
- again to implement its security policy. If your OS has a trapdoor uid
- system this won't work, and several things in Samba may break. Less
- things will break if you use user or server level security instead of
- the default share level security, but you may still strike problems.
-
- The problems don't give rise to any security holes, so don't panic,
- but it does mean some of Samba's capabilities will be unavailable. In
- particular you will not be able to connect to the Samba server as two
- different uids at once. This may happen if you try to print as a
- "guest" while accessing a share as a normal user. It may also affect
- your ability to list the available shares as this is normally done as
- the guest user.
-
- Complain to your OS vendor and ask them to fix their system.
-
- Note: the reason why 65535 is a VERY bad choice of uid and gid is that
- it casts to -1 as a uid, and the setreuid() system call ignores (with
- no error) uid changes to -1. This means any daemon attempting to run
- as uid 65535 will actually run as root. This is not good!
-
-
- 3. Common client questions
-
-
-
-
- 3.1. Are there any Macintosh clients for Samba?
-
-
- Yes! Thursby now have a CIFS Client / Server called DAVE - see
- . They test it against Windows 95, Windows
- NT and samba for compatibility issues. At the time of writing, DAVE
- was at version 1.0.1. The 1.0.0 to 1.0.1 update is available as a free
- download from the Thursby web site (the speed of finder copies has
- been greatly enhanced, and there are bug-fixes included).
-
- Alternatives - There are two free implementations of AppleTalk for
- several kinds of UNIX machnes, and several more commercial ones.
- These products allow you to run file services and print services
- natively to Macintosh users, with no additional support required on
- the Macintosh. The two free omplementations are Netatalk,
- , and CAP,
- . What Samba offers MS
- Windows users, these packages offer to Macs. For more info on these
- packages, Samba, and Linux (and other UNIX-based systems) see
-
- 3.2. Session request failed (131,130)" error
-
-
- The following answer is provided by John E. Miller:
-
- I'll assume that you're able to ping back and forth between the
- machines by IP address and name, and that you're using some security
- model where you're confident that you've got user IDs and passwords
- right. The logging options (-d3 or greater) can help a lot with that.
- DNS and WINS configuration can also impact connectivity as well.
-
- Now, on to 'scope id's. Somewhere in your Win95 TCP/IP network
- configuration (I'm too much of an NT bigot to know where it's located
- in the Win95 setup, but I'll have to learn someday since I teach for a
- Microsoft Solution Provider Authorized Tech Education Center - what an
- acronym...) Note: It's under Control Panel | Network | TCP/IP | WINS
- Configuration there's a little text entry field called something like
-
- This field essentially creates 'invisible' sub-workgroups on the same
- wire. Boxes can only see other boxes whose Scope IDs are set to the
- exact same value - it's sometimes used by OEMs to configure their
- boxes to browse only other boxes from the same vendor and, in most
- environments, this field should be left blank. If you, in fact, have
- something in this box that EXACT value (case-sensitive!) needs to be
- provided to smbclient and nmbd as the -i (lowercase) parameter. So, if
- your Scope ID is configured as the string 'SomeStr' in Win95 then
- you'd have to use smbclient -iSomeStr otherparms in connecting to it.
-
-
- 3.3. How do I synchronise my PC's clock with my Samba server?
-
-
- To syncronize your PC's clock with your Samba server:
-
- o Copy timesync.pif to your windows directory
-
- o timesync.pif can be found at:
-
-
- o Add timesync.pif to your 'Start Up' group/folder
-
- o Open the properties dialog box for the program/icon
-
- o Make sure the 'Run Minimized' option is set in program 'Properties'
-
- o Change the command line section that reads \sambahost to reflect
- the name of your server.
-
- o Close the properties dialog box by choosing 'OK'
-
- Each time you start your computer (or login for Win95) your PC will
- synchronize it's clock with your Samba server.
-
- Alternativley, if you clients support Domain Logons, you can setup
- Domain Logons with Samba - see: BROWSING.txt
- *** for more
- information.
-
- Then add
-
-
- NET TIME \\%L /SET /YES
-
-
-
-
- as one of the lines in the logon script.
-
- 3.4. Problems with WinDD, NTrigue, WinCenterPro etc
-
-
- All of the above programs are applications that sit on an NT box and
- allow multiple users to access the NT GUI applications from remote
- workstations (often over X).
-
- What has this got to do with Samba? The problem comes when these users
- use filemanager to mount shares from a Samba server. The most common
- symptom is that the first user to connect get correct file permissions
- and has a nice day, but subsequent connections get logged in as the
- same user as the first person to login. They find that they cannot
- access files in their own home directory, but that they can access
- files in the first users home directory (maybe not such a nice day
- after all?)
-
- Why does this happen? The above products all share a common heritage
- (and code base I believe). They all open just a single TCP based SMB
- connection to the Samba server, and requests from all users are piped
- over this connection. This is unfortunate, but not fatal.
-
- It means that if you run your Samba server in share level security
- (the default) then things will definately break as described above.
- The share level SMB security model has no provision for multiple user
- IDs on the one SMB connection. See security_level.txt
- in the docs
- for more info on share/user/server level security.
-
- If you run in user or server level security then you have a chance,
- but only if you have a recent version of Samba (at least 1.9.15p6). In
- older versions bugs in Samba meant you still would have had problems.
-
- If you have a trapdoor uid system in your OS then it will never work
- properly. Samba needs to be able to switch uids on the connection and
- it can't if your OS has a trapdoor uid system. You'll know this
- because Samba will note it in your logs.
-
- Also note that you should not use the magic "homes" share name with
- products like these, as otherwise all users will end up with the same
- home directory. Use \serversername instead.
-
-
- 3.5. Problem with printers under NT
-
-
- This info from Stefan Hergeth hergeth@f7axp1.informatik.fh-muenchen.de
- may be useful:
-
- A network-printer (with ethernetcard) is connected to the NT-Clients
- via our UNIX-Fileserver (SAMBA-Server), like the configuration told by
- Matthew Harrell harrell@leech.nrl.navy.mil (see WinNT.txt)
-
- 1. If a user has choosen this printer as the default printer in his
- NT-Session and this printer is not connected to the network (e.g.
- switched off) than this user has a problem with the SAMBA-
- connection of his filesystems. It's very slow.
-
- 2. If the printer is connected to the network everything works fine.
-
- 3. When the smbd ist started with debug level 3, you can see that the
- NT spooling system try to connect to the printer many times. If the
- printer ist not connected to the network this request fails and the
- NT spooler is wasting a lot of time to connect to the printer
- service. This seems to be the reason for the slow network
- connection.
-
- 4. Maybe it's possible to change this behaviour by setting different
- printer properties in the Print-Manager-Menu of NT, but i didn't
- try it yet.
-
-
- 3.6. 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.
-
- 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.
-
- 1. The Unix system clock must have the correct Universal time. Use
- the shell command "sh -c 'TZ=UTC0 date'" to check this.
-
- 2. 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'.
-
- 3. TZ must have the correct value.
-
- a. If possible, use geographical time zone settings (e.g.
- TZ='America/Los_Angeles' or perhaps TZ=':US/Pacific'). These
- are supported by most popular Unix OSes, are easier to get
- right, and are 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
- .
-
- b. 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:
-
- o `Std' is the standard time designation (e.g. `PST').
-
- o `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 daylight-saving time.
-
- o `Dst' is the daylight-saving time designation (e.g. `PDT').
-
- The optional second `Offset' is the number of hours that
- daylight-saving time is behind UTC. The default is 1 hour ahead
- of standard time.
-
- o `Date/Time,Date/Time' specify when daylight-saving time starts
- and ends. The format for a date is `Mm.n.d', which specifies
- the dth day (0 is Sunday) 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 hh: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
- time zone is also set appropriately. [I don't know how to do
- this.] Samba traditionally has had many problems dealing with time
- zones, due to the bizarre ways that Microsoft network protocols
- handle time zones. A common symptom is for file timestamps to be
- off by an hour. To work around the problem, try disconnecting from
- your Samba server and then reconnecting to it; or upgrade your
- Samba server to 1.9.16alpha10 or later.
-
-
- 3.7. How do I set the printer driver name correctly?
-
-
- Question: On NT, I opened "Printer Manager" and "Connect to Printer".
- Enter "\ptdi270s1"
- in the box of printer. I got the following error message:
-
-
- You do not have sufficient access to your machine
- to connect to the selected printer, since a driver
- needs to be installed locally.
-
-
-
-
- Answer:
-
- In the more recent versions of Samba you can now set the "printer
- driver" in smb.conf. This tells the client what driver to use. For
- example:
-
-
- printer driver = HP LaserJet 4L
-
-
-
-
- with this, NT knows to use the right driver. You have to get this
- string exactly right.
-
- To find the exact string to use, you need to get to the dialog box in
- your client where you select which printer driver to install. The
- correct strings for all the different printers are shown in a listbox
- in that dialog box.
-
- You could also try setting the driver to NULL like this:
-
-
- printer driver = NULL
-
-
-
-
- this is effectively what older versions of Samba did, so if that
- worked for you then give it a go. If this does work then let us know
- via samba-bugs@anu.edu.au, and we'll make it the default. Currently
- the default is a 0 length string.
-
-
- 3.8. I've applied NT 4.0 SP3, and now I can't access Samba shares,
- Why?
-
-
- As of SP3, Microsoft has decided that they will no longer default to
- passing clear text passwords over the network. To enable access to
- Samba shares from NT 4.0 SP3, you must do ONE of two things:
-
- 1. Set the Samba configuration option 'security = user' and implement
- all of the stuff detailed in ENCRYPTION.txt
- .
-
- 2. Follow Microsoft's directions for setting your NT box to allow
- plain text passwords. see Knowledge Base Article Q166730
-
-
-
- 4. Specific client application problems
-
-
-
-
- 4.1. MS Office Setup reports "Cannot change properties of 'MSOF-
- FICEUP.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.
-
- To get around this problem, do the installation without admin user
- 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"
- to fix the owner.
-
-
- 5. Miscellaneous
-
-
-
- 5.1. Is Samba Year 2000 compliant?
-
-
- The CIFS protocol that Samba implements negotiates times in various
- formats, all of which are able to cope with dates beyond 2000.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/docs/history b/docs/history
deleted file mode 100644
index a86160e854d..00000000000
--- a/docs/history
+++ /dev/null
@@ -1,196 +0,0 @@
-Contributor: Andrew Tridgell and the Samba Team
-Date: June 27, 1997
-Satus: Always out of date! (Would not be the same without it!)
-
-Subject: A bit of history and a bit of fun
-============================================================================
-
-This is a short history of this project. It's not supposed to be
-comprehensive, just enough so that new users can get a feel for where
-this project has come from and maybe where it's going to.
-
-The whole thing really started in December 1991. I was (and still am)
-a PhD student in the Computer Sciences Laboratory at the Australian
-National University, in Canberra, Australia. We had just got a
-beta copy of eXcursion from Digital, and I was testing it on my PC. At
-this stage I was a MS-DOS user, dabbling in windows.
-
-eXcursion ran (at the time) only with Dec's `Pathworks' network for
-DOS. I had up till then been using PC-NFS to connect to our local sun
-workstations, and was reasonably happy with it. In order to run
-pathworks I had to stop using PC-NFS and try using pathworks to mount
-disk space. Unfortunately pathworks was only available for digital
-workstations running VMS or Ultrix so I couldn't mount from the suns
-anymore.
-
-I had access to a a decstation 3100 running Ultrix that I used to
-administer, and I got the crazy notion that the protocol that
-pathworks used to talk to ultrix couldn't be that hard, and maybe I
-could work it out. I had never written a network program before, and
-certainly didn't know what a socket was.
-
-In a few days, after looking at some example code for sockets, I
-discovered it was pretty easy to write a program to "spy" on the file
-sharing protocol. I wrote and installed this program (the sockspy.c
-program supplied with this package) and captured everything that the
-pathworks client said to the pathworks server.
-
-I then tried writing short C programs (using Turbo C under DOS) to do
-simple file operations on the network drive (open, read, cd etc) and
-looked at the packets that the server and client exchanged. From this
-I worked out what some of the bytes in the packets meant, and started
-to write my own program to do the same thing on a sun.
-
-After a day or so more I had my first successes and actually managed
-to get a connection and to read a file. From there it was all
-downhill, and a week later I was happily (if a little unreliably)
-mounting disk space from a sun to my PC running pathworks. The server
-code had a lot of `magic' values in it, which seemed to be always
-present with the ultrix server. It was not till 2 years later that I
-found out what all these values meant.
-
-Anyway, I thought other people might be interested in what I had done,
-so I asked a few people at uni, and noone seemed much interested. I
-also spoke to a person at Digital in Canberra (the person who had
-organised a beta test of eXcursion) and asked if I could distribute
-what I'd done, or was it illegal. It was then that I first heard the
-word "netbios" when he told me that he thought it was all covered by a
-spec of some sort (the netbios spec) and thus what I'd done was not
-only legal, but silly.
-
-I found the netbios spec after asking around a bit (the RFC1001 and
-RFC1002 specs) and found they looked nothing like what I'd written, so
-I thought maybe the Digital person was mistaken. I didn't realise RFCs
-referred to the name negotiation and packet encapsulation over TCP/IP,
-and what I'd written was really a SMB implementation.
-
-Anyway, he encouraged me to release it so I put out "Server 0.1" in
-January 1992. I got quite a good response from people wanting to use
-pathworks with non-digital unix workstations, and I soon fixed a few
-bugs, and released "Server 0.5" closely followed by "Server 1.0". All
-three releases came out within about a month of each other.
-
-At this point I got an X Terminal on my desk, and I no longer needed eXcursion
-and I prompty forgot about the whole project, apart from a few people
-who e-mailed me occasionally about it.
-
-Nearly two years then passed with just occasional e-mails asking about
-new versions and bugs. I even added a note to the ftp site asking for
-a volunteer to take over the code as I no longer used it. No one
-volunteered.
-
-During this time I did hear from a couple of people who said it should
-be possible to use my code with Lanmanager, but I never got any
-definite confirmation.
-
-One e-mail I got about the code did, however, make an impression. It
-was from Dan Shearer at the university of South Australia, and he said
-this:
-
-
- I heard a hint about a free Pathworks server for Unix in the
- Net channel of the Linux list. After quite a bit of chasing
- (and lots of interested followups from other Linux people) I
- got hold of a release news article from you, posted in Jan 92,
- from someone in the UK.
-
- Can you tell me what the latest status is? I think you might
- suddenly find a whole lot of interested hackers in the Linux
- world at least, which is a place where things tend to happen
- fast (and even some reliable code gets written, BION!)
-
-I asked him what Linux was, and he told me it was a free Unix for PCs.
-This was in November 1992 and a few months later I was a Linux
-convert! I still didn't need a pathworks server though, so I didn't do
-the port, but I think Dan did.
-
-At about this time I got an e-mail from Digital, from a person working
-on the Alpha software distribution. He asked if I would mind if they
-included my server with the "contributed" cd-rom. This was a bit of a
-shock to me as I never expected Dec to ask me if they could use my
-code! I wrote back saying it was OK, but never heard from him again. I
-don't know if it went on the cd-rom.
-
-Anyway, the next big event was in December 1993, when Dan again sent
-me an e-mail saying my server had "raised it's ugly head" on
-comp.protocols.tcpip.ibmpc. I had a quick look on the group, and was
-surprised to see that there were people interested in this thing.
-
-At this time a person from our computer center offered me a couple of
-cheap ethernet cards (3c505s for $15 each) and coincidentially someone
-announced on one of the Linux channels that he had written a 3c505
-driver for Linux. I bought the cards, hacked the driver a little and
-setup a home network between my wifes PC and my Linux box. I then
-needed some way to connect the two, and I didn't own PC-NFS at home,
-so I thought maybe my server could be useful. On the newsgroup among
-the discussions of my server someone had mentioned that there was a
-free client that might work with my server that Microsoft had put up
-for ftp. I downloaded it and found to my surprise that it worked first
-time with my `pathworks' server!
-
-Well, I then did a bit of hacking, asked around a bit and found (I
-think from Dan) that the spec I needed was for the "SMB" protocol, and
-that it was available via ftp. I grabbed it and started removing all
-those ugly constants from the code, now that all was explained.
-
-On December 1st 1993 I announced the start of the "Netbios for Unix"
-project, seeding the mailing list with all the people who had e-mailed
-me over the years asking about the server.
-
-About 35 versions (and two months) later I wrote a short history of
-the project, which you have just read. There are now over a hundred
-people on the mailing list, and lots of people report that they use
-the code and like it. In a few days I will be announcing the release
-of version 1.6 to some of the more popular (and relevant) newsgroups.
-
-
-Andrew Tridgell
-6th February 1994
-
----------------------
-
-It is now May 1995 and there are about 1400 people on the mailing
-list. I got downloads from the main Samba ftp site from around 5000
-unique hosts in a two month period. There are several mirror
-sites as well. The current version number is 1.9.13.
-
----------------------
-
-
----------------------
-It's now March 1996 and version 1.9.16alpha1 has just been
-released. There have been lots of changes recently with master browser
-support and the ability to do domain logons etc. Samba has also been
-ported to OS/2, the amiga and NetWare. There are now 3000 people on
-the samba mailing list.
----------------------
-
-
----------------------
-It's now June 1997 and samba-1.9.17 is due out soon. My how time passes!
-Please refer to the WHATSNEW.txt for an update on new features. Just when
-you think you understand what is happening the ground rules change - this
-is a real world after all. Since the heady days of March 1996 there has
-been a concerted effort within the SMB protocol using community to document
-and standardize the protocols. The CIFS initiative has helped a long way
-towards creating a better understood and more interoperable environment.
-The Samba Team has grown in number and have been very active in the standards
-formation and documentation process.
-
-The net effect has been that we have had to do a lot of work to bring Samba
-into line with new features and capabilities in the SMB protocols.
-
-The past year has been a productive one with the following releases:
- 1.9.16, 1.9.16p2, 1.9.16p6, 1.9.16p9, 1.9.16p10, 1.9.16p11
-
-There are some who believe that 1.9.15p8 was the best release and others
-who would not want to be without the latest. Whatever your perception we
-hope that 1.9.17 will close the gap and convince you all that the long
-wait and the rolling changes really were worth it. Here is functionality
-and a level of code maturity that ..., well - you can be the judge!
-
-Happy SMB networking!
-Samba Team
-
-ps: The bugs are ours, so please report any you find.
----------------------
diff --git a/docs/htmldocs/wfw_slip.htm b/docs/htmldocs/wfw_slip.htm
deleted file mode 100644
index 5b4a0a5e539..00000000000
--- a/docs/htmldocs/wfw_slip.htm
+++ /dev/null
@@ -1,175 +0,0 @@
-
-
-Peter Karrer Announces SLIP for WFW
-
-
-
Winserve
-
-
Peter Karrer Announces SLIP for WFW
-[NEW 03-22-95)
-
-Hello,
-
-I've discovered a way to run WfW's TCP/IP-32 over a SLIP packet driver. This
-allows WfW users to do Windows networking over dialup lines just like it is
-possible with NT and the Windows 95 beta!
-
-For instance, you can mount Microsoft's FTP server as a network drive in File
-Manager or connect to an MS Mail post office over the Internet. Of course,
-the usual Internet stuff works as well. Another interesting site is
-WINSERVE.001; check out www.winserve.com.
-
-This method should work with any class 1 (Ethernet II) packet driver. However,
-I'm not in a position to try anything else than SLIPPER/CSLIPPER.
-
-
- Don Provan's ODI-over-Packet Driver shim. This *must* be version 1.05 (or
- above).
-
-LSL.COM:
-
- Novell's LAN Support Layer. If you're an owner of Windows 3.10, you'll
- have it on one of your install disks. Use "expand a:lsl.co_ lsl.com" to
- expand it. Microsoft has stopped bundling LSL.COM with WfW 3.11, though.
- The newest version of LSL.COM can be downloaded as part of
- ftp://ftp.novell.com/pub/netware/nwos/dosclnt12/vlms/vlmup2.exe.
- However, it's not clear if this one may be legally used outside Netware
- environments.
-
-NET.CFG:
-
- A configuration file for LSL and PDETHER. It should contain the following
- text:
-
- A little hack of mine to disable the COM port used by the SLIP packet driver.
- Usage is e.g. "discomx 2" to disable COM2. This should be run before
- starting WfW, otherwise you'll get "device conflict" messages. Here it is:
-
- (Save this text to disk as filename, then run "uudecode filename".
- uudecode can be found, for instance, at
- ftp://ftp.switch.ch/mirror/simtel/msdos/starter/uudecode.com )
-
-LMHOSTS:
-
- An optional file which should be stored in your Windows subdirectory. It is
- used to map NetBIOS computer names to IP addresses. Example:
-
Put the files mentioned above into a directory, e.g. C:\SLIP.
-
-
Put the following lines into AUTOEXEC.BAT:
-
- cd \slip
- slipper com1 vec=60 baud=57600 ether (may vary with your modem setup)
- lsl
- pdether
- discomx 1 (must correspond to SLIPPER's COM port)
-
- (If you use another vec= setting, you must update that in NET.CFG as well.)
- Use CSLIPPER instead of SLIPPER if your SLIP provider supports VJC.
-
-
Start WfW.
-
-
Under Windows Setup, choose "Change Network Settings".
-
Select "Install Microsoft Windows Network".
-
In "Drivers...", choose "Add Adapter"
- and install the "IPXODI Support driver (Ethernet) [ODI/NDIS3]".
-
In "Add Protocols...", select "Unlisted or Updated Protocol". When asked for a
- driver disk, enter the directory where you expanded WFWT32.EXE.
-
Configure TCP/IP (IP address, enable LMHOSTS lookup, try 204.118.34.11 as primary
- WINS server). Remove all other protocols (NetBEUI, IPX/SPX).
-
-
-
Windows will probably update the first lines of AUTOEXEC.BAT with
-
-
- c:\windows\net start
- c:\windows\odihlp.exe.
-
- The "odihlp" line must be moved behind the "pdether" line.
-
-
Windows will also update NET.CFG with some "Frame" lines. These must
- be removed (except "Frame Ethernet_II").
-
-
Somehow, you will have to dial in to your SLIP provider. I do it manually
- before slipper (or cslipper) gets loaded, using a DOS-based terminal program.
- But there are some automatic dialers around. I've seen recommendations for
- ftp://mvmpc9.ciw.uni-karlsruhe.de/x-slip/slip_it.exe.
-
-
To connect to Microsoft's FTP server (or Winserve) go into File Manager,
- choose "Connect Network drive" and enter "\\ftp" or "\\winserve.001" into
- the "Path:" field.
-
-
-
How it works:
-
-Microsoft's TCP/IP-32 requires an NDIS3 interface. NDIS is Microsoft's way
-to interface with a network.
-
-WfW also contains an NDIS3-over-ODI "shim", whose real mode component is
-ODIHLP.EXE. ODI is Novell's way to interface with a network.
-
-SLIPPER is a Packet Driver (PD) for use over serial lines. PDs are everybody
-else's way to interface with a network. SLIPPER's "ether" option makes it
-look like an Ethernet PD to applications using it.
-
-A "shim" is a program which simulates a network application programming
-interface on top of another.
-
-There is no NDIS SLIP driver which would work with WfW.
-
-There is no NDIS-over-PD shim.
-
-However, there's an ODI-over-PD shim (PDETHER) and an NDIS-over-ODI shim
-(ODIHLP etc.)
-
-OK, so let's do NDIS-over-ODI-over-PD!
-
-This should have worked all the time; however, a non-feature in PDETHER
-versions < 1.05 has prevented the method from functioning until now.
-
-Questions, suggestions etc. please to
-
-
-Peter Karrer pkarrer@ife.ee.ethz.ch
-
-
-
-
diff --git a/docs/manpages/nmbd.8 b/docs/manpages/nmbd.8
deleted file mode 100644
index 148e53478c2..00000000000
--- a/docs/manpages/nmbd.8
+++ /dev/null
@@ -1,231 +0,0 @@
-.TH NMBD 8 nmbd nmbd
-.SH NAME
-nmbd \- provide netbios nameserver support to clients
-.SH SYNOPSIS
-.B nmbd
-[
-.B \-D
-] [
-.B \-H
-.I netbios hosts file
-] [
-.B \-d
-.I debuglevel
-] [
-.B \-l
-.I log basename
-] [
-.B \-n
-.I netbios name
-] [
-.B \-p
-.I port number
-] [
-.B \-s
-.I configuration file
-]
-.SH DESCRIPTION
-This program is part of the Samba suite.
-
-.B nmbd
-is a server that understands and can reply to netbios
-name service requests, like those produced by LanManager
-clients. It also controls browsing.
-
-LanManager clients, when they start up, may wish to locate a LanManager server.
-That is, they wish to know what IP number a specified host is using.
-
-This program simply listens for such requests, and if its own name is specified
-it will respond with the IP number of the host it is running on.
-Its "own name" is by default the name of the host it is running on,
-but this can be overriden with the
-.B \-n
-option (see "OPTIONS" below).
-
-.B nmbd
-can also be used as a WINS (Windows Internet Name Server) server.
-What this basically means is that it will respond to all name requests that
-it receives that are not broadcasts, as long as it can resolve the name.
-Resolvable names include all names in the netbios hosts file (if any, see
-.B \-H
-below), its own name, and any other names that it may have learned about
-from other browsers on the network.
-A change to previous versions is that nmbd will now no longer
-do this automatically by default.
-.SH OPTIONS
-.B \-B
-
-.RS 3
-This option is obsolete. Please use the "interfaces" option in smb.conf instead.
-.RE
-
-.B \-I
-
-.RS 3
-This option is obsolete. Please use the "interfaces" option in smb.conf instead.
-.RE
-
-.B \-D
-
-.RS 3
-If specified, this parameter causes the server to operate as a daemon. That is,
-it detaches itself and runs in the background, fielding requests on the
-appropriate port.
-
-By default, the server will NOT operate as a daemon.
-.RE
-
-.B \-C comment string
-
-.RS 3
-This option is obsolete. Please use the "server string" option in smb.conf
-instead.
-.RE
-
-.B \-G
-
-.RS 3
-This option is obsolete. Please use the "workgroup" option in smb.conf instead.
-.RE
-
-.B \-H
-.I netbios hosts file
-
-.RS 3
-It may be useful in some situations to be able to specify a list of
-netbios names for which the server should send a reply if queried.
-This option allows you to specify a file containing such a list.
-The syntax of the hosts file is similar to the standard /etc/hosts file
-format, but has some extensions.
-
-The file contains three columns. Lines beginning with a # are ignored
-as comments. The first column is an IP address, or a hostname. If it
-is a hostname then it is interpreted as the IP address returned by
-gethostbyname() when read. An IP address of 0.0.0.0 will be
-interpreted as the server's own IP address.
-
-The second column is a netbios name. This is the name that the server
-will respond to. It must be less than 20 characters long.
-
-The third column is optional, and is intended for flags. Currently the
-only flag supported is M, which means that this name is the default
-netbios name for this machine. This has the same effect as specifying the
-.B \-n
-option to
-.BR nmbd .
-
-NOTE: The G and S flags are now obsolete and are replaced by the
-"interfaces" and "remote announce" options in smb.conf.
-
-The default hosts file name is set at compile time, typically as
-.I /etc/lmhosts,
-but this may be changed in the Samba Makefile.
-
-After startup the server waits for queries, and will answer queries for
-any name known to it. This includes all names in the netbios hosts file,
-its own name, and any other names it may have learned about from other
-browsers on the network.
-
-The primary intention of the
-.B \-H
-option is to allow a mapping from netbios names to internet domain names.
-
-.B Example:
-
- # This is a sample netbios hosts file
-
- # DO NOT USE THIS FILE AS-IS
- # YOU MAY INCONVENIENCE THE OWNERS OF THESE IPs
- # if you want to include a name with a space in it then
- # use double quotes.
-
- # next add a netbios alias for a faraway host
- arvidsjaur.anu.edu.au ARVIDSJAUR
-
- # finally put in an IP for a hard to find host
- 130.45.3.213 FREDDY
-
-.RE
-.B \-N
-
-.RS 3
-This option is obsolete. Please use the "interfaces" option in smb.conf instead.
-.RE
-
-.B \-d
-.I debuglevel
-
-.RS 3
-This option sets the debug level. See
-.BR smb.conf (5).
-.RE
-
-.B \-l
-.I log file
-
-.RS 3
-The
-.I log file
-parameter specifies a path and base filename into which operational data
-from the running
-.B nmbd
-server will be logged.
-The actual log file name is generated by appending the extension ".nmb" to
-the specified base name.
-For example, if the name specified was "log" then the file log.nmb would
-contain the debugging data.
-
-The default log file is specified at compile time, typically as
-.I /var/log/log.nmb.
-.RE
-
-.B \-n
-.I netbios name
-
-.RS 3
-This option allows you to override the Netbios name that Samba uses for itself.
-.RE
-
-.B \-p
-.I port number
-.RS 3
-
-port number is a positive integer value.
-
-Don't use this option unless you are an expert, in which case you
-won't need help!
-.RE
-
-.B \-s
-.I configuration file
-
-.RS 3
-The default configuration file name is set at compile time, typically as
-.I /etc/smb.conf,
-but this may be changed in the Samba Makefile.
-
-The file specified contains the configuration details required by the server.
-See
-.BR smb.conf (5)
-for more information.
-.RE
-.SH VERSION
-
-This man page is (mostly) correct for version 1.9.16 of the Samba
-suite, plus some of the recent patches to it. These notes will
-necessarily lag behind development of the software, so it is possible
-that your version of the server has extensions or parameter semantics
-that differ from or are not covered by this man page. Please notify
-these to the address below for rectification.
-.SH SEE ALSO
-.BR inetd (8),
-.BR smbd (8),
-.BR smb.conf (5),
-.BR smbclient (1),
-.BR testparm (1),
-.BR testprns (1)
-.SH CREDITS
-The original Samba software and related utilities were created by
-Andrew Tridgell (samba-bugs@samba.anu.edu.au). Andrew is also the Keeper
-of the Source for this project.
-
diff --git a/docs/manpages/samba.7 b/docs/manpages/samba.7
deleted file mode 100644
index 7e98c850d41..00000000000
--- a/docs/manpages/samba.7
+++ /dev/null
@@ -1,202 +0,0 @@
-.TH SAMBA 7 Samba Samba
-.SH NAME
-Samba \- a LanManager like fileserver for UNIX
-.SH SYNOPSIS
-.B Samba
-.SH DESCRIPTION
-The
-.B Samba
-software suite is a collection of programs that implements the SMB
-protocol for UNIX systems. This protocol is sometimes also referred to
-as the LanManager or Netbios protocol.
-.SH COMPONENTS
-
-The Samba suite is made up of several components. Each component is
-described in a separate manual page. It is strongly recommended that
-you read the documentation that comes with Samba and the manual pages
-of those components that you use. If the manual pages aren't clear
-enough then please send me a patch!
-
-The
-.BR smbd (8)
-daemon provides the file and print services to SMB clients,
-such as Windows for Workgroups, Windows NT or LanManager. The
-configuration file for this daemon is described in
-.BR smb.conf (5).
-
-The
-.BR nmbd (8)
-daemon provides Netbios nameserving and browsing
-support. It can also be run interactively to query other name service
-daemons.
-
-The
-.BR smbclient (1)
-program implements a simple ftp-like client. This is
-useful for accessing SMB shares on other compatible servers (such as
-WfWg), and can also be used to allow a UNIX box to print to a printer
-attached to any SMB server (such as a PC running WfWg).
-
-The
-.BR testparm (1)
-utility allows you to test your
-.BR smb.conf (5)
-configuration file.
-
-The
-.BR smbstatus (1)
-utility allows you to tell who is currently using the
-.BR smbd (8)
-server.
-.SH AVAILABILITY
-
-The Samba software suite is licensed under the Gnu Public License. A
-copy of that license should have come with the package. You are
-encouraged to distribute copies of the Samba suite, but please keep it
-intact.
-
-The latest version of the Samba suite can be obtained via anonymous
-ftp from samba.anu.edu.au in the directory pub/samba/. It is
-also available on several mirror sites worldwide.
-
-You may also find useful information about Samba on the newsgroup
-comp.protocols.smb and the Samba mailing list. Details on how to join
-the mailing list are given in the README file that comes with Samba.
-
-If you have access to a WWW viewer (such as Netscape or Mosaic) then
-you will also find lots of useful information, including back issues
-of the Samba mailing list, at http://samba.canberra.edu.au/pub/samba/
-.SH AUTHOR
-
-The main author of the Samba suite is Andrew Tridgell. He may be
-contacted via e-mail at samba-bugs@samba.anu.edu.au.
-
-There have also been an enormous number of contributors to Samba from
-all over the world. A partial list of these contributors is included
-in the CREDITS section below. The list is, however, badly out of
-date. More up to date info may be obtained from the change-log that
-comes with the Samba source code.
-.SH CONTRIBUTIONS
-
-If you wish to contribute to the Samba project, then I suggest you
-join the Samba mailing list.
-
-If you have patches to submit or bugs to report then you may mail them
-directly to samba-bugs@samba.anu.edu.au. Note, however, that due to the
-enormous popularity of this package I may take some time to repond to
-mail. I prefer patches in "diff \-u" format.
-.SH CREDITS
-
-Contributors to the project are (in alphabetical order by email address):
-
-(NOTE: This list is very out of date)
-
- Adams, Graham
- (gadams@ddrive.demon.co.uk)
- Allison, Jeremy
- (jeremy@netcom.com)
- Andrus, Ross
- (ross@augie.insci.com)
- Auer, Karl
- (Karl.Auer@anu.edu.au)
- Bogstad, Bill
- (bogstad@cs.jhu.edu)
- Boreham, Bryan
- (Bryan@alex.com)
- Boreham, David
- (davidb@ndl.co.uk)
- Butler, Michael
- (imb@asstdc.scgt.oz.au)
- ???
- (charlie@edina.demon.co.uk)
- Chua, Michael
- (lpc@solomon.technet.sg)
- Cochran, Marc
- (mcochran@wellfleet.com)
- Dey, Martin N
- (mnd@netmgrs.co.uk)
- Errath, Maximilian
- (errath@balu.kfunigraz.ac.at)
- Fisher, Lee
- (leefi@microsoft.com)
- Foderaro, Sean
- (jkf@frisky.Franz.COM)
- Greer, Brad
- (brad@cac.washington.edu)
- Griffith, Michael A
- (grif@cs.ucr.edu)
- Grosen, Mark
- (MDGrosen@spectron.COM)
- ????
- (gunjkoa@dep.sa.gov.au)
- Haapanen, Tom
- (tomh@metrics.com)
- Hench, Mike
- (hench@cae.uwm.edu)
- Horstman, Mark A
- (mh2620@sarek.sbc.com)
- Hudson, Tim
- (tim.hudson@gslmail.mincom.oz.au)
- Hulthen, Erik Magnus
- (magnus@axiom.se)
- ???
- (imb@asstdc.scgt.oz.au)
- Iversen, Per Steinar
- (iversen@dsfys1.fi.uib.no)
- Kaara, Pasi
- (ppk@atk.tpo.fi)
- Karman, Merik
- (merik@blackadder.dsh.oz.au)
- Kiff, Martin
- (mgk@newton.npl.co.uk)
- Kiick, Chris
- (cjkiick@flinx.b11.ingr.com)
- Kukulies, Christoph
- (kuku@acds.physik.rwth-aachen.de)
- ???
- (lance@fox.com)
- Leighton, Luke
- (lkcl@pires.co.uk)
- Lendecke, Volker
- (lendecke@namu01.gwdg.de)
- ???
- (lonnie@itg.ti.com)
- Mahoney, Paul Thomas
- (ptm@xact1.xact.com)
- Mauelshagen, Heinz
- (mauelsha@ez.da.telekom.de)
- Merrick, Barry G
- (bgm@atml.co.uk)
- Mol, Marcel
- (marcel@fanout.et.tudeflt.nl)
- ???
- (njw@cpsg.com.au)
- ???
- (noses@oink.rhein.de)
- Owens, John
- (john@micros.com)
- Pierson, Jacques
- (pierson@ketje.enet.dec.com)
- Powell, Mark
- (mark@scot1.ucsalf.ac.uk)
- Reiz, Steven
- (sreiz@aie.nl)
- Schlaeger, Joerg
- (joergs@toppoint.de)
- S{rkel{, Vesa
- (vesku@rankki.kcl.fi)
- Terpstra, John
- (jht@aquasoft.com.au)
- Tridgell, Andrew
- (samba-bugs@samba.anu.edu.au)
- Troyer, Dean
- (troyer@saifr00.ateng.az.honeywell.com)
- Wakelin, Ross
- (rossw@march.co.uk)
- Wessels, Stefan
- (SWESSELS@dos-lan.cs.up.ac.za)
- Young, Ian A
- (iay@threel.co.uk)
- van der Zwan, Paul
- (paulzn@olivetti.nl)
-
diff --git a/docs/manpages/smb.conf.5 b/docs/manpages/smb.conf.5
deleted file mode 100644
index cbae60cc8b8..00000000000
--- a/docs/manpages/smb.conf.5
+++ /dev/null
@@ -1,3390 +0,0 @@
-.TH SMB.CONF 5 smb.conf smb.conf
-.SH NAME
-smb.conf \- configuration file for smbd
-.SH SYNOPSIS
-.B smb.conf
-.SH DESCRIPTION
-The
-.B smb.conf
-file is a configuration file for the Samba suite.
-
-.B smb.conf
-contains runtime configuration information for the
-.B smbd
-program. The
-.B smbd
-program provides LanManager-like services to clients
-using the SMB protocol.
-.SH FILE FORMAT
-The file consists of sections and parameters. A section begins with the
-name of the section in square brackets and continues until the next
-section begins. Sections contain parameters of the form 'name = value'.
-
-The file is line-based - that is, each newline-terminated line represents
-either a comment, a section name or a parameter.
-
-Section and parameter names are not case sensitive.
-
-Only the first equals sign in a parameter is significant. Whitespace before
-or after the first equals sign is discarded. Leading, trailing and internal
-whitespace in section and parameter names is irrelevant. Leading and
-trailing whitespace in a parameter value is discarded. Internal whitespace
-within a parameter value is retained verbatim.
-
-Any line beginning with a semicolon is ignored, as are lines containing
-only whitespace.
-
-Any line ending in a \e is "continued" on the next line in the
-customary UNIX fashion.
-
-The values following the equals sign in parameters are all either a string
-(no quotes needed) or a boolean, which may be given as yes/no, 0/1 or
-true/false. Case is not significant in boolean values, but is preserved
-in string values. Some items such as create modes are numeric.
-.SH SERVICE DESCRIPTIONS
-Each section in the configuration file describes a service. The section name
-is the service name and the parameters within the section define the service's
-attributes.
-
-There are three special sections, [global], [homes] and [printers], which are
-described under 'special sections'. The following notes apply to ordinary
-service descriptions.
-
-A service consists of a directory to which access is being given plus a
-description of the access rights which are granted to the user of the
-service. Some housekeeping options are also specifiable.
-
-Services are either filespace services (used by the client as an extension of
-their native file systems) or printable services (used by the client to access
-print services on the host running the server).
-
-Services may be guest services, in which case no password is required to
-access them. A specified guest account is used to define access privileges
-in this case.
-
-Services other than guest services will require a password to access
-them. The client provides the username. As many clients only provide
-passwords and not usernames, you may specify a list of usernames to
-check against the password using the "user=" option in the service
-definition.
-
-Note that the access rights granted by the server are masked by the access
-rights granted to the specified or guest user by the host system. The
-server does not grant more access than the host system grants.
-
-The following sample section defines a file space service. The user has write
-access to the path /home/bar. The service is accessed via the service name
-"foo":
-
- [foo]
- path = /home/bar
- writable = true
-
-The following sample section defines a printable service. The service is
-readonly, but printable. That is, the only write access permitted is via
-calls to open, write to and close a spool file. The 'guest ok' parameter
-means access will be permitted as the default guest user (specified elsewhere):
-
- [aprinter]
- path = /usr/spool/public
- read only = true
- printable = true
- public = true
-.SH SPECIAL SECTIONS
-
-.SS The [global] section
-.RS 3
-Parameters in this section apply to the server as a whole, or are defaults
-for services which do not specifically define certain items. See the notes
-under 'Parameters' for more information.
-.RE
-
-.SS The [homes] section
-.RS 3
-If a section called 'homes' is included in the configuration file, services
-connecting clients to their home directories can be created on the fly by the
-server.
-
-When the connection request is made, the existing services are scanned. If a
-match is found, it is used. If no match is found, the requested service name is
-treated as a user name and looked up in the local passwords file. If the
-name exists and the correct password has been given, a service is created
-by cloning the [homes] section.
-
-Some modifications are then made to the newly created section:
-
-.RS 3
-The service name is changed from 'homes' to the located username
-
-If no path was given, the path is set to the user's home directory.
-.RE
-
-If you decide to use a path= line in your [homes] section then you may
-find it useful to use the %S macro. For example path=/data/pchome/%S
-would be useful if you have different home directories for your PCs
-than for UNIX access.
-
-This is a fast and simple way to give a large number of clients access to
-their home directories with a minimum of fuss.
-
-A similar process occurs if the requested service name is "homes", except that
-the service name is not changed to that of the requesting user. This method
-of using the [homes] section works well if different users share a client PC.
-
-The [homes] section can specify all the parameters a normal service section
-can specify, though some make more sense than others. The following is a
-typical and suitable [homes] section:
-
- [homes]
- writable = yes
-
-An important point:
-
-.RS 3
-If guest access is specified in the [homes] section, all home directories will
-be accessible to all clients
-.B without a password.
-In the very unlikely event
-that this is actually desirable, it would be wise to also specify read only
-access.
-.RE
-.RE
-
-Note that the browseable flag for auto home directories will be
-inherited from the global browseable flag, not the [homes] browseable
-flag. This is useful as it means setting browseable=no in the [homes]
-section will hide the [homes] service but make any auto home
-directories visible.
-
-.SS The [printers] section
-.RS 3
-This section works like [homes], but for printers.
-
-If a [printers] section occurs in the configuration file, users are able
-to connect to any printer specified in the local host's printcap file.
-
-When a connection request is made, the existing services are scanned. If a
-match is found, it is used. If no match is found, but a [homes] section
-exists, it is used as described above. Otherwise, the requested service name is
-treated as a printer name and the appropriate printcap file is scanned to
-see if the requested service name is a valid printer name. If a match is
-found, a new service is created by cloning the [printers] section.
-
-A few modifications are then made to the newly created section:
-
-.RS 3
-The service name is set to the located printer name
-
-If no printer name was given, the printer name is set to the located printer
-name
-
-If the service does not permit guest access and no username was given, the
-username is set to the located printer name.
-.RE
-
-Note that the [printers] service MUST be printable - if you specify otherwise,
-the server will refuse to load the configuration file.
-
-Typically the path specified would be that of a world-writable spool directory
-with the sticky bit set on it. A typical [printers] entry would look like this:
-
- [printers]
- path = /usr/spool/public
- writable = no
- public = yes
- printable = yes
-
-All aliases given for a printer in the printcap file are legitimate printer
-names as far as the server is concerned. If your printing subsystem doesn't
-work like that, you will have to set up a pseudo-printcap. This is a file
-consisting of one or more lines like this:
-
- alias|alias|alias|alias...
-
-Each alias should be an acceptable printer name for your printing
-subsystem. In the [global] section, specify the new file as your printcap.
-The server will then only recognise names found in your pseudo-printcap,
-which of course can contain whatever aliases you like. The same technique
-could be used simply to limit access to a subset of your local printers.
-
-An alias, by the way, is defined as any component of the first entry of a
-printcap record. Records are separated by newlines, components (if there are
-more than one) are separated by vertical bar symbols ("|").
-.RE
-.SH PARAMETERS
-Parameters define the specific attributes of services.
-
-Some parameters are specific to the [global] section (eg., security).
-Some parameters are usable in all sections (eg., create mode). All others are
-permissible only in normal sections. For the purposes of the following
-descriptions the [homes] and [printers] sections will be considered normal.
-The letter 'G' in parentheses indicates that a parameter is specific to the
-[global] section. The letter 'S' indicates that a parameter can be
-specified in a service specific section. Note that all S parameters
-can also be specified in the [global] section - in which case they
-will define the default behaviour for all services.
-
-Parameters are arranged here in alphabetical order - this may not create
-best bedfellows, but at least you can find them! Where there are synonyms,
-the preferred synonym is described, others refer to the preferred synonym.
-
-.SS VARIABLE SUBSTITUTIONS
-
-Many of the strings that are settable in the config file can take
-substitutions. For example the option "path = /tmp/%u" would be
-interpreted as "path = /tmp/john" if the user connected with the
-username john.
-
-These substitutions are mostly noted in the descriptions below, but
-there are some general substitutions which apply whenever they might be
-relevant. These are:
-
-%S = the name of the current service, if any
-
-%P = the root directory of the current service, if any
-
-%u = user name of the current service, if any
-
-%g = primary group name of %u
-
-%U = session user name (the user name that the client wanted, not
-necessarily the same as the one they got)
-
-%G = primary group name of %U
-
-%H = the home directory of the user given by %u
-
-%v = the Samba version
-
-%h = the hostname that Samba is running on
-
-%m = the netbios name of the client machine (very useful)
-
-%L = the netbios name of the server. This allows you to change your
-config based on what the client calls you. Your server can have a "dual
-personality".
-
-%M = the internet name of the client machine
-
-%d = The process id of the current server process
-
-%a = the architecture of the remote machine. Only some are recognised,
-and those may not be 100% reliable. It currently recognises Samba,
-WfWg, WinNT and Win95. Anything else will be known as "UNKNOWN". If it
-gets it wrong then sending me a level 3 log should allow me to fix it.
-
-%I = The IP address of the client machine
-
-%T = the current date and time
-
-There are some quite creative things that can be done with these
-substitutions and other smb.conf options.
-
-.SS NAME MANGLING
-
-Samba supports "name mangling" so that DOS and Windows clients can use
-files that don't conform to the 8.3 format. It can also be set to adjust
-the case of 8.3 format filenames.
-
-There are several options that control the way mangling is performed,
-and they are grouped here rather than listed separately. For the
-defaults look at the output of the testparm program.
-
-All of these options can be set separately for each service (or
-globally, of course).
-
-The options are:
-
-"mangle case = yes/no" controls if names that have characters that
-aren't of the "default" case are mangled. For example, if this is yes
-then a name like "Mail" would be mangled. Default no.
-
-"case sensitive = yes/no" controls whether filenames are case
-sensitive. If they aren't then Samba must do a filename search and
-match on passed names. Default no.
-
-"default case = upper/lower" controls what the default case is for new
-filenames. Default lower.
-
-"preserve case = yes/no" controls if new files are created with the
-case that the client passes, or if they are forced to be the "default"
-case. Default no.
-
-"short preserve case = yes/no" controls if new files which conform to 8.3
-syntax, that is all in upper case and of suitable length, are created
-upper case, or if they are forced to be the "default" case. This option can
-be use with "preserve case = yes" to permit long filenames to retain their
-case, while short names are lowered. Default no.
-
-.SS COMPLETE LIST OF GLOBAL PARAMETERS
-
-Here is a list of all global parameters. See the section of each
-parameter for details. Note that some are synonyms.
-
-auto services
-
-browse list
-
-character set
-
-client code page
-
-config file
-
-deadtime
-
-debuglevel
-
-default
-
-default service
-
-dfree command
-
-domain controller
-
-domain master
-
-encrypt passwords
-
-getwd cache
-
-homedir map
-
-hosts equiv
-
-include
-
-keepalive
-
-lock dir
-
-load printers
-
-local master
-
-lock directory
-
-log file
-
-log level
-
-logon path
-
-logon script
-
-lpq cache time
-
-mangled stack
-
-max log size
-
-max mux
-
-max packet
-
-max ttl
-
-max xmit
-
-message command
-
-netbios name
-
-nis homedir
-
-null passwords
-
-os level
-
-packet size
-
-passwd chat
-
-passwd program
-
-password level
-
-password server
-
-preferred master
-
-preload
-
-printing
-
-printcap name
-
-protocol
-
-read bmpx
-
-read prediction
-
-read raw
-
-read size
-
-remote announce
-
-root
-
-root dir
-
-root directory
-
-security
-
-server string
-
-shared file entries
-
-shared mem size
-
-smb passwd file
-
-smbrun
-
-socket address
-
-socket options
-
-status
-
-strip dot
-
-syslog
-
-syslog only
-
-time offset
-
-time server
-
-unix realname
-
-username map
-
-use rhosts
-
-valid chars
-
-veto files
-
-workgroup
-
-write raw
-
-.SS COMPLETE LIST OF SERVICE PARAMETERS
-
-Here is a list of all service parameters. See the section of each
-parameter for details. Note that some are synonyms.
-
-admin users
-
-allow hosts
-
-alternate permissions
-
-available
-
-browseable
-
-case sensitive
-
-case sig names
-
-copy
-
-create mask
-
-create mode
-
-comment
-
-default case
-
-delete readonly
-
-deny hosts
-
-directory
-
-directory mask
-
-directory mode
-
-dont descend
-
-exec
-
-fake oplocks
-
-force create mode
-
-force directory mode
-
-force group
-
-force user
-
-guest account
-
-guest ok
-
-guest only
-
-hide dot files
-
-hosts allow
-
-hosts deny
-
-invalid users
-
-locking
-
-lppause command
-
-lpq command
-
-lpresume command
-
-lprm command
-
-magic output
-
-magic script
-
-mangle case
-
-mangled names
-
-mangling char
-
-map archive
-
-map hidden
-
-map system
-
-max connections
-
-min print space
-
-only guest
-
-only user
-
-path
-
-postexec
-
-postscript
-
-preserve case
-
-print command
-
-printer driver
-
-print ok
-
-printable
-
-printer
-
-printer name
-
-public
-
-read only
-
-read list
-
-revalidate
-
-root postexec
-
-root preexec
-
-set directory
-
-share modes
-
-short preserve case
-
-strict locking
-
-sync always
-
-user
-
-username
-
-users
-
-valid users
-
-volume
-
-wide links
-
-writable
-
-write ok
-
-writeable
-
-write list
-
-.SS EXPLANATION OF EACH PARAMETER
-.RS 3
-
-.SS admin users (G)
-
-This is a list of users who will be granted administrative privileges
-on the share. This means that they will do all file operations as the
-super-user (root).
-
-You should use this option very carefully, as any user in this list
-will be able to do anything they like on the share, irrespective of
-file permissions.
-
-.B Default:
- no admin users
-
-.B Example:
- admin users = jason
-
-.SS auto services (G)
-This is a list of services that you want to be automatically added to
-the browse lists. This is most useful for homes and printers services
-that would otherwise not be visible.
-
-Note that if you just want all printers in your printcap file loaded
-then the "load printers" option is easier.
-
-.B Default:
- no auto services
-
-.B Example:
- auto services = fred lp colorlp
-
-.SS allow hosts (S)
-A synonym for this parameter is 'hosts allow'.
-
-This parameter is a comma delimited set of hosts which are permitted to access
-a services. If specified in the [global] section, matching hosts will be
-allowed access to any service that does not specifically exclude them from
-access. Specific services my have their own list, which override those
-specified in the [global] section.
-
-You can specify the hosts by name or IP number. For example, you could
-restrict access to only the hosts on a Class C subnet with something like
-"allow hosts = 150.203.5.". The full syntax of the list is described in
-the man page
-.BR hosts_access (5).
-
-You can also specify hosts by network/netmask pairs and by netgroup
-names if your system supports netgroups. The EXCEPT keyword can also
-be used to limit a wildcard list. The following examples may provide
-some help:
-
-Example 1: allow all IPs in 150.203.*.* except one
-
- hosts allow = 150.203. EXCEPT 150.203.6.66
-
-Example 2: allow hosts that match the given network/netmask
-
- hosts allow = 150.203.15.0/255.255.255.0
-
-Example 3: allow a couple of hosts
-
- hosts allow = lapland, arvidsjaur
-
-Example 4: allow only hosts in netgroup "foonet" or localhost, but
-deny access from one particular host
-
- hosts allow = @foonet, localhost
- hosts deny = pirate
-
-Note that access still requires suitable user-level passwords.
-
-See
-.BR testparm (1)
-for a way of testing your host access to see if it
-does what you expect.
-
-.B Default:
- none (i.e., all hosts permitted access)
-
-.B Example:
- allow hosts = 150.203.5. myhost.mynet.edu.au
-
-.SS alternate permissions (S)
-
-This option affects the way the "read only" DOS attribute is produced
-for UNIX files. If this is false then the read only bit is set for
-files on writeable shares which the user cannot write to.
-
-If this is true then it is set for files whos user write bit is not set.
-
-The latter behaviour is useful for when users copy files from each
-others directories, and use a file manager that preserves
-permissions. Without this option they may get annoyed as all copied
-files will have the "read only" bit set.
-
-.B Default:
- alternate permissions = no
-
-.B Example:
- alternate permissions = yes
-
-.SS available (S)
-This parameter lets you 'turn off' a service. If 'available = no', then
-ALL attempts to connect to the service will fail. Such failures are logged.
-
-.B Default:
- available = yes
-
-.B Example:
- available = no
-.SS browseable (S)
-This controls whether this share is seen in the list of available
-shares in a net view and in the browse list.
-
-.B Default:
- browseable = Yes
-
-.B Example:
- browseable = No
-.SS browse list(G)
-This controls whether the smbd will serve a browse list to a client
-doing a NetServerEnum call. Normally set to true. You should never
-need to change this.
-
-.B Default:
- browse list = Yes
-
-.SS case sensitive (G)
-See the discussion on NAME MANGLING.
-
-.SS case sig names (G)
-See "case sensitive"
-
-.SS character set (G)
-This allows a smbd to map incoming characters from a DOS 850 Code page
-to either a Western European (ISO8859-1) or Easter European (ISO8859-2)
-code page. Normally not set, meaning no filename translation is done.
-
-.B Default
-
- character set =
-
-.B Example
-
- character set = iso8859-1
-
-.SS client code page (G)
-Currently (Samba 1.9.17 and above) this may be set to one of two
-values, 850 or 437. It specifies the base DOS code page that the
-clients accessing Samba are using. To determine this, open a DOS
-command prompt and type the command "chcp". This will output the
-code page. The default for USA MS-DOS, Windows 95, and Windows NT
-releases is code page 437. The default for western european
-releases of the above operating systems is code page 850.
-
-This parameter co-operates with the "valid chars" parameter in
-determining what characters are valid in filenames and how
-capitalization is done. It has been added as a convenience for
-clients whose code page is either 437 or 850 so a convoluted
-"valid chars" string does not have to be determined. If you
-set both this parameter and the "valid chars" parameter the
-"client code page" parameter MUST be set before the "valid chars"
-in the smb.conf file. The "valid chars" string will then augment
-the character settings in the "client code page" parameter.
-
-If "client code page" is set to a value other than 850 or 437
-it will default to 850.
-
-See also : "valid chars".
-
-.B Default
-
- client code page = 850
-
-.B Example
-
- client code page = 437
-
-.SS comment (S)
-This is a text field that is seen when a client does a net view to
-list what shares are available. It will also be used when browsing is
-fully supported.
-
-.B Default:
- No comment string
-
-.B Example:
- comment = Fred's Files
-
-.SS config file (G)
-
-This allows you to override the config file to use, instead of the
-default (usually smb.conf). There is a chicken and egg problem here as
-this option is set in the config file!
-
-For this reason, if the name of the config file has changed when the
-parameters are loaded then it will reload them from the new config
-file.
-
-This option takes the usual substitutions, which can be very useful.
-
-If the config file doesn't exist then it won't be loaded (allowing
-you to special case the config files of just a few clients).
-
-.B Example:
- config file = /usr/local/samba/lib/smb.conf.%m
-
-.SS copy (S)
-This parameter allows you to 'clone' service entries. The specified
-service is simply duplicated under the current service's name. Any
-parameters specified in the current section will override those in the
-section being copied.
-
-This feature lets you set up a 'template' service and create similar
-services easily. Note that the service being copied must occur earlier
-in the configuration file than the service doing the copying.
-
-.B Default:
- none
-
-.B Example:
- copy = otherservice
-.SS create mask (S)
-A synonym for this parameter is 'create mode'.
-
-This parameter is the octal modes which are used when converting DOS modes
-to UNIX modes.
-
-When a file is created, the neccessary permissions are calculated
-according to the mapping from DOS modes to UNIX permissions, and
-the resulting UNIX mode is then bit-wise 'AND'ed with this parameter.
-This parameter may be thought of as a bit-wise MASK for the UNIX
-modes of a file. Any bit *not* set here will be removed from the
-modes set on a file when it is created.
-
-The default value of this parameter removes the 'user' execute
-bit and the 'group' and 'other' write and execute bits from the
-UNIX modes.
-
-Following this Samba will bit-wise 'OR' the UNIX mode created from
-this parameter with the value of the "force create mode" parameter
-which is set to 0700 by default. This causes the 'user' read, write
-and execute bits to be set for every file created. You must have at
-least 'user' read, write and execute bits set for Samba to work properly.
-
-For Samba 1.9.17 and above this parameter no longer affects directory
-modes. See the parameter 'directory mode' for details.
-
-See also the "force create mode" parameter for forcing particular
-mode bits to be set on created files.
-See also the "directory mode" paramter for masking mode bits on created
-directories.
-
-.B Default:
- create mask = 0644
-
-.B Example:
- create mask = 0775
-.SS create mode (S)
-See
-.B create mask.
-
-.SS dead time (G)
-The value of the parameter (a decimal integer) represents the number of
-minutes of inactivity before a connection is considered dead, and it
-is disconnected. The deadtime only takes effect if the number of open files
-is zero.
-
-This is useful to stop a server's resources being exhausted by a large
-number of inactive connections.
-
-Most clients have an auto-reconnect feature when a connection is broken so
-in most cases this parameter should be transparent to users.
-
-Using this parameter with a timeout of a few minutes is recommended
-for most systems.
-
-A deadtime of zero indicates that no auto-disconnection should be performed.
-
-.B Default:
- dead time = 0
-
-.B Example:
- dead time = 15
-.SS debug level (G)
-The value of the parameter (an integer) allows the debug level
-(logging level) to be specified in the
-.B smb.conf
-file. This is to give
-greater flexibility in the configuration of the system.
-
-The default will be the debug level specified on the command line.
-
-.B Example:
- debug level = 3
-.SS default (G)
-See
-.B default service.
-.SS default case (S)
-
-See the section on "NAME MANGLING" Also note the addition of "short
-preserve case"
-
-.SS default service (G)
-A synonym for this parameter is 'default'.
-
-This parameter specifies the name of a service which will be connected to
-if the service actually requested cannot be found. Note that the square
-brackets are NOT given in the parameter value (see example below).
-
-There is no default value for this parameter. If this parameter is not given,
-attempting to connect to a nonexistent service results in an error.
-
-Typically the default service would be a public, read-only service.
-
-Also note that as of 1.9.14 the apparent service name will be changed to
-equal that of the requested service, this is very useful as it allows
-you to use macros like %S to make a wildcard service.
-
-Note also that any _ characters in the name of the service used in the
-default service will get mapped to a /. This allows for interesting
-things.
-
-
-.B Example:
- default service = pub
-
- [pub]
- path = /%S
-
-
-.SS delete readonly (S)
-This parameter allows readonly files to be deleted. This is not normal DOS
-semantics, but is allowed by UNIX.
-
-This option may be useful for running applications such as rcs, where UNIX
-file ownership prevents changing file permissions, and DOS semantics prevent
-deletion of a read only file.
-
-.B Default:
- delete readonly = No
-
-.B Example:
- delete readonly = Yes
-.SS deny hosts (S)
-A synonym for this parameter is 'hosts deny'.
-
-The opposite of 'allow hosts' - hosts listed here are NOT permitted
-access to services unless the specific services have their own lists to
-override this one. Where the lists conflict, the 'allow' list takes precedence.
-
-.B Default:
- none (i.e., no hosts specifically excluded)
-
-.B Example:
- deny hosts = 150.203.4. badhost.mynet.edu.au
-.SS dfree command (G)
-The dfree command setting should only be used on systems where a
-problem occurs with the internal disk space calculations. This has
-been known to happen with Ultrix, but may occur with other operating
-systems. The symptom that was seen was an error of "Abort Retry
-Ignore" at the end of each directory listing.
-
-This setting allows the replacement of the internal routines to
-calculate the total disk space and amount available with an external
-routine. The example below gives a possible script that might fulfill
-this function.
-
-The external program will be passed a single parameter indicating a
-directory in the filesystem being queried. This will typically consist
-of the string "./". The script should return two integers in ascii. The
-first should be the total disk space in blocks, and the second should
-be the number of available blocks. An optional third return value
-can give the block size in bytes. The default blocksize is 1024 bytes.
-
-Note: Your script should NOT be setuid or setgid and should be owned by
-(and writable only by) root!
-
-.B Default:
- By default internal routines for determining the disk capacity
-and remaining space will be used.
-
-.B Example:
- dfree command = /usr/local/samba/bin/dfree
-
- Where the script dfree (which must be made executable) could be
-
-.nf
- #!/bin/sh
- df $1 | tail -1 | awk '{print $2" "$4}'
-.fi
-
- or perhaps (on Sys V)
-
-.nf
- #!/bin/sh
- /usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
-.fi
-
- Note that you may have to replace the command names with full
-path names on some systems.
-.SS directory (S)
-See
-.B path.
-
-.SS directory mask (S)
-A synonym for this parameter is 'directory mode'.
-
-This parameter is the octal modes which are used when converting DOS modes
-to UNIX modes when creating UNIX directories.
-
-When a directory is created, the neccessary permissions are calculated
-according to the mapping from DOS modes to UNIX permissions, and
-the resulting UNIX mode is then bit-wise 'AND'ed with this parameter.
-This parameter may be thought of as a bit-wise MASK for the UNIX
-modes of a directory. Any bit *not* set here will be removed from the
-modes set on a directory when it is created.
-
-The default value of this parameter removes the 'group' and 'other'
-write bits from the UNIX mode.
-
-Following this Samba will bit-wise 'OR' the UNIX mode created from
-this parameter with the value of the "force directory mode" parameter.
-This parameter is set to 000 by default (ie. no extra mode bits are added).
-
-See the "force directory mode" parameter to cause particular mode
-bits to always be set on created directories.
-
-See also the "create mode" parameter for masking mode bits on created
-files.
-
-.B Default:
- directory mask = 0755
-
-.B Example:
- directory mask = 0775
-.SS directory mode (S)
-See
-.B directory mask.
-.SS domain controller (G)
-
-Specifies the DNS name or IP address of the machine to refer domain
-logons from Win95 machines to. You should never need to set this parameter.
-
-.B Default:
- domain controller =
-
-.SS domain master (G)
-
-Enable WAN-wide browse list collation. Local master browsers on
-broadcast-isolated subnets will give samba their local browse lists, and
-ask for a complete copy of the browse list for the whole wide area network.
-Browser clients will then contact their local master browser, and will
-receive the domain-wide browse list, instead of just the list for their
-broadcast-isolated subnet.
-
-.B Default:
- domain master = no
-
-.SS dont descend (S)
-There are certain directories on some systems (eg., the /proc tree under
-Linux) that are either not of interest to clients or are infinitely deep
-(recursive). This parameter allows you to specify a comma-delimited list
-of directories that the server should always show as empty.
-
-Note that Samba can be very fussy about the exact format of the "dont
-descend" entries. For example you may need "./proc" instead of just
-"/proc". Experimentation is the best policy :-)
-
-.B Default:
- none (i.e., all directories are OK to descend)
-
-.B Example:
- dont descend = /proc,/dev
-
-.SS encrypt passwords (G)
-
-This boolean controls whether encrypted passwords will be negotiated
-with the client. Note that this option has no effect if you haven't
-compiled in the necessary des libraries and encryption code. It
-defaults to no.
-
-.SS exec (S)
-
-This is an alias for preexec
-
-.SS fake oplocks (S)
-
-Oplocks are the way that SMB clients get permission from a server to
-locally cache file operations. If a server grants an oplock
-(opportunistic lock) then the client is free to assume that it is the
-only one accessing the file and it will aggressively cache file
-data. With some oplock types the client may even cache file open/close
-operations. This can give enormous performance benefits.
-
-Samba does not support opportunistic locks because they are very
-difficult to do under Unix. Samba can fake them, however, by granting
-a oplock whenever a client asks for one. This is controlled using the
-smb.conf option "fake oplocks". If you set "fake oplocks = yes" then
-you are telling the client that it may aggressively cache the file
-data.
-
-By enabling this option on all read-only shares or shares that you know
-will only be accessed from one client at a time you will see a big
-performance improvement on many operations. If you enable this option
-on shares where multiple clients may be accessing the files read-write
-at the same time you can get data corruption. Use this option
-carefully!
-
-This option is disabled by default.
-
-.SS force create mode (S)
-This parameter specifies a set of UNIX mode bit permissions that
-will *always* be set on a file created by Samba. This is done
-by bitwise 'OR'ing these bits onto the mode bits of a file that
-is being created. The default for this parameter is (in octel)
-0700 as files must have at least 'user' read/write/execute bits
-set for Samba to work correctly. This operation is done after
-the mode mask in the parameter "create mask" is applied.
-
-See also the parameter "create mask" for details on masking mode
-bits on created files.
-
-.B Default:
- force create mode = 0700
-
-.B Example:
- force create mode = 0755
-
-would force all created files to have read and execute permissions
-set for 'group' and 'other' as well as the read/write/execute bits
-set for the 'user'.
-
-.SS force directory mode (S)
-This parameter specifies a set of UNIX mode bit permissions that
-will *always* be set on a directory created by Samba. This is done
-by bitwise 'OR'ing these bits onto the mode bits of a directory that
-is being created. The default for this parameter is (in octel)
-0000 which will not add any extra permission bits to a created
-directory. This operation is done after the mode mask in the parameter
-"directory mask" is applied.
-
-See also the parameter "directory mask" for details on masking mode
-bits on created directories.
-
-.B Default:
- force directory mode = 000
-
-.B Example:
- force directory mode = 0755
-
-would force all created directories to have read and execute permissions
-set for 'group' and 'other' as well as the read/write/execute bits
-set for the 'user'.
-
-.SS force group (S)
-This specifies a group name that all connections to this service
-should be made as. This may be useful for sharing files.
-
-.B Default:
- no forced group
-
-.B Example:
- force group = agroup
-
-.SS force user (S)
-This specifies a user name that all connections to this service
-should be made as. This may be useful for sharing files. You should
-also use it carefully as using it incorrectly can cause security
-problems.
-
-This user name only gets used once a connection is established. Thus
-clients still need to connect as a valid user and supply a valid
-password. Once connected, all file operations will be performed as the
-"forced user", not matter what username the client connected as.
-
-.B Default:
- no forced user
-
-.B Example:
- force user = auser
-
-.SS getwd cache (G)
-This is a tuning option. When this is enabled a cacheing algorithm will
-be used to reduce the time taken for getwd() calls. This can have a
-significant impact on performance, especially when widelinks is False.
-
-.B Default:
- getwd cache = No
-
-.B Example:
- getwd cache = Yes
-
-.SS group (S)
-This is an alias for "force group" and is only kept for compatibility
-with old versions of Samba. It may be removed in future versions.
-
-.SS guest account (S)
-This is a username which will be used for access to services which are
-specified as 'guest ok' (see below). Whatever privileges this user has
-will be available to any client connecting to the guest
-service. Typically this user will exist in the password file, but will
-not have a valid login. If a username is specified in a given service,
-the specified username overrides this one.
-
-One some systems the account "nobody" may not be able to print. Use
-another account in this case. You should test this by trying to log in
-as your guest user (perhaps by using the "su \-" command) and trying to
-print using
-.BR lpr .
-
-Note that as of version 1.9 of Samba this option may be set
-differently for each service.
-
-.B Default:
- specified at compile time
-
-.B Example:
- guest account = nobody
-.SS guest ok (S)
-See
-.B public.
-.SS guest only (S)
-If this parameter is 'yes' for a service, then only guest connections to the
-service are permitted. This parameter will have no affect if "guest ok" or
-"public" is not set for the service.
-
-See the section below on user/password validation for more information about
-this option.
-
-.B Default:
- guest only = no
-
-.B Example:
- guest only = yes
-.SS hide dot files (S)
-This is a boolean parameter that controls whether files starting with
-a dot appear as hidden files.
-
-.B Default:
- hide dot files = yes
-
-.B Example:
- hide dot files = no
-.SS homedir map (G)
-If "nis homedir" is true, this parameter specifies the NIS (or YP) map
-from which the server for the user's home directory should be extracted.
-At present, only the Sun auto.home map format is understood. The form of
-the map is:
-
-username server:/some/file/system
-
-and the program will extract the servername from before the first ':'.
-There should probably be a better parsing system that copes with different
-map formats and also Amd (another automounter) maps.
-
-NB: The -DNETGROUP option is required in the Makefile for option to work
-and on some architectures the line -lrpcsvc needs to be added to the
-LIBSM variable. This is required for Solaris 2, FreeBSD and HPUX.
-
-See also "nis homedir"
-
-.B Default:
- homedir map = auto.home
-
-.B Example:
- homedir map = amd.homedir
-.SS hosts allow (S)
-See
-.B allow hosts.
-.SS hosts deny (S)
-See
-.B deny hosts.
-
-.SS hosts equiv (G)
-If this global parameter is a non-null string, it specifies the name of
-a file to read for the names of hosts and users who will be allowed access
-without specifying a password.
-
-This is not be confused with
-.B allow hosts
-which is about hosts access to services and is more useful for guest services.
-.B hosts equiv
-may be useful for NT clients which will not supply passwords to samba.
-
-NOTE: The use of hosts.equiv can be a major security hole. This is
-because you are trusting the PC to supply the correct username. It is
-very easy to get a PC to supply a false username. I recommend that the
-hosts.equiv option be only used if you really know what you are doing,
-or perhaps on a home network where you trust your wife and kids :-)
-
-.B Default
- No host equivalences
-
-.B Example
- hosts equiv = /etc/hosts.equiv
-
-.SS include (G)
-
-This allows you to include one config file inside another. The file is
-included literally, as though typed in place.
-
-It takes the standard substitutions, except %u, %P and %S
-
-.SS interfaces (G)
-
-This option allows you to setup multiple network interfaces, so that
-Samba can properly handle browsing on all interfaces.
-
-The option takes a list of ip/netmask pairs. The netmask may either be
-a bitmask, or a bitlength.
-
-For example, the following line:
-
-interfaces = 192.168.2.10/24 192.168.3.10/24
-
-would configure two network interfaces with IP addresses 192.168.2.10
-and 192.168.3.10. The netmasks of both interfaces would be set to
-255.255.255.0.
-
-You could produce an equivalent result by using:
-
-interfaces = 192.168.2.10/255.255.255.0 192.168.3.10/255.255.255.0
-
-if you prefer that format.
-
-If this option is not set then Samba will attempt to find a primary
-interface, but won't attempt to configure more than one interface.
-
-.SS invalid users (S)
-This is a list of users that should not be allowed to login to this
-service. This is really a "paranoid" check to absolutely ensure an
-improper setting does not breach your security.
-
-A name starting with @ is interpreted as a UNIX group.
-
-The current servicename is substituted for %S. This is useful in the
-[homes] section.
-
-See also "valid users"
-
-.B Default
- No invalid users
-
-.B Example
- invalid users = root fred admin @wheel
-
-.SS keep alive (G)
-The value of the parameter (an integer) represents the number of seconds
-between 'keepalive' packets. If this parameter is zero, no keepalive packets
-will be sent. Keepalive packets, if sent, allow the server to tell whether a
-client is still present and responding.
-
-Keepalives should, in general, not be needed if the socket being used
-has the SO_KEEPALIVE attribute set on it (see "socket
-options"). Basically you should only use this option if you strike
-difficulties.
-
-.B Default:
- keep alive = 0
-
-.B Example:
- keep alive = 60
-.SS load printers (G)
-A boolean variable that controls whether all printers in the printcap
-will be loaded for browsing by default.
-
-.B Default:
- load printers = no
-
-.B Example:
- load printers = yes
-
-.SS local master (G)
-This option allows the nmbd to become a local master browser on a
-subnet. If set to False then nmbd will not attempt to become a local
-master browser on a subnet and will also lose in all browsing elections.
-By default this value is set to true. Setting this value to true doesn't
-mean that Samba will become the local master browser on a subnet, just
-that the nmbd will participate in elections for local master browser.
-
-.B Default:
- local master = yes
-
-.SS lock directory (G)
-This option specifies the directory where lock files will be placed.
-The lock files are used to implement the "max connections" option.
-
-.B Default:
- lock directory = /tmp/samba
-
-.B Example:
- lock directory = /usr/local/samba/var/locks
-.SS locking (S)
-This controls whether or not locking will be performed by the server in
-response to lock requests from the client.
-
-If "locking = no", all lock and unlock requests will appear to succeed and
-all lock queries will indicate that the queried lock is clear.
-
-If "locking = yes", real locking will be performed by the server.
-
-This option may be particularly useful for read-only filesystems which
-do not need locking (such as cdrom drives).
-
-Be careful about disabling locking either globally or in a specific
-service, as lack of locking may result in data corruption.
-
-.B Default:
- locking = yes
-
-.B Example:
- locking = no
-
-.SS log file (G)
-
-This options allows you to override the name of the Samba log file
-(also known as the debug file).
-
-This option takes the standard substitutions, allowing you to have
-separate log files for each user or machine.
-
-.B Example:
- log file = /usr/local/samba/var/log.%m
-
-.SS log level (G)
-see "debug level"
-
-.SS logon path (G)
-
-This parameter specifies the home directory where roaming profiles
-(USER.DAT / USER.MAN files) are stored.
-
-This option takes the standard substitutions, allowing you to have
-separate logon scripts for each user or machine. It also specifies
-the directory from which the "desktop", "start menu", "nethood" and
-"programs" folders, and their contents, are loaded and displayed
-on your Windows 95 client.
-
-The share and the path must be readable by the user for the preferences
-and directories to be loaded onto the Windows 95 client. The share
-must be writeable when the logs in for the first time, in order that
-the Windows 95 client can create the user.dat and other directories.
-
-Thereafter, the directories and any of contents can, if required,
-be made read-only. It is not adviseable that the USER.DAT file be made
-read-only - rename it to USER.MAN to achieve the desired effect
-(a MANdatory profile).
-
-.B Default:
- logon path = \\\\%L\\%U
-
-.B Example:
- logon path = \\\\PROFILESERVER\\HOME_DIR\\%U
-
-.SS logon script (G)
-
-This parameter specifies the batch file (.bat) or NT command file (.cmd)
-to be downloaded and run on a machine when a user successfully logs in.
-The file must contain the DOS style cr/lf line endings. Using a DOS-style
-editor to create the file is recommended.
-
-The script must be a relative path to the [netlogon] service. If the
-[netlogon] service specifies a path of /usr/local/samba/netlogon, and
-logon script = STARTUP.BAT, then file that will be downloaded is:
-
-.B /usr/local/samba/netlogon/STARTUP.BAT
-
-The contents of the batch file is entirely your choice. A suggested
-command would be to add NET TIME \\\\SERVER /SET /YES, to force every
-machine to synchronise clocks with the same time server. Another use
-would be to add NET USE U: \\\\SERVER\\UTILS for commonly used utilities,
-or NET USE Q: \\\\SERVER\\ISO9001_QA.
-
-Note that it is particularly important not to allow write access to
-the [netlogon] share, or to grant users write permission on the
-batch files in a secure environment, as this would allow the batch
-files to be arbitrarily modified.
-
-.B
-This option takes the standard substitutions, allowing you to have
-separate logon scripts for each user or machine.
-
-.B Example:
- logon script = scripts/%U.bat
-
-.SS lppause command (S)
-This parameter specifies the command to be executed on the server host in
-order to stop printing or spooling a specific print job.
-
-This command should be a program or script which takes a printer name and
-job number to pause the print job. Currently I don't know of any print
-spooler system that can do this with a simple option, except for the PPR
-system from Trinity College (ppr\-dist.trincoll.edu/pub/ppr). One way
-of implementing this is by using job priorities, where jobs having a too
-low priority won't be sent to the printer. See also the
-.B lppause
-command.
-
-If a %p is given then the printername is put in its place. A %j is
-replaced with the job number (an integer).
-On HPUX (see printing=hpux), if the -p%p option is added to the lpq
-command, the job will show up with the correct status, i.e. if the job
-priority is lower than the set fence priority it will have the PAUSED
-status, whereas if the priority is equal or higher it will have the
-SPOOLED or PRINTING status.
-
-Note that it is good practice to include the absolute path in the lppause
-command as the PATH may not be available to the server.
-
-.B Default:
- Currently no default value is given to this string
-
-.B Example for HPUX:
- lppause command = /usr/bin/lpalt %p-%j -p0
-
-.SS lpq cache time (G)
-
-This controls how long lpq info will be cached for to prevent the lpq
-command being called too often. A separate cache is kept for each
-variation of the lpq command used by the system, so if you use
-different lpq commands for different users then they won't share cache
-information.
-
-The cache files are stored in /tmp/lpq.xxxx where xxxx is a hash
-of the lpq command in use.
-
-The default is 10 seconds, meaning that the cached results of a
-previous identical lpq command will be used if the cached data is less
-than 10 seconds old. A large value may be advisable if your lpq
-command is very slow.
-
-A value of 0 will disable cacheing completely.
-
-.B Default:
- lpq cache time = 10
-
-.B Example:
- lpq cache time = 30
-
-.SS lpq command (S)
-This parameter specifies the command to be executed on the server host in
-order to obtain "lpq"-style printer status information.
-
-This command should be a program or script which takes a printer name
-as its only parameter and outputs printer status information.
-
-Currently six styles of printer status information are supported; BSD,
-SYSV, AIX, HPUX, QNX, LPRNG and PLP. This covers most UNIX systems. You
-control which type is expected using the "printing =" option.
-
-Some clients (notably Windows for Workgroups) may not correctly send the
-connection number for the printer they are requesting status information
-about. To get around this, the server reports on the first printer service
-connected to by the client. This only happens if the connection number sent
-is invalid.
-
-If a %p is given then the printername is put in its place. Otherwise
-it is placed at the end of the command.
-
-Note that it is good practice to include the absolute path in the lpq
-command as the PATH may not be available to the server.
-
-.B Default:
- depends on the setting of "printing ="
-
-.B Example:
- lpq command = /usr/bin/lpq %p
-
-.SS lpresume command (S)
-This parameter specifies the command to be executed on the server host in
-order to restart or continue printing or spooling a specific print job.
-
-This command should be a program or script which takes a printer name and
-job number to resume the print job. See also the lppause command.
-
-If a %p is given then the printername is put in its place. A %j is
-replaced with the job number (an integer).
-
-Note that it is good practice to include the absolute path in the lpresume
-command as the PATH may not be available to the server.
-
-.B Default:
- Currently no default value is given to this string
-
-.B Example for HPUX:
- lpresume command = /usr/bin/lpalt %p-%j -p2
-
-.SS lprm command (S)
-This parameter specifies the command to be executed on the server host in
-order to delete a print job.
-
-This command should be a program or script which takes a printer name
-and job number, and deletes the print job.
-
-Currently seven styles of printer control are supported; BSD, SYSV, AIX
-HPUX, QNX, LPRNG and PLP. This covers most UNIX systems. You control
-which type is expected using the "printing =" option.
-
-If a %p is given then the printername is put in its place. A %j is
-replaced with the job number (an integer).
-
-Note that it is good practice to include the absolute path in the lprm
-command as the PATH may not be available to the server.
-
-.B Default:
- depends on the setting of "printing ="
-
-.B Example 1:
- lprm command = /usr/bin/lprm -P%p %j
-
-.B Example 2:
- lprm command = /usr/bin/cancel %p-%j
-
-.SS magic output (S)
-This parameter specifies the name of a file which will contain output
-created by a magic script (see
-.I magic script
-below).
-
-Warning: If two clients use the same magic script in the same directory the
-output file content is undefined.
-.B Default:
- magic output = .out
-
-.B Example:
- magic output = myfile.txt
-.SS magic script (S)
-This parameter specifies the name of a file which, if opened, will be
-executed by the server when the file is closed. This allows a UNIX script
-to be sent to the Samba host and executed on behalf of the connected user.
-
-Scripts executed in this way will be deleted upon completion, permissions
-permitting.
-
-If the script generates output, output will be sent to the file specified by
-the
-.I magic output
-parameter (see above).
-
-Note that some shells are unable to interpret scripts containing
-carriage-return-linefeed instead of linefeed as the end-of-line
-marker. Magic scripts must be executable "as is" on the host, which
-for some hosts and some shells will require filtering at the DOS end.
-
-Magic scripts are EXPERIMENTAL and should NOT be relied upon.
-
-.B Default:
- None. Magic scripts disabled.
-
-.B Example:
- magic script = user.csh
-
-.SS mangle case (S)
-
-See the section on "NAME MANGLING"
-
-.SS mangled map (S)
-This is for those who want to directly map UNIX file names which are
-not representable on DOS. The mangling of names is not always what is
-needed. In particular you may have documents with file extensions
-that differ between DOS and UNIX. For example, under UNIX it is common
-to use .html for HTML files, whereas under DOS .htm is more commonly
-used.
-
-So to map 'html' to 'htm' you put:
-
- mangled map = (*.html *.htm)
-
-One very useful case is to remove the annoying ;1 off the ends of
-filenames on some CDROMS (only visible under some UNIXes). To do this
-use a map of (*;1 *)
-
-.B default:
- no mangled map
-
-.B Example:
- mangled map = (*;1 *)
-
-.SS mangled names (S)
-This controls whether non-DOS names under UNIX should be mapped to
-DOS-compatible names ("mangled") and made visible, or whether non-DOS names
-should simply be ignored.
-
-See the section on "NAME MANGLING" for details on how to control the
-mangling process.
-
-If mangling is used then the mangling algorithm is as follows:
-.RS
-- the first (up to) five alphanumeric characters before the rightmost dot of
-the filename are preserved, forced to upper case, and appear as the first (up
-to) five characters of the mangled name.
-
-- a tilde ("~") is appended to the first part of the mangled name, followed
-by a two-character unique sequence, based on the original root name
-(i.e., the original filename minus its final extension). The final
-extension is included in the hash calculation only if it contains any upper
-case characters or is longer than three characters.
-
-Note that the character to use may be specified using the "mangling
-char" option, if you don't like ~.
-
-- the first three alphanumeric characters of the final extension are preserved,
-forced to upper case and appear as the extension of the mangled name. The
-final extension is defined as that part of the original filename after the
-rightmost dot. If there are no dots in the filename, the mangled name will
-have no extension (except in the case of hidden files - see below).
-
-- files whose UNIX name begins with a dot will be presented as DOS hidden
-files. The mangled name will be created as for other filenames, but with the
-leading dot removed and "___" as its extension regardless of actual original
-extension (that's three underscores).
-.RE
-
-The two-digit hash value consists of upper case alphanumeric characters.
-
-This algorithm can cause name collisions only if files in a directory share
-the same first five alphanumeric characters. The probability of such a clash
-is 1/1300.
-
-The name mangling (if enabled) allows a file to be copied between UNIX
-directories from DOS while retaining the long UNIX filename. UNIX files can
-be renamed to a new extension from DOS and will retain the same basename.
-Mangled names do not change between sessions.
-
-.B Default:
- mangled names = yes
-
-.B Example:
- mangled names = no
-.SS mangling char (S)
-This controls what character is used as the "magic" character in name
-mangling. The default is a ~ but this may interfere with some
-software. Use this option to set it to whatever you prefer.
-
-.B Default:
- mangling char = ~
-
-.B Example:
- mangling char = ^
-
-.SS mangled stack (G)
-This parameter controls the number of mangled names that should be cached in
-the Samba server.
-
-This stack is a list of recently mangled base names (extensions are only
-maintained if they are longer than 3 characters or contains upper case
-characters).
-
-The larger this value, the more likely it is that mangled names can be
-successfully converted to correct long UNIX names. However, large stack
-sizes will slow most directory access. Smaller stacks save memory in the
-server (each stack element costs 256 bytes).
-
-It is not possible to absolutely guarantee correct long file names, so
-be prepared for some surprises!
-
-.B Default:
- mangled stack = 50
-
-.B Example:
- mangled stack = 100
-
-.SS map archive (S)
-This controls whether the DOS archive attribute should be mapped to UNIX
-execute bits. The DOS archive bit is set when a file has been modified
-since its last backup. One motivation for this option it to keep Samba/your
-PC from making any file it touches from becoming executable under UNIX.
-This can be quite annoying for shared source code, documents, etc...
-
-.B Default:
- map archive = yes
-
-.B Example:
- map archive = no
-
-.SS map hidden (S)
-This controls whether DOS style hidden files should be mapped to UNIX
-execute bits.
-
-.B Default:
- map hidden = no
-
-.B Example:
- map hidden = yes
-.SS map system (S)
-This controls whether DOS style system files should be mapped to UNIX
-execute bits.
-
-.B Default:
- map system = no
-
-.B Example:
- map system = yes
-.SS max connections (S)
-This option allows the number of simultaneous connections to a
-service to be limited. If "max connections" is greater than 0 then
-connections will be refused if this number of connections to the
-service are already open. A value of zero mean an unlimited number of
-connections may be made.
-
-Record lock files are used to implement this feature. The lock files
-will be stored in the directory specified by the "lock directory" option.
-
-.B Default:
- max connections = 0
-
-.B Example:
- max connections = 10
-
-.SS max disk size (G)
-This option allows you to put an upper limit on the apparent size of
-disks. If you set this option to 100 then all shares will appear to be
-not larger than 100 MB in size.
-
-Note that this option does not limit the amount of data you can put on
-the disk. In the above case you could still store much more than 100
-MB on the disk, but if a client ever asks for the amount of free disk
-space or the total disk size then the result will be bounded by the
-amount specified in "max disk size".
-
-This option is primarily useful to work around bugs in some pieces of
-software that can't handle very large disks, particularly disks over
-1GB in size.
-
-A "max disk size" of 0 means no limit.
-
-.B Default:
- max disk size = 0
-
-.B Example:
- max disk size = 1000
-
-.SS max log size (G)
-
-This option (an integer in kilobytes) specifies the max size the log
-file should grow to. Samba periodically checks the size and if it is
-exceeded it will rename the file, adding a .old extension.
-
-A size of 0 means no limit.
-
-.B Default:
- max log size = 5000
-
-.B Example:
- max log size = 1000
-
-.SS max mux (G)
-
-This option controls the maximum number of simultaneous reads that
-samba tells the client it will allow. You should never need to set this
-parameter.
-
-.B Default:
- max mux = 2
-
-.SS max packet (G)
-
-A synonym for this parameter is 'packet size'.
-
-.SS max ttl (G)
-
-This option tells nmbd what the default 'time to live' of NetBIOS
-names should be (in seconds). You should never need to change this parameter.
-
-.B Default:
- max ttl = 14400
-.SS max xmit (G)
-
-This option controls the maximum packet size that will be negotiated
-by Samba. The default is 65535, which is the maximum. In some cases
-you may find you get better performance with a smaller value. A value
-below 2048 is likely to cause problems.
-
-.B Default:
- max xmit = 65535
-
-.B Example:
- max xmit = 8192
-
-.SS message command (G)
-
-This specifies what command to run when the server receives a WinPopup
-style message.
-
-This would normally be a command that would deliver the message
-somehow. How this is to be done is up to your imagination.
-
-What I use is:
-
- message command = csh -c 'xedit %s;rm %s' &
-
-This delivers the message using xedit, then removes it
-afterwards. NOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN
-IMMEDIATELY. That's why I have the & on the end. If it doesn't return
-immediately then your PCs may freeze when sending messages (they
-should recover after 30secs, hopefully).
-
-All messages are delivered as the global guest user. The command takes
-the standard substitutions, although %u won't work (%U may be better
-in this case).
-
-Apart from the standard substitutions, some additional ones apply. In
-particular:
-
-%s = the filename containing the message
-
-%t = the destination that the message was sent to (probably the server
-name)
-
-%f = who the message is from
-
-You could make this command send mail, or whatever else takes your
-fancy. Please let me know of any really interesting ideas you have.
-
-Here's a way of sending the messages as mail to root:
-
-message command = /bin/mail -s 'message from %f on %m' root < %s; rm %s
-
-If you don't have a message command then the message won't be
-delivered and Samba will tell the sender there was an
-error. Unfortunately WfWg totally ignores the error code and carries
-on regardless, saying that the message was delivered.
-
-If you want to silently delete it then try "message command = rm %s".
-
-For the really adventurous, try something like this:
-
-message command = csh -c 'csh < %s |& /usr/local/samba/bin/smbclient \e
- -M %m; rm %s' &
-
-this would execute the command as a script on the server, then give
-them the result in a WinPopup message. Note that this could cause a
-loop if you send a message from the server using smbclient! You better
-wrap the above in a script that checks for this :-)
-
-.B Default:
- no message command
-
-.B Example:
- message command = csh -c 'xedit %s;rm %s' &
-
-.SS min print space (S)
-
-This sets the minimum amount of free disk space that must be available
-before a user will be able to spool a print job. It is specified in
-kilobytes. The default is 0, which means no limit.
-
-.B Default:
- min print space = 0
-
-.B Example:
- min print space = 2000
-
-.SS netbios name (G)
-
-This sets the NetBIOS name by which a Samba server is known. By
-default it is the same as the first component of the host's DNS name.
-
-.SS nis homedir (G)
-Get the home share server from a NIS (or YP) map. For unix systems that
-use an automounter, the user's home directory will often be mounted on
-a workstation on demand from a remote server. When the Samba logon server
-is not the actual home directory server, two network hops are required
-to access the home directory and this can be very slow especially with
-writing via Samba to an NFS mounted directory. This option allows samba
-to return the home share as being on a different server to the logon
-server and as long as a samba daemon is running on the home directory
-server, it will be mounted on the Samba client directly from the directory
-server. When Samba is returning the home share to the client, it will
-consult the NIS (or YP) map specified in "homedir map" and return the
-server listed there.
-
-.B Default:
- nis homedir = false
-
-.B Example:
- nis homedir = true
-
-.SS null passwords (G)
-Allow or disallow access to accounts that have null passwords.
-
-.B Default:
- null passwords = no
-
-.B Example:
- null passwords = yes
-
-.SS only guest (S)
-A synonym for this command is 'guest only'.
-
-.SS only user (S)
-This is a boolean option that controls whether connections with
-usernames not in the user= list will be allowed. By default this
-option is disabled so a client can supply a username to be used by
-the server.
-
-Note that this also means Samba won't try to deduce usernames from the
-service name. This can be annoying for the [homes] section. To get
-around this you could use "user = %S" which means your "user" list
-will be just the service name, which for home directories is the name
-of the user.
-
-.B Default:
- only user = False
-
-.B Example:
- only user = True
-
-.SS os level (G)
-This integer value controls what level Samba advertises itself as for
-browse elections. See BROWSING.txt for details.
-
-.SS packet size (G)
-The maximum transmit packet size during a raw read. This option is no
-longer implemented as of version 1.7.00, and is kept only so old
-configuration files do not become invalid.
-
-.SS passwd chat (G)
-This string controls the "chat" conversation that takes places
-between smbd and the local password changing program to change the
-users password. The string describes a sequence of response-receive
-pairs that smbd uses to determine what to send to the passwd program
-and what to expect back. If the expected output is not received then
-the password is not changed.
-
-This chat sequence is often quite site specific, depending on what
-local methods are used for password control (such as NIS+ etc).
-
-The string can contain the macros %o and %n which are substituted for
-the old and new passwords respectively. It can also contain the
-standard macros \en \er \et and \es to give line-feed, carriage-return,
-tab and space.
-
-The string can also contain a * which matches any sequence of
-characters.
-
-Double quotes can be used to collect strings with spaces in them into
-a single string.
-
-If the send string in any part of the chat sequence is a fullstop "."
-then no string is sent. Similarly, is the expect string is a fullstop
-then no string is expected.
-
-.B Example:
- passwd chat = "*Enter OLD password*" %o\en "*Enter NEW password*" %n\en \e
- "*Reenter NEW password*" %n\en "*Password changed*"
-
-
-.B Default:
- passwd chat = *old*password* %o\en *new*password* %n\en *new*password* %n\en *changed*
-
-.SS passwd program (G)
-The name of a program that can be used to set user passwords.
-
-This is only necessary if you have enabled remote password changing at
-compile time. Any occurrences of %u will be replaced with the user
-name.
-
-Also note that many passwd programs insist in "reasonable" passwords,
-such as a minimum length, or the inclusion of mixed case chars and
-digits. This can pose a problem as some clients (such as Windows for
-Workgroups) uppercase the password before sending it.
-
-.B Default:
- passwd program = /bin/passwd
-
-.B Example:
- passwd program = /sbin/passwd %u
-
-.SS password level (G)
-Some client/server combinations have difficulty with mixed-case passwords.
-One offending client is Windows for Workgroups, which for some reason forces
-passwords to upper case when using the LANMAN1 protocol, but leaves them alone
-when using COREPLUS!
-
-This parameter defines the maximum number of characters that may be upper case
-in passwords.
-
-For example, say the password given was "FRED". If
-.B password level
-is set to 1 (one), the following combinations would be tried if "FRED" failed:
-"Fred", "fred", "fRed", "frEd", "freD". If
-.B password level was set to 2 (two), the following combinations would also be
-tried: "FRed", "FrEd", "FreD", "fREd", "fReD", "frED". And so on.
-
-The higher value this parameter is set to the more likely it is that a mixed
-case password will be matched against a single case password. However, you
-should be aware that use of this parameter reduces security and increases the
-time taken to process a new connection.
-
-A value of zero will cause only two attempts to be made - the password as is
-and the password in all-lower case.
-
-If you find the connections are taking too long with this option then
-you probably have a slow crypt() routine. Samba now comes with a fast
-"ufc crypt" that you can select in the Makefile. You should also make
-sure the PASSWORD_LENGTH option is correct for your system in local.h
-and includes.h. On most systems only the first 8 chars of a password
-are significant so PASSWORD_LENGTH should be 8, but on some longer
-passwords are significant. The includes.h file tries to select the
-right length for your system.
-
-.B Default:
- password level = 0
-
-.B Example:
- password level = 4
-
-.SS password server (G)
-
-By specifying the name of another SMB server (such as a WinNT box)
-with this option, and using "security = server" you can get Samba to
-do all its username/password validation via a remote server.
-
-This options sets the name of the password server to use. It must be a
-netbios name, so if the machine's netbios name is different from its
-internet name then you may have to add its netbios name to
-/etc/hosts.
-
-The password server much be a machine capable of using the "LM1.2X002"
-or the "LM NT 0.12" protocol, and it must be in user level security
-mode.
-
-NOTE: Using a password server means your UNIX box (running Samba) is
-only as secure as your password server. DO NOT CHOOSE A PASSWORD
-SERVER THAT YOU DON'T COMPLETELY TRUST.
-
-Never point a Samba server at itself for password serving. This will
-cause a loop and could lock up your Samba server!
-
-The name of the password server takes the standard substitutions, but
-probably the only useful one is %m, which means the Samba server will
-use the incoming client as the password server. If you use this then
-you better trust your clients, and you better restrict them with hosts
-allow!
-
-If you list several hosts in the "password server" option then smbd
-will try each in turn till it finds one that responds. This is useful
-in case your primary server goes down.
-
-.SS path (S)
-A synonym for this parameter is 'directory'.
-
-This parameter specifies a directory to which the user of the service is to
-be given access. In the case of printable services, this is where print data
-will spool prior to being submitted to the host for printing.
-
-For a printable service offering guest access, the service should be readonly
-and the path should be world-writable and have the sticky bit set. This is not
-mandatory of course, but you probably won't get the results you expect if you
-do otherwise.
-
-Any occurrences of %u in the path will be replaced with the username
-that the client is connecting as. Any occurrences of %m will be
-replaced by the name of the machine they are connecting from. These
-replacements are very useful for setting up pseudo home directories
-for users.
-
-Note that this path will be based on 'root dir' if one was specified.
-.B Default:
- none
-
-.B Example:
- path = /home/fred+
-
-.SS postexec (S)
-
-This option specifies a command to be run whenever the service is
-disconnected. It takes the usual substitutions. The command may be run
-as the root on some systems.
-
-An interesting example may be do unmount server resources:
-
-postexec = /etc/umount /cdrom
-
-See also preexec
-
-.B Default:
- none (no command executed)
-
-.B Example:
- postexec = echo \e"%u disconnected from %S from %m (%I)\e" >> /tmp/log
-
-.SS postscript (S)
-This parameter forces a printer to interpret the print files as
-postscript. This is done by adding a %! to the start of print output.
-
-This is most useful when you have lots of PCs that persist in putting
-a control-D at the start of print jobs, which then confuses your
-printer.
-
-.B Default:
- postscript = False
-
-.B Example:
- postscript = True
-
-.SS preexec (S)
-
-This option specifies a command to be run whenever the service is
-connected to. It takes the usual substitutions.
-
-An interesting example is to send the users a welcome message every
-time they log in. Maybe a message of the day? Here is an example:
-
-preexec = csh -c 'echo \e"Welcome to %S!\e" | \e
- /usr/local/samba/bin/smbclient -M %m -I %I' &
-
-Of course, this could get annoying after a while :-)
-
-See also postexec
-
-.B Default:
- none (no command executed)
-
-.B Example:
- preexec = echo \e"%u connected to %S from %m (%I)\e" >> /tmp/log
-
-.SS preferred master (G)
-This boolean parameter controls if Samba is a preferred master browser
-for its workgroup.
-If this is set to true, on startup, samba will force an election,
-and it will have a slight advantage in winning the election.
-It is recommended that this parameter is used in conjunction
-with domain master = yes, so that samba can guarantee becoming
-a domain master.
-
-Use this option with caution, because if there are several hosts
-(whether samba servers, Windows 95 or NT) that are preferred master
-browsers on the same subnet, they will each periodically and continuously
-attempt to become the local master browser. This will result in
-unnecessary broadcast traffic and reduced browsing capabilities.
-
-See
-.B os level = nn
-
-.B Default:
- preferred master = no
-
-.SS preload
-This is an alias for "auto services"
-
-.SS preserve case (S)
-
-This controls if new filenames are created with the case that the
-client passes, or if they are forced to be the "default" case.
-
-.B Default:
- preserve case = no
-
-See the section on "NAME MANGLING" for a fuller discussion.
-
-.SS print command (S)
-After a print job has finished spooling to a service, this command will be
-used via a system() call to process the spool file. Typically the command
-specified will submit the spool file to the host's printing subsystem, but
-there is no requirement that this be the case. The server will not remove the
-spool file, so whatever command you specify should remove the spool file when
-it has been processed, otherwise you will need to manually remove old spool
-files.
-
-The print command is simply a text string. It will be used verbatim,
-with two exceptions: All occurrences of "%s" will be replaced by the
-appropriate spool file name, and all occurrences of "%p" will be
-replaced by the appropriate printer name. The spool file name is
-generated automatically by the server, the printer name is discussed
-below.
-
-The full path name will be used for the filename if %s is not preceded
-by a /. If you don't like this (it can stuff up some lpq output) then
-use %f instead. Any occurrences of %f get replaced by the spool
-filename without the full path at the front.
-
-The print command MUST contain at least one occurrence of "%s" or %f -
-the "%p" is optional. At the time a job is submitted, if no printer
-name is supplied the "%p" will be silently removed from the printer
-command.
-
-If specified in the [global] section, the print command given will be used
-for any printable service that does not have its own print command specified.
-
-If there is neither a specified print command for a printable service nor a
-global print command, spool files will be created but not processed and (most
-importantly) not removed.
-
-Note that printing may fail on some UNIXes from the "nobody"
-account. If this happens then create an alternative guest account that
-can print and set the "guest account" in the [global] section.
-
-You can form quite complex print commands by realising that they are
-just passed to a shell. For example the following will log a print
-job, print the file, then remove it. Note that ; is the usual
-separator for command in shell scripts.
-
-print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s
-
-You may have to vary this command considerably depending on how you
-normally print files on your system.
-
-.B Default:
- print command = lpr -r -P %p %s
-
-.B Example:
- print command = /usr/local/samba/bin/myprintscript %p %s
-.SS print ok (S)
-See
-.B printable.
-.SS printable (S)
-A synonym for this parameter is 'print ok'.
-
-If this parameter is 'yes', then clients may open, write to and submit spool
-files on the directory specified for the service.
-
-Note that a printable service will ALWAYS allow writing to the service path
-(user privileges permitting) via the spooling of print data. The 'read only'
-parameter controls only non-printing access to the resource.
-
-.B Default:
- printable = no
-
-.B Example:
- printable = yes
-
-.SS printcap name (G)
-This parameter may be used to override the compiled-in default printcap
-name used by the server (usually /etc/printcap). See the discussion of the
-[printers] section above for reasons why you might want to do this.
-
-For those of you without a printcap (say on SysV) you can just create a
-minimal file that looks like a printcap and set "printcap name =" in
-[global] to point at it.
-
-A minimal printcap file would look something like this:
-
-print1|My Printer 1
-.br
-print2|My Printer 2
-.br
-print3|My Printer 3
-.br
-print4|My Printer 4
-.br
-print5|My Printer 5
-
-where the | separates aliases of a printer. The fact that the second
-alias has a space in it gives a hint to Samba that it's a comment.
-
-NOTE: Under AIX the default printcap name is "/etc/qconfig". Samba
-will assume the file is in AIX "qconfig" format if the string
-"/qconfig" appears in the printcap filename.
-
-.B Default:
- printcap name = /etc/printcap
-
-.B Example:
- printcap name = /etc/myprintcap
-.SS printer (S)
-A synonym for this parameter is 'printer name'.
-
-This parameter specifies the name of the printer to which print jobs spooled
-through a printable service will be sent.
-
-If specified in the [global] section, the printer name given will be used
-for any printable service that does not have its own printer name specified.
-
-.B Default:
- none (but may be 'lp' on many systems)
-
-.B Example:
- printer name = laserwriter
-
-.SS printer driver (S)
-This option allows you to control the string that clients receive when
-they ask the server for the printer driver associated with a
-printer. If you are using Windows95 or WindowsNT then you can use this
-to automate the setup of printers on your system.
-
-You need to set this parameter to the exact string (case sensitive)
-that describes the appropriate printer driver for your system.
-If you don't know the exact string to use then you should first try
-with no "printer driver" option set and the client will give you a
-list of printer drivers. The appropriate strings are shown in a
-scrollbox after you have chosen the printer manufacturer.
-
-.B Example:
- printer driver = HP LaserJet 4L
-
-.SS printer name (S)
-See
-.B printer.
-
-.SS printing (G)
-This parameters controls how printer status information is interpreted
-on your system, and also affects the default values for the "print
-command", "lpq command" and "lprm command".
-
-Currently six printing styles are supported. They are "printing =
-bsd", "printing = sysv", "printing = hpux", "printing = aix",
-"printing = qnx" and "printing = plp".
-
-To see what the defaults are for the other print commands when using
-these three options use the "testparm" program.
-
-
-.SS protocol (G)
-The value of the parameter (a string) is the highest protocol level that will
-be supported by the server.
-
-Possible values are CORE, COREPLUS, LANMAN1, LANMAN2 and NT1. The relative
-merits of each are discussed in the README file.
-
-Normally this option should not be set as the automatic negotiation
-phase in the SMB protocol takes care of choosing the appropriate protocol.
-
-.B Default:
- protocol = NT1
-
-.B Example:
- protocol = LANMAN1
-.SS public (S)
-A synonym for this parameter is 'guest ok'.
-
-If this parameter is 'yes' for a service, then no password is required
-to connect to the service. Privileges will be those of the guest
-account.
-
-See the section below on user/password validation for more information about
-this option.
-
-.B Default:
- public = no
-
-.B Example:
- public = yes
-.SS read list (S)
-This is a list of users that are given read-only access to a
-service. If the connecting user is in this list then they will
-not be given write access, no matter what the "read only" option
-is set to. The list can include group names using the @group syntax.
-
-See also the "write list" option
-
-.B Default:
- read list =
-
-.B Example:
- read list = mary, @students
-
-.SS read only (S)
-See
-.B writable
-and
-.B write ok.
-Note that this is an inverted synonym for writable and write ok.
-.SS read prediction (G)
-This options enables or disables the read prediction code used to
-speed up reads from the server. When enabled the server will try to
-pre-read data from the last accessed file that was opened read-only
-while waiting for packets.
-
-.SS Default:
- read prediction = False
-
-.SS Example:
- read prediction = True
-.SS read raw (G)
-This parameter controls whether or not the server will support raw reads when
-transferring data to clients.
-
-If enabled, raw reads allow reads of 65535 bytes in one packet. This
-typically provides a major performance benefit.
-
-However, some clients either negotiate the allowable block size incorrectly
-or are incapable of supporting larger block sizes, and for these clients you
-may need to disable raw reads.
-
-In general this parameter should be viewed as a system tuning tool and left
-severely alone. See also
-.B write raw.
-
-.B Default:
- read raw = yes
-
-.B Example:
- read raw = no
-.SS read size (G)
-
-The option "read size" affects the overlap of disk reads/writes with
-network reads/writes. If the amount of data being transferred in
-several of the SMB commands (currently SMBwrite, SMBwriteX and
-SMBreadbraw) is larger than this value then the server begins writing
-the data before it has received the whole packet from the network, or
-in the case of SMBreadbraw, it begins writing to the network before
-all the data has been read from disk.
-
-This overlapping works best when the speeds of disk and network access
-are similar, having very little effect when the speed of one is much
-greater than the other.
-
-The default value is 2048, but very little experimentation has been
-done yet to determine the optimal value, and it is likely that the best
-value will vary greatly between systems anyway. A value over 65536 is
-pointless and will cause you to allocate memory unnecessarily.
-
-.B Default:
- read size = 2048
-
-.B Example:
- read size = 8192
-
-.SS remote announce (G)
-
-This option allows you to setup nmbd to periodically announce itself
-to arbitrary IP addresses with an arbitrary workgroup name.
-
-This is useful if you want your Samba server to appear in a remote
-workgroup for which the normal browse propagation rules don't
-work. The remote workgroup can be anywhere that you can send IP
-packets to.
-
-For example:
-
- remote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF
-
-the above line would cause nmbd to announce itself to the two given IP
-addresses using the given workgroup names. If you leave out the
-workgroup name then the one given in the "workgroup" option is used
-instead.
-
-The IP addresses you choose would normally be the broadcast addresses
-of the remote networks, but can also be the IP addresses of known
-browse masters if your network config is that stable.
-
-This option replaces similar functionality from the nmbd lmhosts file.
-
-.SS revalidate (S)
-
-This options controls whether Samba will allow a previously validated
-username/password pair to be used to attach to a share. Thus if you
-connect to \e\eserver\eshare1 then to \e\eserver\eshare2 it won't
-automatically allow the client to request connection to the second
-share as the same username as the first without a password.
-
-If "revalidate" is True then the client will be denied automatic
-access as the same username.
-
-.B Default:
- revalidate = False
-
-.B Example:
- revalidate = True
-
-.SS root (G)
-See
-.B root directory.
-.SS root dir (G)
-See
-.B root directory.
-.SS root directory (G)
-Synonyms for this parameter are 'root dir' and 'root'.
-
-The server will chroot() to this directory on startup. This is not
-strictly necessary for secure operation. Even without it the server
-will deny access to files not in one of the service entries. It may
-also check for, and deny access to, soft links to other parts of the
-filesystem, or attempts to use .. in file names to access other
-directories (depending on the setting of the "wide links" parameter).
-
-Adding a "root dir" entry other than "/" adds an extra level of security,
-but at a price. It absolutely ensures that no access is given to files not
-in the sub-tree specified in the "root dir" option, *including* some files
-needed for complete operation of the server. To maintain full operability
-of the server you will need to mirror some system files into the "root dir"
-tree. In particular you will need to mirror /etc/passwd (or a subset of it),
-and any binaries or configuration files needed for printing (if required).
-The set of files that must be mirrored is operating system dependent.
-
-.B Default:
- root directory = /
-
-.B Example:
- root directory = /homes/smb
-.SS root postexec (S)
-
-This is the same as postexec except that the command is run as
-root. This is useful for unmounting filesystems (such as cdroms) after
-a connection is closed.
-
-.SS root preexec (S)
-
-This is the same as preexec except that the command is run as
-root. This is useful for mounting filesystems (such as cdroms) before
-a connection is finalised.
-
-.SS security (G)
-This option affects how clients respond to Samba.
-
-The option sets the "security mode bit" in replies to protocol negotiations
-to turn share level security on or off. Clients decide based on this bit
-whether (and how) to transfer user and password information to the server.
-
-The default is "security=SHARE", mainly because that was the only
-option at one stage.
-
-The alternatives are "security = user" or "security = server".
-
-If your PCs use usernames that are the same as their usernames on the
-UNIX machine then you will want to use "security = user". If you
-mostly use usernames that don't exist on the UNIX box then use
-"security = share".
-
-There is a bug in WfWg that may affect your decision. When in user
-level security a WfWg client will totally ignore the password you type
-in the "connect drive" dialog box. This makes it very difficult (if
-not impossible) to connect to a Samba service as anyone except the
-user that you are logged into WfWg as.
-
-If you use "security = server" then Samba will try to validate the
-username/password by passing it to another SMB server, such as an NT
-box. If this fails it will revert to "security = USER".
-
-See the "password server" option for more details.
-
-.B Default:
- security = SHARE
-
-.B Example:
- security = USER
-.SS server string (G)
-This controls what string will show up in the printer comment box in
-print manager and next to the IPC connection in "net view". It can be
-any string that you wish to show to your users.
-
-It also sets what will appear in browse lists next to the machine name.
-
-A %v will be replaced with the Samba version number.
-
-A %h will be replaced with the hostname.
-
-.B Default:
- server string = Samba %v
-
-.B Example:
- server string = University of GNUs Samba Server
-
-.SS set directory (S)
-If 'set directory = no', then users of the service may not use the setdir
-command to change directory.
-
-The setdir command is only implemented in the Digital Pathworks client. See the
-Pathworks documentation for details.
-
-.B Default:
- set directory = no
-
-.B Example:
- set directory = yes
-
-.SS shared file entries (G)
-This parameter is only useful when Samba has been compiled with FAST_SHARE_MODES.
-It specifies the number of hash bucket entries used for share file locking.
-You should never change this parameter unless you have studied the source
-and know what you are doing.
-
-.B Default
- shared file entries = 113
-
-.SS shared mem size (G)
-This parameter is only useful when Samba has been compiled with FAST_SHARE_MODES.
-It specifies the size of the shared memory (in bytes) to use between smbd
-processes. You should never change this parameter unless you have studied
-the source and know what you are doing.
-
-.B Default
- shared mem size = 102400
-
-.SS smb passwd file (G)
-This option sets the path to the encrypted smbpasswd file. This is a *VERY
-DANGEROUS OPTION* if the smb.conf is user writable. By default the path
-to the smbpasswd file is compiled into Samba.
-
-.SS smbrun (G)
-This sets the full path to the smbrun binary. This defaults to the
-value in the Makefile.
-
-You must get this path right for many services to work correctly.
-
-.B Default:
-taken from Makefile
-
-.B Example:
- smbrun = /usr/local/samba/bin/smbrun
-
-.SS share modes (S)
-
-This enables or disables the honouring of the "share modes" during a
-file open. These modes are used by clients to gain exclusive read or
-write access to a file.
-
-These open modes are not directly supported by UNIX, so they are
-simulated using lock files in the "lock directory". The "lock
-directory" specified in smb.conf must be readable by all users.
-
-The share modes that are enabled by this option are DENY_DOS,
-DENY_ALL, DENY_READ, DENY_WRITE, DENY_NONE and DENY_FCB.
-
-Enabling this option gives full share compatibility but may cost a bit
-of processing time on the UNIX server. They are enabled by default.
-
-.B Default:
- share modes = yes
-
-.B Example:
- share modes = no
-
-.SS short preserve case (S)
-
-This controls if new short filenames are created with the case that
-the client passes, or if they are forced to be the "default" case.
-
-.B Default:
- short preserve case = no
-
-See the section on "NAME MANGLING" for a fuller discussion.
-
-.SS socket address (G)
-
-This option allows you to control what address Samba will listen for
-connections on. This is used to support multiple virtual interfaces on
-the one server, each with a different configuration.
-
-By default samba will accept connections on any address.
-
-.B Example:
- socket address = 192.168.2.20
-
-.SS socket options (G)
-This option (which can also be invoked with the -O command line
-option) allows you to set socket options to be used when talking with
-the client.
-
-Socket options are controls on the networking layer of the operating
-systems which allow the connection to be tuned.
-
-This option will typically be used to tune your Samba server for
-optimal performance for your local network. There is no way that Samba
-can know what the optimal parameters are for your net, so you must
-experiment and choose them yourself. I strongly suggest you read the
-appropriate documentation for your operating system first (perhaps
-"man setsockopt" will help).
-
-You may find that on some systems Samba will say "Unknown socket
-option" when you supply an option. This means you either mis-typed it
-or you need to add an include file to includes.h for your OS. If the
-latter is the case please send the patch to me
-(samba-bugs@samba.anu.edu.au).
-
-Any of the supported socket options may be combined in any way you
-like, as long as your OS allows it.
-
-This is the list of socket options currently settable using this
-option:
-
- SO_KEEPALIVE
-
- SO_REUSEADDR
-
- SO_BROADCAST
-
- TCP_NODELAY
-
- IPTOS_LOWDELAY
-
- IPTOS_THROUGHPUT
-
- SO_SNDBUF *
-
- SO_RCVBUF *
-
- SO_SNDLOWAT *
-
- SO_RCVLOWAT *
-
-Those marked with a * take an integer argument. The others can
-optionally take a 1 or 0 argument to enable or disable the option, by
-default they will be enabled if you don't specify 1 or 0.
-
-To specify an argument use the syntax SOME_OPTION=VALUE for example
-SO_SNDBUF=8192. Note that you must not have any spaces before or after
-the = sign.
-
-If you are on a local network then a sensible option might be
-
-socket options = IPTOS_LOWDELAY
-
-If you have an almost unloaded local network and you don't mind a lot
-of extra CPU usage in the server then you could try
-
-socket options = IPTOS_LOWDELAY TCP_NODELAY
-
-If you are on a wide area network then perhaps try setting
-IPTOS_THROUGHPUT.
-
-Note that several of the options may cause your Samba server to fail
-completely. Use these options with caution!
-
-.B Default:
- no socket options
-
-.B Example:
- socket options = IPTOS_LOWDELAY
-
-
-
-
-.SS status (G)
-This enables or disables logging of connections to a status file that
-.B smbstatus
-can read.
-
-With this disabled
-.B smbstatus
-won't be able to tell you what
-connections are active.
-
-.B Default:
- status = yes
-
-.B Example:
- status = no
-
-.SS strict locking (S)
-This is a boolean that controls the handling of file locking in the
-server. When this is set to yes the server will check every read and
-write access for file locks, and deny access if locks exist. This can
-be slow on some systems.
-
-When strict locking is "no" the server does file lock checks only when
-the client explicitly asks for them.
-
-Well behaved clients always ask for lock checks when it is important,
-so in the vast majority of cases "strict locking = no" is preferable.
-
-.B Default:
- strict locking = no
-
-.B Example:
- strict locking = yes
-
-.SS strip dot (G)
-This is a boolean that controls whether to strip trailing dots off
-filenames. This helps with some CDROMs that have filenames ending in a
-single dot.
-
-NOTE: This option is now obsolete, and may be removed in future. You
-should use the "mangled map" option instead as it is much more
-general.
-
-.SS syslog (G)
-This parameter maps how Samba debug messages are logged onto the
-system syslog logging levels. Samba debug level zero maps onto
-syslog LOG_ERR, debug level one maps onto LOG_WARNING, debug
-level two maps to LOG_NOTICE, debug level three maps onto LOG_INFO.
-The paramter sets the threshold for doing the mapping, all Samba
-debug messages above this threashold are mapped to syslog LOG_DEBUG
-messages.
-
-.B Default:
-
- syslog = 1
-
-.SS syslog only (G)
-If this parameter is set then Samba debug messages are logged into
-the system syslog only, and not to the debug log files.
-
-.B Default:
- syslog only = no
-
-.SS sync always (S)
-
-This is a boolean parameter that controls whether writes will always
-be written to stable storage before the write call returns. If this is
-false then the server will be guided by the client's request in each
-write call (clients can set a bit indicating that a particular write
-should be synchronous). If this is true then every write will be
-followed by a fsync() call to ensure the data is written to disk.
-
-.B Default:
- sync always = no
-
-.B Example:
- sync always = yes
-
-.SS time offset (G)
-This parameter is a setting in minutes to add to the normal GMT to
-local time conversion. This is useful if you are serving a lot of PCs
-that have incorrect daylight saving time handling.
-
-.B Default:
- time offset = 0
-
-.B Example:
- time offset = 60
-
-.SS time server (G)
-This parameter determines if nmbd advertises itself as a time server
-to Windows clients. The default is False.
-
-.B Default:
- time server = False
-
-.B Example:
- time server = True
-
-.SS unix realname (G)
-This boolean parameter when set causes samba to supply the real name field
-from the unix password file to the client. This is useful for setting up
-mail clients and WWW browsers on systems used by more than one person.
-
-.B Default:
- unix realname = no
-
-.B Example:
- unix realname = yes
-
-.SS user (S)
-See
-.B username.
-.SS username (S)
-A synonym for this parameter is 'user'.
-
-Multiple users may be specified in a comma-delimited list, in which case the
-supplied password will be tested against each username in turn (left to right).
-
-The username= line is needed only when the PC is unable to supply its own
-username. This is the case for the coreplus protocol or where your
-users have different WfWg usernames to UNIX usernames. In both these
-cases you may also be better using the \e\eserver\eshare%user syntax
-instead.
-
-The username= line is not a great solution in many cases as it means Samba
-will try to validate the supplied password against each of the
-usernames in the username= line in turn. This is slow and a bad idea for
-lots of users in case of duplicate passwords. You may get timeouts or
-security breaches using this parameter unwisely.
-
-Samba relies on the underlying UNIX security. This parameter does not
-restrict who can login, it just offers hints to the Samba server as to
-what usernames might correspond to the supplied password. Users can
-login as whoever they please and they will be able to do no more
-damage than if they started a telnet session. The daemon runs as the
-user that they log in as, so they cannot do anything that user cannot
-do.
-
-To restrict a service to a particular set of users you can use the
-"valid users=" line.
-
-If any of the usernames begin with a @ then the name will be looked up
-in the groups file and will expand to a list of all users in the group
-of that name. Note that searching though a groups file can take quite
-some time, and some clients may time out during the search.
-
-See the section below on username/password validation for more information
-on how this parameter determines access to the services.
-
-.B Default:
- The guest account if a guest service, else the name of the service.
-
-.B Examples:
- username = fred
- username = fred, mary, jack, jane, @users, @pcgroup
-
-.SS username map (G)
-
-This option allows you to to specify a file containing a mapping of
-usernames from the clients to the server. This can be used for several
-purposes. The most common is to map usernames that users use on DOS or
-Windows machines to those that the UNIX box uses. The other is to map
-multiple users to a single username so that they can more easily share
-files.
-
-The map file is parsed line by line. Each line should contain a single
-UNIX username on the left then a '=' followed by a list of usernames
-on the right. The list of usernames on the right may contain names of
-the form @group in which case they will match any UNIX username in
-that group. The special client name '*' is a wildcard and matches any
-name.
-
-The file is processed on each line by taking the supplied username and
-comparing it with each username on the right hand side of the '='
-signs. If the supplied name matches any of the names on the right
-hand side then it is replaced with the name on the left. Processing
-then continues with the next line.
-
-If any line begins with a '#' or a ';' then it is ignored
-
-For example to map from the name "admin" or "administrator" to the UNIX
-name "root" you would use
-
- root = admin administrator
-
-Or to map anyone in the UNIX group "system" to the UNIX name "sys" you
-would use
-
- sys = @system
-
-You can have as many mappings as you like in a username map file.
-
-Note that the remapping is applied to all occurrences of
-usernames. Thus if you connect to "\e\eserver\efred" and "fred" is
-remapped to "mary" then you will actually be connecting to
-"\e\eserver\emary" and will need to supply a password suitable for
-"mary" not "fred". The only exception to this is the username passed
-to the "password server" (if you have one). The password server will
-receive whatever username the client supplies without modification.
-
-Also note that no reverse mapping is done. The main effect this has is
-with printing. Users who have been mapped may have trouble deleting
-print jobs as PrintManager under WfWg will think they don't own the
-print job.
-
-.B Default
- no username map
-
-.B Example
- username map = /usr/local/samba/lib/users.map
-
-.SS valid chars (S)
-
-The option allows you to specify additional characters that should be
-considered valid by the server in filenames. This is particularly
-useful for national character sets, such as adding u-umlaut or a-ring.
-
-The option takes a list of characters in either integer or character
-form with spaces between them. If you give two characters with a colon
-between them then it will be taken as an lowercase:uppercase pair.
-
-If you have an editor capable of entering the characters into the
-config file then it is probably easiest to use this method. Otherwise
-you can specify the characters in octal, decimal or hexadecimal form
-using the usual C notation.
-
-For example to add the single character 'Z' to the charset (which is a
-pointless thing to do as it's already there) you could do one of the
-following
-
-valid chars = Z
-valid chars = z:Z
-valid chars = 0132:0172
-
-The last two examples above actually add two characters, and alter
-the uppercase and lowercase mappings appropriately.
-
-Note that you MUST specify this parameter after the "client code page"
-parameter if you have both set. If "client code page" is set after
-the "valid chars" parameter the "valid chars" settings will be
-overwritten.
-
-See also the "client code page" parameter.
-
-.B Default
-.br
- Samba defaults to using a reasonable set of valid characters
-.br
- for english systems
-
-.B Example
- valid chars = 0345:0305 0366:0326 0344:0304
-
-The above example allows filenames to have the swedish characters in
-them.
-
-NOTE: It is actually quite difficult to correctly produce a "valid
-chars" line for a particular system. To automate the process
-tino@augsburg.net has written a package called "validchars" which will
-automatically produce a complete "valid chars" line for a given client
-system. Look in the examples subdirectory for this package.
-
-.SS valid users (S)
-This is a list of users that should be allowed to login to this
-service. A name starting with @ is interpreted as a UNIX group.
-
-If this is empty (the default) then any user can login. If a username
-is in both this list and the "invalid users" list then access is
-denied for that user.
-
-The current servicename is substituted for %S. This is useful in the
-[homes] section.
-
-See also "invalid users"
-
-.B Default
- No valid users list. (anyone can login)
-
-.B Example
- valid users = greg, @pcusers
-
-
-.SS veto files(S)
-This is a list of files and directories that are neither visible nor
-accessible. Each entry in the list must be separate by a "/", which
-allows spaces to be included in the entry. Note that '*' and '?' at
-present cannot be used to specify multiple files or directories.
-
-.B Default
- No files or directories are vetoed.
-
-.B Example
- veto files = DesktopFolderDB/TrashFor%m/resource.frk
-
-The above example is based on files that the Macintosh client (DAVE)
-creates for internal use.
-
-.SS volume (S)
-This allows you to override the volume label returned for a
-share. Useful for CDROMs with installation programs that insist on a
-particular volume label.
-
-The default is the name of the share
-
-.SS wide links (S)
-This parameter controls whether or not links in the UNIX file system may be
-followed by the server. Links that point to areas within the directory tree
-exported by the server are always allowed; this parameter controls access
-only to areas that are outside the directory tree being exported.
-
-.B Default:
- wide links = yes
-
-.B Example:
- wide links = no
-
-.SS wins proxy (G)
-
-This is a boolean that controls if nmbd will respond to broadcast name
-queries on behalf of other hosts. You may need to set this to no for
-some older clients.
-
-.B Default:
- wins proxy = no
-.SS wins server (G)
-
-This specifies the DNS name (or IP address) of the WINS server that Samba
-should register with. If you have a WINS server on your network then you
-should set this to the WINS servers name.
-
-You should point this at your WINS server if you have a multi-subnetted
-network.
-.B Default:
- wins server =
-
-.SS wins support (G)
-
-This boolean controls if Samba will act as a WINS server. You should
-not set this to true unless you have a multi-subnetted network and
-you wish a particular nmbd to be your WINS server. Note that you
-should *NEVER* set this to true on more than one machine in your
-network.
-
-.B Default:
- wins support = no
-.SS workgroup (G)
-
-This controls what workgroup your server will appear to be in when
-queried by clients.
-
-.B Default:
- set in the Makefile
-
-.B Example:
- workgroup = MYGROUP
-
-.SS writable (S)
-A synonym for this parameter is 'write ok'. An inverted synonym is 'read only'.
-
-If this parameter is 'no', then users of a service may not create or modify
-files in the service's directory.
-
-Note that a printable service ('printable = yes') will ALWAYS allow
-writing to the directory (user privileges permitting), but only via
-spooling operations.
-
-.B Default:
- writable = no
-
-.B Examples:
- read only = no
- writable = yes
- write ok = yes
-.SS write list (S)
-This is a list of users that are given read-write access to a
-service. If the connecting user is in this list then they will be
-given write access, no matter what the "read only" option is set
-to. The list can include group names using the @group syntax.
-
-Note that if a user is in both the read list and the write list then
-they will be given write access.
-
-See also the "read list" option
-
-.B Default:
- write list =
-
-.B Example:
- write list = admin, root, @staff
-
-.SS write ok (S)
-See
-.B writable
-and
-.B read only.
-.SS write raw (G)
-This parameter controls whether or not the server will support raw writes when
-transferring data from clients.
-
-.B Default:
- write raw = yes
-
-.B Example:
- write raw = no
-.SH NOTE ABOUT USERNAME/PASSWORD VALIDATION
-There are a number of ways in which a user can connect to a
-service. The server follows the following steps in determining if it
-will allow a connection to a specified service. If all the steps fail
-then the connection request is rejected. If one of the steps pass then
-the following steps are not checked.
-
-If the service is marked "guest only = yes" then steps 1 to 5 are skipped
-
-Step 1: If the client has passed a username/password pair and that
-username/password pair is validated by the UNIX system's password
-programs then the connection is made as that username. Note that this
-includes the \e\eserver\eservice%username method of passing a username.
-
-Step 2: If the client has previously registered a username with the
-system and now supplies a correct password for that username then the
-connection is allowed.
-
-Step 3: The client's netbios name and any previously used user names
-are checked against the supplied password, if they match then the
-connection is allowed as the corresponding user.
-
-Step 4: If the client has previously validated a username/password
-pair with the server and the client has passed the validation token
-then that username is used. This step is skipped if "revalidate = yes"
-for this service.
-
-Step 5: If a "user = " field is given in the smb.conf file for the
-service and the client has supplied a password, and that password
-matches (according to the UNIX system's password checking) with one of
-the usernames from the user= field then the connection is made as the
-username in the "user=" line. If one of the username in the user= list
-begins with a @ then that name expands to a list of names in the group
-of the same name.
-
-Step 6: If the service is a guest service then a connection is made as
-the username given in the "guest account =" for the service,
-irrespective of the supplied password.
-.SH WARNINGS
-Although the configuration file permits service names to contain spaces,
-your client software may not. Spaces will be ignored in comparisons anyway,
-so it shouldn't be a problem - but be aware of the possibility.
-
-On a similar note, many clients - especially DOS clients - limit service
-names to eight characters. Smbd has no such limitation, but attempts
-to connect from such clients will fail if they truncate the service names.
-For this reason you should probably keep your service names down to eight
-characters in length.
-
-Use of the [homes] and [printers] special sections make life for an
-administrator easy, but the various combinations of default attributes can be
-tricky. Take extreme care when designing these sections. In particular,
-ensure that the permissions on spool directories are correct.
-.SH VERSION
-This man page is (mostly) correct for version 1.9.16 of the Samba suite, plus some
-of the recent patches to it. These notes will necessarily lag behind
-development of the software, so it is possible that your version of
-the server has extensions or parameter semantics that differ from or are not
-covered by this man page. Please notify these to the address below for
-rectification.
-
-Prior to version 1.5.21 of the Samba suite, the configuration file was
-radically different (more primitive). If you are using a version earlier than
-1.8.05, it is STRONGLY recommended that you upgrade.
-.SH OPTIONS
-Not applicable.
-.SH FILES
-Not applicable.
-.SH ENVIRONMENT VARIABLES
-Not applicable.
-.SH SEE ALSO
-.BR smbd (8),
-.BR smbclient (1),
-.BR nmbd (8),
-.BR testparm (1),
-.BR testprns (1),
-.BR lpq (1),
-.BR hosts_access (5)
-.SH DIAGNOSTICS
-[This section under construction]
-
-Most diagnostics issued by the server are logged in a specified log file. The
-log file name is specified at compile time, but may be overridden on the
-smbd command line (see
-.BR smbd (8)).
-
-The number and nature of diagnostics available depends on the debug level used
-by the server. If you have problems, set the debug level to 3 and peruse the
-log files.
-
-Most messages are reasonably self-explanatory. Unfortunately, at time of
-creation of this man page the source code is still too fluid to warrant
-describing each and every diagnostic. At this stage your best bet is still
-to grep the source code and inspect the conditions that gave rise to the
-diagnostics you are seeing.
-.SH BUGS
-None known.
-
-Please send bug reports, comments and so on to:
-
-.RS 3
-.B samba-bugs@samba.anu.edu.au (Andrew Tridgell)
-
-.RS 3
-or to the mailing list:
-.RE
-
-.B samba@listproc.anu.edu.au
-
-.RE
-You may also like to subscribe to the announcement channel:
-
-.RS 3
-.B samba-announce@listproc.anu.edu.au
-.RE
-
-To subscribe to these lists send a message to
-listproc@listproc.anu.edu.au with a body of "subscribe samba Your
-Name" or "subscribe samba-announce Your Name".
-
-Errors or suggestions for improvements to the Samba man pages should be
-mailed to:
-
-.RS 3
-.B samba-bugs@samba.anu.edu.au (Andrew Tridgell)
-.RE
-
diff --git a/docs/manpages/smbclient.1 b/docs/manpages/smbclient.1
deleted file mode 100644
index 6ae454f2f24..00000000000
--- a/docs/manpages/smbclient.1
+++ /dev/null
@@ -1,1204 +0,0 @@
-.TH SMBCLIENT 1 smbclient smbclient
-.SH NAME
-smbclient \- ftp-like Lan Manager client program
-.SH SYNOPSIS
-.B smbclient
-.B servicename
-[
-.B password
-] [
-.B \-A
-] [
-.B \-E
-] [
-.B \-L
-.I host
-] [
-.B \-M
-.I host
-] [
-.B \-I
-.I IP number
-] [
-.B \-N
-] [
-.B \-P
-] [
-.B \-U
-.I username
-] [
-.B \-d
-.I debuglevel
-] [
-.B \-l
-.I log basename
-] [
-.B \-n
-.I netbios name
-] [
-.B \-W
-.I workgroup
-] [
-.B \-O
-.I socket options
-] [
-.B \-p
-.I port number
-] [
-.B \-c
-.I command string
-] [
-.B \-T
-.I tar options
-] [
-.B \-D
-.I initial directory
-]
-.SH DESCRIPTION
-This program is part of the Samba suite.
-
-.B smbclient
-is a client that can 'talk' to a Lan Manager server. It offers
-an interface similar to that of the
-.B ftp
-program (see
-.BR ftp (1)).
-Operations include things like getting files from the
-server to the local machine, putting files from the local machine to
-the server, retrieving directory information from the server and so on.
-.SH OPTIONS
-.B servicename
-.RS 3
-.B servicename
-is the name of the service you want to use on the server. A service
-name takes the form
-.B "\e\eserver\eservice"
-where
-.B server
-is the netbios name of the Lan Manager server offering the desired service and
-.B service
-is the name of the service offered. Thus to connect to the service "printer"
-on the Lan Manager server "lanman", you would use the servicename
-
-.RS 10
-.B "\e\elanman\eprinter"
-.RE
-
-Note that the server name required is NOT necessarily the host name of the
-server! The name required is a Lan Manager server name, which may or may not
-be the same as the hostname of the machine running the server.
-.RE
-
-.B password
-.RS 3
-.B
-password
-is the password required to access the specified service on the
-specified server. If supplied, the
-.B \-N
-option (suppress password prompt) is assumed.
-
-There is no default password. If no password is supplied on the command line
-(either here or using the
-.B \-U
-option (see below)) and
-.B \-N
-is not specified, the client will prompt for a password, even if the desired
-service does not require one. (If no password is
-required, simply press ENTER to provide a null password.)
-
-Note: Some servers (including OS/2 and Windows for Workgroups) insist
-on an uppercase password. Lowercase or mixed case passwords may be
-rejected by these servers.
-
-Be cautious about including passwords in scripts.
-.RE
-
-.B \-A
-
-.RS 3
-This parameter, if specified, causes the maximum debug level to be selected.
-Be warned that this generates prodigious amounts of debug data. There is also
-a security issue involved, as at the maximum debug level cleartext passwords
-may be written to some log files.
-.RE
-
-.B \-L
-
-.RS 3
-This option allows you to look at what services are available on a
-server. You use it as "smbclient -L host" and a list should appear.
-The
-.B \-I
-option may be useful if your netbios names don't match your
-tcp/ip host names or if you are trying to reach a host on another
-network. For example:
-
-smbclient -L ftp -I ftp.microsoft.com
-
-will list the shares available on Microsoft's public server.
-.RE
-
-.B \-M
-
-.RS 3
-This options allows you to send messages, using the "WinPopup"
-protocol, to another computer. Once a connection is established you
-then type your message, pressing ^D (control-D) to end.
-
-If the receiving computer is running WinPopup the user will receive
-the message and probably a beep. If they are not running WinPopup the
-message will be lost, and no error message will occur.
-
-The message is also automatically truncated if the message is over
-1600 bytes, as this is the limit of the protocol.
-
-One useful trick is to cat the message through
-.BR smbclient .
-For example:
-
-cat mymessage.txt | smbclient -M FRED
-
-will send the message in the file "mymessage.txt" to the machine FRED.
-
-You may also find the
-.B \-U
-and
-.B \-I
-options useful, as they allow you to
-control the FROM and TO parts of the message.
-
-See the message command section of
-.BR smb.conf (5)
-for a description of how to handle incoming WinPopup messages in Samba.
-
-Note: Copy WinPopup into the startup group on your WfWg PCs if you
-want them to always be able to receive messages.
-.RE
-
-.B \-E
-
-.RS 3
-This parameter, if specified, causes the client to write messages to the
-standard error stream (stderr) rather than to the standard output stream.
-
-By default, the client writes messages to standard output - typically the
-user's tty.
-.RE
-
-.B \-I
-.I IP number
-
-.RS 3
-.I IP number
-represents the IP number of the server to connect to. It should
-be specified in standard "a.b.c.d" notation.
-
-Normally the client will attempt to locate the specified Lan Manager server
-by looking it up - that is, broadcasting a request for the given server to
-identify itself. Using this parameter will force the client to assume that
-the server is on the machine with the specified IP number.
-
-There is no default for this parameter. If not supplied, it will be determined
-automatically by the client as described above.
-.RE
-
-.B \-N
-
-.RS 3
-If specified, this parameter suppresses the normal password prompt from the
-client to the user. This is useful when accessing a service that does not
-require a password.
-
-Unless a password is specified on the command line or this parameter is
-specified, the client will request a password.
-.RE
-
-.B \-O
-.I socket options
-
-.RS 3
-See the socket options section of
-.BR smb.conf (5)
-for details.
-.RE
-
-.B \-P
-
-.RS 3
-If specified, the service requested will be connected to as a printer service
-rather than as a normal filespace service. Operations such as put and get
-will not be applicable for such a connection.
-
-By default, services will be connected to as NON-printer services.
-.RE
-
-.B \-U
-.I username
-
-.RS 3
-.I username
-is the user name that will be used by the client to make a connection,
-assuming your server is running a protocol that allows for usernames.
-
-Some servers are fussy about the case of this name, and some insist
-that it must be a valid netbios name.
-
-If no
-.I username
-is supplied, it will default to an uppercase version of the
-environment variable
-.B USER
-or
-.B LOGNAME
-in that order.
-If no
-.I username
-is supplied and neither environment variable exists the user name will
-be empty.
-
-If the service you are connecting to requires a password, it can be supplied
-using the
-.B \-U
-option, by appending a percent symbol ("%") then the password to
-.I username.
-For example, to attach to a service as user "fred" with password "secret", you
-would specify
-.B \-U
-.I fred%secret
-on the command line. Note that there are no spaces around the percent symbol.
-
-If you specify the password as part of
-.I username
-then the
-.B \-N
-option (suppress password prompt) is assumed.
-
-If you specify the password as a parameter AND as part of
-.I username
-then the password as part of
-.I username
-will take precedence. Putting nothing before or nothing after the percent
-symbol will cause an empty username or an empty password to be used,
-respectively.
-
-Note: Some servers (including OS/2 and Windows for Workgroups) insist
-on an uppercase password. Lowercase or mixed case passwords may be
-rejected by these servers.
-
-Be cautious about including passwords in scripts.
-.RE
-
-.B \-d
-.I debuglevel
-
-.RS 3
-debuglevel is an integer from 0 to 5.
-
-The default value if this parameter is not specified is zero.
-
-The higher this value, the more detail will be logged to the log files about
-the activities of the client. At level 0, only critical errors and serious
-warnings will be logged. Level 1 is a reasonable level for day to day running
-- it generates a small amount of information about operations carried out.
-
-Levels above 1 will generate considerable amounts of log data, and should
-only be used when investigating a problem. Levels above 3 are designed for
-use only by developers and generate HUGE amounts of log data, most of which
-is extremely cryptic.
-.RE
-
-.B \-l
-.I log basename
-
-.RS 3
-If specified,
-.I log basename
-specifies a base filename into which operational data from the running client
-will be logged.
-
-The default base name is specified at compile time.
-
-The base name is used to generate actual log file names. For example, if the
-name specified was "log", the following files would be used for log data:
-
-.RS 3
-log.client.debug (containing debugging information)
-
-log.client.in (containing inbound transaction data)
-
-log.client.out (containing outbound transaction data)
-.RE
-
-The log files generated are never removed by the client.
-.RE
-
-.B \-n
-.I netbios name
-
-.RS 3
-By default, the client will use the local machine's hostname (in
-uppercase) as its netbios name. This parameter allows you to override
-the host name and use whatever netbios name you wish.
-.RE
-
-.B \-W
-.I workgroup
-
-.RS 3
-Override what workgroup is used for the connection. This may be needed
-to connect to some servers.
-.RE
-
-.B \-p
-.I port number
-
-.RS 3
-port number is a positive integer value.
-
-The default value if this parameter is not specified is 139.
-
-This number is the port number that will be used when making connections to
-the server. The standard (well-known) port number for the server is 139,
-hence the default.
-
-This parameter is not normally specified.
-.RE
-
-.B \-T
-.I tar options
-
-.RS 3
-where
-.I tar options
-consists of one or more of
-.BR c ,
-.BR x ,
-.BR I ,
-.BR X ,
-.BR b ,
-.BR g ,
-.BR N
-or
-.BR a ;
-used as:
-.LP
-smbclient
-.B "\e\eserver\eshare"
-\-TcxIXbgNa
-[
-.IR blocksize
-]
-[
-.IR newer-file
-]
-.IR tarfile
-[
-.IR filenames....
-]
-
-.RS 3
-.B c
-Create a tar file on UNIX. Must be followed by the name of a tar file,
-tape device or "\-" for standard output. (May be useful to set debugging
-low
-.RB ( -d0 ))
-to avoid corrupting your tar file if using "\-"). Mutually
-exclusive with the
-.B x
-flag.
-
-.B x
-Extract (restore) a local tar file back to a share. Unless the
-.B \-D
-option is given, the tar files will be restored from the top level of
-the share. Must be followed by the name of the tar file, device or "\-"
-for standard input. Mutually exclusive with the
-.B c
-flag.
-
-.B I
-Include files and directories. Is the default behaviour when
-.IR filenames
-are specified above. Causes tar files to be included in an extract or create
-(and therefore everything else to be excluded). See example below.
-Filename globbing does not work for included files for extractions (yet).
-
-.B X
-Exclude files and directories. Causes tar files to be excluded from
-an extract or create. See example below.
-Filename globbing does not work for excluded files (yet).
-
-.B b
-Blocksize. Must be followed by a valid (greater than zero) blocksize.
-Causes tar file to be written out in blocksize*TBLOCK (usually 512 byte)
-blocks.
-
-.B g
-Incremental. Only back up files that have the archive bit set. Useful
-only with the
-.B c
-flag.
-
-.B N
-Newer than. Must be followed by the name of a file whose date is
-compared against files found on the share during a create. Only files
-newer than the file specified are backed up to the tar file. Useful
-only with the
-.B c
-flag.
-
-.B a
-Set archive bit. Causes the archive bit to be reset when a file is backed
-up. Useful with the
-.B g
-(and
-.BR c )
-flags.
-.LP
-
-.B Examples
-
-smbclient \e\emypc\emyshare "" -N -Tx backup.tar
-
-Restore from tar file backup.tar into myshare on mypc (no password on share).
-
-smbclient \e\emypc\emyshare "" -N -TXx backup.tar users/docs
-
-Restore everything except users/docs
-
-smbclient \e\emypc\emyshare "" -N -Tc backup.tar users/docs
-
-Create a tar file of the files beneath users/docs.
-.RE
-.RE
-
-.B \-D
-.I initial directory
-
-.RS 3
-Change to initial directory before starting. Probably only of any use
-with the tar
-.RB ( \-T )
-option.
-.RE
-
-.B \-c
-.I command string
-
-.RS 3
-command string is a semicolon separated list of commands to be
-executed instead of prompting from stdin.
-.B \-N
-is implied by
-.BR \-c .
-
-This is particularly useful in scripts and for printing stdin to
-the server, e.g. \-c 'print \-'.
-.RE
-.SH OPERATIONS
-Once the client is running, the user is presented with a prompt, "smb: \e>".
-The backslash ("\e") indicates the current working directory on the server,
-and will change if the current working directory is changed.
-
-The prompt indicates that the client is ready and waiting to carry out a user
-command. Each command is a single word, optionally followed by parameters
-specific to that command. Command and parameters are space-delimited unless
-these notes specifically state otherwise. All commands are case-insensitive.
-Parameters to commands may or may not be case sensitive, depending on the
-command.
-
-You can specify file names which have spaces in them by quoting the
-name with double quotes, for example "a long file name".
-
-Parameters shown in square brackets (eg., "[parameter]") are optional. If not
-given, the command will use suitable defaults. Parameters shown in angle
-brackets (eg., "") are required.
-
-Note that all commands operating on the server are actually performed by
-issuing a request to the server. Thus the behaviour may vary from server to
-server, depending on how the server was implemented.
-
-The commands available are given here in alphabetical order.
-
-.B ?
-.RS 3
-.B Parameters:
-.RS 3
-.I [command]
-
-.RE
-.B Description:
-.RS 3
-If
-.I command
-is specified, the
-.B ?
-command will display a brief informative message about the specified command.
-
-If no command is specified, a list of available commands will be displayed.
-.RE
-.RE
-
-.B !
-.RS 3
-.B Parameters:
-.RS 3
-.I [shell command]
-
-.RE
-.B Description:
-.RS 3
-If
-.I shell command
-is specified, the
-.B !
-command will execute a shell locally and run the specified shell command. If
-no command is specified, a shell will be run.
-.RE
-.RE
-
-.B cd
-.RS 3
-.B Parameters:
-.RS 3
-.I [directory name]
-
-.RE
-.B Description:
-.RS 3
-If
-.I directory name
-is specified, the current working directory
-.B on the server
-will be changed to the directory specified. This operation will fail if for
-any reason the specified directory is inaccessible.
-
-If no directory name is specified, the current working directory
-.B on the server
-will be reported.
-.RE
-.RE
-
-.B del
-.RS 3
-.B Parameters:
-.RS 3
-.I
-
-.RE
-.B Description:
-.RS 3
-The client will request that the server attempt to delete all files matching
-.I mask
-from the current working directory
-.B on the server.
-.RE
-.RE
-
-.B dir
-.RS 3
-.B Parameters:
-.RS 3
-.I
-
-.RE
-.B Description:
-.RS 3
-A list of the files matching
-.I mask
-in the current working directory
-.B on the server
-will be retrieved from the server and displayed.
-.RE
-.RE
-
-.B exit
-.RS 3
-.B Parameters:
-.RS 3
-None.
-
-.RE
-.B Description:
-.RS 3
-Terminate the connection with the server and exit from the program.
-.RE
-.RE
-
-.B get
-.RS 3
-.B Parameters:
-.RS 3
-.I [local file name]
-
-.RE
-.B Description:
-.RS 3
-Copy the file called
-.I remote file name
-from the server to the machine running the client. If specified, name the
-local copy
-.I local file name.
-Note that all transfers in
-.B smbclient
-are binary. See also the
-.B lowercase
-command.
-.RE
-.RE
-
-.B help
-.RS 3
-.B Parameters:
-.RS 3
-.I [command]
-
-.RE
-.B Description:
-.RS 3
-See the
-.B ?
-command above.
-.RE
-.RE
-
-.B lcd
-.RS 3
-.B Parameters:
-.RS 3
-.I [directory name]
-
-.RE
-.B Description:
-.RS 3
-If
-.I directory name
-is specified, the current working directory
-.B on the local machine
-will be changed to the directory specified. This operation will fail if for
-any reason the specified directory is inaccessible.
-
-If no directory name is specified, the name of the current working directory
-.B on the local machine
-will be reported.
-.RE
-.RE
-
-.B lowercase
-.RS 3
-.B Parameters:
-.RS 3
-None.
-
-.RE
-.B Description:
-.RS 3
-Toggle lowercasing of filenames for the
-.B get
-and
-.B mget
-commands.
-
-When lowercasing is toggled ON, local filenames are converted to lowercase
-when using the
-.B get
-and
-.B mget
-commands. This is often useful when copying (say) MSDOS files from a server,
-because lowercase filenames are the norm on UNIX systems.
-.RE
-.RE
-
-.B ls
-.RS 3
-.B Parameters:
-.RS 3
-.I
-
-.RE
-.B Description:
-.RS 3
-See the
-.B dir
-command above.
-.RE
-.RE
-
-.B mask
-.RS 3
-.B Parameters:
-.RS 3
-.I
-
-.RE
-.B Description:
-.RS 3
-This command allows the user to set up a mask which will be used during
-recursive operation of the
-.B mget
-and
-.B mput
-commands.
-
-The masks specified to the
-.B mget
-and
-.B mput
-commands act as filters for directories
-rather than files when recursion is toggled ON.
-
-The mask specified with the
-.B mask
-command is necessary to filter files within those directories. For example,
-if the mask specified in an
-.B mget
-command is "source*"
-.I and
-the mask specified with the
-.B mask
-command is "*.c"
-.I and
-recursion is toggled ON, the
-.B mget
-command will retrieve all files matching "*.c" in all directories below
-and including all directories matching "source*" in the current working
-directory.
-
-Note that the value for
-.I mask
-defaults to blank (equivalent to "*") and remains so until the
-.B mask
-command is used to change it. It retains the most recently specified value
-indefinitely. To avoid unexpected results it would be wise to change the
-value of
-.I mask
-back to "*" after using the
-.B mget
-or
-.B mput
-commands.
-.RE
-.RE
-
-.B md
-.RS 3
-.B Parameters:
-.RS 3
-.I
-
-.RE
-.B Description:
-.RS 3
-See the
-.B mkdir
-command.
-.RE
-.RE
-
-.B mget
-.RS 3
-.B Parameters:
-.RS 3
-.I
-
-.RE
-.B Description:
-.RS 3
-Copy all files matching
-.I mask
-from the server to the machine running the client.
-
-Note that
-.I mask
-is interpreted differently during recursive operation and non-recursive
-operation - refer to the
-.B recurse
-and
-.B mask
-commands for more information. Note that all transfers in
-.B smbclient
-are binary. See also the
-.B lowercase
-command.
-.RE
-.RE
-
-.B mkdir
-.RS 3
-.B Parameters:
-.RS 3
-.I
-
-.RE
-.B Description:
-.RS 3
-Create a new directory
-.B on the server
-(user access privileges permitting) with the specified name.
-.RE
-.RE
-
-.B mput
-.RS 3
-.B Parameters:
-.RS 3
-.I
-
-.RE
-.B Description:
-.RS 3
-Copy all files matching
-.I mask
-in the current working directory
-.B on the local machine
-to the current working directory on the server.
-
-Note that
-.I mask
-is interpreted differently during recursive operation and non-recursive
-operation - refer to the
-.B recurse
-and
-.B mask
-commands for more information. Note that all transfers in
-.B smbclient
-are binary.
-.RE
-.RE
-
-.B print
-.RS 3
-.B Parameters:
-.RS 3
-.I
-
-.RE
-.B Description:
-.RS 3
-Print the specified file
-.B from the local machine
-through a printable service on the server.
-
-See also the
-.B printmode
-command.
-.RE
-.RE
-
-.B printmode
-.RS 3
-.B Parameters:
-.RS 3
-.I
-
-.RE
-.B Description:
-.RS 3
-Set the print mode to suit either binary data (such as graphical information)
-or text. Subsequent
-.B print
-commands will use the currently set print mode.
-.RE
-.RE
-
-.B prompt
-.RS 3
-.B Parameters:
-.RS 3
-None.
-
-.RE
-.B Description:
-.RS 3
-Toggle prompting for filenames during operation of the
-.B mget
-and
-.B mput
-commands.
-
-When toggled ON, the user will be prompted to confirm the transfer of each
-file during these commands. When toggled OFF, all specified files will be
-transferred without prompting.
-.RE
-.RE
-
-.B put
-.RS 3
-.B Parameters:
-.RS 3
-.I [remote file name]
-
-.RE
-.B Description:
-.RS 3
-Copy the file called
-.I local file name
-from the machine running the client to the server. If specified, name the
-remote copy
-.I remote file name.
-Note that all transfers in
-.B smbclient
-are binary. See also the
-.B lowercase
-command.
-.RE
-.RE
-
-.B queue
-.RS 3
-.B Parameters:
-.RS 3
-None.
-
-.RE
-.B Description:
-.RS 3
-Displays the print queue, showing the job id, name, size and current status.
-.RE
-.RE
-
-.B quit
-.RS 3
-.B Parameters:
-.RS 3
-None.
-
-.RE
-.B Description:
-.RS 3
-See the
-.B exit
-command.
-.RE
-.RE
-
-.B rd
-.RS 3
-.B Parameters:
-.RS 3
-.I
-
-.RE
-.B Description:
-.RS 3
-See the
-.B rmdir
-command.
-.RE
-.RE
-
-.B recurse
-.RS 3
-.B Parameters:
-.RS 3
-None.
-
-.RE
-.B Description:
-.RS 3
-Toggle directory recursion for the commands
-.B mget
-and
-.BR mput .
-
-When toggled ON, these commands will process all directories in the source
-directory (i.e., the directory they are copying
-.IR from )
-and will recurse into any that match the mask specified to the command. Only
-files that match the mask specified using the
-.B mask
-command will be retrieved. See also the
-.B mask
-command.
-
-When recursion is toggled OFF, only files from the current working
-directory on the source machine that match the mask specified to the
-.B mget
-or
-.B mput
-commands will be copied, and any mask specified using the
-.B mask
-command will be ignored.
-.RE
-.RE
-
-.B rm
-.RS 3
-.B Parameters:
-.RS 3
-.I
-
-.RE
-.B Description:
-.RS 3
-Remove all files matching
-.I mask
-from the current working directory
-.B on the server.
-.RE
-.RE
-
-.B rmdir
-.RS 3
-.B Parameters:
-.RS 3
-.I
-
-.RE
-.B Description:
-.RS 3
-Remove the specified directory (user access privileges permitting)
-.B from the server.
-.RE
-.RE
-
-.B tar
-.RS 3
-.B Parameters:
-.RS 3
-.I [IXbgNa]
-
-.RE
-.B Description:
-.RS 3
-Performs a tar operation - see the
-.B \-T
-command line option above. Behaviour
-may be affected by the
-.B tarmode
-command (see below). Using g (incremental) and N (newer) will affect
-tarmode settings. Note that using the "\-" option with tar x may not
-work - use the command line option instead.
-.RE
-.RE
-
-.B blocksize
-.RS 3
-.B Parameters
-.RS 3
-.I
-
-.RE
-.B Description
-.RS 3
-Blocksize. Must be followed by a valid (greater than zero) blocksize.
-Causes tar file to be written out in blocksize*TBLOCK (usually 512 byte)
-blocks.
-.RE
-.RE
-
-.B tarmode
-.RS 3
-.B Parameters
-.RS 3
-.I
-
-.RE
-.B Description
-.RS 3
-Changes tar's behaviour with regard to archive bits. In full mode,
-tar will back up everything regardless of the archive bit setting (this
-is the default mode). In incremental mode, tar will only back up files
-with the archive bit set. In reset mode, tar will reset the archive bit
-on all files it backs up (implies read/write share).
-.RE
-.RE
-
-.B setmode
-.RS 3
-.B Parameters
-.RS 3
-.I
-
-.RE
-.B Description
-.RS 3
-A version of the DOS attrib command to set file permissions. For example,
-
-setmode myfile +r
-
-would make myfile read only.
-.RE
-.RE
-.SH NOTES
-Some servers are fussy about the case of supplied usernames, passwords, share
-names (aka service names) and machine names. If you fail to connect try
-giving all parameters in uppercase.
-
-It is often necessary to use the
-.B \-n
-option when connecting to some types
-of servers. For example OS/2 LanManager insists on a valid netbios name
-being used, so you need to supply a valid name that would be known to
-the server.
-
-.B smbclient
-supports long file names where the server supports the LANMAN2
-protocol.
-.SH FILES
-Not applicable.
-.SH ENVIRONMENT VARIABLES
-.B USER
-.RS 3
-The variable USER may contain the username of the person using the client.
-This information is used only if the protocol level is high enough to support
-session-level passwords.
-.RE
-.SH INSTALLATION
-The location of the client program is a matter for individual system
-administrators. The following are thus suggestions only.
-
-It is recommended that the client software be installed under the
-/usr/local/samba
-hierarchy, in a directory readable by all, writeable only by root. The client
-program itself should be executable by all. The client should NOT be setuid
-or setgid!
-
-The client log files should be put in a directory readable and writable only
-by the user.
-
-To test the client, you will need to know the name of a running Lan manager
-server. It is possible to run
-.B smbd
-(see
-.BR smbd (8))
-as an ordinary user - running that server as a daemon on a
-user-accessible port (typically any port number over 1024) would
-provide a suitable test server.
-.SH VERSION
-This man page is (mostly) correct for version 1.9.00 of the Samba suite, plus some
-of the recent patches to it. These notes will necessarily lag behind
-development of the client software, so it is possible that your version of
-the client has extensions or parameter semantics that differ from or are not
-covered by this man page. Please notify these to the address below for
-rectification.
-.SH SEE ALSO
-.BR smbd (8)
-.SH DIAGNOSTICS
-[This section under construction]
-
-Most diagnostics issued by the client are logged in a specified log file. The
-log file name is specified at compile time, but may be overridden on the
-command line.
-
-The number and nature of diagnostics available depends on the debug level used
-by the client. If you have problems, set the debug level to 3 and peruse the
-log files.
-
-Most messages are reasonably self-explanatory. Unfortunately, at time of
-creation of this man page the source code is still too fluid to warrant
-describing each and every diagnostic. At this stage your best bet is still
-to grep the source code and inspect the conditions that gave rise to the
-diagnostics you are seeing.
-.SH BUGS
-None known.
-.SH CREDITS
-The original Samba software and related utilities were created by
-Andrew Tridgell (samba-bugs@samba.anu.edu.au). Andrew is also the Keeper
-of the Source for this project.
-
-See
-.BR smb.conf (5)
-for a full list of contributors and details on how to
-submit bug reports, comments etc.
diff --git a/docs/manpages/smbd.8 b/docs/manpages/smbd.8
deleted file mode 100644
index 6c26c83c0d1..00000000000
--- a/docs/manpages/smbd.8
+++ /dev/null
@@ -1,418 +0,0 @@
-.TH SMBD 8 smbd smbd
-.SH NAME
-smbd \- provide SMB (aka LanManager) services to clients
-.SH SYNOPSIS
-.B smbd
-[
-.B \-D
-] [
-.B \-a
-] [
-.B \-d
-.I debuglevel
-] [
-.B \-l
-.I log file
-] [
-.B \-p
-.I port number
-] [
-.B \-O
-.I socket options
-] [
-.B \-s
-.I configuration file
-]
-.SH DESCRIPTION
-This program is part of the Samba suite.
-
-.B smbd
-is a server that can provide most SMB services. The
-server provides filespace and printer services to clients using the SMB
-protocol. This is compatible with the LanManager protocol, and can
-service LanManager clients.
-
-An extensive description of the services that the server can provide is given
-in the man page for the configuration file controlling the attributes of those
-services (see
-.BR smb.conf (5)).
-This man page will not describe the services, but
-will concentrate on the administrative aspects of running the server.
-
-Please note that there are significant security implications to running this
-server, and
-.BR smb.conf (5)
-should be regarded as mandatory reading before proceeding with
-installation.
-
-A session is created whenever a client requests one. Each client gets a copy
-of the server for each session. This copy then services all connections made
-by the client during that session. When all connections from its client are
-are closed, the copy of the server for that client terminates.
-
-The configuration file is automatically reloaded if it changes. You
-can force a reload by sending a SIGHUP to the server.
-.SH OPTIONS
-.B \-D
-
-.RS 3
-If specified, this parameter causes the server to operate as a daemon. That is,
-it detaches itself and runs in the background, fielding requests on the
-appropriate port.
-
-By default, the server will NOT operate as a daemon.
-.RE
-
-.B \-a
-
-.RS 3
-If this parameter is specified, the log files will be overwritten with each
-new connection. By default, the log files will be appended to.
-.RE
-
-.B \-d
-.I debuglevel
-.RS 3
-
-debuglevel is an integer from 0 to 5.
-
-The default value if this parameter is not specified is zero.
-
-The higher this value, the more detail will be logged to the log files about
-the activities of the server. At level 0, only critical errors and serious
-warnings will be logged. Level 1 is a reasonable level for day to day running
-- it generates a small amount of information about operations carried out.
-
-Levels above 1 will generate considerable amounts of log data, and should
-only be used when investigating a problem. Levels above 3 are designed for
-use only by developers and generate HUGE amounts of log data, most of which
-is extremely cryptic.
-.RE
-
-.B \-l
-.I log file
-
-.RS 3
-If specified,
-.I logfile
-specifies a base filename into which operational data from the running server
-will be logged.
-
-The default base name is specified at compile time.
-
-The base name is used to generate actual log file names. For example, if the
-name specified was "log", the following files would be used for log data:
-
-.RS 3
-log.debug (containing debugging information)
-
-log.in (containing inbound transaction data)
-
-log.out (containing outbound transaction data)
-.RE
-
-The log files generated are never removed by the server.
-.RE
-
-.B \-O
-.I socket options
-.RS 3
-
-See the socket options section of
-.BR smb.conf (5)
-for details
-
-.RE
-.B \-p
-.I port number
-.RS 3
-
-port number is a positive integer value.
-
-The default value if this parameter is not specified is 139.
-
-This number is the port number that will be used when making connections to
-the server from client software. The standard (well-known) port number for the
-server is 139, hence the default. If you wish to run the server as an ordinary
-user rather than as root, most systems will require you to use a port number
-greater than 1024 - ask your system administrator for help if you are in this
-situation.
-
-This parameter is not normally specified except in the above situation.
-.RE
-
-.B \-s
-.I configuration file
-
-.RS 3
-The default configuration file name is determined at compile time.
-
-The file specified contains the configuration details required by the server.
-The information in this file includes server-specific information such as
-what printcap file to use, as well as descriptions of all the services that the
-server is to provide. See
-.BR smb.conf (5)
-for more information.
-.RE
-.SH FILES
-
-.B /etc/inetd.conf
-
-.RS 3
-If the server is to be run by the inetd meta-daemon, this file must contain
-suitable startup information for the meta-daemon. See the section
-"INSTALLATION" below.
-.RE
-
-.B /etc/rc
-
-.RS 3
-(or whatever initialisation script your system uses)
-
-If running the server as a daemon at startup, this file will need to contain
-an appropriate startup sequence for the server. See the section "INSTALLATION"
-below.
-.RE
-
-.B /etc/services
-
-.RS 3
-If running the server via the meta-daemon inetd, this file must contain a
-mapping of service name (eg., netbios-ssn) to service port (eg., 139) and
-protocol type (eg., tcp). See the section "INSTALLATION" below.
-.RE
-
-.B /usr/local/samba/lib/smb.conf
-
-.RS 3
-This file describes all the services the server is to make available to
-clients. See
-.BR smb.conf (5)
-for more information.
-.RE
-.SH LIMITATIONS
-
-On some systems
-.B smbd
-cannot change uid back to root after a setuid() call.
-Such systems are called "trapdoor" uid systems. If you have such a system,
-you will be unable to connect from a client (such as a PC) as two different
-users at once. Attempts to connect the second user will result in "access
-denied" or similar.
-.SH ENVIRONMENT VARIABLES
-
-.B PRINTER
-
-.RS 3
-If no printer name is specified to printable services, most systems will
-use the value of this variable (or "lp" if this variable is not defined)
-as the name of the printer to use. This is not specific to the server,
-however.
-.RE
-.SH INSTALLATION
-The location of the server and its support files is a matter for individual
-system administrators. The following are thus suggestions only.
-
-It is recommended that the server software be installed under the
-/usr/local/samba hierarchy, in a directory readable by all, writeable only
-by root. The server program itself should be executable by all, as
-users may wish to run the server themselves (in which case it will of
-course run with their privileges). The server should NOT be
-setuid. On some systems it may be worthwhile to make smbd setgid to an
-empty group. This is because some systems may have a security hole where
-daemon processes that become a user can be attached to with a
-debugger. Making the smbd file setgid to an empty group may prevent
-this hole from being exploited. This security hole and the suggested
-fix has only been confirmed on Linux at the time this was written. It
-is possible that this hole only exists in Linux, as testing on other
-systems has thus far shown them to be immune.
-
-The server log files should be put in a directory readable and writable only
-by root, as the log files may contain sensitive information.
-
-The configuration file should be placed in a directory readable and writable
-only by root, as the configuration file controls security for the services
-offered by the server. The configuration file can be made readable by all if
-desired, but this is not necessary for correct operation of the server and
-is not recommended. A sample configuration file "smb.conf.sample" is supplied
-with the source to the server - this may be renamed to "smb.conf" and
-modified to suit your needs.
-
-The remaining notes will assume the following:
-
-.RS 3
-.B smbd
-(the server program) installed in /usr/local/samba/bin
-
-smb.conf (the configuration file) installed in /usr/local/samba/lib
-
-log files stored in /var/adm/smblogs
-.RE
-
-The server may be run either as a daemon by users or at startup, or it may
-be run from a meta-daemon such as inetd upon request. If run as a daemon, the
-server will always be ready, so starting sessions will be faster. If run from
-a meta-daemon some memory will be saved and utilities such as the tcpd
-TCP-wrapper may be used for extra security.
-
-When you've decided, continue with either "RUNNING THE SERVER AS A DAEMON" or
-"RUNNING THE SERVER ON REQUEST".
-.SH RUNNING THE SERVER AS A DAEMON
-To run the server as a daemon from the command line, simply put the
-.B \-D
-option
-on the command line. There is no need to place an ampersand at the end of the
-command line - the
-.B \-D
-option causes the server to detach itself from the
-tty anyway.
-
-Any user can run the server as a daemon (execute permissions permitting, of
-course). This is useful for testing purposes, and may even be useful as a
-temporary substitute for something like ftp. When run this way, however, the
-server will only have the privileges of the user who ran it.
-
-To ensure that the server is run as a daemon whenever the machine is started,
-and to ensure that it runs as root so that it can serve multiple clients, you
-will need to modify the system startup files. Wherever appropriate (for
-example, in /etc/rc), insert the following line, substituting
-port number, log file location, configuration file location and debug level as
-desired:
-
-.RS 3
-/usr/local/samba/bin/smbd -D -l /var/adm/smblogs/log -s /usr/local/samba/lib/smb.conf
-.RE
-
-(The above should appear in your initialisation script as a single line.
-Depending on your terminal characteristics, it may not appear that way in
-this man page. If the above appears as more than one line, please treat any
-newlines or indentation as a single space or TAB character.)
-
-If the options used at compile time are appropriate for your system, all
-parameters except the desired debug level and
-.B \-D
-may be omitted. See the
-section "OPTIONS" above.
-.SH RUNNING THE SERVER ON REQUEST
-If your system uses a meta-daemon such as inetd, you can arrange to have the
-smbd server started whenever a process attempts to connect to it. This requires
-several changes to the startup files on the host machine. If you are
-experimenting as an ordinary user rather than as root, you will need the
-assistance of your system administrator to modify the system files.
-
-You will probably want to set up the name server
-.B nmbd
-at the same time as
-.B smbd
-- refer to the man page
-.BR nmbd (8).
-
-First, ensure that a port is configured in the file /etc/services. The
-well-known port 139 should be used if possible, though any port may be used.
-
-Ensure that a line similar to the following is in /etc/services:
-
-.RS 3
-netbios-ssn 139/tcp
-.RE
-
-Note for NIS/YP users - you may need to rebuild the NIS service maps rather
-than alter your local /etc/services file.
-
-Next, put a suitable line in the file /etc/inetd.conf (in the unlikely event
-that you are using a meta-daemon other than inetd, you are on your own). Note
-that the first item in this line matches the service name in /etc/services.
-Substitute appropriate values for your system in this line (see
-.BR inetd (8)):
-
-.RS 3
-.\" turn off right adjustment
-.ad l
-netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd -d1
--l/var/adm/smblogs/log -s/usr/local/samba/lib/smb.conf
-.ad
-.RE
-
-(The above should appear in /etc/inetd.conf as a single line. Depending on
-your terminal characteristics, it may not appear that way in this man page.
-If the above appears as more than one line, please treat any newlines or
-indentation as a single space or TAB character.)
-
-Note that there is no need to specify a port number here, even if you are
-using a non-standard port number.
-
-Lastly, edit the configuration file to provide suitable services. To start
-with, the following two services should be all you need:
-
-.RS 3
-[homes]
-.RS 3
- writable = yes
-.RE
-
-[printers]
-.RS 3
- writable = no
- printable = yes
- path = /tmp
- public = yes
-.RE
-.RE
-
-This will allow you to connect to your home directory and print to any printer
-supported by the host (user privileges permitting).
-.SH TESTING THE INSTALLATION
-If running the server as a daemon, execute it before proceeding. If
-using a meta-daemon, either restart the system or kill and restart the
-meta-daemon. Some versions of inetd will reread their configuration tables if
-they receive a HUP signal.
-
-If your machine's name is "fred" and your name is "mary", you should now be
-able to connect to the service "\e\efred\emary".
-
-To properly test and experiment with the server, we recommend using the
-smbclient program (see
-.BR smbclient (1)).
-.SH VERSION
-This man page is (mostly) correct for version 1.9.00 of the Samba suite, plus some
-of the recent patches to it. These notes will necessarily lag behind
-development of the software, so it is possible that your version of
-the server has extensions or parameter semantics that differ from or are not
-covered by this man page. Please notify these to the address below for
-rectification.
-.SH SEE ALSO
-.BR hosts_access (5),
-.BR inetd (8),
-.BR nmbd (8),
-.BR smb.conf (5),
-.BR smbclient (1),
-.BR testparm (1),
-.BR testprns (1)
-.SH DIAGNOSTICS
-[This section under construction]
-
-Most diagnostics issued by the server are logged in a specified log file. The
-log file name is specified at compile time, but may be overridden on the
-command line.
-
-The number and nature of diagnostics available depends on the debug level used
-by the server. If you have problems, set the debug level to 3 and peruse the
-log files.
-
-Most messages are reasonably self-explanatory. Unfortunately, at time of
-creation of this man page the source code is still too fluid to warrant
-describing each and every diagnostic. At this stage your best bet is still
-to grep the source code and inspect the conditions that gave rise to the
-diagnostics you are seeing.
-.SH BUGS
-None known.
-.SH CREDITS
-The original Samba software and related utilities were created by
-Andrew Tridgell (samba-bugs@samba.anu.edu.au). Andrew is also the Keeper
-of the Source for this project.
-
-
-See
-.BR smb.conf (5)
-for a full list of contributors and details on how to
-submit bug reports, comments etc.
diff --git a/docs/manpages/smbrun.1 b/docs/manpages/smbrun.1
deleted file mode 100644
index c6b2a91fa83..00000000000
--- a/docs/manpages/smbrun.1
+++ /dev/null
@@ -1,74 +0,0 @@
-.TH SMBRUN 1 smbrun smbrun
-.SH NAME
-smbrun \- interface program between smbd and external programs
-.SH SYNOPSIS
-.B smbrun
-.I shell-command
-.SH DESCRIPTION
-This program is part of the Samba suite.
-
-.B smbrun
-is a very small 'glue' program, which runs shell commands for
-the
-.B smbd
-daemon (see
-.BR smbd (8)).
-
-It first changes to the highest effective user and group ID that it can,
-then runs the command line provided using the system() call. This program is
-necessary to allow some operating systems to run external programs as non-root.
-.SH OPTIONS
-.I shell-command
-
-.RS 3
-The shell command to execute.
-
-The command should have a fully-qualified path.
-.RE
-.SH ENVIRONMENT VARIABLES
-The PATH variable set for the environment in which
-.B smbrun
-is executed will affect what executables are located and executed if a
-fully-qualified path is not given in the command.
-.SH INSTALLATION
-The location of the server and its support files is a matter for individual
-system administrators. The following are thus suggestions only.
-
-It is recommended that the
-.B smbrun
-program be installed under the /usr/local/samba hierarchy, in a directory readable
-by all, writeable only by root. The program should be executable by all.
-The program should NOT be setuid or setgid!
-.SH VERSION
-This man page is (mostly) correct for version 1.9.00 of the Samba suite, plus some
-of the recent patches to it. These notes will necessarily lag behind
-development of the software, so it is possible that your version of
-the program has extensions or parameter semantics that differ from or are not
-covered by this man page. Please notify these to the address below for
-rectification.
-.SH SEE ALSO
-.BR smbd (8),
-.BR smb.conf (8)
-.SH DIAGNOSTICS
-If
-.B smbrun
-cannot be located or cannot be executed by
-.B smbd
-then appropriate messages will be found in the
-.B smbd
-logs. Other diagnostics are
-dependent on the shell-command being run. It is advisable for your shell
-commands to issue suitable diagnostics to aid trouble-shooting.
-.SH BUGS
-None known.
-.SH CREDITS
-The original Samba software and related utilities were created by
-Andrew Tridgell (samba-bugs@samba.anu.edu.au). Andrew is also the Keeper
-of the Source for this project.
-
-This man page was written by Karl Auer. Bug reports to samba-bugs@anu.edu.au.
-
-See
-.BR smb.conf (5)
-for a full list of contributors and details of how to
-submit bug reports, comments etc.
diff --git a/docs/manpages/smbstatus.1 b/docs/manpages/smbstatus.1
deleted file mode 100644
index e59f815b78b..00000000000
--- a/docs/manpages/smbstatus.1
+++ /dev/null
@@ -1,70 +0,0 @@
-.TH SMBSTATUS 1 smbstatus smbstatus
-.SH NAME
-smbstatus \- report on current Samba connections
-.SH SYNOPSIS
-.B smbstatus
-[
-.B \-b
-] [
-.B \-d
-] [
-.B \-p
-] [
-.B \-s
-.I configuration file
-]
-.SH DESCRIPTION
-This program is part of the Samba suite.
-
-.B smbstatus
-is a very simple program to list the current Samba connections.
-
-Just run the program and the output is self explanatory.
-.SH OPTIONS
-.B \-b
-gives brief output.
-
-.B \-d
-gives verbose output.
-
-.B \-p
-print a list of
-.B smbd
-processes and exit. Useful for scripting.
-
-.B \-s
-.I configuration file
-
-.RS 3
-The default configuration file name is determined at compile time.
-
-The file specified contains the configuration details required by the server.
-See
-.BR smb.conf (5)
-for more information.
-.RE
-.SH ENVIRONMENT VARIABLES
-Not applicable.
-.SH INSTALLATION
-The location of the server and its support files is a matter for individual
-system administrators. The following are thus suggestions only.
-
-It is recommended that the
-.B smbstatus
-program be installed under the /usr/local/samba hierarchy, in a directory readable
-by all, writeable only by root. The program itself should be executable by all.
-.SH VERSION
-This man page is (mostly) correct for version 1.9.00 of the Samba suite, plus some
-of the recent patches to it. These notes will necessarily lag behind
-development of the software, so it is possible that your version of
-the program has extensions or parameter semantics that differ from or are not
-covered by this man page. Please notify these to the address below for
-rectification.
-.SH SEE ALSO
-.BR smb.conf (5),
-.BR smbd (8)
-
-See
-.BR smb.conf (5)
-for a full list of contributors and details on how to
-submit bug reports, comments etc.
diff --git a/docs/manpages/smbtar.1 b/docs/manpages/smbtar.1
deleted file mode 100644
index 75fbac17954..00000000000
--- a/docs/manpages/smbtar.1
+++ /dev/null
@@ -1,178 +0,0 @@
-.TH SMBTAR 1 smbtar smbtar
-.SH NAME
-smbtar \- shell script for backing up SMB shares directly to UNIX tape drive
-.SH SYNOPSIS
-.B smbtar
-.B \-s
-.I server
-[
-.B \-p
-.I password
-] [
-.B \-x
-.I service
-] [
-.B \-X
-] [
-.B \-d
-.I directory
-] [
-.B \-u
-.I user
-] [
-.B \-t
-.I tape
-] [
-.B \-b
-.I blocksize
-] [
-.B \-N
-.I filename
-] [
-.B \-i
-] [
-.B \-r
-] [
-.B \-l
-.I log level
-] [
-.B \-v
-]
-.I filenames...
-.SH DESCRIPTION
-This program is an extension to the Samba suite.
-
-.B smbtar
-is a very small shell script on top of
-.BR smbclient ,
-which dumps SMB shares directly to tape.
-.SH OPTIONS
-.B \-s
-.I server
-.RS 3
-The PC that the share resides upon.
-.RE
-
-.B \-x
-.I service
-.RS 3
-The share name on the PC to connect to. Default:
-.I backup.
-.RE
-
-.B \-X
-.RS 3
-Exclude mode. Exclude
-.I filenames...
-from tar create or restore.
-.RE
-
-.B \-d
-.I directory
-.RS 3
-Change to initial
-.I directory
-before restoring / backing up files.
-.RE
-
-.B \-v
-.RS 3
-Verbose mode.
-.RE
-
-.B \-p
-.I password
-
-.RS 3
-The password to use to access a share. Default: none
-.RE
-
-.B \-u
-.I user
-.RS 3
-The user id to connect as. Default: UNIX login name.
-.RE
-
-.B \-t
-.I tape
-.RS 3
-Tape device. May be regular file or tape device. Default: Tape environmental
-variable; if not set, a file called
-.IR tar.out .
-.RE
-
-.B \-b
-.I blocksize
-.RS 3
-Blocking factor. Defaults to 20. See
-.BR tar (1)
-for a fuller explanation.
-.RE
-
-.B \-N
-.I filename
-.RS 3
-Backup only files newer than filename. Could be used (for example) on a log
-file to implement incremental backups.
-.RE
-
-.B \-i
-.RS 3
-Incremental mode; tar files are only backed up if they have the
-archive bit set. The archive bit is reset after each file is read.
-.RE
-
-.B \-r
-.RS 3
-Restore. Files are restored to the share from the tar file.
-.RE
-
-.B \-l
-.I log level
-.RS 3
-Log (debug) level. Corresponds to
-.B \-d
-flag of
-.BR smbclient (1).
-.RE
-.SH ENVIRONMENT VARIABLES
-The TAPE variable specifies the default tape device to write to. May
-be overridden with the
-.B \-t
-option.
-.SH BUGS
-The
-.B smbtar
-script has different options from ordinary tar and tar
-called from
-.BR smbclient .
-.SH CAVEATS
-Sites that are more careful about security may not like the way
-the script handles PC passwords. Backup and restore work on entire shares,
-should work on file lists.
-.SH VERSION
-This man page is correct for version 1.9.15p8 of the Samba suite.
-.SH SEE ALSO
-.BR smbclient (8),
-.BR smb.conf (8)
-.SH DIAGNOSTICS
-See diagnostics for
-.B smbclient
-command.
-.SH CREDITS
-The original Samba software and related utilities were created by
-Andrew Tridgell (samba-bugs@samba.anu.edu.au). Andrew is also the Keeper
-of the Source for this project.
-
-Ricky Poulten (poultenr@logica.co.uk) wrote the tar extension and this
-man page. The
-.B smbtar
-script was heavily rewritten and improved by
-Martin Kraemer . Many thanks to everyone
-who suggested extensions, improvements, bug fixes, etc.
-
-See
-.BR smb.conf (5)
-for a full list of contributors and details of how to submit bug reports,
-comments etc.
-
diff --git a/docs/manpages/testparm.1 b/docs/manpages/testparm.1
deleted file mode 100644
index 9cdc1406996..00000000000
--- a/docs/manpages/testparm.1
+++ /dev/null
@@ -1,109 +0,0 @@
-.TH TESTPARM 1 testparm testparm
-.SH NAME
-testparm \- check an smbd configuration file for internal correctness
-.SH SYNOPSIS
-.B testparm
-[
-.I configfilename
-[
-.I hostname
-.I hostIP
-]
-]
-.SH DESCRIPTION
-This program is part of the Samba suite.
-
-.B testparm
-is a very simple test program to check an
-.B smbd
-configuration
-file for internal correctness. If this program reports no problems, you can use
-the configuration file with confidence that
-.B smbd
-will successfully
-load the configuration file.
-
-Note that this is NOT a guarantee that the services specified in the
-configuration file will be available or will operate as expected.
-
-If the optional host name and host IP address are specified on the
-command line, this test program will run through the service entries
-reporting whether the specified host has access to each service.
-.SH OPTIONS
-.I configfilename
-
-.RS 3
-This is the name of the configuration file to check.
-.RE
-
-.I hostname
-
-.RS 3
-This is the name of the host to check access on.
-
-If this parameter is supplied, the
-.I hostIP
-parameter must also be supplied, or strange things may happen.
-.RE
-
-.I hostIP
-
-.RS 3
-This is the IP number of the host specified in the previous parameter.
-
-This number must be supplied if the
-.I hostname
-parameter is supplied, or strange things may happen.
-.RE
-.SH FILES
-.B smb.conf
-.RS 3
-This is usually the name of the configuration file used by
-.BR smbd .
-.RE
-.SH ENVIRONMENT VARIABLES
-Not applicable.
-.SH INSTALLATION
-The location of the server and its support files is a matter for individual
-system administrators. The following are thus suggestions only.
-
-It is recommended that the
-.B testparm
-program be installed under the /usr/local/samba hierarchy, in a directory readable
-by all, writeable only by root. The program itself should be executable by all.
-The program should NOT be setuid or setgid!
-.SH VERSION
-This man page is (mostly) correct for version 1.9.00 of the Samba suite, plus some
-of the recent patches to it. These notes will necessarily lag behind
-development of the software, so it is possible that your version of
-the program has extensions or parameter semantics that differ from or are not
-covered by this man page. Please notify these to the address below for
-rectification.
-.SH SEE ALSO
-.BR smb.conf (5),
-.BR smbd (8)
-.SH DIAGNOSTICS
-The program will issue a message saying whether the configuration file loaded
-OK or not. This message may be preceded by errors and warnings if the file
-did not load. If the file was loaded OK, the program then dumps all known
-service details to stdout.
-
-If a host name is specified but no host IP number, all bets are off.
-
-Other messages are self-explanatory.
-.SH BUGS
-None known.
-.SH CREDITS
-The original Samba software and related utilities were created by
-Andrew Tridgell (samba-bugs@samba.anu.edu.au). Andrew is also the Keeper
-of the Source for this project.
-
-The
-.B testparm
-program and this man page were written by Karl Auer. Bug reports to
-samba-bugs@anu.edu.au.
-
-See
-.BR samba (7)
-for a full list of contributors and details on how to
-submit bug reports, comments etc.
diff --git a/docs/manpages/testprns.1 b/docs/manpages/testprns.1
deleted file mode 100644
index 94908a55814..00000000000
--- a/docs/manpages/testprns.1
+++ /dev/null
@@ -1,112 +0,0 @@
-.TH TESTPRNS 1 testprns testprns
-.SH NAME
-testprns \- check printer name for validity with smbd
-.SH SYNOPSIS
-.B testprns
-.I printername
-[
-.I printcapname
-]
-.SH DESCRIPTION
-This program is part of the Samba suite.
-
-.B testprns
-is a very simple test program to determine whether a given
-printer name is valid for use in a service to be provided by
-.B smbd.
-
-"Valid" in this context means "can be found in the printcap specified". This
-program is very stupid - so stupid in fact that it would be wisest to always
-specify the printcap file to use.
-.SH OPTIONS
-.I printername
-
-.RS 3
-The printer name to validate.
-
-Printer names are taken from the first field in each record in the printcap
-file, single printer names and sets of aliases separated by vertical bars
-("|") are recognised. Note that no validation or checking of the printcap
-syntax is done beyond that required to extract the printer name. It may
-be that the print spooling system is more forgiving or less forgiving
-than
-.BR testprns .
-However, if
-.B testprns
-finds the printer then
-.B smbd
-should do so as well.
-.RE
-
-.I printcapname
-
-.RS 3
-This is the name of the printcap file to search for the given printer name
-in.
-
-If no printcap name is specified,
-.B testprns
-will attempt to scan the printcap file specified at compile time
-(PRINTCAP_NAME).
-.RE
-.SH FILES
-.B /etc/printcap
-.RS 3
-This is usually the default printcap file to scan. See
-.BR printcap (5)).
-.RE
-.SH ENVIRONMENT VARIABLES
-Not applicable.
-.SH INSTALLATION
-The location of the server and its support files is a matter for individual
-system administrators. The following are thus suggestions only.
-
-It is recommended that the
-.B testprns
-program be installed under the /usr/local/samba hierarchy, in a directory readable
-by all, writeable only by root. The program should be executable by all.
-The program should NOT be setuid or setgid!
-.SH VERSION
-This man page is (mostly) correct for version 1.9.00 of the Samba suite, plus some
-of the recent patches to it. These notes will necessarily lag behind
-development of the software, so it is possible that your version of
-the program has extensions or parameter semantics that differ from or are not
-covered by this man page. Please notify these to the address below for
-rectification.
-.SH SEE ALSO
-.BR printcap (5),
-.BR smbd (8),
-.BR smbclient (1)
-.SH DIAGNOSTICS
-If a printer is found to be valid, the message "Printer name is
-valid" will be displayed.
-
-If a printer is found to be invalid, the message "Printer name
-is not valid" will be displayed.
-
-All messages that would normally be logged during operation of
-.B smbd
-are
-logged by this program to the file
-.I test.log
-in the current directory. The program runs at debuglevel 3, so quite extensive
-logging information is written. The log should be checked carefully for errors
-and warnings.
-
-Other messages are self-explanatory.
-.SH BUGS
-None known.
-.SH CREDITS
-The original Samba software and related utilities were created by
-Andrew Tridgell (samba-bugs@samba.anu.edu.au). Andrew is also the Keeper
-of the Source for this project.
-
-The
-.B testprns
-program and this man page were written by Karl Auer. Bug reports to
-samba-bugs@anu.edu.au.
-
-See
-.BR samba (7)
-for a full list of contributors and details of how to
-submit bug reports, comments etc.
diff --git a/docs/samba.faq b/docs/samba.faq
deleted file mode 100644
index e74585b9769..00000000000
--- a/docs/samba.faq
+++ /dev/null
@@ -1,900 +0,0 @@
-
- Frequently Asked Questions
-
- about the
-
- SAMBA Suite
-
- (FAQ version 1.9.15a, Samba version 1.09.15)
-
--------------------------------------------------------------------------------
-
-This FAQ was originally prepared by Karl Auer and is
-currently maintained by Paul Blackman (ictinus@lake.canberra.edu.au).
-
-As Karl originally said, 'this FAQ was prepared with lots of help from numerous
-net.helpers', and that's the way I'd like to keep it. So if you find anything
-that you think should be in here don't hesitate to contact me.
-
-Thanks to Karl for the work he's done, and continuing thanks to Andrew Tridgell
-for developing Samba.
-
-Note: This FAQ is (and probably always will be) under construction. Some
-sections exist only as optimistic entries in the Contents page.
-
--------------------------------------------------------------------------------
-
-Contents
-
- * SECTION ONE: General information
- All about Samba - what it is, how to get it, related sources of
- information, how to understand the version numbering scheme,
- pizza details
- * SECTION TWO: Compiling and installing Samba on a Unix host
- Common problems that arise when building and installing Samba under
- Unix.
- * SECTION THREE: Common client problems
- Common problems that arise when trying to communicate from a client
- computer to a Samba server. All problems which have symptoms you see
- at the client end will be in this section.
- * SECTION FOUR: Specific client problems
- This section covers problems that are specific to certain clients,
- such as Windows for Workgroups or Windows NT. Please check Section
- Three first!
- * SECTION FIVE: Specific client application problems
- This section covers problems that are specific to certain products,
- such as Windows for Workgroups or Windows NT. Please check Sections
- Three and Four first!
- * SECTION SIX: Miscellaneous
- All the questions that aren't classifiable into any other section.
-
-
-===============================================================================
-SECTION ONE: General information
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 1: What is Samba?
-
-Samba is a suite of programs which work together to allow clients to access
-to a server's filespace and printers via the SMB (Session Message Block)
-protocol. Initially written for Unix, Samba now also runs on Netware, OS/2 and
-AmigaDOS.
-
-In practice, this means that you can redirect disks and printers to Unix disks
-and printers from Lan Manager clients, Windows for Workgroups 3.11 clients,
-Windows NT clients, Linux clients and OS/2 clients. There is also a generic
-Unix client program supplied as part of the suite which allows Unix users to
-use an ftp-like interface to access filespace and printers on any other SMB
-servers. This gives the capability for these operating systems to behave much
-like a LAN Server or Windows NT Server machine, only with added functionality
-and flexibility designed to make life easier for administrators.
-
-The components of the suite are (in summary):
-
- * smbd, the SMB server. This handles actual connections from clients,
- doing all the file, permission and username work
- * nmbd, the Netbios name server, which helps clients locate servers,
- doing the browsing work and managing domains as this capability is
- being built into Samba
- * smbclient, the Unix-hosted client program
- * smbrun, a little 'glue' program to help the server run external
- programs
- * testprns, a program to test server access to printers
- * testparms, a program to test the Samba configuration file for
- correctness
- * smb.conf, the Samba configuration file
- * smbprint, a sample script to allow a Unix host to use smbclient to
- print to an SMB server
- * documentation! DON'T neglect to read it - you will save a great deal
- of time!
-
-The suite is supplied with full source (of course!) and is GPLed.
-
-The primary creator of the Samba suite is Andrew Tridgell. Later versions
-incorporate much effort by many net.helpers. The man pages and this FAQ were
-originally written by Karl Auer.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 2: What is the current version of Samba?
-
-At time of writing, the current version was 1.9.16. If you want to be sure
-check the bottom of the change-log file.
-(ftp://samba.anu.edu.au/pub/samba/alpha/change-log)
-
-For more information see question 5, "What do the version numbers mean?"
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 3: Where can I get it?
-
-The Samba suite is available via anonymous ftp from samba.anu.edu.au. The
-latest and greatest versions of the suite are in the directory:
-
-/pub/samba/
-
-Development (read "alpha") versions, which are NOT necessarily stable and which
-do NOT necessarily have accurate documentation, are available in the directory:
-
-/pub/samba/alpha
-
-Note that binaries are NOT included in any of the above. Samba is distributed
-ONLY in source form, though binaries may be available from other sites. Recent
-versions of some Linux distributions, for example, do contain Samba binaries
-for that platform.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 5: 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 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:
-
-1) 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.)
-
-2) 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 are just
-looking for the latest version to install.
-
-3) when Andrew 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.
-
-4) 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)
- :
- 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.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 4: 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, the Makefile claimed support for:
-
- * SunOS
- * Linux with shadow passwords
- * Linux without shadow passwords
- * SOLARIS
- * SOLARIS 2.2 and above (aka SunOS 5)
- * SVR4
- * ULTRIX
- * OSF1 (alpha only)
- * OSF1 with NIS and Fast Crypt (alpha only)
- * OSF1 V2.0 Enhanced Security (alpha only)
- * AIX
- * BSDI
- * NetBSD
- * NetBSD 1.0
- * SEQUENT
- * HP-UX
- * SGI
- * SGI IRIX 4.x.x
- * SGI IRIX 5.x.x
- * FreeBSD
- * NeXT 3.2 and above
- * NeXT OS 2.x
- * NeXT OS 3.0
- * ISC SVR3V4 (POSIX mode)
- * ISC SVR3V4 (iBCS2 mode)
- * A/UX 3.0
- * SCO with shadow passwords.
- * SCO with shadow passwords, without YP.
- * SCO with TCB passwords
- * SCO 3.2v2 (ODT 1.1) with TCP passwords
- * intergraph
- * DGUX
- * Apollo Domain/OS sr10.3 (BSD4.3)
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 5: How can I find out more about Samba?
-
-There are two mailing lists devoted to discussion of Samba-related matters.
-There is also the newsgroup, comp.protocols.smb, which has a great deal of
-discussion on Samba. There is also a WWW site 'SAMBA Web Pages' at
-http://samba.canberra.edu.au/pub/samba/samba.html, under which there is a
-comprehensive survey of Samba users. Another useful resource is the hypertext
-archive of the Samba mailing list.
-
-Send email to listproc@samba.anu.edu.au. Make sure the subject line is
-blank, and include the following two lines in the body of the message:
-
- subscribe samba Firstname Lastname
- subscribe samba-announce Firstname Lastname
-
-Obviously you should substitute YOUR first name for "Firstname" and YOUR last
-name for "Lastname"! Try not to send any signature stuff, it sometimes confuses
-the list processor.
-
-The samba list is a digest list - every eight hours or so it regurgitates a
-single message containing all the messages that have been received by the list
-since the last time and sends a copy of this message to all subscribers.
-
-If you stop being interested in Samba, please send another email to
-listproc@samba.anu.edu.au. Make sure the subject line is blank, and
-include the following two lines in the body of the message:
-
- unsubscribe samba
- unsubscribe samba-announce
-
-The From: line in your message MUST be the same address you used when you
-subscribed.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 6: Something's gone wrong - what should I do?
-
-[#] *** IMPORTANT! *** [#]
-DO NOT post messages on mailing lists or in newsgroups until you have carried
-out the first three steps given here!
-
-Firstly, see if there are any likely looking entries in this FAQ! If you have
-just installed Samba, have you run through the checklist in DIAGNOSIS.txt? It
-can save you a lot of time and effort.
-
-Secondly, read the man pages for smbd, nmbd and smb.conf, looking for topics
-that relate to what you are trying to do.
-
-Thirdly, if there is no obvious solution to hand, try to get a look at the log
-files for smbd and/or nmbd for the period during which you were having
-problems. You may need to reconfigure the servers to provide more extensive
-debugging information - usually level 2 or level 3 provide ample debugging
-info. Inspect these logs closely, looking particularly for the string "Error:".
-
-Fourthly, if you still haven't got anywhere, ask the mailing list or newsgroup.
-In general nobody minds answering questions provided you have followed the
-preceding steps. It might be a good idea to scan the archives of the mailing
-list, which are available through the Samba web site described in the previous
-section.
-
-If you successfully solve a problem, please mail the FAQ maintainer a succinct
-description of the symptom, the problem and the solution, so I can incorporate
-it in the next version.
-
-If you make changes to the source code, _please_ submit these patches so that
-everyone else gets the benefit of your work. This is one of the most important
-aspects to the maintainence of Samba. Send all patches to
-samba-bugs@samba.anu.edu.au, not Andrew Tridgell or any other individual and
-not the samba team mailing list.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* n: Pizza Supply Details
-
-Those who have registered in the Samba survey as "Pizza Factory" will already
-know this, but the rest may need some help. Andrew doesn't ask for payment,
-but he does appreciate it when people give him pizza. This calls for a little
-organisation when the pizza donor is twenty thousand kilometres away, but
-it has been done.
-
-Method 1: Ring up your local branch of an international pizza chain and see if
-they honour their vouchers internationally. Pizza Hut do, which is how the
-entire Canberra Linux Users Group got to eat pizza one night, courtesy of
-someone in the US
-
-Method 2: Ring up a local pizza shop in Canberra and quote a credit card
-number for a certain amount, and tell them that Andrew will be collecting
-it (don't forget to tell him.) One kind soul from Germany did this.
-
-Method 3: Purchase a pizza voucher from your local pizza shop that has no
-international affiliations and send it to Andrew. It is completely useless
-but he can hang it on the wall next to the one he already has from Germany :-)
-
-Method 4: Air freight him a pizza with your favourite regional flavours. It will
-probably get stuck in customs or torn apart by hungry sniffer dogs but it will
-have been a noble gesture.
-
-===============================================================================
-SECTION TWO: Compiling and installing Samba on a Unix host
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-
-===============================================================================
-SECTION THREE: Common client problems
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 1: I can't see the Samba server in any browse lists!
-
-*** Until the FAQ can be updated, please check the file:
-*** ftp://samba.anu.edu.au/pub/samba/docs/BROWSING.txt
-*** for more information on browsing.
-
-If your GUI client does not permit you to select non-browsable servers, you may
-need to do so on the command line. For example, under Lan Manager you might
-connect to the above service as disk drive M: thusly:
-
- net use M: \\mary\fred
-
-The details of how to do this and the specific syntax varies from client to
-client - check your client's documentation.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 2: Some files that I KNOW are on the server doesn't show up when I view the
- directories from my client!
-
-If you check what files are not showing up, you will note that they are files
-which contain upper case letters or which are otherwise not DOS-compatible (ie,
-they are not legal DOS filenames for some reason).
-
-The Samba server can be configured either to ignore such files completely, or
-to present them to the client in "mangled" form. If you are not seeing the
-files at all, the Samba server has most likely been configured to ignore them.
-Consult the man page smb.conf(5) for details of how to change this - the
-parameter you need to set is "mangled names = yes".
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 3: Some files on the server show up with really wierd filenames when I view
-the directories from my client!
-
-If you check what files are showing up wierd, you will note that they are files
-which contain upper case letters or which are otherwise not DOS-compatible (ie,
-they are not legal DOS filenames for some reason).
-
-The Samba server can be configured either to ignore such files completely, or
-to present them to the client in "mangled" form. If you are seeing strange file
-names, they are most likely "mangled". If you would prefer to have such files
-ignored rather than presented in "mangled" form, consult the man page
-smb.conf(5) for details of how to change the server configuration - the
-parameter you need to set is "mangled names = no".
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 4: My client reports "cannot locate specified computer" or similar.
-
-This indicates one of three things: You supplied an incorrect server name, the
-underlying TCP/IP layer is not working correctly, or the name you specified
-cannot be resolved.
-
-After carefully checking that the name you typed is the name you should have
-typed, try doing things like pinging a host or telnetting to somewhere on your
-network to see if TCP/IP is functioning OK. If it is, the problem is most
-likely name resolution.
-
-If your client has a facility to do so, hardcode a mapping between the hosts IP
-and the name you want to use. For example, with Man Manager or Windows for
-Workgroups you would put a suitable entry in the file LMHOSTS. If this works,
-the problem is in the communication between your client and the netbios name
-server. If it does not work, then there is something fundamental wrong with
-your naming and the solution is beyond the scope of this document.
-
-If you do not have any server on your subnet supplying netbios name resolution,
-hardcoded mappings are your only option. If you DO have a netbios name server
-running (such as the Samba suite's nmbd program), the problem probably lies in
-the way it is set up. Refer to Section Two of this FAQ for more ideas.
-
-By the way, remember to REMOVE the hardcoded mapping before further tests :-)
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 5: 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.
-
-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 doco 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.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 6: My client reports "cannot find domain controller", "cannot log on to the
-network" or similar.
-
-Nothing is wrong - Samba does not implement the primary domain name controller
-stuff for several reasons, including the fact that the whole concept of a
-primary domain controller and "logging in to a network" doesn't fit well with
-clients possibly running on multiuser machines (such as users of smbclient
-under Unix). Having said that, several developers are working hard on
-building it in to the next major version of Samba. If you can contribute,
-send a message to samba-bugs!
-
-Seeing this message should not affect your ability to mount redirected disks
-and printers, which is really what all this is about.
-
-For many clients (including Windows for Workgroups and Lan Manager), setting
-the domain to STANDALONE at least gets rid of the message.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 7: Printing doesn't work :-(
-
-Make sure that the specified print command for the service you are connecting
-to is correct and that it has a fully-qualified path (eg., use "/usr/bin/lpr"
-rather than just "lpr").
-
-Make sure that the spool directory specified for the service is writable by the
-user connected to the service. In particular the user "nobody" often has
-problems with printing, even if it worked with an earlier version of Samba. Try
-creating another guest user other than "nobody".
-
-Make sure that the user specified in the service is permitted to use the
-printer.
-
-Check the debug log produced by smbd. Search for the printer name and see if
-the log turns up any clues. Note that error messages to do with a service ipc$
-are meaningless - they relate to the way the client attempts to retrieve status
-information when using the LANMAN1 protocol.
-
-If using WfWg then you need to set the default protocol to TCP/IP, not Netbeui.
-This is a WfWg bug.
-
-If using the Lanman1 protocol (the default) then try switching to coreplus.
-Also not that print status error messages don't mean printing won't work. The
-print status is received by a different mechanism.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 8: My programs install on the server OK, but refuse to work properly.
-
-There are numerous possible reasons for this, but one MAJOR possibility is that
-your software uses locking. Make sure you are using Samba 1.6.11 or later. It
-may also be possible to work around the problem by setting "locking=no" in the
-Samba configuration file for the service the software is installed on. This
-should be regarded as a strictly temporary solution.
-
-In earlier Samba versions there were some difficulties with the very latest
-Microsoft products, particularly Excel 5 and Word for Windows 6. These should
-have all been solved. If not then please let Andrew Tridgell know.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 9: My "server string" doesn't seem to be recognized, my client reports the
- default setting, eg. "Samba 1.9.15p4", instead of what I have changed it
- to in the smb.conf file.
-
-You need to use the -C option in nmbd. The "server string" affects
-what smbd puts out and -C affects what nmbd puts out. In a future
-version these will probably be combined and -C will be removed, but
-for now use -C
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 10: When I attempt to get a listing of available resources from the Samba
- server, my client reports
- "This server is not configured to list shared resources".
-
-Your guest account is probably invalid for some reason. Samba uses
-the guest account for browsing in smbd. Check that your guest account is
-valid.
-
-See also 'guest account' in smb.conf man page.
-
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 11: You get the message "you appear to have a trapdoor uid system"
- in your logs
-
-This can have several causes. It might be because you are using a uid
-or gid of 65535 or -1. This is a VERY bad idea, and is a big security
-hole. Check carefully in your /etc/passwd file and make sure that no
-user has uid 65535 or -1. Especially check the "nobody" user, as many
-broken systems are shipped with nobody setup with a uid of 65535.
-
-It might also mean that your OS has a trapdoor uid/gid system :-)
-
-This means that once a process changes effective uid from root to
-another user it can't go back to root. Unfortunately Samba relies on
-being able to change effective uid from root to non-root and back
-again to implement its security policy. If your OS has a trapdoor uid
-system this won't work, and several things in Samba may break. Less
-things will break if you use user or server level security instead of
-the default share level security, but you may still strike
-problems.
-
-The problems don't give rise to any security holes, so don't panic,
-but it does mean some of Samba's capabilities will be unavailable.
-In particular you will not be able to connect to the Samba server as
-two different uids at once. This may happen if you try to print as a
-"guest" while accessing a share as a normal user. It may also affect
-your ability to list the available shares as this is normally done as
-the guest user.
-
-Complain to your OS vendor and ask them to fix their system.
-
-Note: the reason why 65535 is a VERY bad choice of uid and gid is that
-it casts to -1 as a uid, and the setreuid() system call ignores (with
-no error) uid changes to -1. This means any daemon attempting to run
-as uid 65535 will actually run as root. This is not good!
-
-===============================================================================
-SECTION FOUR: Specific client problems
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 1: Are any MacIntosh clients for Samba.
-
-Yes. Thursby Software Systems have released 'Dave' - a SMB client for
-MacIntosh systems. This is a commercial product and inclusion in this
-faq does not imply any endorsement by the Samba developers. Having said
-that, the first public demonstration of 'Dave' was to the Samba server
-run by Andrew Tridgell over the Internet from Redmond, Washington, USA to
-Australia as part of the first CIFS developers conference.
-
-For more details on 'Dave' contact :
-
-Web contact: www.thursby.com
-
-Thursby Software Systems, Inc.
-5840 W. Interstate 20
-Arlington, Texas 76017 U.S.A.
-Voice: 817-478-5070
-FAX: 817-561-2313
-sales@thursby.com
-
-There are currently no Free Software solutions other than to make
-your UNIX server talk AppleTalk.
-
-In Rob Newberry's words (rob@eats.com, Sun, 4 Dec 1994):
-
-In future Apple System Software, you may see support for other protocols, such
-as SMB -- Applet is working on a new networking architecture that will make it
-easier to support additional protocols. But it's not here yet.
-
-If you want your Unix machine to speak Appletalk, there are several options.
-"Netatalk" and "CAP" are free, and available on the net. There are also
-several commercial options, such as "PacerShare" and "Helios" (I think).
-In any case, you'll have to look around for a server, not anything for the Mac.
-
-Depending on your OS, some of these may not help you. I am currently
-coordinating the effort to get CAP working with Native Ethertalk under Linux,
-but we're not done yet.
-
-Rob
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 2: I am getting a "Session request failed (131,130)" error when I try to
- connect to my Win95 PC with smbclient. I am able to connect from the PC
- to the Samba server without problems. What gives?
-
-The following answer is provided by John E. Miller:
-
-I'll assume that you're able to ping back and forth between the machines by
-IP address and name, and that you're using some security model where you're
-confident that you've got user IDs and passwords right. The logging options
-(-d3 or greater) can help a lot with that. DNS and WINS configuration can
-also impact connectivity as well.
-
-Now, on to 'scope id's. Somewhere in your Win95 TCP/IP network configuration
-(I'm too much of an NT bigot to know where it's located in the Win95 setup,
-but I'll have to learn someday since I teach for a Microsoft Solution Provider
-Authorized Tech Education Center - what an acronym...) [Note: It's under
-Control Panel | Network | TCP/IP | WINS Configuration] there's a little text
-entry field called something like 'Scope ID'.
-
-This field essentially creates 'invisible' sub-workgroups on the same wire.
-Boxes can only see other boxes whose Scope IDs are set to the exact same
-value - it's sometimes used by OEMs to configure their boxes to browse only
-other boxes from the same vendor and, in most environments, this field should
-be left blank. If you, in fact, have something in this box that EXACT value
-(case-sensitive!) needs to be provided to smbclient and nmbd as the -i
-(lowercase) parameter. So, if your Scope ID is configured as the string
-'SomeStr' in Win95 then you'd have to use smbclient -iSomeStr
-in connecting to it.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 3: How do I synchronize my PC's clock with my Samba server?
-
-To syncronize your PC's clock with your Samba server:
-
-* Copy timesync.pif to your windows directory
- * timesync.pif can be found at:
- http://samba.canberra.edu.au/pub/samba/binaries/miscellaneous/timesync.pif
-* Add timesync.pif to your 'Start Up' group/folder
-* Open the properties dialog box for the program/icon
- * Make sure the 'Run Minimized' option is set in program 'Properties'
- * Change the command line section that reads \\sambahost to reflect the name
- of your server.
-* Close the properties dialog box by choosing 'OK'
-
-Each time you start your computer (or login for Win95) your PC will
-synchronize it's clock with your Samba server.
-
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 4: Problems with WinDD, NTrigue, WinCenterPro etc
-
-All of the above programs are applications that sit on an NT box and
-allow multiple users to access the NT GUI applications from remote
-workstations (often over X).
-
-What has this got to do with Samba? The problem comes when these users
-use filemanager to mount shares from a Samba server. The most common
-symptom is that the first user to connect get correct file permissions
-and has a nice day, but subsequent connections get logged in as the
-same user as the first person to login. They find that they cannot
-access files in their own home directory, but that they can access
-files in the first users home directory (maybe not such a nice day
-after all?)
-
-Why does this happen? The above products all share a common heritage
-(and code base I believe). They all open just a single TCP based SMB
-connection to the Samba server, and requests from all users are piped
-over this connection. This is unfortunate, but not fatal.
-
-It means that if you run your Samba server in share level security
-(the default) then things will definately break as described above. The
-share level SMB security model has no provision for multiple user IDs
-on the one SMB connection. See security_level.txt in the docs for more
-info on share/user/server level security.
-
-If you run in user or server level security then you have a chance,
-but only if you have a recent version of Samba (at least 1.9.15p6). In
-older versions bugs in Samba meant you still would have had problems.
-
-If you have a trapdoor uid system in your OS then it will never work
-properly. Samba needs to be able to switch uids on the connection and
-it can't if your OS has a trapdoor uid system. You'll know this
-because Samba will note it in your logs.
-
-Also note that you should not use the magic "homes" share name with
-products like these, as otherwise all users will end up with the same
-home directory. Use \\server\username instead.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 5: Problem with printers under NT
-
-This info from Stefan Hergeth may be useful:
-
- A network-printer (with ethernetcard) is connected to the NT-Clients via
- our UNIX-Fileserver (SAMBA-Server), like the configuration told by
- Matthew Harrell (see WinNT.txt)
-
- 1.) If a user has choosen this printer as the default printer in his
- NT-Session and this printer is not connected to the network
- (e.g. switched off) than this user has a problem with the SAMBA-
- connection of his filesystems. It's very slow.
-
- 2.) If the printer is connected to the network everything works fine.
-
- 3.) When the smbd ist started with debug level 3, you can see that the
- NT spooling system try to connect to the printer many times. If the
- printer ist not connected to the network this request fails and the
- NT spooler is wasting a lot of time to connect to the printer service.
- This seems to be the reason for the slow network connection.
-
- 4.) Maybe it's possible to change this behaviour by setting different printer
- properties in the Print-Manager-Menu of NT, but i didn't try it
- yet.
-
- I hope this information will help in some way.
-
- Stefan Hergeth
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 6: Why are my file's timestamps off by an hour, or by a few hours?
-
-This is from Paul Eggert .
-
-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.
-
- 1. The Unix system clock must have the correct Universal time.
- Use the shell command "sh -c 'TZ=UTC0 date'" to check this.
-
- 2. 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'.
-
- 3. TZ must have the correct value.
-
- 3a. If possible, use geographical time zone settings
- (e.g. TZ='America/Los_Angeles' or perhaps
- TZ=':US/Pacific'). These are supported by most
- popular Unix OSes, are easier to get right, and are
- 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 .
-
- 3b. If your system does not support geographical time zone
- 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').
- 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
- daylight-saving time.
-
- `Dst' is the daylight-saving time designation
- (e.g. `PDT').
-
- The optional second `Offset' is the number of
- hours that daylight-saving time is behind UTC.
- The default is 1 hour ahead of standard time.
-
- `Date/Time,Date/Time' specify when daylight-saving
- time starts and ends. The format for a date is
- `Mm.n.d', which specifies the dth day (0 is Sunday)
- 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
-time zone is also set appropriately. [[I don't know how to do this.]]
-
-Samba traditionally has had many problems dealing with time zones, due
-to the bizarre ways that Microsoft network protocols handle time
-zones. A common symptom is for file timestamps to be off by an hour.
-To work around the problem, try disconnecting from your Samba server
-and then reconnecting to it; or upgrade your Samba server to
-1.9.16alpha10 or later.
-
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 7: How do I set the printer driver name correctly?
-
-Question:
-> On NT, I opened "Printer Manager" and "Connect to Printer".
-> Enter "\\ptdi270\ps1" in the box of printer. I got the
-> following error message:
->
-> You do not have sufficient access to your machine
-> to connect to the selected printer, since a driver
-> needs to be installed locally.
-
-Answer:
-
-In the more recent versions of Samba you can now set the "printer
-driver" in smb.conf. This tells the client what driver to use. For
-example, I have:
-
- printer driver = HP LaserJet 4L
-
-and NT knows to use the right driver. You have to get this string
-exactly right.
-
-To find the exact string to use, you need to get to the dialog box in
-your client where you select which printer driver to install. The
-correct strings for all the different printers are shown in a listbox
-in that dialog box.
-
-You could also try setting the driver to NULL like this:
-
- printer driver = NULL
-
-this is effectively what older versions of Samba did, so if that
-worked for you then give it a go. If this does work then let me know
-and I'll make it the default. Currently the default is a 0 length
-string.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-* 8: I have upgraded my NT 4.0 system to service pack 3. Why
- can't I connect anymore ?
-
-This is not a bug. Microsoft has changed their policy on sending
-unencrypted passwords over the net. They no longer default to allowing
-unencrypted passwords to be sent over the net. This effects all Samba
-servers which are configured to use security=share or security=user level
-security without password encryption. They do, however, have a fix which
-can be applied to the registry to fix the problem. Here's a synopsis
-from the SP3 web page that discusses how to enable unencrypted password
-sending from an NT 4.0 box.
-
-A better solution is to re-compile Samba to use encrypted passwords.
-See the document :
-
-ftp://samba.anu.edu.au/pub/samba/docs/ENCRYPTION.txt
-
->SYMPTOMS
->==========
->
->Connecting to SMB servers (such as Samba) with unencrypted password fails
-after upgrading to Windows NT 4.0 service pack 3 version 1.76.
->
->CAUSE
->======
->
->The SMB redirector in Windows NT 4.0 service pack 3 version 1.76 handles
->unencrypted passwords differently than previous version of Windows NT.
->Beginning with this version, the SMB redirector will not send an
->unencrypted password unless you add a registry entry to enable them.
->
->RESOLUTION
->===========
->
->To enable unencrypted (plain text) passwords modify the registry in this way.
->
->
->
->WARNING: Using Registry Editor incorrectly can cause serious, system-wide
->problems that may require you to reinstall Windows NT to correct them.
->Microsoft cannot guarantee that any problems resulting from the use of
->Registry Editor can be solved. Use this tool at your own risk.
->
->
->
->1. Run Registry Editor (REGEDT32.EXE).
->
->2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:
->
->
->
->\system\currentcontrolset\services\rdr\parameters
->
->
->
->3. From the Edit menu, select Add Value.
->
->4. Add the following:
->
->
->
->Value Name: EnablePlainTextPassword
->
->Data Type: REG_DWORD
->
->Data: 1
->
->
->
->5. Choose OK and quit Registry Editor.
->
->6. Shutdown and restart Windows NT.
->
->
------------------------------------------------------------------------
-
-===============================================================================
-SECTION FIVE: Specific client application problems
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-* 1: MS Office Setup reports "Cannot change properties of the file named:
- X:\MSOFFICE\SETUP.INI"
-
-When installing MS Office on a Samba drive for which you have admin user
-permissions, ie. admin users = , you will find the setup program
-unable to complete the installation.
-
-To get around this problem, do the installation without admin user 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" to fix
-the owner.
-
-===============================================================================
-SECTION SIX: Miscellaneous
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Maintained By Paul Blackman, Email:ictinus@lake.canberra.edu.au
diff --git a/docs/samba.lsm b/docs/samba.lsm
deleted file mode 100644
index 36abbba769a..00000000000
--- a/docs/samba.lsm
+++ /dev/null
@@ -1,26 +0,0 @@
-Begin2
-Title = Samba
-Version = 1.8.0
-Desc1 = Samba is a SMB based file and print server for unix. It
-Desc2 = provides access to unix file and print services from
-Desc3 = SMB compatible clients such as WinNT, WfWg, OS/2
-Desc4 = and Pathworks. It also includes a ftp-style unix client
-Desc5 = and a netbios nameserver.
-Author = Andrew Tridgell
-AuthorEmail = samba-bugs@samba.anu.edu.au
-Maintainer = Andrew Tridgell
-MaintEmail = samba-bugs@samba.anu.edu.au
-Site1 = samba.anu.edu.au
-Path1 = pub/samba/
-File1 = samba-latest.tar.gz
-FileSize1 = 200K
-Required1 = Ansi-C compiler and a TCP/IP network.
-CopyPolicy1 = GNU Public License
-Keywords = LanManager, SMB, Networking
-Comment1 = To join the Samba mailing list send mail to
-Comment2 = listproc@listproc.anu.edu.au with a body of
-Comment3 = "subscribe samba Your Name"
-Entered = October 1994
-EnteredBy = Andrew Tridgell
-End
-
diff --git a/docs/textdocs/Application_Serving.txt b/docs/textdocs/Application_Serving.txt
deleted file mode 100644
index caed027893a..00000000000
--- a/docs/textdocs/Application_Serving.txt
+++ /dev/null
@@ -1,49 +0,0 @@
-January 7, 1997
-Updated: June 27, 1997
-Contributor: John H Terpstra
-Status: Current
-
-Subject: Using a Samba share as an administrative share for MS Office, etc.
-==============================================================================
-
-Problem:
-========
-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
-installed onto workstation clients.
-
-The general mechanism for implementing an adminstrative installation involves
-running:
- X:\setup /A, where X is the drive letter of either CDROM or floppy
-
-This installation process will NOT install the product for use per se, but
-rather results in unpacking of the compressed distribution files into a target
-shared folder. For this process you need write privilidge to the share and it
-is desirable to enable file locking and share mode operation during this
-process.
-
-Subsequent installation of MS Office from this share will FAIL unless certain
-precautions are taken. This failure will be caused by share mode operation
-which will prevent the MS Office installation process from re-opening various
-dynamic link library files and will cause sporadic file not found problems.
-
-Solution:
-=========
-1. As soon as the administrative installation (unpacking) has completed
- set the following parameters on the share containing it:
- [MSOP95]
- path = /where_you_put_it
- comment = Your comment
- volume = "The_CD_ROM_Label"
- read only = yes
- available = yes
- share modes = no
- locking = no
- browseable = yes
- public = yes
-
-2. Now you are ready to run the setup program from the Microsoft Windows
-workstation as follows:-
- \\"Server_Name"\MSOP95\msoffice\setup
-
diff --git a/docs/textdocs/BROWSING.txt b/docs/textdocs/BROWSING.txt
deleted file mode 100644
index 12d3417a294..00000000000
--- a/docs/textdocs/BROWSING.txt
+++ /dev/null
@@ -1,546 +0,0 @@
-Author/s: Many (Thanks to Luke, Jeremy, Andrew, etc.)
-Updated: June 29, 1997
-Status: Current - For VERY Advanced Users ONLY
-
-Summary: This describes how to configure Samba for improved browsing.
-=====================================================================
-
-OVERVIEW:
-=========
-SMB networking provides a mechanism by which clients can access a list
-of machines that are available within the network. This list is called
-the browse list and is heavily used by all SMB clients. Configuration
-of SMB browsing has been problematic for some Samba users, hence this
-document.
-
-=====================================================================
-
-BROWSING
-========
-Samba now fully supports browsing. The browsing is supported by nmbd
-and is also controlled by options in the smb.conf file (see smb.conf(5)).
-
-Samba can act as a local browse master for a workgroup and the ability
-for samba to support domain logons and scripts is now available. See
-DOMAIN.txt for more information on domain logons.
-
-Samba can also act as a domain master browser for a workgroup. This
-means that it will collate lists from local browse masters into a
-wide area network server list. In order for browse clients to
-resolve the names they may find in this list, it is recommended that
-both samba and your clients use a WINS server
-
-Note that you should NOT set Samba to be the domain master for a
-workgroup that has the same name as an NT Domain.
-
-[Note that nmbd can be configured as a WINS server, but it is not
-necessary to specifically use samba as your WINS server. NTAS can
-be configured as your WINS server. In a mixed NT server and
-samba environment on a Wide Area Network, it is recommended that
-you use the NT server's WINS server capabilities. In a samba-only
-environment, it is recommended that you use one and only one nmbd
-as your WINS server].
-
-To get browsing to work you need to run nmbd as usual, but will need
-to use the "workgroup" option in smb.conf to control what workgroup
-Samba becomes a part of.
-
-Samba also has a useful option for a Samba server to offer itself for
-browsing on another subnet. It is recommended that this option is only
-used for 'unusual' purposes: announcements over the internet, for
-example. See "remote announce" in the smb.conf man page.
-
-If something doesn't work then hopefully the log.nmb file will
-help you track down the problem. Try a debug level of 2 or 3 for
-finding problems.
-
-Note that if it doesn't work for you, then you should still be able to
-type the server name as \\SERVER in filemanager then hit enter and
-filemanager should display the list of available shares.
-
-Some people find browsing fails because they don't have the global
-"guest account" set to a valid account. Remember that the IPC$
-connection that lists the shares is done as guest, and thus you must
-have a valid guest account.
-
-Also, a lot of people are getting bitten by the problem of too many
-parameters on the command line of nmbd in inetd.conf. This trick is to
-not use spaces between the option and the parameter (eg: -d2 instead
-of -d 2), and to not use the -B and -N options. New versions of nmbd
-are now far more likely to correctly find your broadcast and network
-addess, so in most cases these aren't needed.
-
-The other big problem people have is that their broadcast address,
-netmask or IP address is wrong (specified with the "interfaces" option
-in smb.conf)
-
-BROWSING ACROSS SUBNETS
-=======================
-
-With the release of Samba 1.9.17(alpha1 and above) Samba has been
-updated to enable it to support the replication of browse lists
-across subnet boundaries. New code and options have been added to
-achieve this. This section describes how to set this feature up
-in different settings.
-
-To see browse lists that span TCP/IP subnets (ie. networks separated
-by routers that don't pass broadcast traffic) you must set up at least
-one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing
-NetBIOS name to IP address translation to be done by doing a direct
-query of the WINS server. This is done via a directed UDP packet on
-port 137 to the WINS server machine. The reason for a WINS server is
-that by default, all NetBIOS name to IP address translation is done
-by broadcasts from the querying machine. This means that machines
-on one subnet will not be able to resolve the names of machines on
-another subnet without using a WINS server.
-
-Remember, for browsing across subnets to work correctly, all machines,
-be they Windows 95, Windows NT, or Samba servers must have the IP address
-of a WINS server given to them by a DHCP server, or by manual configuration
-(for Win95 and WinNT, this is in the TCP/IP Properties, under Network
-settings) for Samba this is in the smb.conf file.
-
-How does cross subnet browsing work ?
-=====================================
-
-Cross subnet browsing is a complicated dance, containing multiple
-moving parts. It has taken Microsoft several years to get the code
-that achieves this correct, and Samba lags behind in some areas.
-However, with the 1.9.17 release, Samba is capable of cross subnet
-browsing when configured correctly.
-
-Consider a network set up as follows :
-
- (DMB)
- N1_A N1_B N1_C N1_D N1_E
- | | | | |
- -------------------------------------------------------
- | subnet 1 |
- +---+ +---+
- |R1 | Router 1 Router 2 |R2 |
- +---+ +---+
- | |
- | subnet 2 subnet 3 |
- -------------------------- ------------------------------------
- | | | | | | | |
- N2_A N2_B N2_C N2_D N3_A N3_B N3_C N3_D
- (WINS)
-
-Consisting of 3 subnets (1, 2, 3) conneted by two routers
-(R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines
-on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume
-for the moment that all these machines are configured to be in the
-same workgroup (for simplicities sake). Machine N1_C on subnet 1
-is configured as Domain Master Browser (ie. it will collate the
-browse lists for the workgroup). Machine N2_D is configured as
-WINS server and all the other machines are configured to register
-their NetBIOS names with it.
-
-As all these machines are booted up, elections for master browsers
-will take place on each of the three subnets. Assume that machine
-N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on
-subnet 3 - these machines are known as local master browsers for
-their particular subnet. N1_C has an advantage in winning as the
-local master browser on subnet 1 as it is set up as Domain Master
-Browser.
-
-On each of the three networks, machines that are configured to
-offer sharing services will broadcast that they are offering
-these services. The local master browser on each subnet will
-receive these broadcasts and keep a record of the fact that
-the machine is offering a service. This list of records is
-the basis of the browse list. For this case, assume that
-all the machines are configured to offer services so all machines
-will be on the browse list.
-
-For each network, the local master browser on that network is
-considered 'authoritative' for all the names it receives via
-local broadcast. This is because a machine seen by the local
-master browser via a local broadcast must be on the same
-network as the local master browser and thus is a 'trusted'
-and 'verifiable' resource. Machines on other networks that
-the local master browsers learn about when collating their
-browse lists have not been directly seen - these records are
-called 'non-authoritative'.
-
-At this point the browse lists look as follows (these are
-the machines you would see in your network neighborhood if
-you looked in it on a particular network right now).
-
-Subnet Browse Master List
------- ------------- ----
-Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E
-
-Subnet2 N2_B N2_A, N2_B, N2_C, N2_D
-
-Subnet3 N3_D N3_A, N3_B, N3_C, N3_D
-
-Note that at this point all the subnets are separate, no
-machine is seen across any of the subnets.
-
-Now examine subnet 2. As soon as N2_B has become the local
-master browser it looks for a Domain master browser to synchronize
-its browse list with. It does this by querying the WINS server
-(N2_D) for the IP address associated with the NetBIOS name
-WORKGROUP<1B>. This name was registerd by the Domain master
-browser (N1_C) with the WINS server as soon as it was booted.
-
-Once N2_B knows the address of the Domain master browser it
-tells it that is the local master browser for subnet 2 by
-sending a MasterAnnouncement packet as a UDP port 138 packet.
-It then synchronizes with it by doing a NetServerEnum2 call. This
-tells the Domain Master Browser to send it all the server
-names it knows about. Once the domain master browser receives
-the MasterAnnouncement packet it schedules a synchronization
-request to the sender of that packet. After both synchronizations
-are done the browse lists look like :
-
-Subnet Browse Master List
------- ------------- ----
-Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E,
- N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Subnet2 N2_B N2_A, N2_B, N2_C, N2_D
- N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-
-Subnet3 N3_D N3_A, N3_B, N3_C, N3_D
-
-Servers with a (*) after them are non-authoritative names.
-
-At this point users looking in their network neighborhood on
-subnets 1 or 2 will see all the servers on both, users on
-subnet 3 will still only see the servers on their own subnet.
-
-The same sequence of events that occured for N2_B now occurs
-for the local master browser on subnet 3 (N3_D). When it
-synchronizes browse lists with the domain master browser (N1_A)
-it gets both the server entries on subnet 1, and those on
-subnet 2. After N3_D has synchronized with N1_C and vica-versa
-the browse lists look like.
-
-Subnet Browse Master List
------- ------------- ----
-Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E,
- N2_A(*), N2_B(*), N2_C(*), N2_D(*),
- N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet2 N2_B N2_A, N2_B, N2_C, N2_D
- N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-
-Subnet3 N3_D N3_A, N3_B, N3_C, N3_D
- N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
- N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Servers with a (*) after them are non-authoritative names.
-
-At this point users looking in their network neighborhood on
-subnets 1 or 3 will see all the servers on all sunbets, users on
-subnet 2 will still only see the servers on subnets 1 and 2, but not 3.
-
-Finally, the local master browser for subnet 2 (N2_B) will sync again
-with the domain master browser (N1_C) and will recieve the missing
-server entries. Finally - and as a steady state (if no machines
-are removed or shut off) the browse lists will look like :
-
-Subnet Browse Master List
------- ------------- ----
-Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E,
- N2_A(*), N2_B(*), N2_C(*), N2_D(*),
- N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet2 N2_B N2_A, N2_B, N2_C, N2_D
- N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
- N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet3 N3_D N3_A, N3_B, N3_C, N3_D
- N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
- N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Servers with a (*) after them are non-authoritative names.
-
-Synchronizations between the domain master browser and local
-master browsers will continue to occur, but this should be a
-steady state situation.
-
-If either router R1 or R2 fails the following will occur:
-
-1) Names of computers on each side of the inaccessible network fragments
-will be maintained for as long as 36 minutes, in the network neighbourhood
-lists.
-
-2) Attempts to connect to these inaccessible computers will fail, but the
-names will not be removed from the network neighbourhood lists.
-
-3) If one of the fragments is cut off from the WINS server, it will only
-be able to access servers on its local subnet, by using subnet-isolated
-broadcast NetBIOS name resolution. The effects are similar to that of
-losing access to a DNS server.
-
-Setting up a WINS server
-========================
-
-Either a Samba machine or a Windows NT Server machine may be set up
-as a WINS server. To set a Samba machine to be a WINS server you must
-add the following option to the smb.conf file on the selected machine :
-in the [globals] section add the line
-
- wins support = yes
-
-Versions of Samba previous to 1.9.17 had this parameter default to
-yes. If you have any older versions of Samba on your network it is
-strongly suggested you upgrade to 1.9.17 or above, or at the very
-least set the parameter to 'no' on all these machines.
-
-Machines with "wins support = yes" will keep a list of all NetBIOS
-names registered with them, acting as a DNS for NetBIOS names.
-
-You should set up only ONE wins server. Do NOT set the
-"wins support = yes" option on more than one Samba server.
-
-To set up a Windows NT Server as a WINS server you need to set up
-the WINS service - see your NT documentation for details. Note that
-Windows NT WINS Servers can replicate to each other, allowing more
-than one to be set up in a complex subnet environment. As Microsoft
-refuse to document these replication protocols Samba cannot currently
-participate in these replications. It is possible in the future that
-a Samba->Samba WINS replication protocol may be defined, in which
-case more than one Samba machine could be set up as a WINS server
-but currently only one Samba server should have the "wins support = yes"
-parameter set.
-
-After the WINS server has been configured you must ensure that all
-machines participating on the network are configured with the address
-of this WINS server. If your WINS server is a Samba machine, fill in
-the Samba machine IP address in the "Primary WINS Server" field of
-the "Control Panel->Network->Protocols->TCP->WINS Server" dialogs
-in Windows 95 or Windows NT. To tell a Samba server the IP address
-of the WINS server add the following line to the [global] section of
-all smb.conf files :
-
- wins server =
-
-where is either the DNS name of the WINS server
-machine or it's IP address.
-
-Note that this line MUST NOT BE SET in the smb.conf file of the Samba
-server acting as the WINS server itself. If you set both the
-"wins support = yes" option and the "wins server = " option then
-nmbd will fail to start.
-
-There are two possible scenarios for setting up cross subnet browsing.
-The first details setting up cross subnet browsing on a network containing
-Windows 95, Samba and Windows NT machines that are not configured as
-part of a Windows NT Domain. The second details setting up cross subnet
-browsing on networks that contain NT Domains.
-
-Setting up Browsing in a WORKGROUP
-==================================
-
-To set up cross subnet browsing on a network containing machines
-in up to be in a WORKGROUP, not an NT Domain you need to set up one
-Samba server to be the Domain Master Browser (note that this is *NOT*
-the same as a Primary Domain Controller, although in an NT Domain the
-same machine plays both roles). The role of a Domain master browser is
-to collate the browse lists from local master browsers on all the
-subnets that have a machine participating in the workgroup. Without
-one machine configured as a domain master browser each subnet would
-be an isolated workgroup, unable to see any machines on any other
-subnet. It is the presense of a domain master browser that makes
-cross subnet browsing possible for a workgroup.
-
-In an WORKGROUP environment the domain master browser must be a
-Samba server, and there must only be one domain master browser per
-workgroup name (although the same Samba server can act as Domain
-master browser for multiple workgroup names). To set up a Samba
-server as a domain master browser set the following option in the
-[global] section of the smb.conf file :
-
- domain master = yes
-
-The domain master browser should also preferrably be the local master
-browser for it's own subnet. In order to achieve this set the following
-options in the [global] section of the smb.conf file :
-
- domain master = yes
- local master = yes
- preferred master = yes
- os level = 65
-
-The domain master browser may be the same machine as the WINS
-server, if you require.
-
-Next, you should ensure that each of the subnets contains a
-machine that can act as a local master browser for the
-workgroup. Any NT machine should be able to do this, as will
-Windows 95 machines (although these tend to get rebooted more
-often, so it's not such a good idea to use these). To make a
-Samba server a local master browser set the following
-options in the [global] section of the smb.conf file :
-
- domain master = no
- local master = yes
- preferred master = yes
- os level = 65
-
-Do not do this for more than one Samba server on each subnet,
-or they will war with each other over which is to be the local
-master browser.
-
-The "local master" parameter allows Samba to act as a local master
-browser. The "preferred master" causes nmbd to force a browser
-election on startup and the "os level" parameter sets Samba high
-enough so that it should win any browser elections.
-
-If you have an NT machine on the subnet that you wish to
-be the local master browser then you can disable Samba from
-becoming a local master browser by setting the following
-options in the [global] section of the smb.conf file :
-
- domain master = no
- local master = no
- preferred master = no
- os level = 0
-
-Setting up Browsing in a DOMAIN
-===============================
-
-If you are adding Samba servers to a Windows NT Domain then
-you must not set up a Samba server as a domain master browser.
-By default, a Windows NT Primary Domain Controller for a Domain
-name is also the Domain master browser for that name, and many
-things will break if a Samba server registers the Domain master
-browser NetBIOS name (DOMAIN<1B>) with WINS instead of the PDC.
-
-For subnets other than the one containing the Windows NT PDC
-you may set up Samba servers as local master browsers as
-described. To make a Samba server a local master browser set
-the following options in the [global] section of the smb.conf
-file :
-
- domain master = no
- local master = yes
- preferred master = yes
- os level = 65
-
-If you wish to have a Samba server fight the election with machines
-on the same subnet you may set the "os level" parameter to lower
-levels. By doing this you can tune the order of machines that
-will become local master browsers if they are running. For
-more details on this see the section "FORCING SAMBA TO BE THE MASTER"
-below.
-
-If you have Windows NT machines that are members of the domain
-on all subnets, and you are sure they will always be running then
-you can disable Samba from taking part in browser elections and
-ever becoming a local master browser by setting following options
-in the [global] section of the smb.conf file :
-
- domain master = no
- local master = no
- preferred master = no
- os level = 0
-
-FORCING SAMBA TO BE THE MASTER
-==============================
-
-Who becomes the "master browser" is determined by an election process
-using broadcasts. Each election packet contains a number of parameters
-which determine what precedence (bias) a host should have in the
-election. By default Samba uses a very low precedence and thus loses
-elections to just about anyone else.
-
-If you want Samba to win elections then just set the "os level" global
-option in smb.conf to a higher number. It defaults to 0. Using 34
-would make it win all elections over every other system (except other
-samba systems!)
-
-A "os level" of 2 would make it beat WfWg and Win95, but not NTAS. A
-NTAS domain controller uses level 32.
-
-The maximum os level is 255
-
-If you want samba to force an election on startup, then set the
-"preferred master" global option in smb.conf to "yes". Samba will
-then have a slight advantage over other potential master browsers
-that are not preferred master browsers. Use this parameter with
-care, as if you have two hosts (whether they are windows 95 or NT or
-samba) on the same local subnet both set with "preferred master" to
-"yes", then periodically and continually they will force an election
-in order to become the local master browser.
-
-If you want samba to be a "domain master browser", then it is
-recommended that you also set "preferred master" to "yes", because
-samba will not become a domain master browser for the whole of your
-LAN or WAN if it is not also a local master browser on its own
-broadcast isolated subnet.
-
-It is possible to configure two samba servers to attempt to become
-the domain master browser for a domain. The first server that comes
-up will be the domain master browser. All other samba servers will
-attempt to become the domain master browser every 5 minutes. They
-will find that another samba server is already the domain master
-browser and will fail. This provides automatic redundancy, should
-the current domain master browser fail.
-
-
-MAKING SAMBA THE DOMAIN MASTER
-==============================
-
-The domain master is responsible for collating the browse lists of
-multiple subnets so that browsing can occur between subnets. You can
-make samba act as the domain master by setting "domain master = yes"
-in smb.conf. By default it will not be a domain master.
-
-Note that you should NOT set Samba to be the domain master for a
-workgroup that has the same name as an NT Domain.
-
-When samba is the domain master and the master browser it will listen
-for master announcements (made roughly every twelve minutes) from local
-master browsers on other subnets and then contact them to synchronise
-browse lists.
-
-If you want samba to be the domain master then I suggest you also set
-the "os level" high enough to make sure it wins elections, and set
-"preferred master" to "yes", to get samba to force an election on
-startup.
-
-Note that all your servers (including samba) and clients should be
-using a WINS server to resolve NetBIOS names. If your clients are only
-using broadcasting to resolve NetBIOS names, then two things will occur:
-
-a) your local master browsers will be unable to find a domain master
- browser, as it will only be looking on the local subnet.
-
-b) if a client happens to get hold of a domain-wide browse list, and
- a user attempts to access a host in that list, it will be unable to
- resolve the NetBIOS name of that host.
-
-If, however, both samba and your clients are using a WINS server, then:
-
-a) your local master browsers will contact the WINS server and, as long as
- samba has registered that it is a domain master browser with the WINS
- server, your local master browser will receive samba's ip address
- as its domain master browser.
-
-b) when a client receives a domain-wide browse list, and a user attempts
- to access a host in that list, it will contact the WINS server to
- resolve the NetBIOS name of that host. as long as that host has
- registered its NetBIOS name with the same WINS server, the user will
- be able to see that host.
-
-NOTE ABOUT BROADCAST ADDRESSES
-==============================
-
-If your network uses a "0" based broadcast address (for example if it
-ends in a 0) then you will strike problems. Windows for Workgroups
-does not seem to support a 0's broadcast and you will probably find
-that browsing and name lookups won't work.
-
-
-MULTIPLE INTERFACES
-===================
-
-Samba now supports machines with multiple network interfaces. If you
-have multiple interfaces then you will need to use the "interfaces"
-option in smb.conf to configure them. See smb.conf(5) for details.
-
diff --git a/docs/textdocs/BUGS.txt b/docs/textdocs/BUGS.txt
deleted file mode 100644
index 0bd12e8af0a..00000000000
--- a/docs/textdocs/BUGS.txt
+++ /dev/null
@@ -1,135 +0,0 @@
-Contributor: Samba Team
-Updated: June 27, 1997
-
-Subject: This file describes how to report Samba bugs.
-============================================================================
-
->> The email address for bug reports is samba-bugs@samba.anu.edu.au <<
-
-Please take the time to read this file before you submit a bug
-report. Also, please see if it has changed between releases, as we
-may be changing the bug reporting mechanism at some time.
-
-Please also do as much as you can yourself to help track down the
-bug. Samba is maintained by a dedicated group of people who volunteer
-their time, skills and efforts. We receive far more mail about it than
-we can possibly answer, so you have a much higher chance of an answer
-and a fix if you send us a "developer friendly" bug report that lets
-us fix it fast.
-
-Do not assume that if you post the bug to the comp.protocols.smb
-newsgroup or the mailing list that we will read it. If you suspect that your
-problem is not a bug but a configuration problem then it is better to send
-it to the Samba mailing list, as there are (at last count) 5000 other users on
-that list that may be able to help you.
-
-You may also like to look though the recent mailing list archives,
-which are conveniently accessible on the Samba web pages
-at http://samba.canberra.edu.au/pub/samba/
-
-
-GENERAL INFO
-------------
-
-Before submitting a bug report check your config for silly
-errors. Look in your log files for obvious messages that tell you that
-you've misconfigured something and run testparm to test your config
-file for correct syntax.
-
-Have you run through DIAGNOSIS.txt? This is very important.
-
-If you include part of a log file with your bug report then be sure to
-annotate it with exactly what you were doing on the client at the
-time, and exactly what the results were.
-
-
-DEBUG LEVELS
-------------
-
-If the bug has anything to do with Samba behaving incorrectly as a
-server (like refusing to open a file) then the log files will probably
-be very useful. Depending on the problem a log level of between 3 and
-10 showing the problem may be appropriate. A higher level givesmore
-detail, but may use too much disk space.
-
-To set the debug level use "log level =" in your smb.conf. You may
-also find it useful to set the log level higher for just one machine
-and keep separate logs for each machine. To do this use:
-
-log level = 10
-log file = /usr/local/samba/lib/log.%m
-include = /usr/local/samba/lib/smb.conf.%m
-
-then create a file "/usr/local/samba/lib/smb.conf.machine" where
-"machine" is the name of the client you wish to debug. In that file
-put any smb.conf commands you want, for example "log level=" may be
-useful. This also allows you to experiment with different security
-systems, protocol levels etc on just one machine.
-
-The smb.conf entry "log level =" is synonymous with the entry
-"debuglevel =" that has been used in older versions of Samba and
-is being retained for backwards compatibility of smb.conf files.
-
-As the "log level =" value is increased you will record a significantly
-increasing level of debugging information. For most debugging operations
-you may not need a setting higher than 3. Nearly all bugs can be tracked
-at a setting of 10, but be prepared for a VERY large volume of log data.
-
-
-INTERNAL ERRORs
----------------
-
-If you get a "INTERNAL ERROR" message in your log files it means that
-Samba got an unexpected signal while running. It is probably a
-segmentation fault and almost certainly means a bug in Samba (unless
-you have faulty hardware or system software)
-
-If the message came from smbd then it will probably be accompanied by
-a message which details the last SMB message received by smbd. This
-info is often very useful in tracking down the problem so please
-include it in your bug report.
-
-You should also detail how to reproduce the problem, if
-possible. Please make this reasonably detailed.
-
-You may also find that a core file appeared in a "corefiles"
-subdirectory of the directory where you keep your samba log
-files. This file is the most useful tool for tracking down the bug. To
-use it you do this:
-
-gdb smbd core
-
-adding appropriate paths to smbd and core so gdb can find them. If you
-don't have gdb then try "dbx". Then within the debugger use the
-command "where" to give a stack trace of where the problem
-occurred. Include this in your mail.
-
-If you known any assembly language then do a "disass" of the routine
-where the problem occurred (if its in a library routine then
-disassemble the routine that called it) and try to work out exactly
-where the problem is by looking at the surrounding code. Even if you
-don't know assembly then incuding this info in the bug report can be
-useful.
-
-
-ATTACHING TO A RUNNING PROCESS
-------------------------------
-
-Unfortunately some unixes (in particular some recent linux kernels)
-refuse to dump a core file if the task has changed uid (which smbd
-does often). To debug with this sort of system you could try to attach
-to the running process using "gdb smbd PID" where you get PID from
-smbstatus. Then use "c" to continue and try to cause the core dump
-using the client. The debugger should catch the fault and tell you
-where it occurred.
-
-
-PATCHES
--------
-
-The best sort of bug report is one that includes a fix! If you send us
-patches please use "diff -u" format if your version of diff supports
-it, otherwise use "diff -c4". Make sure your do the diff against a
-clean version of the source and let me know exactly what version you
-used.
-
diff --git a/docs/textdocs/DIAGNOSIS.txt b/docs/textdocs/DIAGNOSIS.txt
deleted file mode 100644
index 5f20f610310..00000000000
--- a/docs/textdocs/DIAGNOSIS.txt
+++ /dev/null
@@ -1,251 +0,0 @@
-Contributor: Andrew Tridgell
-Updated: June 27, 1997
-
-Subject: DIAGNOSING YOUR SAMBA SERVER
-===========================================================================
-
-This file contains a list of tests you can perform to validate your
-Samba server. It also tells you what the likely cause of the problem
-is if it fails any one of these steps. If it passes all these tests
-then it is probably working fine.
-
-You should do ALL the tests, in the order shown. I have tried to
-carefully choose them so later tests only use capabilities verified in
-the earlier tests.
-
-I would welcome additions to this set of tests. Please mail them to
-samba-bugs@samba.anu.edu.au
-
-If you send me an email saying "it doesn't work" and you have not
-followed this test procedure then you should not be surprised if I
-ignore your email.
-
-
-ASSUMPTIONS
------------
-
-In all of the tests I assume you have a Samba server called BIGSERVER
-and a PC called ACLIENT. I also assume the PC is running windows for
-workgroups with a recent copy of the microsoft tcp/ip stack. Alternatively,
-your PC may be running Windows 95 or Windows NT (Workstation or Server).
-
-The procedure is similar for other types of clients.
-
-I also assume you know the name of an available share in your
-smb.conf. I will assume this share is called "tmp". You can add a
-"tmp" share like by adding the following to smb.conf:
-
-[tmp]
- comment = temporary files
- path = /tmp
- read only = yes
-
-
-THESE TESTS ASSUME VERSION 1.9.16 OR LATER OF THE SAMBA SUITE. SOME
-COMMANDS SHOWN DID NOT EXIST IN EARLIER VERSIONS
-
-
-TEST 1:
--------
-
-In the directory in which you store your smb.conf file, run the command
-"testparm smb.conf". If it reports any errors then your smb.conf
-configuration file is faulty.
-
-Note: Your smb.conf file may be located in: /etc
- or in: /usr/local/samba/lib
-
-
-TEST 2:
--------
-
-run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from
-the unix box. If you don't get a valid response then your TCP/IP
-software is not correctly installed.
-
-Note that you will need to start a "dos prompt" window on the PC to
-run ping.
-
-If you get a message saying "host not found" or similar then your DNS
-software or /etc/hosts file is not correctly setup. It is possible to
-run samba without DNS entries for the server and client, but I assume
-you do have correct entries for the remainder of these tests.
-
-
-TEST 3:
--------
-
-Run the command "smbclient -L BIGSERVER" on the unix box. You
-should get a list of available shares back.
-
-If you get a error message containing the string "Bad password" then
-you probably have either an incorrect "hosts allow", "hosts deny" or
-"valid users" line in your smb.conf, or your guest account is not
-valid. Check what your guest account is using "testparm" and
-temporarily remove any "hosts allow", "hosts deny", "valid users" or
-"invalid users" lines.
-
-If you get a "connection refused" response then the smbd server could
-not be running. If you installed it in inetd.conf then you probably edited
-that file incorrectly. If you installed it as a daemon then check that
-it is running, and check that the netbios-ssn port is in a LISTEN
-state using "netstat -a".
-
-If you get a "session request failed" then the server refused the
-connection. If it says "your server software is being unfriendly" then
-its probably because you have invalid command line parameters to smbd,
-or a similar fatal problem with the initial startup of smbd. Also
-check your config file (smb.conf) for syntax errors with "testparm"
-and that the various directories where samba keeps its log and lock
-files exist.
-
-Another common cause of these two errors is having something already running
-on port 139, such as Samba (ie: smbd is running from inetd already) or
-something like Digital's Pathworks. Check your inetd.conf file before trying
-to start smbd as a daemon, it can avoid a lot of frustration!
-
-
-TEST 4:
--------
-
-Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the
-IP address of your Samba server back.
-
-If you don't then nmbd is incorrectly installed. Check your inetd.conf
-if you run it from there, or that the daemon is running and listening
-to udp port 137.
-
-One common problem is that many inetd implementations can't take many
-parameters on the command line. If this is the case then create a
-one-line script that contains the right parameters and run that from
-inetd.
-
-
-TEST 5:
--------
-
-run the command "nmblookup -B ACLIENT '*'"
-
-You should get the PCs IP address back. If you don't then the client
-software on the PC isn't installed correctly, or isn't started, or you
-got the name of the PC wrong.
-
-
-TEST 6:
--------
-
-Run the command "nmblookup -d 2 '*'"
-
-This time we are trying the same as the previous test but are trying
-it via a broadcast to the default broadcast address. A number of
-Netbios/TCPIP hosts on the network should respond, although Samba may
-not catch all of the responses in the short time it listens. You
-should see "got a positive name query response" messages from several
-hosts.
-
-If this doesn't give a similar result to the previous test then
-nmblookup isn't correctly getting your broadcast address through its
-automatic mechanism. In this case you should experiment use the
-"interfaces" option in smb.conf to manually configure your IP
-address, broadcast and netmask.
-
-If your PC and server aren't on the same subnet then you will need to
-use the -B option to set the broadcast address to the that of the PCs
-subnet.
-
-
-TEST 7:
--------
-
-Run the command "smbclient '\\BIGSERVER\TMP'". You should then be
-prompted for a password. You should use the password of the account
-you are logged into the unix box with. If you want to test with
-another account then add the -U option to the command
-line.
-
-Once you enter the password you should get the "smb>" prompt. If you
-don't then look at the error message. If it says "invalid network
-name" then the service "tmp" is not correctly setup in your smb.conf.
-
-If it says "bad password" then the likely causes are:
-
-- you have shadow passords (or some other password system) but didn't
-compile in support for them in smbd
-- your "valid users" configuration is incorrect
-- you have a mixed case password and you haven't enabled the "password
-level" option at a high enough level
-- the "path =" line in smb.conf is incorrect. Check it with testparm
-- you enabled password encryption but didn't create the SMB encrypted
-password file
-
-Once connected you should be able to use the commands "dir" "get"
-"put" etc. Type "help " for instructions. You should
-especially check that the amount of free disk space shown is correct
-when you type "dir".
-
-
-TEST 8:
--------
-
-On the PC type the command "net view \\BIGSERVER". You will need to do
-this from within a "dos prompt" window. You should get back a list of
-available shares on the server.
-
-If you get a "network name not found" or similar error then netbios
-name resolution is not working. This is usually caused by a problem in
-nmbd. To overcome it you could do one of the following (you only need
-to choose one of them):
-
-- fixup the nmbd installation
-- add the IP address of BIGSERVER to the "wins server" box in the
-advanced tcp/ip setup on the PC.
-- enable windows name resolution via DNS in the advanced section of
-the tcp/ip setup
-- add BIGSERVER to your lmhosts file on the PC.
-
-If you get a "invalid network name" or "bad password error" then the
-same fixes apply as they did for the "smbclient -L" test above. In
-particular, make sure your "hosts allow" line is correct (see the man
-pages)
-
-
-
-TEST 9:
---------
-
-Run the command "net use x: \\BIGSERVER\TMP". You should be prompted
-for a password then you should get a "command completed successfully"
-message. If not then your PC software is incorrectly installed or your
-smb.conf is incorrect. make sure your "hosts allow" and other config
-lines in smb.conf are correct.
-
-It's also possible that the server can't work out what user name to
-connect you as. To see if this is the problem add the line "user =
-USERNAME" to the [tmp] section of smb.conf where "USERNAME" is the
-username corresponding to the password you typed. If you find this
-fixes things you may need the username mapping option.
-
-
-TEST 10:
---------
-
-From file manager try to browse the server. Your samba server should
-appear in the browse list of your local workgroup (or the one you
-specified in smb.conf). You should be able to double click on the name
-of the server and get a list of shares. If you get a "invalid
-password" error when you do then you are probably running WinNT and it
-is refusing to browse a server that has no encrypted password
-capability and is in user level security mode. In this case either set
-"security = server" AND "password server = Windows_NT_Machine" in your
-smb.conf file, or enable encrypted passwords AFTER compiling in support
-for encrypted passwords (refer to the Makefile).
-
-
-Still having troubles?
-----------------------
-
-Try the mailing list or newsgroup, or use the tcpdump-smb utility to
-sniff the problem.
-
-Also look at the other docs in the Samba package!
-
diff --git a/docs/textdocs/DNIX.txt b/docs/textdocs/DNIX.txt
deleted file mode 100644
index 51005e6ec8c..00000000000
--- a/docs/textdocs/DNIX.txt
+++ /dev/null
@@ -1,69 +0,0 @@
-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.
-
-For this reason Samba by default defines the macro NO_EID in the DNIX
-section of includes.h. This works around the problem in a limited way,
-but it is far from ideal, some things still won't work right.
-
-To fix the problem properly you need to assemble the following two
-functions and then either add them to your C library or link them into
-Samba.
-
-put this in the file setegid.s:
-
- .globl _setegid
-_setegid:
- moveq #47,d0
- movl #100,a0
- moveq #1,d1
- movl 4(sp),a1
- trap #9
- bccs 1$
- jmp cerror
-1$:
- clrl d0
- rts
-
-
-put this in the file seteuid.s:
-
- .globl _seteuid
-_seteuid:
- moveq #47,d0
- movl #100,a0
- moveq #0,d1
- movl 4(sp),a1
- trap #9
- bccs 1$
- jmp cerror
-1$:
- clrl d0
- rts
-
-after creating the above files you then assemble them using
-
-as seteuid.s
-as setegid.s
-
-that should produce the files seteuid.o and setegid.o
-
-then you need to add these to the LIBSM line in the DNIX section of
-the Samba Makefile. Your LIBSM line will then look something like this:
-
-LIBSM = setegid.o seteuid.o -ln
-
-You should then remove the line:
-
-#define NO_EID
-
-from the DNIX section of includes.h
-
-Then recompile and try it out!
-
-Note that this file was derived from an email from Peter Olsson
-. I don't have DNIX myself, so you're probably better
-off contacting Peter if you have problems.
-
-Andrew
-
diff --git a/docs/textdocs/DOMAIN.txt b/docs/textdocs/DOMAIN.txt
deleted file mode 100644
index b2d8a3f34d2..00000000000
--- a/docs/textdocs/DOMAIN.txt
+++ /dev/null
@@ -1,179 +0,0 @@
-Contributor: Samba Team
-Updated: June 27, 1997
-
-Subject: Network Logons and Roving Profiles
-===========================================================================
-
-Samba supports domain logons, network logon scripts and user profiles.
-The support is still experimental, but it seems to work.
-
-The support is also not complete. Samba does not yet support the
-sharing of the SAM database with other systems, or remote administration.
-Support for these kind of things should be added sometime in the future.
-
-The domain support works for WfWg and Win95 clients. Support for Windows
-NT and OS/2 clients is still being worked on and is still experimental.
-
-Using these features you can make your clients verify their logon via
-the Samba server, make clients run a batch file when they logon to
-the network and download their preferences, desktop and start menu.
-
-
-Configuration Instructions: Network Logons
-==============================================
-
-To use domain logons and profiles you need to do the following:
-
-1) Setup nmbd and smbd and configure the smb.conf so that Samba is
-acting as the master browser. See INSTALL.txt and BROWSING.txt for
-details.
-
-2) create a share called [netlogon] in your smb.conf. This share should
-be readable by all users, and probably should not be writeable. This
-share will hold your network logon scripts, and the CONFIG.POL file
-(Note: for details on the CONFIG.POL file, refer to the Microsoft
-Windows NT Administration documentation. The format of these files
-is not known, so you will need to use Microsoft tools.)
-
-For example I have used:
-
- [netlogon]
- path = /data/dos/netlogon
- writeable = no
- guest ok = yes
-
-Note that it is important that this share is not writeable by ordinary
-users, in a secure environment: ordinary users should not be allowed
-to modify or add files that another user's computer would then download
-when they log in.
-
-3) in the [global] section of smb.conf set the following:
-
- domain logons = yes
- logon script = %U.bat
-
-the choice of batch file is, of course, up to you. The above would
-give each user a separate batch file as the %U will be changed to
-their username automatically. The other standard % macros may also be
-used. You can make the batch files come from a subdirectory by using
-soemthing like:
-
- logon script = scripts\%U.bat
-
-4) create the batch files to be run when the user logs in. If the batch
-file doesn't exist then no batch file will be run.
-
-In the batch files you need to be careful to use DOS style cr/lf line
-endings. If you don't then DOS may get confused. I suggest you use a
-DOS editor to remotely edit the files if you don't know how to produce
-DOS style files under unix.
-
-5) Use smbclient with the -U option for some users to make sure that
-the \\server\NETLOGON share is available, the batch files are visible
-and they are readable by the users.
-
-6) you will probabaly find that your clients automatically mount the
-\\SERVER\NETLOGON share as drive z: while logging in. You can put some
-useful programs there to execute from the batch files.
-
-NOTE: You must be using "security = user" or "security = server" for
-domain logons to work correctly. Share level security won't work
-correctly.
-
-
-
-Configuration Instructions: Setting up Roaming User Profiles
-================================================================
-
-1) in the [global] section of smb.conf set the following:
-
- logon path = \\profileserver\profileshare\profilepath\%U
-
-The default for this option is \\%L\%U, namely \\sambaserver\username,
-The \\L%\%U services is created automatically by the [homes] service.
-
-If you are using a samba server for the profiles, you _must_ make the
-share specified in the logon path browseable. Windows 95 appears to
-check that it can see the share and any subdirectories within that share
-specified by the logon path option, rather than just connecting straight
-away.
-
-When a user first logs in on Windows 95, the file user.dat is created,
-as are folders "start menu", "desktop", "programs" and "nethood".
-These directories and their contents will be merged with the local
-versions stored in c:\windows\profiles\username on subsequent logins,
-taking the most recent from each.
-
-The user.dat file contains all the user's preferences. If you wish to
-enforce a set of preferences, rename their user.dat file to user.man,
-and deny them write access to the file.
-
-2) On the Windows 95 machine, go to Control Panel | Passwords and
- select the User Profiles tab. Select the required level of
- roaming preferences. Press OK, but do _not_ allow the computer
- to reboot.
-
-3) On the Windows 95 machine, go to Control Panel | Network |
- Client for Microsoft Networks | Preferences. Select 'Log on to
- NT Domain'. Press OK, and this time allow the computer to reboot.
-
-You will now find that the Microsoft Networks Login box contains
-[user, password, domain] instead of just [user, password]. Type in
-the samba server's domain name (or any other domain known to exist),
-user name and user's password.
-
-Once the user has been successfully validated, the Windows 95 machine
-will inform you that 'The user has not logged on before' and asks you
-if you wish to save the user's preferences? Select 'yes'.
-
-Once the Windows 95 client comes up with the desktop, you should be able
-to examine the contents of the directory specified in the "logon path"
-(the default is \\samba_server\username) and verify that the "desktop",
-"start menu", "programs" and "nethood" folders have been created.
-
-These folders will be cached locally on the client, and updated when
-the user logs off (if you haven't made them read-only by then :-).
-
-
-If you have problems creating user profiles, you can reset the user's
-local desktop cache, as shown below. When this user then next logs in,
-they will be told that they are logging in "for the first time".
-
-
-1) instead of logging in under the [user, password, domain] dialog],
- press escape.
-
-2) run the regedit.exe program, and look in:
-
- HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList
-
- you will find an entry, for each user, of ProfilePath. Note the
- contents of this key (likely to be c:\windows\profiles\username),
- then delete the key ProfilePath for the required user.
-
- [Exit the registry editor].
-
-3) WARNING - before deleting the contents of the directory listed in
- the ProfilePath (this is likely to be c:\windows\profiles\username),
- ask them if they have any important files stored on their desktop
- or in their start menu. delete the contents of the directory
- ProfilePath (making a backup if any of the files are needed).
-
- This will have the effect of removing the local (read-only hidden
- system file) user.dat in their profile directory, as well as the
- local "desktop", "nethood", "start menu" and "programs" folders.
-
-4) search for the user's .PWL password-cacheing file in the c:\windows
- directory, and delete it.
-
-5) log off the windows 95 client.
-
-6) check the contents of the profile path (see "logon path" described
- above), and delete the user.dat or user.man file for the user,
- making a backup if required.
-
-
-If all else fails, increase samba's debug log levels to between 3 and 10,
-and / or run a packet trace program such as tcpdump or netmon.exe, and
-look for any error reports.
-
diff --git a/docs/textdocs/DOMAIN_CONTROL.txt b/docs/textdocs/DOMAIN_CONTROL.txt
deleted file mode 100644
index 19d702040c7..00000000000
--- a/docs/textdocs/DOMAIN_CONTROL.txt
+++ /dev/null
@@ -1,90 +0,0 @@
-Initial Release: August 22, 1996
-Contributor: John H Terpstra
-Updated: June 27, 1997
-Status: Current - New Content
-
-Subject: Windows NT Domain Control & Samba
-============================================================================
-
-****NOTE:****
-=============
-Microsoft Windows NT Domain Control is an extremely complex protocol.
-We have received countless requests to implement Domain Control in Samba
-and have seriously investigated the potential to support this. The Samba
-Team have now concluded that since Domain Control is a completely
-undocumented protocol we ought NOT to implement our best guess of this
-technology. It is a Microsoft business policy NOT to release the information
-necessary to enable this to be implemented in a dependable manner.
-============================================================================
-
-Windows NT Server can be installed as either a plain file and print server
-(WORKGROUP workstaion or server) or as a server that participates in Domain
-Control (DOMAIN member, Primary Domain controller or Backup Domain controller).
-
-The same is true for OS/2 Warp Server, Digital Pathworks and other similar
-products, all of which can participate in Domain Control along with Windows NT.
-
-To many people these terms can be confusing, so let's try to clear the air.
-
-Every Windows NT system (workstation or server) has a registry database.
-The registry contains entries that describe the initialisation information
-for all services (the equivalent of Unix Daemons) that run within the Windows
-NT environment. The registry also contains entries that tell application
-software where to find dynamically loadable libraries that they depend upon.
-In fact, the registry contains entries that describes everything that anything
-may need to know to interact with the rest of the system.
-
-The registry files will can be located on any Windows NT machine by opening a
-command prompt and typing:
- dir %SystemRoot%\System32\config
-
-The environment variable %SystemRoot% value can be obtained by typing:
- echo %SystemRoot%
-
-The active parts of the registry that you may want to be familiar with are
-the files called: default, system, software, sam and security.
-
-In a domain environment, Microsoft Windows NT domain controllers participate
-in replication of the SAM and SECURITY files so that all controllers within
-the domain have an exactly identical copy of each.
-
-The Microsoft Windows NT system is structured within a security model that
-says that all applications and services must authenticate themselves before
-they can obtain permission from the security manager to do what they set out
-to do.
-
-The Windows NT User database also resides within the registry. This part of
-the registry contains the user's security identifier, home directory, group
-memberships, desktop profile, and so on.
-
-Every Windows NT system (workstation as well as server) will have it's own
-registry. Windows NT Servers that participate in Domain Security control
-have a database that they share in common - thus they do NOT own an
-independant full registry database of their own, as do Workstations and
-plain Servers.
-
-The User database is called the SAM (Security Access Manager) database and
-is used for all user authentication as well as for authentication of inter-
-process authentication (ie: to ensure that the service action a user has
-requested is permitted within the limits of that user's privilidges).
-
-Windows for Workgroups, Windows 95, and Windows NT Workstations and Servers
-can participate in a Domain security system that is controlled by Windows NT
-servers that have been correctly configured. At most every domain will have
-ONE Primary Domain Controller (PDC). It is desirable that each domain will
-have at least one Backup Domain Controller (BDC).
-
-The PDC and BDCs then participate in replication of the SAM database so that
-each Domain Controlling participant will have an up to date SAM component
-within it's registry.
-
-Samba can NOT at this time function as a Domain Controller for any of these
-security services, but like all other domain members can interact with the
-Windows NT security system for all access authentication.
-
-When Samba is configured with the 'security = server' option and the
-'password server = Your_Windows_NT_Server_Name' option, then it will
-redirect all access authentication to that server. This way you can
-use Windows NT to act as your password server with full support for
-Microsoft encrypted passwords.
-
diff --git a/docs/textdocs/ENCRYPTION.txt b/docs/textdocs/ENCRYPTION.txt
deleted file mode 100644
index 04822eed329..00000000000
--- a/docs/textdocs/ENCRYPTION.txt
+++ /dev/null
@@ -1,350 +0,0 @@
-Contributor: Jeremy Allison
-Updated: June 27, 1997
-Note: Please refer to WinNT.txt also
-
-Subject: LanManager / Samba Password Encryption.
-============================================================================
-
-With the development of LanManager and Windows NT compatible password
-encryption for Samba, it is now able to validate user connections in
-exactly the same way as a LanManager or Windows NT server.
-
-This document describes how the SMB password encryption algorithm
-works and what issues there are in choosing whether you want to use
-it. You should read it carefully, especially the part about security
-and the "PROS and CONS" section.
-
-How does it work ?
-------------------
-
- LanManager encryption is somewhat similar to UNIX password
-encryption. The server uses a file containing a hashed value of a
-users password. This is created by taking the users paintext
-password, capitalising it, and either truncating to 14 bytes (or
-padding to 14 bytes with null bytes). This 14 byte value is used as
-two 56 bit DES keys to encrypt a 'magic' eight byte value, forming a
-16 byte value which is stored by the server and client. Let this value
-be known as the *hashed password*.
-
- Windows NT encryption is a higher quality mechanism, consisting
-of doing an MD4 hash on a Unicode version of the users password. This
-also produces a 16 byte hash value that is non-reversible.
-
-When a client (LanManager, Windows for WorkGroups, Windows 95 or
-Windows NT) wishes to mount a Samba drive (or use a Samba resource) it
-first requests a connection and negotiates the protocol that the client
-and server will use. In the reply to this request the Samba server
-generates and appends an 8 byte, random value - this is stored in the
-Samba server after the reply is sent and is known as the *challenge*.
-
-The challenge is different for every client connection.
-
-The client then uses the hashed password (16 byte values described
-above), appended with 5 null bytes, as three 56 bit DES keys, each of
-which is used to encrypt the challenge 8 byte value, forming a 24 byte
-value known as the *response*.
-
-In the SMB call SMBsessionsetupX (when user level security is
-selected) or the call SMBtconX (when share level security is selected)
-the 24 byte response is returned by the client to the Samba server.
-For Windows NT protocol levels the above calculation is done on
-both hashes of the users password and both responses are returned
-in the SMB call, giving two 24 byte values.
-
-The Samba server then reproduces the above calculation, using it's own
-stored value of the 16 byte hashed password (read from the smbpasswd
-file - described later) and the challenge value that it kept from the
-negotiate protocol reply. It then checks to see if the 24 byte value it
-calculates matches the 24 byte value returned to it from the client.
-
-If these values match exactly, then the client knew the correct
-password (or the 16 byte hashed value - see security note below) and
-is this allowed access. If not then the client did not know the
-correct password and is denied access.
-
-Note that the Samba server never knows or stores the cleartext of the
-users password - just the 16 byte hashed values derived from it. Also
-note that the cleartext password or 16 byte hashed values are never
-transmitted over the network - thus increasing security.
-
-IMPORTANT NOTE ABOUT SECURITY
------------------------------
-
-The unix and SMB password encryption techniques seem similar on the
-surface. This similarity is, however, only skin deep. The unix scheme
-typically sends clear text passwords over the nextwork when logging
-in. This is bad. The SMB encryption scheme never sends the cleartext
-password over the network but it does store the 16 byte hashed values
-on disk. This is also bad. Why? Because the 16 byte hashed values are a
-"password equivalent". You cannot derive the users password from them,
-but they could potentially be used in a modified client to gain access
-to a server. This would require considerable technical knowledge on
-behalf of the attacker but is perfectly possible. You should thus
-treat the smbpasswd file as though it contained the cleartext
-passwords of all your users. Its contents must be kept secret, and the
-file should be protected accordingly.
-
-Ideally we would like a password scheme which neither requires plain
-text passwords on the net or on disk. Unfortunately this is not
-available as Samba is stuck with being compatible with other SMB
-systems (WinNT, WfWg, Win95 etc).
-
-
-PROS AND CONS
--------------
-
-There are advantages and disadvantages to both schemes.
-
-Advantages of SMB Encryption:
------------------------------
-
-- plain text passwords are not passed across the network. Someone using
-a network sniffer cannot just record passwords going to the SMB server.
-
-- WinNT doesn't like talking to a server that isn't using SMB
-encrypted passwords. It will refuse to browse the server if the server
-is also in user level security mode. It will insist on promting the
-user for the password on each connection, which is very annoying. The
-only things you can do to stop this is to use SMB encryption.
-
-Advantages of non-encrypted passwords:
---------------------------------------
-
-- plain text passwords are not kept on disk.
-
-- uses same password file as other unix services such as login and
-ftp
-
-- you are probably already using other services (such as telnet and
-ftp) which send plain text passwords over the net, so not sending them
-for SMB isn't such a big deal.
-
-Note that Windows NT 4.0 Service pack 3 changed the default for
-permissible authentication so that plaintext passwords are *never*
-sent over the wire. The solution to this is either to switch to
-encrypted passwords with Samba or edit the Windows NT registry to
-re-enable plaintext passwords. See the document WinNT.txt for
-details on how to do this.
-
-The smbpasswd file.
--------------------
-
- In order for Samba to participate in the above protocol it must
-be able to look up the 16 byte hashed values given a user name.
-Unfortunately, as the UNIX password value is also a one way hash
-function (ie. it is impossible to retrieve the cleartext of the users
-password given the UNIX hash of it) then a separate password file
-containing this 16 byte value must be kept. To minimise problems with
-these two password files, getting out of sync, the UNIX /etc/passwd and
-the smbpasswd file, a utility, mksmbpasswd.sh, is provided to generate
-a smbpasswd file from a UNIX /etc/passwd file.
-
-To generate the smbpasswd file from your /etc/passwd file use the
-following command :-
-
-cat /etc/passwd | mksmbpasswd.sh >/usr/local/samba/private/smbpasswd
-
-If you are running on a system that uses NIS, use
-
-ypcat passwd | mksmbpasswd.sh >/usr/local/samba/private/smbpasswd
-
-The mksmbpasswd.sh program is found in the Samba source directory. By
-default, the smbpasswd file is stored in :-
-
-/usr/local/samba/private/smbpasswd
-
-The owner of the /usr/local/samba/private directory should be set to
-root, and the permissions on it should be set to :-
-
-r-x------
-
-The command
-
-chmod 500 /usr/local/samba/private
-
-will do the trick. Likewise, the smbpasswd file inside the private
-directory should be owned by root and the permissions on is should be
-set to
-
-rw-------
-
-by the command :-
-
-chmod 600 smbpasswd.
-
-The format of the smbpasswd file is
-
-username:uid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:Long name:user home dir:user shell
-
-Although only the username, uid, and XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-sections are significant and are looked at in the Samba code.
-
-It is *VITALLY* important that there by 32 'X' characters between the
-two ':' characters in the XXX sections - the smbpasswd and Samba code
-will fail to validate any entries that do not have 32 characters
-between ':' characters. The first XXX section is for the Lanman password
-hash, the second is for the Windows NT version.
-
-When the password file is created all users have password entries
-consisting of 32 'X' characters. By default this disallows any access
-as this user. When a user has a password set, the 'X' characters change
-to 32 ascii hexadecimal digits (0-9, A-F). These are an ascii
-representation of the 16 byte hashed value of a users password.
-
-To set a user to have no password (not recommended), edit the file
-using vi, and replace the first 11 characters with the asci text
-
-NO PASSWORD
-
-Eg. To clear the password for user bob, his smbpasswd file entry would
-look like :
-
-bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:Bob's full name:/bobhome:/bobshell
-
-If you are allowing users to use the smbpasswd command to set their own
-passwords, you may want to give users NO PASSWORD initially so they do
-not have to enter a previous password when changing to their new
-password (not recommended).
-
-Note : This file should be protected very carefully. Anyone with
-access to this file can (with enough knowledge of the protocols) gain
-access to your SMB server. The file is thus more sensitive than a
-normal unix /etc/passwd file.
-
-The smbpasswd Command.
-----------------------
-
- The smbpasswd command maintains the two 32 byte password fields in
-the smbpasswd file. If you wish to make it similar to the unix passwd
-or yppasswd programs, install it in /usr/local/samba/bin (or your main
-Samba binary directory) and make it setuid root.
-
-Note that if you do not do this then the root user will have to set all
-users passwords.
-
-To set up smbpasswd as setuid root, change to the Samba binary install
-directory and then type (as root) :
-
-chown root smbpasswd
-chmod 4555 smbpasswd
-
-If smbpasswd is installed as setuid root then you would use it as
-follows.
-
-smbpasswd
-Old SMB password:
-New SMB Password: < type new value >
-Repeat New SMB Password: < re-type new value >
-
-If the old value does not match the current value stored for that user,
-or the two new values do not match each other, then the password will
-not be changed.
-
-If invoked by an ordinary user it will only allow the user to change
-his or her own Samba password.
-
-If run by the root user smbpasswd may take an optional argument,
-specifying the user name whose SMB password you wish to change. Note
-that when run as root smbpasswd does not prompt for or check the old
-password value, thus allowing root to set passwords for users who have
-forgotten their passwords.
-
-smbpasswd is designed to work in the same way and be familiar to UNIX
-users who use the passwd or yppasswd commands.
-
-NOTE. As smbpasswd is designed to be installed as setuid root I would
-appreciate it if everyone examined the source code to look for
-potential security flaws. A setuid program, if not written properly can
-be an open door to a system cracker. Please help make this program
-secure by reporting all problems to me (the author, Jeremy Allison).
-
-My email address is :-
-
-jallison@whistle.com
-
-Setting up Samba to support LanManager Encryption.
---------------------------------------------------
-
-This is a very brief description on how to setup samba to support
-password encryption. More complete instructions will probably be added
-later.
-
-1) get and compile the libdes libraries. the source is available from
-ftp://samba.anu.edu.au/pub/libdes/
-
-2) enable the encryption stuff in the Samba makefile, making sure you
-point it to the libdes library and include file (it needs des.h)
-The entries you need to uncomment are the four lines after the comment :-
-
-# This is for SMB encrypted (lanman) passwords.
-
-Note that you may have to change the variable DES_BASE to
-point at the place where you installed the DES library.
-
-3) compile and install samba as usual
-
-4) f your system can't compile the module getsmbpass.c then remove the
--DSMBGETPASS define from the Makefile.
-
-5) enable encrypted passwords in smb.conf by adding the line
-"encrypt passwords = yes" in the [global] section
-
-6) create the initial smbpasswd password file in the place you
-specified in the Makefile. A simple way to do this based on your
-existing Makefile (assuming it is in a reasonably standard format) is
-like this:
-
-cat /etc/passwd | mksmbpasswd.sh > /usr/local/samba/private/smbpasswd
-
-Change ownership of private and smbpasswd to root.
-
-chown -R root /usr/local/samba/private
-
-Set the correct permissions on /usr/local/samba/private
-
-chmod 500 /usr/local/samba/private
-
-Set the correct permissions on /usr/local/samba/private/smbpasswd
-
-chmod 600 /usr/local/samba/private/smbpasswd
-
-note that the mksmbpasswd.sh script is in the samba source directory.
-
-If this fails then you will find that you will need entries that look
-like this:
-
-# SMB password file.
-tridge:148:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:Andrew Tridgell:/home/tridge:/bin/tcsh
-
-note that the uid and username fields must be right. Also, you must get
-the number of X's right (there should be 32).
-
-If you wish, install the smbpasswd program as suid root.
-
-chown root /usr/local/samba/bin/smbpasswd
-chmod 4555 /usr/local/samba/bin/smbpasswd
-
-7) set the passwords for users using the smbpasswd command. For
-example, as root you could do "smbpasswd tridge"
-
-8) try it out!
-
-Note that you can test things using smbclient, as it also now supports
-encryption.
-
-NOTE TO USA Sites that Mirror Samba
------------------------------------
-
-The DES library is considered a munition in the USA. Under US Law it is
-illegal to export this software, or to put it in a freely available ftp
-site.
-
-Please do not mirror the libdes directory from the site on
-samba.anu.edu.au
-
-Thank you,
-
-Jeremy Allison.
-
-==============================================================================
-Footnote: Please refer to WinNT.txt also
diff --git a/docs/textdocs/Faxing.txt b/docs/textdocs/Faxing.txt
deleted file mode 100644
index 511640d556f..00000000000
--- a/docs/textdocs/Faxing.txt
+++ /dev/null
@@ -1,163 +0,0 @@
-Contributor: Gerhard Zuber
-Initial Release: ?
-
-Subject: F A X I N G with S A M B A
-=============================================================================
-
-This text describes how to turn your SAMBA-server into a fax-server
-for any environment, especially for Windows.
-
-Requirements:
- UNIX box (Linux preferred) with SAMBA
- ghostscript package
- mgetty+sendfax package
- pbm package (portable bitmap tools)
-
-FTP sites:
- mgetty099-May31.tar.gz
- I got it from: ftp://ftp.gwdg.de/pub/linux/misc/mgetty/mgetty099-May31.tar.gz
-
-
-making mgetty+sendfax running:
-==============================
-
- go to source tree: /usr/src/mgetty+sendfax
- cp policy.h-dist policy.h
-
- change your settings: valid tty ports, modem initstring, Station-Id
-
-#define MODEM_INIT_STRING "AT &F S0=0 &D3 &K3 &C1\\\\N2"
-
-#define FAX_STATION_ID "49 30 12345678"
-
-#define FAX_MODEM_TTYS "ttyS1:ttyS2:ttyS3"
-
- Modem initstring is for rockwell based modems
- if you want to use mgetty+sendfax as PPP-dialin-server,
- define AUTO_PPP in Makefile:
-
-CFLAGS=-O2 -Wall -pipe -DAUTO_PPP
-
- compile it and install the package.
- edit your /etc/inittab and let mgetty running on your preferred
- ports:
-
-s3:45:respawn:/usr/local/sbin/mgetty ttyS2 vt100
-
- now issue a
- kill -HUP 1
- and enjoy with the lightning LEDs on your modem
- your now are ready to receive faxes !
-
-
- if you want a PPP dialin-server, edit
- /usr/local/etc/mgetty+sendfax/login.config
-
-/AutoPPP/ - ppp /usr/sbin/pppd auth debug passive modem
-
-
-
-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.
-
-
-
-Now making the fax-server:
-===========================
-
- fetch the file
- mgetty+sendfax/frontends/winword/faxfilter
-
- and place it in
-
- /usr/local/etc/mgetty+sendfax/
-
- prepare your faxspool file as mentioned in this file
- /usr/local/bin/faxspool
-
- if [ "$user" = "root" -o "$user" = "fax" -o \
- "$user" = "lp" -o "$user" = "daemon" -o "$user" = "bin" ]
-
- make sure you have pbmtext (from the pbm-package). This is
- needed for creaating the small header line on each page.
-
- make sure your ghostscript is functional. You need fonts !
- I prefer these from the OS/2 disks
-
-
- 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:
-
-
-
-
- edit your /usr/local/samba/lib/smb.conf
-
- so you have a smb based printer named "fax"
-
-
-
-The final step:
-===============
-
- 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
- are ready to fax.
-
- On Windows 3.1 95 and NT:
-
- Install a printer wich produces postscript output,
- e.g. apple laserwriter
-
- 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.
-
- Usually each fax has a header page. It carries your name,
- 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.
-
- 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.
-
- Now print your fax through the fax-printer and it will be
- queued for later transmission. Use faxrunq for sending the
- queue out.
-
diff --git a/docs/textdocs/GOTCHAS.txt b/docs/textdocs/GOTCHAS.txt
deleted file mode 100644
index d4e5f3e842d..00000000000
--- a/docs/textdocs/GOTCHAS.txt
+++ /dev/null
@@ -1,68 +0,0 @@
-This file lists Gotchas to watch out for:
-=========================================================================
-Item Number: 1.0
-Description: Problem Detecting Interfaces
-Symptom: Workstations do NOT see Samba server in Browse List
-OS: RedHat - Rembrandt Beta 2
-Platform: Intel
-Date: August 16, 1996
-Submitted By: John H Terpstra
-Details:
- 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
- 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
-=========================================================================
-Item Number: 2.0
-Description: Problems with MS Windows NT Server network logon service
-Symptom: Loss of Domain Logon Services and failed Windows NT / 95
- logon attempts.
-OS: All Unix systems with Windows NT Domain Control environments.
-Platform: All
-Date: February 1, 1997
-Submitted By: John H Terpstra
-Details:
- Samba is configured for Domain logon control in a network
- where a Windows NT Domain Primary Controller is running.
-
- Case 1:
- The Windows NT Server is shut down, then restarted. Then
- the Samba server is reconfigured so that it NO LONGER offers
- Domain logon services. Windows NT and 95 workstations can no
- longer log onto the domain. Ouch!!!
-
- Case 2:
- The Windows NT Server which is running the Network logon
- Service is shut down and restarted while Samba is a domain
- controller offering the Domain LogOn service. Windows NT
- Workstation and Server can no longer log onto the network.
-
- Cause:
- Windows NT checks at start up to see if any domain logon
- controllers are already running within the domain. It finds
- Samba claiming to offer the service and therefore does NOT
- start it's Network Logon Service.
-
- Windows NT needs the Windows NT network logon service to gain
- from it's Domain controller's SAM database the security
- identifier for the user loging on.
-
-Work-around: Stop the Samba nmbd and smbd processes, then on the Windows
- NT Primary Domain Controller start the Network Logon Service.
- Now restart the Samba nmbd and smbd services.
-
- Better still: DO NOT CONFIGURE SAMBA AS THE NETWORK LOGON
- SERVER, DO NOT SET SAMBA TO BE THE DOMAIN MASTER, DO NOT
- SET SAMBA TO OS LEVEL GREATER THAN 0.
-
- ie: Let Windows NT Server be the Domain Logon server, the
- domain master browser and do NOT interfere with any aspect
- of Microsoft Windows NT Domain Control.
-=========================================================================
diff --git a/docs/textdocs/HINTS.txt b/docs/textdocs/HINTS.txt
deleted file mode 100644
index f5781ee4232..00000000000
--- a/docs/textdocs/HINTS.txt
+++ /dev/null
@@ -1,209 +0,0 @@
-Contributor: Many
-Updated: Not for a long time!
-
-Subject: A collection of hints
-Status: May be useful information but NOT current
-===============================================================================
-
-Here are some random hints that you may find useful. These really
-should be incorporated in the main docs someday.
-
-
-----------------------
-HINT: Always test your smb.conf with testparm before using it
-
-If your smb.conf file is invalid then samba will fail to load. Run
-testparm over it before you install it just to make sure there aren't
-any basic syntax or logical errors.
-
-
-----------------------
-HINT: Try printing with smbclient first
-
-If you have problems printing, test with smbclient first. Just connect using
-"smbclient '\\server\printer' -P" and use the "print" command.
-
-Once this works, you know that Samba is setup correctly for printing,
-and you should be able to get it to work from your PCs.
-
-This particularly helps in getting the "print command" right.
-
-
-----------------------
-HINT: Mount cdroms with conv=binary
-
-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.
-
-To overcome this problem use conv=binary when mounting the cdrom
-before exporting it with Samba.
-
-
-----------------------
-HINT: 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.
-
-Get it from
-ftp://samba.anu.edu.au/pub/samba/contributed/fixcrlf.zip
-
-----------------------
-HINT: Use the "username map" option
-
-If the usernames used on your PCs don't match those used on the unix
-server then you will find the "username map" option useful.
-
------------------------
-HINT: Use "security = user" in [global]
-
-If you have the same usernames on the unix box and the PCs or have
-mapped them with the "username map" option then choose "security =
-user" in the [global] section of smb.conf.
-
-This will mean your password is checked only when you first connect,
-and subsequent connections to printers, disks etc will go more
-smoothly and much faster.
-
-The main problem with "security = user" if you use WfWg is that you
-will ONLY be able to connect as the username that you log into WfWg
-with. This is because WfWg silently ignores the password field in the
-connect drive dialog box if the server is in user security mode.
-
-------------------------
-HINT: Make your printers not "guest ok"
-
-If your printers are not "guest ok" and you are using "security =
-user" and have matching unix and PC usernames then you will attach to
-the printer without trouble as your own username. This will mean you
-will be able to delete print jobs (in 1.8.06 and above) and printer
-accounting will be possible.
-
-
------------------------
-HINT: Use a sensible "guest" account
-
-Even if all your services are not available to "guest" you will need a
-guest account. This is because the browsing is done as guest. In many
-cases setting "guest account = ftp" will do the trick. Using the
-default guest account or "guest account = nobody" will give problems on
-many unixes. If in doubt create another account with minimal
-privilages and use it instead. Your users don't need to know the
-password of the guest account.
-
-
------------------------
-HINT: Use the latest TCP/IP stack from microsoft if you use Windows
-for workgroups.
-
-The early TCP/IP stacks had lots of bugs.
-
-Microsoft has released an incremental upgrade to their TCP/IP 32-Bit
-VxD drivers. The latest release can be found on their ftp site at
-ftp.microsoft.com, located in /peropsys/windows/public/tcpip/wfwt32.exe.
-There is an update.txt file there that describes the problems that were
-fixed. New files include WINSOCK.DLL, TELNET.EXE, WSOCK.386, VNBT.386,
-WSTCP.386, TRACERT.EXE, NETSTAT.EXE, and NBTSTAT.EXE.
-
-
------------------------
-HINT: nmbd can act as a "WINS" server
-
-By default SMB clients use broadcasts to find shares. Recent clients
-(such as WfWg) can use a "wins" server instead, whcih reduces your
-broadcast traffic and allows you to find names across routers.
-
-Just point your WfWg, Win95 and NT clients at the Samba box in the WINS option.
-
-Note: nmbd does not support all WINS operations. Anyone out there have
-a spec they could send me?
-
------------------------
-HINT: you may need to delete your .pwl files when you change password.
-
-WfWg does a lousy job with passwords. I find that if I change my
-password on either the unix box or the PC the safest thing to do is to
-delete the .pwl files in the windows directory. The PC will complain about not finding the files, but will soon get over it, allowing you to enter the new password.
-
-If you don't do this you may find that WfWg remembers and uses the old
-password, even if you told it a new one.
-
-Often WfWg will totally ignore a password you give it in a dialog box.
-
-----------------------
-HINT: Using MS Access
-
-Here are some notes on running MS-Access on a Samba drive from Stefan
-Kjellberg
-
-1. Opening a database in 'exclusive' mode does NOT work. Samba ignores
- r/w/share modes on file open.
-
-2. Make sure that you open the database as 'shared' and to 'lock modified
- records'
-
-3. Of course locking must be enabled for the particular share (smb.conf)
-
-
----------------------
-HINT: password cacheing in WfWg
-
-Here is a hint from michael@ecel.uwa.edu.au (Michael Simmons):
-
-In case people where not aware. There is a program call admincfg.exe
-on the last disk (disk 8) of the WFW 3.11 disk set. To install it
-type EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE Then add an icon
-for it via the "Progam Manager" "New" Menu. This program allows you
-to control how WFW handles passwords. ie disable Password Caching etc
-for use with "security = user"
-
-
---------------------
-HINT: file descriptor limits
-
-If you have problems with the limits on the number of open files you
-can edit local.h to fix it.
-
---------------------
-HINT: HPUX initgroups() problem
-
-here is a hint from Frank Wales [frank@arcglade.demon.co.uk]:
-
-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
-initgroups() reads the latter. Most system admins who know the ropes
-symlink /etc/group to /etc/logingroup (hard link doesn't work for reasons
-too stupid to go into here). initgroups() will complain if one of the
-groups you're in in /etc/logingroup has what it considers to be an invalid
-ID, which means outside the range [0..UID_MAX], where UID_MAX is (I think)
-60000 currently on HP-UX. This precludes -2 and 65534, the usual 'nobody'
-GIDs.
-
-Perhaps you could suggest to users that, if they encounter this problem,
-they make sure that the programs that are failing 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).
-
-
----------------------
-HINT: Patch your SCO system
-
-If you run SCO Unix then you may need to get important TCP/IP patches
-for Samba to work correctly. Try
-
-Paul_Davis@mindlink.bc.ca writes:
-
- I was having problems with Accpac using 1.9.02 on SCO Unix. One
- posting function reported corrupted data. After installing uod385a,
- the problem went away (a restore from backup and then another
- run-thru).
-
- It appears that the uod385a update for SCO may be fairly important for
- a lot of different DOS and Windows software under Samba.
-
- uod385a can be found at ftp.sco.com /SLS/uod385a.Z and uod385a.ltr.Z.
-
-
diff --git a/docs/textdocs/INSTALL.sambatar b/docs/textdocs/INSTALL.sambatar
deleted file mode 100644
index 413f54d3c65..00000000000
--- a/docs/textdocs/INSTALL.sambatar
+++ /dev/null
@@ -1,33 +0,0 @@
-Contributor: Ricky Poulten
-Date: Unknown
-Status: Current
-
-Subject: Using smbtar
-=============================================================================
-
-Please see the readme and the man page for general info.
-
-1) Follow the samba installation instructions.
-
-2) If all goes well, test it out by creating a share on your PC (called
-backup for example) then doing something like,
-
- ./smbtar -s mypc -t /dev/rmt/0ubn -x backup
-
-substituting whatever your tape drive is for the -t option, or set your
-tape environmental variable.
-
-If all does not go well, feel free to mail the author (poultenr@logica.co.uk)
-about bug reports / help / money / pizza / etc.
-
-3) Read the man page and the NOTES file for more information
-
-4) Work smbtar into your usual nightly backup scheme (presuming you
-have one :-}).
-
-
-NOTE:
-
-If you have problems with smbtar then it's probably best to contact the
-author Ricky Poulten (poultenr@logica.co.uk).
-
diff --git a/docs/textdocs/NetBIOS.txt b/docs/textdocs/NetBIOS.txt
deleted file mode 100644
index 3ea9e3c479b..00000000000
--- a/docs/textdocs/NetBIOS.txt
+++ /dev/null
@@ -1,131 +0,0 @@
-Contributor: Unknown
-Date: Unknown
-Status: Current
-
-Subject: Definition of NetBIOS Protocol and Name Resolution Modes
-=============================================================================
-
-=======
-NETBIOS
-=======
-
-NetBIOS runs over the following tranports: TCP/IP; NetBEUI and IPX/SPX.
-Samba only uses NetBIOS over TCP/IP. For details on the TCP/IP NetBIOS
-Session Service NetBIOS Datagram Service, and NetBIOS Names, see
-rfc1001.txt and rfc1002.txt.
-
-NetBEUI is a raw NetBIOS frame protocol implementation that allows NetBIOS
-datagrams to be sent out over the 'wire' embedded within LLC frames.
-NetBEUI is not required when using NetBIOS over TCP/IP protocols and it
-is preferrable NOT to install NetBEUI if it can be avoided.
-
-NetBIOS applications (such as samba) offer their services (for example,
-SMB file and print sharing) on a NetBIOS name. They must claim this name
-on the network before doing so. The NetBIOS session service will then
-accept connections on the application's behalf (on the NetBIOS name
-claimed by the application). A NetBIOS session between the application
-and the client can then commence.
-
-NetBIOS names consist of 15 characters plus a 'type' character. This is
-similar, in concept, to an IP address and a TCP port number, respectively.
-A NetBIOS-aware application on a host will offer different services under
-different NetBIOS name types, just as a host will offer different TCP/IP
-services on different port numbers.
-
-NetBIOS names must be claimed on a network, and must be defended. The use
-of NetBIOS names is most suitable on a single subnet; a Local Area Network
-or a Wide Area Network.
-
-NetBIOS names are either UNIQUE or GROUP. Only one application can claim a
-UNIQUE NetBIOS name on a network.
-
-There are two kinds of NetBIOS Name resolution: Broadcast and Point-to-Point.
-
-=================
-BROADCAST NetBIOS
-=================
-
-Clients can claim names, and therefore offer services on successfully claimed
-names, on their broadcast-isolated subnet. One way to get NetBIOS services
-(such as browsing: see ftp.microsoft.com/drg/developr/CIFS/browdiff.txt; and
-SMB file/print sharing: see cifs4.txt) working on a LAN or WAN is to make
-your routers forward all broadcast packets from TCP/IP ports 137, 138 and 139.
-
-This, however, is not recommended. If you have a large LAN or WAN, you will
-find that some of your hosts spend 95 percent of their time dealing with
-broadcast traffic. [If you have IPX/SPX on your LAN or WAN, you will find
-that this is already happening: a packet analyzer will show, roughly
-every twelve minutes, great swathes of broadcast traffic!].
-
-
-============
-NBNS NetBIOS
-============
-
-rfc1001.txt describes, amongst other things, the implementation and use
-of, a 'NetBIOS Name Service'. NT/AS offers 'Windows Internet Name Service'
-which is fully rfc1001/2 compliant, but has had to take specific action
-with certain NetBIOS names in order to make it useful. (for example, it
-deals with the registration of <1c> <1d> <1e> names all in different ways.
-I recommend the reading of the Microsoft WINS Server Help files for full
-details).
-
-Samba also offers WINS server capabilities. Samba does not interact
-with NT/AS (WINS replication), so if you have a mixed NT server and
-Samba server environment, it is recommended that you use the NT server's
-WINS capabilities, instead of samba's WINS server capabilities.
-
-The use of a WINS server cuts down on broadcast network traffic for
-NetBIOS name resolution. It has the effect of pulling all the broadcast
-isolated subnets together into a single NetBIOS scope, across your LAN
-or WAN, while avoiding the use of TCP/IP broadcast packets.
-
-When you have a WINS server on your LAN, WINS clients will be able to
-contact the WINS server to resolve NetBIOS names. Note that only those
-WINS clients that have registered with the same WINS server will be
-visible. The WINS server _can_ have static NetBIOS entries added to its
-database (usually for security reasons you might want to consider putting
-your domain controllers or other important servers as static entries,
-but you should not rely on this as your sole means of security), but for
-the most part, NetBIOS names are registered dynamically.
-
-[It is important to mention that samba's browsing capabilities (as a WINS
-client) must have access to a WINS server. if you are using samba also
-as a WINS server, then it will have a direct short-cut into the WINS
-database.
-
-This provides some confusion for lots of people, and is worth mentioning
-here: a Browse Server is NOT a WINS Server, even if these services are
-implemented in the same application. A Browse Server _needs_ a WINS server
-because a Browse Server is a WINS client, which is _not_ the same thing].
-
-Clients can claim names, and therefore offer services on successfully claimed
-names, on their broadcast-isolated subnet. One way to get NetBIOS services
-(such as browsing: see ftp.microsoft.com/drg/developr/CIFS/browdiff.txt; and
-SMB file/print sharing: see cifs4.txt) working on a LAN or WAN is to make
-your routers forward all broadcast packets from TCP/IP ports 137, 138 and 139.
-
-WINS Clients therefore claim names from the WINS server. If the WINS
-server allows them to register a name, the client's NetBIOS session service
-can then offer services on this name. Other WINS clients will then
-contact the WINS server to resolve a NetBIOS name.
-
-To configure samba as a WINS server, you must add "wins support = yes" to
-the [global] section of your smb.conf file. This will enable WINS server
-capabilities in nmbd.
-
-To configure samba as a WINS client, you must add "wins server = x.x.x.x"
-to the [global] section of your smb.conf file, where x.x.x.x is the TCP/IP
-address of your WINS server. The browsing capabilities in nmbd will then
-register (and resolve) WAN-wide NetBIOS names with this WINS server.
-
-Note that if samba has "wins support = yes", then the browsing capabilities
-will _not_ use the "wins server" option to resolve NetBIOS names: it will
-go directly to the internal WINS database for NetBIOS name resolution. It
-is therefore invalid to have both "wins support = yes" and
-"wins server = x.x.x.x". Note, in particular, that if you configure the
-"wins server" parameter to be the ip address of your samba server itself
-(as might one intuitively think), that you will run into difficulties.
-Do not use both parameters!
-
-
diff --git a/docs/textdocs/PROJECTS b/docs/textdocs/PROJECTS
deleted file mode 100644
index 07f82c74d94..00000000000
--- a/docs/textdocs/PROJECTS
+++ /dev/null
@@ -1,88 +0,0 @@
- Samba Projects Directory
- ========================
-
-
->>>>> NOTE: THIS FILE IS NOW VERY OUT OF DATE <<<<<
-
-
-This is a list of who's working on what in Samba. It's not guaranteed
-to be uptodate or accurate but I hope it will help us getting
-coordinated.
-
-If you are working on something to do with Samba and you aren't here
-then please let me know! Also, if you are listed below and you have
-any corrections or updates then please let me know.
-
-Email contact:
-samba-bugs@samba.anu.edu.au
-
-========================================================================
-Documentation and FAQ
-
-Docs and FAQ files for the Samba suite of software.
-
-Contact samba-bugs@samba.anu.edu.au with the diffs. These are urgently
-required.
-
-The FAQ is being added to on an ad hoc basis, see the web pages for info.
-
-Mark Preston was working on a set of formatted docs for Samba. Is this
-still happening? Contact mpreston@sghms.ac.uk
-
-Status last updated 2nd October 1996
-========================================================================
-
-========================================================================
-Netbeui support
-
-This aimed to produce patches so that Samba can be used with clients
-that do not have TCP/IP. It will try to remain as portable as possible.
-Contact Brian.Onn@Canada.Sun.COM (Brian Onn) Unfortunately it died, and
-although a lot of people have expressed interest nobody has come forward
-to do it. The Novell port (see Samba web pages) includes NetBEUI
-functionality in a proprietrary library which should still be helpful as
-we have the interfaces. Alan Cox (a.cox@li.org) has the information
-required to write the state machine if someone is going to do the work.
-
-Status last updated 2nd October 1996
-========================================================================
-
-========================================================================
-Smbfs
-
-A mountable smb filesystem for Linux using the userfs userspace filesystem
-
-Contact lendecke@namu01.gwdg.de (Volker Lendecke)
-
-This works really well, and is measurably more efficient than commercial
-client software. It is now part of the Linux kernel. Long filename support
-is in use.
-
-Status last updated June 1997
-========================================================================
-
-========================================================================
-Admin Tool
-
-Aims to produce a nice smb.conf editor and other useful tools for
-administering a Samba system.
-
-Contact: Steve Brown (steve@unicorn.dungeon.com)
-
-In the design phase.
-
-Status last updated 4th September 1994
-========================================================================
-
-
-========================================================================
-Lanman Client.
-
-Contact: john@amanda.xs4all.nl (John Stewart)
-
-Aims to produce a reliable LANMAN Client implementation for LINUX,
-and possibly other variations of UNIX. Project ably started by
-Tor Lillqvist; tml@hemuli.tte.vtt.fi
-
-Status last updated 17th January 1995
-========================================================================
diff --git a/docs/textdocs/Passwords.txt b/docs/textdocs/Passwords.txt
deleted file mode 100644
index 3d7acac9dd3..00000000000
--- a/docs/textdocs/Passwords.txt
+++ /dev/null
@@ -1,46 +0,0 @@
-Contributor: Unknown
-Date: Unknown
-Status: Current
-
-Subject: NOTE ABOUT PASSWORDS
-=============================================================================
-
-Unix systems use a wide variety of methods for checking the validity
-of a password. This is primarily controlled with the Makefile defines
-mentioned in the Makefile.
-
-Also note that some clients (notably WfWg) uppercase the password
-before sending it. The server tries the password as it receives it and
-also after lowercasing it.
-
-The Samba server can also be configured to try different
-upper/lowercase combinations. This is controlled by the [global]
-parameter "password level". A level of N means to try all combinations
-up to N uppercase characters in the password. A high value can chew a
-fair bit of CPU time and can lower the security of your system. Do not
-use this options unless you really need it - the time taken for
-password checking can become so high that clients time out.
-
-If you do use the "password level" option then you might like to use
--DUFC_CRYPT in your Makefile. On some machine this makes password
-checking _much_ faster. This is also useful if you use the @group
-syntax in the user= option.
-
-If your site uses AFS (the Andrew File System), you can use the AFS section
-in the Makefile. This will first attempt to authenticate a username and
-password to AFS. If that succeeds, then the associated AFS rights will be
-granted. Otherwise, the password checking routine falls back to whatever
-Unix password checking method you are using. Note that the AFS code is
-only written and tested for AFS 3.3 and later.
-
-
-SECURITY = SERVER
-=================
-
-Samba can use a remote server to do it's username/password
-validation. This allows you to have one central machine (for example a
-NT box) control the passwords for the Unix box.
-
-See the section on "security =" in smb.conf(5) for details.
-
-
diff --git a/docs/textdocs/Printing.txt b/docs/textdocs/Printing.txt
deleted file mode 100644
index e8a2d2ad27f..00000000000
--- a/docs/textdocs/Printing.txt
+++ /dev/null
@@ -1,93 +0,0 @@
-Contributor: Unknown
-Date: Unknown
-Status: Current
-
-Subject: Dubugging Printing Problems
-=============================================================================
-
-This is a short description of how to debug printing problems with
-Samba. This describes how to debug problems with printing from a SMB
-client to a Samba server, not the other way around. For the reverse
-see the examples/printing directory.
-
-Please send enhancements to this file to samba-bugs@samba.anu.edu.au
-
-Ok, so you want to print to a Samba server from your PC. The first
-thing you need to understand is that Samba does not actually do any
-printing itself, it just acts as a middleman between your PC client
-and your Unix printing subsystem. Samba receives the file from the PC
-then passes the file to a external "print command". What print command
-you use is up to you.
-
-The whole things is controlled using options in smb.conf. The most
-relevant options (which you should look up in the smb.conf man page)
-are:
- print command
- lpq command
- lprm command
-
-Samba should set reasonable defaults for these depending on your
-system type, but it isn't clairvoyant. It is not uncommon that you
-have to tweak these for local conditions.
-
-On my system I use the following settings:
-
- print command = lpr -r -P%p %s
- lpq command = lpq -P%p
- lprm command = lprm -P%p %j
-
-The % bits are "macros" that get dynamically replaced with variables
-when they are used. The %s gets replaced with the name of the spool
-file that Samba creates and the %p gets replaced with the name of the
-printer. The %j gets replaced with the "job number" which comes from
-the lpq output.
-
-When I'm debugging printing problems I often replace these command
-with pointers to shell scripts that record the arguments, and the
-contents of the print file. A simple example of this kind of things
-might be:
-
- print command = cp %s /tmp/tmp.print
-
-then you print a file and look at the /tmp/tmp.print file to see what
-is produced. Try printing this file with lpr. Does it work? If not
-then your problem with with your lpr system, not with Samba. Often
-people have problems with their /etc/printcap file or permissions on
-various print queues.
-
-Another common problem is that /dev/null is not world writeable. Yes,
-amazing as it may seem, some systems make /dev/null only writeable by
-root. Samba uses /dev/null as a place to discard output from external
-commands like the "print command" so if /dev/null is not writeable
-then nothing will work.
-
-Other really common problems:
-
-- lpr isn't in the search path when Samba tries to run it. Fix this by
-using the full path name in the "print command"
-
-- the user that the PC is trying to print as doesn't have permission
-to print. Fix your lpr system.
-
-- you get an extra blank page of output. Fix this in your lpr system,
-probably by editing /etc/printcap. It could also be caused by
-incorrect setting on your client. For example, under Win95 there is a
-option Printers|Printer Name|(Right
-Click)Properties|Postscript|Advanced| that allows you to choose if a
-Ctrl-D is appended to all jobs. This will affect if a blank page is
-output.
-
-- you get raw postscript instead of nice graphics on the output. Fix
-this either by using a "print command" that cleans up the file before
-sending it to lpr or by using the "postscript" option in smb.conf.
-
-Note that you can do some pretty magic things by using your
-imagination with the "print command" option and some shell
-scripts. Doing print accounting is easy by passing the %U option to a
-print command shell script. You could even make the print command
-detect the type of output and its size and send it to an appropriate
-printer.
-
-If the above debug tips don't help, then maybe you need to bring in
-the bug gun, system tracing. See Tracing.txt in this directory.
-
diff --git a/docs/textdocs/README.DCEDFS b/docs/textdocs/README.DCEDFS
deleted file mode 100644
index da9bb2197da..00000000000
--- a/docs/textdocs/README.DCEDFS
+++ /dev/null
@@ -1,78 +0,0 @@
-Contributor: Jim Doyle
-Date: 06-02-95
-Status: Current but needs updating
-
-Subject: Basic DCE/DFS Support for SAMBA 1.9.13
-=============================================================================
-
-Functionality:
---------------
-
- Per-instance authentication for DCE/DFS.
-
-Missing Functionality in this Implementation:
----------------------------------------------
-
- * No automatic refresh of credentials
-
- To do so would not be that hard.. One could simply
- stash the clear-text key in memory, spawn a key management
- thread to wake up right before credentials expire and
- refresh the login context.
-
- * No UNIX Signals support (SIGCLD, SIGPIPE, SIGHUP, SIGBUS, SIGSEGV)
-
-
- There is no support for signal processing in Samba daemons
- that need to authenticate with DCE. The explanation for this
- is that the smbd is linked against thread-safe libraries in
- order to be able to use DCE authentication mechanisms.
- Because smbd uses signal() and fork(), it represents the
- worst case scenario for DCE portability. In order
- to properly support signals in a forked server environment,
- some rework of smbd is needed in order to properly
- construct, shutdown and reconstruct asynchronous signal
- handling threads and synchronous signal traps across the
- parent and child. I have not had contiguous time to work
- on it, I expect it to be a weeks worth of work to cleanly
- integrate thread-safe signal handing into the code and
- test it. Until I can get to this task, I will leave it up
- to someone adventurous enough to engineer it and negotiate
- with Andrew to integrate the changes into the mainline branch.
-
- The lack of full signal support means that you cannot
- rely upon SIGHUP-ing the parent daemon to refresh
- the configuration data. Likewise, you cannot take advantage
- of the builtin SIGBUS/SIGSEGV traps to diagnose failures.
- You will have to halt Samba in order to make changes
- and then have them take effect.
-
- The SMBD server as it stands is suitable to use if you
- already have experience with configuring and running
- SAMBA.
-
-Tested Platforms:
------------------
-
- HP-UX 9.05 / HP-UX DCE 1.2.1
- AIX 3.2.5 / AIX DCE/6000 1.3
- DEC OSF-1 3.0 / DEC DCE 1.3
-
-Building:
----------
-
- - Uncomment the the appropriate block in the Makefile
- for the platform you wish to build on.
-
- - Samples of Samba server configuration files for our
- DFS environment are included in samples.dcedfs/
-
-
-
-Bugs, Suggestions, etc..
---------------------------
-
- Please post them to the mailing list.
- That way I will see them and they will become part of
- the archives so others can share the knowledge.
-
diff --git a/docs/textdocs/README.jis b/docs/textdocs/README.jis
deleted file mode 100644
index 50ff0cced74..00000000000
--- a/docs/textdocs/README.jis
+++ /dev/null
@@ -1,149 +0,0 @@
-$B!|(B samba $BF|K\8lBP1~$K$D$$$F(B
-
-1. $BL\E*(B
-
- $BF|K\8lBP1~$O!"(B
-
- (1) MS-Windows $B>e$G!"4A;z%U%!%$%kL>$r$I$&$7$F$b07$&I,MW$N$"$k%"%W%j%1!<%7%g%s$,$A$c(B
- $B$s$HF0:n$9$k!#Nc$($P!"(BMS-WORD 5 $B$J$I$O!"%$%s%9%H!<%k;~$K4A;z$N%U%!%$%kL>$r>!l9g$K$A$c$s$HBP1~$G$-$k$h$&$K$9$k!#(B
-
- (2) UNIX $B$O!":G6a$G$O$[$H$s$I$N$b$N$,(B 8 bits $B$N%U%!%$%kL>$r%5%]!<%H$7$F$$$^$9$,!"(B
- $BCf$K$O!"$3$l$r%5%]!<%H$7$F$$$J$$$b$N$b$"$j$^$9!#$3$N$h$&$J>l9g$G$b!"(B(1)$B$NL\E*(B
- $B$,K~B-$G$-$k$h$&$K$9$k!#(B
-
- $B$rL\E*$H$7$F$$$^$9!#$=$N$?$a!"F|K\8lBP1~$O!"I,MW:G>.8B$7$+9T$J$C$F$*$j$^$;$s!#(B
-
- $BF|K\8lBP1~$7$?(B samba $B$rMxMQ$9$k$?$a$K$O!"%3%s%Q%$%k$9$k;~$K!"I,$:!"(BKANJI $B$NDj5A$rDI(B
- $B2C$7$F$/$@$5$$!#$3$N%*%W%7%g%s$r;XDj$7$F$$$J$$>l9g$O!"F|K\8l$N%U%!%$%kL>$r@5$7$/07(B
- $B$&$3$H$O$G$-$^$;$s!#!J%3%s%Q%$%k$K$D$$$F$O!"2<5-(B 3. $B$r;2>H$7$F2<$5$$!K(B
-
-2. $BMxMQJ}K!(B
-
-(1) $BDI2C$7$?%Q%i%a!<%?(B
-
- smb.conf $B%U%!%$%k$N(B global $B%;%/%7%g%s$K0J2<$N%Q%i%a!<%?$r@_Dj$G$-$k$h$&$K$7$^$7$?!#(B
-
- [global]
- ....
- coding system = <$B%3!<%I7O(B>
-
- $B$3$3$G;XDj$5$l$?%3!<%I7O$,(B UNIX $B>e$N%U%!%$%k%7%9%F%`$N%U%!%$%kL>$N%3!<%I$K$J$j$^$9!#(B
- $B@_Dj$G$-$k$b$N$O!"A0$O!"(B':83:49:83:74:83:42:83:58' $B$N$h$&$K!"(B':' $B$N8e$K#27e(B
- $B$N(B16$B?J?t$rB3$1$k7A<0$K$J$j$^$9!#(B
- $B$3$3$G!"(B':' $B$rB>$NJ8;z$KJQ99$7$?$$>l9g$O!"(Bhex $B$N8e$m$K$=$NJ8;z$r;XDj$7$^$9!#(B
- $BNc$($P!"(B@$B$rJQ$o$j$K;H$$$?$$>l9g$O!"(B'hex@'$B$N$h$&$K;XDj$7$^$9!#(B
- cap: 7 bits $B$N(B ASCII $B%3!<%I0J30$N%3!<%I$r0J2<$N7A<0$GI=$9J}<0$H$$$&E@$G$O(B
- hex$B$HF1MM$G$9$,!"(BCAP (The Columbia AppleTalk Package)$B$H8_49@-$r;}$DJQ49(B
- $BJ}<0$H$J$C$F$$$^$9!#(Bhex$B$H$N0c$$$O(B0x80$B0J>e$N%3!<%I$N$_(B':80'$B$N$h$&$KJQ49(B
- $B$5$l!"$=$NB>$O(BASCII$B%3!<%I$G8=$5$l$^$9!#(B
- $BNc$($P!"(B'$B%*%U%#%9(B'$B$H$$$&L>A0$O!"(B':83I:83t:83B:83X'$B$H$J$j$^$9!#(B
-
- JIS $B%3!<%I$K$D$$$F$O!"0J2<$NI=$r;2>H$7$F2<$5$$!#(B
- $B(#(!(!(!(((!(!(!(!(((!(!(!(!(((!(!(!(!(((!(!(!(!(((!(!(!(!(((!(!(!(!(!(!(!(!(!($(B
- $B(";XDj(B $B("4A;z3+;O("4A;z=*N;("%+%J3+;O("%+%J=*N;("1Q?t3+;O("Hw9M(B $B("(B
- $B('(!(!(!(+(!(!(!(!(+(!(!(!(!(+(!(!(!(!(+(!(!(!(!(+(!(!(!(!(+(!(!(!(!(!(!(!(!(!()(B
- $B("(Bjis7 $B("(B\E$B $B("(B\E(J $B("(B0x0e $B("(B0x0f $B("(B\E(J $B("(Bjis 7$BC10LId9f(B $B("(B
- $B("(Bjunet $B("(B\E$B $B("(B\E(J $B("(B\E(I $B("(B\E(J $B("(B\E(J $B("(B7bits $B%3!<%I(B $B("(B
- $B("(Bjis8 $B("(B\E$B $B("(B\E(J $B("(B-- $B("(B-- $B("(B\E(J $B("(Bjis 8$BC10LId9f(B $B("(B
- $B("(Bj7bb $B("(B\E$B $B("(B\E(B $B("(B0x0e $B("(B0x0f $B("(B\E(B $B("(B $B("(B
- $B("(Bj7bj $B("(B\E$B $B("(B\E(J $B("(B0x0e $B("(B0x0f $B("(B\E(J $B("(Bjis7$B$HF1$8(B $B("(B
- $B("(Bj7bh $B("(B\E$B $B("(B\E(H $B("(B0x0e $B("(B0x0f $B("(B\E(H $B("(B $B("(B
- $B("(Bj7@b $B("(B\E$@ $B("(B\E(B $B("(B0x0e $B("(B0x0f $B("(B\E(B $B("(B $B("(B
- $B("(Bj7@j $B("(B\E$@ $B("(B\E(J $B("(B0x0e $B("(B0x0f $B("(B\E(J $B("(B $B("(B
- $B("(Bj7@h $B("(B\E$@ $B("(B\E(H $B("(B0x0e $B("(B0x0f $B("(B\E(H $B("(B $B("(B
- $B("(Bj8bb $B("(B\E$B $B("(B\E(B $B("(B-- $B("(B-- $B("(B\E(B $B("(B $B("(B
- $B("(Bj8bj $B("(B\E$B $B("(B\E(J $B("(B-- $B("(B-- $B("(B\E(J $B("(Bjis8$B$HF1$8(B $B("(B
- $B("(Bj8bh $B("(B\E$B $B("(B\E(H $B("(B-- $B("(B-- $B("(B\E(H $B("(B $B("(B
- $B("(Bj8@b $B("(B\E@@ $B("(B\E(B $B("(B-- $B("(B-- $B("(B\E(B $B("(B $B("(B
- $B("(Bj8@j $B("(B\E$@ $B("(B\E(J $B("(B-- $B("(B-- $B("(B\E(J $B("(B $B("(B
- $B("(Bj8@h $B("(B\E$@ $B("(B\E(H $B("(B-- $B("(B-- $B("(B\E(H $B("(B $B("(B
- $B("(Bjubb $B("(B\E$B $B("(B\E(B $B("(B\E(I $B("(B\E(B $B("(B\E(B $B("(B $B("(B
- $B("(Bjubj $B("(B\E$B $B("(B\E(J $B("(B\E(I $B("(B\E(J $B("(B\E(J $B("(Bjunet$B$HF1$8(B $B("(B
- $B("(Bjubh $B("(B\E$B $B("(B\E(H $B("(B\E(I $B("(B\E(H $B("(B\E(H $B("(B $B("(B
- $B("(Bju@b $B("(B\E$@ $B("(B\E(B $B("(B\E(I $B("(B\E(B $B("(B\E(B $B("(B $B("(B
- $B("(Bju@j $B("(B\E$@ $B("(B\E(J $B("(B\E(I $B("(B\E(J $B("(B\E(J $B("(B $B("(B
- $B("(Bju@h $B("(B\E$@ $B("(B\E(H $B("(B\E(I $B("(B\E(H $B("(B\E(H $B("(B $B("(B
- $B(&(!(!(!(*(!(!(!(!(*(!(!(!(!(*(!(!(!(!(*(!(!(!(!(*(!(!(!(!(*(!(!(!(!(!(!(!(!(!(%(B
-
- $B$$$:$l$N>l9g$b!"$9$G$KB8:_$7$F$$$kL>A0$KBP$7$F$O!"4A;z$N3+;O=*N;%7!<%1%s%9$O!"0J2<(B
- $B$N$b$N$rG'<1$7$^$9!#(B
- $B4A;z$N;O$^$j(B: \E$B $B$+(B \E$@
- $B4A;z$N=*$j(B: \E(J $B$+(B \E(B $B$+(B \E(H
-
-(2) smbclient $B$N%*%W%7%g%s(B
-
- $B%/%i%$%"%s%H%W%m%0%i%`$G$b!"4A;z$d2>L>$r4^$s$@%U%!%$%k$r07$($k$h$&$K!"
-
- $B$3$3$G!"(B<$B%?!<%_%J%k%3!<%I7O(B>$B$K;XDj$G$-$k$b$N$O!">e$N(B<$B%3!<%I7O(B>$B$HF1$8$b$N$G$9!#(B
-
-(3) $B%G%U%)%k%H(B
-
- $B%G%U%)%k%H$N%3!<%I7O$O!"%3%s%Q%$%k;~$K7h$^$j$^$9!#(B
-
-3. $B%3%s%Q%$%k;~$N@_Dj(B
-
- Makefile $B$K@_Dj$9$k9`L\$r0J2<$K<($7$^$9!#(B
-
-(1) KANJI $B%U%i%0(B
-
- $B%3%s%Q%$%k%*%W%7%g%s$K(B -DKANJI=\"$B%3!<%I7O(B\" $B$r;XDj$7$^$9!#$3$N%3!<%I7O$O(B 2. $B$G;X(B
- $BDj$9$k$b$N$HF1$8$G$9!#Nc$($P!"(B-DKANJI=\"euc\" $B$r(BFLAGSM $B$K@_Dj$9$k$H(B UNIX $B>e$N%U%!(B
- $B%$%kL>$O!"(BEUC $B%3!<%I$K$J$j$^$9!#$3$3$G;XDj$7$?%3!<%I7O$O!"%5!<%P5Z$S%/%i%$%"%s%H(B
- $B%W%m%0%i%`$N%G%U%)%k%H$KCM$J$j$^$9!#(B
-
- $B>0!"%*%W%7%g%sCf$N(B \ $B$d(B " $B$bK:$l$:$K;XDj$7$F2<$5$$!#(B
-
-3. $B@)8B;v9`(B
-
-(1) $B4A;z%3!<%I(B
- smbd $B$rF0:n$5$;$k%[%9%H$N(B UNIX $B$,%5%]!<%H$7$F$$$J$$4A;z%3!<%I$O!"MxMQ$G$-$J$$$3$H$,(B
- $B$"$j$^$9!#JQ$JF0:n$r$9$k$h$&$J$i(B hex $B$N;XDj$r$9$k$N$,NI$$$G$7$g$&!#(B
-
-(2) smbclient $B%3%^%s%I(B
- $B%7%U%H%3!<%I$J$I$N4X78$G!"4A;z$d2>L>$r4^$s$@%U%!%$%kL>$N(B ls $B$NI=<($,Mp$l$k$3$H$,$"$j(B
- $B$^$9!#(B
-
-(3) $B%o%$%k%I%+!<%I$K$D$$$F(B
- $B$A$c$s$H$7$?%9%Z%C%/$,$h$/$o$+$i$J$+$C$?$N$G$9$,!"0l1~!"(BDOS/V $B$NF0:n$HF1$8F0:n$r9T$J(B
- $B$&$h$&$K$J$C$F$$$^$9!#(B
-
-(4) $B%m%s%0%U%!%$%kL>$K$D$$$F(B
- Windows NT/95 $B$G$O!"%m%s%0%U%!%$%kL>$,07$($^$9!#%m%s%0%U%!%$%kL>$r(B 8.3 $B%U%)!<%^%C%H(B
- $B$G07$&$?$a$K!"(Bmangling $B$7$F$$$^$9$,!"$3$NJ}K!$O!"(BNT $B$d(B 95 $B$,9T$J$C$F$$$k(B mangling $B$H(B
- $B$O0[$J$j$^$9$N$GCm0U$7$F2<$5$$!#(B
-
-4. $B>c32Ey$N%l%]!<%H$K$D$$$F(B
-
- $BF|K\8l$N%U%!%$%kL>$K4X$7$F!"J8;z2=$1Ey$N>c32$,$"$l$P!";d$K%l%]!<%H$7$FD:$1$l$P9,$$$G(B
-$B$9!#$?$@$7!"%*%j%8%J%k$+$i$NLdBjE@$d@\Ld$$9g$o$;$k(B
-$B$+!"$b$7$/$O%a!<%j%s%0%j%9%H$J$I$X%l%]!<%H$9$k$h$&$K$7$F2<$5$$!#(B
-
-$B%l%]!<%H$5$l$k>l9g!"MxMQ$5$l$F$$$k4D6-(B(UNIX $B5Z$S(B PC $BB&$N(BOS$B$J$I(B)$B$H$G$-$^$7$?$i@_Dj%U%!(B
-$B%$%k$d%m%0$J$I$rE:IU$7$FD:$1$k$H9,$$$G$9!#(B
-
-5. $B$=$NB>(B
-
- $B%3!<%IJQ49$O0J2<$NJ}!9$,:n$i$l$?%W%m%0%i%`$rMxMQ$7$F$$$^$9!#(B
-
- hex $B7A<0(B $BBgLZ!wBgDM!&C^GH(B $B;a(B
- cap $B7A<0(B $BI%ED(B $BF;O:(B (michiro@po.iijnet.or.jp)(michiro@dms.toppan.co.jp)$B;a(B
-
- $B$=$NB>!"$?$/$5$s$NJ}!9$+$i$$$m$$$m$H8f65<($$$?$@$-$"$j$,$H$&$4$6$$$^$7$?!#:#8e$H$b$h(B
-$B$m$7$/$*4j$$CW$7$^$9!#(B
-
-1994$BG/(B10$B7n(B28$BF|(B $BBh#1HG(B
-1995$BG/(B 8$B7n(B16$BF|(B $BBh#2HG(B
-1995$BG/(B11$B7n(B24$BF|(B $BBh#3HG(B
-1996$BG/(B 5$B7n(B13$BF|(B $BBh#4HG(B
-
-$BF#ED(B $B?r(B fujita@ainix.isac.co.jp
-
diff --git a/docs/textdocs/README.sambatar b/docs/textdocs/README.sambatar
deleted file mode 100644
index af7250c2a49..00000000000
--- a/docs/textdocs/README.sambatar
+++ /dev/null
@@ -1,23 +0,0 @@
-Contributor/s: Martin.Kraemer
- and Ricky Poulten (ricky@logcam.co.uk)
-Date: Unknown - circa 1994
-Status: Obsoleted - smbtar has been a stable part of Samba
- since samba-1.9.13
-
-Subject: Sambatar (now smbtar)
-=============================================================================
-
-This is version 1.4 of my small extension to samba that allows PC shares
-to be backed up directly to a UNIX tape. It only has been tested under
-Solaris 2.3, Linux 1.1.59 and DG/UX 5.4r3.10 with version 1.9.13 of samba.
-
-See the file INSTALL for installation instructions, and
-the man page and NOTES file for some basic usage. Please let me know if you
-have any problems getting it to work under your flavour of Unix.
-
-This is only (yet another) intermediate version of sambatar.
-This version also comes with an extra gift, zen.bas, written in
-microsoft qbasic by a colleague. It is (apparently) based on a 70s
-British sci-fi series known as Blake's 7. If you have any questions
-about this program, or any suggestions (e.g. what about servillan.bas
-?), feel free to mail the author (of zen.bas) greenm@lilhd.logica.com.
diff --git a/docs/textdocs/SCO.txt b/docs/textdocs/SCO.txt
deleted file mode 100644
index 7c01aa57c6c..00000000000
--- a/docs/textdocs/SCO.txt
+++ /dev/null
@@ -1,19 +0,0 @@
-Contributor: Geza Makay
-Date: Unknown
-Status: Obsolete - Dates to SCO Unix v3.2.4 approx.
-
-Subject: TCP/IP Bug in SCO Unix
-============================================================================
-
-There is an annoying TCPIP bug in SCO Unix. This causes corruption when
-transferring files with Samba.
-
-Geza Makay (makayg@math.u-szeged.hu) sends this information:
-
-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).
-
-You do not need anything else but the above patch. It installs in seconds,
-and corrected the Excel problem. We also had some other minor problems (not
-only with Samba) that disappeared by installing this patch.
-
diff --git a/docs/textdocs/SMBTAR.notes b/docs/textdocs/SMBTAR.notes
deleted file mode 100644
index 679d776f56c..00000000000
--- a/docs/textdocs/SMBTAR.notes
+++ /dev/null
@@ -1,46 +0,0 @@
-Contributor: Unknown
-Date: 1994
-Status: Mostly Current - refer man page
-
-Subject: Smbtar
-============================================================================
-
-Intro
------
-
-sambatar is just a small extension to the smbclient program distributed with
-samba. A basic front end shell script, smbtar, is provided as an interface
-to the smbclient extensions.
-
-Extensions
-----------
-
-This release adds the following extensions to smbclient,
-
-tar [c|x] filename
- creates or restores from a tar file. The tar file may be a tape
-or a unix tar file. tar's behaviour is modified with the newer and tarmode
-commands.
-
-tarmode [full|inc|reset|noreset]
- With no arguments, tarmode prints the current tar mode (by default full,
-noreset). In full mode, every file is backed up during a tar command.
-In incremental, only files with the dos archive bit set are backed up.
-The archive bit is reset if in reset mode, or left untouched if in noreset.
-In reset mode, the share has to be writable, which makes sambatar even
-less secure. An alternative might be to use tarmode inc noreset which
-would implement an "expanding incremental" backup (which some may prefer
-anyway).
-
-setmode filename
- This is a "freebie" - nothing really to do with sambatar. This
-is a crude attrib like command (only the other way around). Setmode string
-is a combination of +-rhsa. So for example -rh would reset the read only
-bit on filename.
-
-newer filename
- This is in fact part of the 1.9.13 samba distribution, but comes
-into its own with sambatar. This causes tar (or get, mget, etc) to
-only copy files newer than the specified file name. Could be used
-against the previous nights (or whatever) log file to implement incremental
-backups.
diff --git a/docs/textdocs/Speed.txt b/docs/textdocs/Speed.txt
deleted file mode 100644
index b11885fc377..00000000000
--- a/docs/textdocs/Speed.txt
+++ /dev/null
@@ -1,318 +0,0 @@
-Contributor: Andrew Tridgell
-Date: January 1995
-Status: Current
-
-Subject: Samba performance issues
-============================================================================
-
-This file tries to outline the ways to improve the speed of a Samba server.
-
-COMPARISONS
------------
-
-The Samba server uses TCP to talk to the client. Thus if you are
-trying to see if it performs well you should really compare it to
-programs that use the same protocol. The most readily available
-programs for file transfer that use TCP are ftp or another TCP based
-SMB server.
-
-If you want to test against something like a NT or WfWg server then
-you will have to disable all but TCP on either the client or
-server. Otherwise you may well be using a totally different protocol
-(such as Netbeui) and comparisons may not be valid.
-
-Generally you should find that Samba performs similarly to ftp at raw
-transfer speed. It should perform quite a bit faster than NFS,
-although this very much depends on your system.
-
-Several people have done comparisons between Samba and Novell, NFS or
-WinNT. In some cases Samba performed the best, in others the worst. I
-suspect the biggest factor is not Samba vs some other system but the
-hardware and drivers used on the various systems. Given similar
-hardware Samba should certainly be competitive in speed with other
-systems.
-
-
-OPLOCKS
--------
-
-Oplocks are the way that SMB clients get permission from a server to
-locally cache file operations. If a server grants an oplock
-(opportunistic lock) then the client is free to assume that it is the
-only one accessing the file and it will agressively cache file
-data. With some oplock types the client may even cache file open/close
-operations. This can give enormous performance benefits.
-
-Samba does not support opportunistic locks because they are very
-difficult to do under Unix. Samba can fake them, however, by granting
-a oplock whenever a client asks for one. This is controlled using the
-smb.conf option "fake oplocks". If you set "fake oplocks = yes" then
-you are telling the client that it may agressively cache the file
-data.
-
-By enabling this option on all read-only shares or shares that you know
-will only be accessed from one client at a time you will see a big
-performance improvement on many operations. If you enable this option
-on shares where multiple clients may be accessing the files read-write
-at the same time you can get data corruption. Use this option
-carefully!
-
-This option is disabled by default.
-
-SOCKET OPTIONS
---------------
-
-There are a number of socket options that can greatly affect the
-performance of a TCP based server like Samba.
-
-The socket options that Samba uses are settable both on the command
-line with the -O option, or in the smb.conf file.
-
-The "socket options" section of the smb.conf manual page describes how
-to set these and gives recommendations.
-
-Getting the socket options right can make a big difference to your
-performance, but getting them wrong can degrade it by just as
-much. The correct settings are very dependent on your local network.
-
-The socket option TCP_NODELAY is the one that seems to make the
-biggest single difference for most networks. Many people report that
-adding "socket options = TCP_NODELAY" doubles the read performance of
-a Samba drive. The best explanation I have seen for this is that the
-Microsoft TCP/IP stack is slow in sending tcp ACKs.
-
-
-READ SIZE
----------
-
-The option "read size" affects the overlap of disk reads/writes with
-network reads/writes. If the amount of data being transferred in
-several of the SMB commands (currently SMBwrite, SMBwriteX and
-SMBreadbraw) is larger than this value then the server begins writing
-the data before it has received the whole packet from the network, or
-in the case of SMBreadbraw, it begins writing to the network before
-all the data has been read from disk.
-
-This overlapping works best when the speeds of disk and network access
-are similar, having very little effect when the speed of one is much
-greater than the other.
-
-The default value is 16384, but very little experimentation has been
-done yet to determine the optimal value, and it is likely that the best
-value will vary greatly between systems anyway. A value over 65536 is
-pointless and will cause you to allocate memory unnecessarily.
-
-
-MAX XMIT
---------
-
-At startup the client and server negotiate a "maximum transmit" size,
-which limits the size of nearly all SMB commands. You can set the
-maximum size that Samba will negotiate using the "max xmit = " option
-in smb.conf. Note that this is the maximum size of SMB request that
-Samba will accept, but not the maximum size that the *client* will accept.
-The client maximum receive size is sent to Samba by the client and Samba
-honours this limit.
-
-It defaults to 65536 bytes (the maximum), but it is possible that some
-clients may perform better with a smaller transmit unit. Trying values
-of less than 2048 is likely to cause severe problems.
-
-In most cases the default is the best option.
-
-
-LOCKING
--------
-
-By default Samba does not implement strict locking on each read/write
-call (although it did in previous versions). If you enable strict
-locking (using "strict locking = yes") then you may find that you
-suffer a severe performance hit on some systems.
-
-The performance hit will probably be greater on NFS mounted
-filesystems, but could be quite high even on local disks.
-
-
-SHARE MODES
------------
-
-Some people find that opening files is very slow. This is often
-because of the "share modes" code needed to fully implement the dos
-share modes stuff. You can disable this code using "share modes =
-no". This will gain you a lot in opening and closing files but will
-mean that (in some cases) the system won't force a second user of a
-file to open the file read-only if the first has it open
-read-write. For many applications that do their own locking this
-doesn't matter, but for some it may. Most Windows applications
-depend heavily on "share modes" working correctly and it is
-recommended that the Samba share mode support be left at the
-default of "on".
-
-The share mode code in Samba has been re-written in the 1.9.17
-release following tests with the Ziff-Davis NetBench PC Benchmarking
-tool. It is now believed that Samba 1.9.17 implements share modes
-similarly to Windows NT.
-
-NOTE: In the most recent versions of Samba there is an option to use
-shared memory via mmap() to implement the share modes. This makes
-things much faster. See the Makefile for how to enable this.
-
-
-LOG LEVEL
----------
-
-If you set the log level (also known as "debug level") higher than 2
-then you may suffer a large drop in performance. This is because the
-server flushes the log file after each operation, which can be very
-expensive.
-
-
-WIDE LINKS
-----------
-
-The "wide links" option is now enabled by default, but if you disable
-it (for better security) then you may suffer a performance hit in
-resolving filenames. The performance loss is lessened if you have
-"getwd cache = yes", which is now the default.
-
-
-READ RAW
---------
-
-The "read raw" operation is designed to be an optimised, low-latency
-file read operation. A server may choose to not support it,
-however. and Samba makes support for "read raw" optional, with it
-being enabled by default.
-
-In some cases clients don't handle "read raw" very well and actually
-get lower performance using it than they get using the conventional
-read operations.
-
-So you might like to try "read raw = no" and see what happens on your
-network. It might lower, raise or not affect your performance. Only
-testing can really tell.
-
-
-WRITE RAW
----------
-
-The "write raw" operation is designed to be an optimised, low-latency
-file write operation. A server may choose to not support it,
-however. and Samba makes support for "write raw" optional, with it
-being enabled by default.
-
-Some machines may find "write raw" slower than normal write, in which
-case you may wish to change this option.
-
-READ PREDICTION
----------------
-
-Samba can do read prediction on some of the SMB commands. Read
-prediction means that Samba reads some extra data on the last file it
-read while waiting for the next SMB command to arrive. It can then
-respond more quickly when the next read request arrives.
-
-This is disabled by default. You can enable it by using "read
-prediction = yes".
-
-Note that read prediction is only used on files that were opened read
-only.
-
-Read prediction should particularly help for those silly clients (such
-as "Write" under NT) which do lots of very small reads on a file.
-
-Samba will not read ahead more data than the amount specified in the
-"read size" option. It always reads ahead on 1k block boundaries.
-
-
-MEMORY MAPPING
---------------
-
-Samba supports reading files via memory mapping them. One some
-machines this can give a large boost to performance, on others it
-makes not difference at all, and on some it may reduce performance.
-
-To enable you you have to recompile Samba with the -DUSE_MMAP option
-on the FLAGS line of the Makefile.
-
-Note that memory mapping is only used on files opened read only, and
-is not used by the "read raw" operation. Thus you may find memory
-mapping is more effective if you disable "read raw" using "read raw =
-no".
-
-
-SLOW CLIENTS
-------------
-
-One person has reported that setting the protocol to COREPLUS rather
-than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).
-
-I suspect that his PC's (386sx16 based) were asking for more data than
-they could chew. I suspect a similar speed could be had by setting
-"read raw = no" and "max xmit = 2048", instead of changing the
-protocol. Lowering the "read size" might also help.
-
-
-SLOW LOGINS
------------
-
-Slow logins are almost always due to the password checking time. Using
-the lowest practical "password level" will improve things a lot. You
-could also enable the "UFC crypt" option in the Makefile.
-
-CLIENT TUNING
--------------
-
-Often a speed problem can be traced to the client. The client (for
-example Windows for Workgroups) can often be tuned for better TCP
-performance.
-
-See your client docs for details. In particular, I have heard rumours
-that the WfWg options TCPWINDOWSIZE and TCPSEGMENTSIZE can have a
-large impact on performance.
-
-Also note that some people have found that setting DefaultRcvWindow in
-the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a
-big improvement. I don't know why.
-
-My own experience wth DefaultRcvWindow is that I get much better
-performance with a large value (16384 or larger). Other people have
-reported that anything over 3072 slows things down enourmously. One
-person even reported a speed drop of a factor of 30 when he went from
-3072 to 8192. I don't know why.
-
-It probably depends a lot on your hardware, and the type of unix box
-you have at the other end of the link.
-
-
-MY RESULTS
-----------
-
-Some people want to see real numbers in a document like this, so here
-they are. I have a 486sx33 client running WfWg 3.11 with the 3.11b
-tcp/ip stack. It has a slow IDE drive and 20Mb of ram. It has a SMC
-Elite-16 ISA bus ethernet card. The only WfWg tuning I've done is to
-set DefaultRcvWindow in the [MSTCP] section of system.ini to 16384. My
-server is a 486dx3-66 running Linux. It also has 20Mb of ram and a SMC
-Elite-16 card. You can see my server config in the examples/tridge/
-subdirectory of the distribution.
-
-I get 490k/s on reading a 8Mb file with copy.
-I get 441k/s writing the same file to the samba server.
-
-Of course, there's a lot more to benchmarks than 2 raw throughput
-figures, but it gives you a ballpark figure.
-
-I've also tested Win95 and WinNT, and found WinNT gave me the best
-speed as a samba client. The fastest client of all (for me) is
-smbclient running on another linux box. Maybe I'll add those results
-here someday ...
-
-
-COMMENTS
---------
-
-If you've read this far then please give me some feedback! Which of
-the above suggestions worked for you?
-
-Mail the samba mailing list or samba-bugs@samba.anu.edu.au
diff --git a/docs/textdocs/Support.txt b/docs/textdocs/Support.txt
deleted file mode 100644
index 3c7430d1736..00000000000
--- a/docs/textdocs/Support.txt
+++ /dev/null
@@ -1,1388 +0,0 @@
-The Samba Consultants List
-==========================
-
-This is a list of people who are prepared to commercialy support
-Samba. Being on this list does not imply any sort of endorsement by
-anyone, it is just provided in the hope that it will be useful.
-
-Note that the organisations listed below will expect you to pay for
-The support that they offer. We have been told that several people
-assumed this was a list of kindly companies offering free commercial
-support!
-
-For free support use the Samba mailing list and the comp.protocols.smb
-newsgroup.
-
-If you want to be added to the list, or want your entry modified then
-contact the address below. Please make sure to include a header line
-giving the region and country, eg CANBERRA - AUSTRALIA.
-
-You can contact the maintainers at samba-bugs@samba.anu.edu.au
-
-The support list has now been re-arranged into geographical areas
-and are sorted by state/region/town within these areas.
-These are currently:
-
-Region Number of entries
-----------------------------------------------------
- AFRICA 2
- AMERICA - CENTRAL & SOUTH 3
- AMERICA - USA 22
- ASIA 1
- AUSTRALIA & NEW ZEALAND 18
- CANADA 6
- EUROPE 28
-
-
-AFRICA
-======
-
-------------------------------------------------------------------------------
-GAUTENG - SOUTH AFRICA
-
-Company: Obsidian Systems
-Street Addr: Boskruin Office Park Unit 3, Bosbok street, Randpark Ridge
- Gauteng, 2156, South Africa.
-Postal Addr: PO Box 4938, Cresta, South Africa, 2118
-Contact no's: +2711 792-6500/38, Fax: +2711-792-6522
- Cell: +2783-379-6889/90/91 or +2783-377-4946 or +27832660199
-
-Our level of experience: Low level programming and support for all samba
-security and compatability issues. We use Samba in South African Schools
-and commercial companies as an affordable solution for LAN and WAN
-networking.
-
-For futher information, please consult our website www.obsidian.co.za
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-JOHANNESBURG - SOUTH AFRICA
-
- Company: Symphony Research (Pty) Ltd
- Contact: Dr Evan Summers, , cell 082 900-8632.
-keywords: Samba on Linux, support and consulting
- Johannesburg (South Africa)
-
-Evan Summers, PhD Tel +27 82 900-8632 Symphony
-Linux systems integration http://sr.co.za Research
-Johannesburg, South Africa mailto:evan@sr.co.za (Pty)Ltd
-------------------------------------------------------------------------------
-
-
-
-
-
-
-
-AMERICA - CENTRAL & SOUTH
-=========================
-
-
-------------------------------------------------------------------------------
-CHILE - SOUTH AMERICA
-
-Company: Magic Consulting Group/Magic Dealer
-Street Addr: Alberto Reyes #035 Barrio Bellavista
- Providencia Santiago
-Contact no's: +56 2 365 19 18, Fax: +56 2 365 14 55
-
-Contact Person: Marcelo Bartsch or Roy Zderich
-
-
-Our level of experience: support for all Samba and Linux security and
-compatability issues. We use Samba in our local network and we have
-experience instaling it on some other locations. we also provide
-techincal support for Linux, Novell, Windows NT, OS/2 and other
-Operating Systems.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-HONDURAS - CENTRAL AMERICA
-
-Open Systems, S.A.
-
-Open Systems, S.A. provides support to SAMBA in SCO UnixWare 2.X:
-
-Server Platform: SCO UnixWare 2.X
-Client Platform: Windows NT, Windows 95, WFW (3.11), DOS.
-
-Open Systems, S.A. also provides consulting services and technical
-support in the following server platforms since 1987:
-
-SCO Open Server 3.0 and 5.0
-SCO UnixWare 2.X (SVR4.2MP)
-UNIX SVR4 (NCR, UNISYS)
-
-Contact:
-Selim Jose Miselem
-Open Systems, S.A.
-Centro Comercial Dallas
-San Pedro Sula, Honduras, Central America
-Tel/Fax 011 (504) 529868
-e-mail: selim@opensys.hn
-URL: http://www.opensys.hn
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-VILLAHERMOSA, TAB. - MEXICO
-
-Carlos Enrique García Díaz
-E-mail: cgarcia@tnet.net.mx
-Phone: (93) 12-33-91
-
-Samba experience:
-Server: Samba 1.9.15 and above with Solaris (Sparc & x86), SG Irix 5.2 - 6.3,
-AIX 3.2, DEC OSF1 v4.0, DG/UX v4.11, SunOS.
-Client: WinNT, Win95, WfWg, Win 3.1 & LAN WorkPlace.
-------------------------------------------------------------------------------
-
-
-
-
-
-
-
-AMERICA - USA
-=============
-
-------------------------------------------------------------------------------
-BAY AREA, SILICON VALLEY CALIFORNIA - USA
-
-Adital Corp.
-
-7291 Coronado Dr. ,Suite 4 San-Jose Ca 95129
-
-Phone : (408) 257-7717 Fax : (408) 257-7772 E-Mail: ephi@adital.com
-
-Contact: Ephi Dror, Director of software development.
-
-Adital is a company that specialized in networking products development.
-We have been doing many development projects on Windows (NT/95), Macintosh,
-UNIX and embedded system platforms in the area of networking drivers and
-applications during the last few years. In regards to SAMBA, we have a lot
-of experience in SMB/CIFS protocol development.
-
-We have special expertise in porting SAMBA to embedded system environments for
-NT/WIN95/WFW client/server connectivity.
-
-We can help you defining and specifying your product as well as designing,
-implementing, testing, upgrading and maintaining it.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-SAN FRANCISCO BAY AREA - USA
-
-Alex Davis --- President of FTL
-Faster Than Light, 2570 Ocean Ave. #114, San Francisco, California, 94132
-HTTP://www.ftl.net/ EMAIL:davis@ftl.net TEL:415.334.2922 FAX:415.337.6135
-
-We are located in the "Bay Area" of California, USA. We provide
-consultant and training for Unix, Windows, Macintosh applications,
-and hardware. We also provide Internet access to many of the local
-companies as a part of our "one-stop-shop" model.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-SAN FRANCISCO BAY AREA - USA
-
-2125 Hamilton Ave. Suite 100
-San Jose, CA 95125
-888-ACCLAIM [Inside California]
-(408) 879 - 3100
-(408) 377-4900 [Fax]
-
-We can provide commercial support for Samba. We have created additional
-scripts that we can add to the Samba distribution to create an installation in
-Sun Solaris "package add" format. We are a Sun Reseller, but we can also
-support Samba on HP, SGI, Linux, in addition to Sun Solaris Sparc/X86.
-
-To find out more about our company, look at our website:
- http://www.acclaim.com
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-CALIFORNIA - USA
-
-Cliff Skolnick
-Steam Tunnel Operations
-900 Tennessee St, suite 22
-San Francisco, CA 94107
-http://www.steam.com/
-(415) 920-3800
-cliff@steam.com
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-CALIFORNIA - USA
-
-Craftwork Solutions Inc.
-
-Craftwork Solutions Inc. is dedicated to providing the best possible
-services to our customers. The Craftworks team will provide you with a
-total solution package that will work for you both today and tomorrow.
-With our own Linux Distribution which we are constantly improving to make
-it the best and using it to provide total solutions for companies which
-are open to using Linux.
-
-Please contact mary@craftwork.com
-------------------------------------------------------------------------------
-
------------------------------------------------------------------------
-SOUTHERN CALIFORNIA - USA
-
-Michael St. Laurent
-Serving Los Angeles and Orange Counties. Please contact via email.
-rowl@earthlink.net
-Michael St. Laurent
-Hartwell Corporation
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-SOUTHERN CALIFORNIA - USA
-
-Yuri Diomin
-Yuri Software
-13791 Ruette Le Parc, Ste. C
-Del Mar, CA 92014
-Phone: 619-350-8541
-Fax: 619-350-7641
-yuri@yurisw.com
-http://www.yurisw.com
-
-We have been supporting Samba in commercial installations for several years
-on a variety of client and server platforms. We have extensive experience
-in all aspects of UNIX-Windows connectivity solutions for mixed platform
-corporate setups. We are a contributor to Samba source code.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-FORT COLLINS, CO - USA
-
-Granite Computing Solutions
-ATTN: Brian Grossman
-P.O. Box 270103
-Fort Collins, CO 80527-0103
-U.S.A.
-Tel: +1 (970) 225-2370
-Email: granite@SoftHome.Net WWW: http://www.SoftHome.Net/granite/
-
-Information services, including WfWG, NT, Apple <=> Unix interoperability.
-WWW solutions. WWW education. Unix education. Custom software
-development - eg. http://www.SoftHome.Net/modsim/.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-FLORIDA - USA
-
-Swaney & Associates, Inc.
-ATTN: Stephen Swaney
- 2543 Lincoln Avenue
- Miami, Florida 33133
- U.S.A
- (305) 860-0570
-
-Specializing in:
- High Availability system & networks
- UNIX to PC connectivity
- Market Data systems
- Messaging Systems (Sendmail & Microsoft Exchange)
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-FLORIDA - USA
-
-Progressive Computer Concepts, Inc.
-1371 Cassat Avenue
-Jacksonville, FL 32205
-info@progressive-comp.com
-800-580-2640 - 904-389-3236 - 904-389-6584 fax
-
-Related Products and Services:
- ncLinux (Network Computer) consulting, installations, and turnkey
- networks. Multi-user NT and Samba consulting, installation and
- administration (both remote and onsite), Internet and Intranet
- connectivity, LAN and WAN, firewall installation, security,
- troubleshooting and training, custom LAN/WAN/Intranet business
- systems development, WWW/CGI development (e.g. database gateways,
- catalogs).
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-GEORGIA - USA
-
-Hoppe Computer Services
-2171 Brooks Road
-Dacula(Atlanta), Georgia 30019
-770-995-5099 fax 770-338-3885
-
-Supporting the Atlanta, Georgia USA area for two and a half years.
-In the computer field for 22 years.
-
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-OWA - USA
-
-Afan Ottenheimer
-JEONET
-PO Box 1282
-Iowa City, IA 52244
-Phone: 319-338-6353
-Fax: 319-338-6353
-Email: afan@jeonet.com
-WWW: http://www.jeonet.com/jeonet/
-
-Specializing in systems integration, database, and advanced web
-site design since 1995. Have extensive experience in
-Linux<->NT<->Windows 3.11<->Windows 95 interaction using SAMBA.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-ILLONOIS - USA
-
-Information One, Inc.
-736 Hinman Ave, Suite 2W
-Evanston, IL 60202
-708-328-9137 708-328-0117 FAX
-info@info1.com
-
-Providing custom Internet and networking solutions.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-KANSAS - USA
-
-NT Integrators
-2400 W. 31st Street
-Lawrence, KS 66046
-USA
-913-842-1100
-http://www.ntintegrators.com/
-email: watts@sunflower.com
-
-My consulting company does NT/Linux/Samba/etc support.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-LAS VEGAS, NEVADA - USA
-
-DPN, Inc. Las Vegas NV
-
-(702) 873-3282 Ph.
-(702) 873-3913 Fax
-Email duane@dpn.com
-
-Can provide commercial support for samba running on any version of
-SCO above 3.0 and for Linux. We currently have installed and are
-supporting several versions of samba on over 25 client sites across
-the US, in addition to our 6 in-house samba servers. Our largest client
-site has approx. 100 users.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-NEW JERSEY - USA
-
-William J. Maggio
-LAN & Computer Integrators, Inc.
-242 Old New Brunswick Road Email: bmaggio@lci.com
-Suite 440 Voice: 908-981-1991
-Piscataway, NJ 08855 Fax : 908-981-1858
-
- Specializing in Internet connectivity and security, Sun integration and
- high speed, enterprise network design and deployment.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-NEW YORK - USA
-
-67.2 Psytronics Solutions
-
- 90 County Line Road
- Massapequa, NY 11758
- U.S.A.
-
-Phone: +1 516 598 4619
-
-Fax: +1 516 598 4619
-
-EMail: info@psytronics.com
-
-URL: http://www.psytronics.com
-
-Contact: Jaron Rubenstein
-
-Type of support: Whatever is required. Support contracts available.
-
-Special expertise:
-
- Familiar with most topics. Specializing in dial-up server (PPP)
-installation and configuration, custom programming, and Internet and
-Intranet server configuration. Authorized Red Hat Reseller.
-
-Sample prices:
-
- Upon request, usually US$50-$100/hour. Educational discounts
-available.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-TEXAS - USA
-
-Jody Winston
-xprt Computer Consulting, Inc.
-731 Voyager
-Houston, TX 77062
-(281) 480 8649, jody@sccsi.com
-
-We have been supporting software from the Free Software Foundation and
-other groups such as Linux for over 8 years. The base rate is 150.00
-US dollars per hour. Please contact us for more information on our
-rates and services.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-UNITED STATES
-
-Stelias Computing is the developer of the InfoMagic Workgroup Server, a
-Linux distribution customized for use as a PC and Macintosh file and
-print server (using Samba and netatalk respectively). Stelias also
-offers custom system programming and Samba support contracts.
-
-For information about the InfoMagic Workgroup Server contact InfoMagic:
- http://www.infomagic.com/
- questions@infomagic.com
- voice: 800-800-6613 or 520-526-9565
- fax: 520-526-9573
-
-To contact Stelias about custom arrangments, send email to
-info@stelias.com.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-WASHINGTON DC METRO - USA
-
-Asset Software, Inc. has been running Samba since the 1.6 release on various
-platforms, including SunOS 4.x, Solaris 2.x, IRIX 4.x and 5.x, Linux 1.1x,
-1.2x, and 1.3x, and BSD UNIX 4.3 and above. We specialize in small office
-network solutions and provide services to enhance a small office's
-operations. Primarily a custom software operation, our vast knowledge of
-Windows, DOS, Unix, Windows NT, MacOS, and OS/2 enable us to provide quality
-technical assistance to the small office environment at a reasonable price.
-Our upcoming multi-mailbox mail client, IQ Mail, enables users with more
-than one mailbox to send and retrieve their mail from a single, consistent
-mail client running in Windows.
-
-David J. Fenwick Asset Software, Inc.
-President djf@assetsw.com
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-WASHINGTON STATE - USA
-
-Brian Meyer
-Personal Data Services
-9792 Edmonds Way Suite 121
-Seattle, Washington 98020 USA
-Voice: (206) 365-8212
-E-mail: admin@pdsnorth.com
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-WASHINGTON - USA
-
-Olympic Peninsula Consulting; 1241 Lansing Ave W., Bremerton, WA 98312-4343
-telephone 1+ 360 792 6938; mailto:opc@aa.net; http://www.aa.net/~opc;
-Unix Systems and TCP/IP Network design, programming, and administration.
-------------------------------------------------------------------------------
-
-
-
-
-
-
-ASIA
-====
-
-------------------------------------------------------------------------------
-SEOUL - KOREA
-
-MultiMedia KOREA Inc, E-Mail : info@seoul.korea.co.kr
-Internet,WWW,Network Support Group, TEL : +82-02-597-1631
- FAX : +82-02-521-4463
-SeoChoGu SeoChoDong 1537-6 WWW : http://www.korea.co.kr
-JungAng B/D #401
-SEOUL KOREA
-
-SAMBA Experience : SunOS, Solaris, Linux, SCO-Unix, Win95/NT/3.1
-------------------------------------------------------------------------------
-
-
-
-
-
-
-AUSTRALIA & NEW ZEALAND
-=======================
-
-------------------------------------------------------------------------------
-ADELAIDE, AUSTRALIA
-
-NS Computer Software and Services P/L
-PO Box 86
-Ingle Farm
-SA 5098
-
-Contact: Richard Sharpe
- Ph: +61-8-281-0063 (08-281-0063) AH
- FAX:+61-8-250-2080 (08-250-2080)
-
-Experience with: ULTRIX, Digital UNIX, SunOS, WfW 3.11, Win95, WNT 3.51
-
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-ADELAIDE - AUSTRALIA
-
-Richard Sharpe, sharpe@ns.aus.com
-NS Computer Software and Services P/L
-PO Box 86,
-Ingle Farm, SA 5098
-Australia
-
-Located in Adelaide, South Australia.
-
-Proficient with Digital UNIX, ULTRIX, SunOS, Linux, Win 95, WfWg, Win NT.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-BRISBANE - AUSTRALIA
-
-Brett Worth
-Select Computer Technology - Brisbane
-431 Logan Road
-Stones Corner QLD 4120
-E-Mail: brett@sct.com.au
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-CANBERRA - AUSTRALIA
-
-Paul Blackman (ictinus@lake.canberra.edu.au, Ph. 06 2012518) is
-available for consultation. Paul's Samba background is with
-Solaris 2.3/4 and WFWG/Win95 machines. Paul is also the maintainer
-of the SAMBA Web Pages.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-CANBERRA - AUSTRALIA
-
-Ben Elliston
-E-mail: bje@air.net.au
-Samba systems: Solaris 2.x, Linux, HP-UX.
-------------------------------------------------------------------------------
-
------------------------------------------------------------------------
-MELBOURNE - AUSTRALIA
-
-Michael Ciavarella
-Cybersoruce Pty Ltd.
-8/140 Queen Street
-Melbourne VIC 3000
-Phone: +61-3-9642-5997
-Fax: +61-3-9642-5998
-Email: mikec@cyber.com.au
-WWW: http://www.cyber.com.au
-
-Cybersource specialises in TCP/IP network integration and Open Systems
-administration. Cybersource is an Australian-owned and operated
-company, with clients including some of Australia's largest financial,
-petrochemical and state government organisations.
------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-MELBOURNE - AUSTRALIA
-
-Company Name DARX Consulting
-Postal Address PO Box 12329
- A'Beckett St PO
- Melbourne 3000
-Area of Service Melb Metro and SE Suburbs
-Phone +61 3 9822 1216
-Email info@darx.com.au
-
-We provide setup and support of samba based systems as well as
-Novell/NT Systems.
------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-N.T - AUSTRALIA
-
-Open Systems Network Support
-
-Server Platforms - Unix/Linux
-Client Platforms - Windows3.1/95/NT, Macintosh, Unix/Linux
-
---
-David Schroeder Darwin Network Services
-Ph/Fax (08) 8932 1156 PO Box 82383
-(Int) +61 8 8932 1156 Casuarina N.T
-Email: djsc@it.ntu.edu.au Australia 0811
------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-NEW SOUTH WALES - AUSTRALIA
-
-BITcom Telecommunications Phone: (02) 9747 0011
-P.O. Box 15 Int'l: +61 2 9747 0011
-Burwood NSW 2134 Australia Fax: (02) 9747 6918
-Contact: Craig Bevins Email: consult@bitcom.net.au
-
-BITcom is an open systems and networking consultancy. We have been
-doing Open Systems since long before the term was coined, a key staff
-member having participated in the IEEE working group which produced
-the POSIX standard for Un*x-like systems in 1988.
-
-We tend to have a Unix orientation (all flavours) but our focus is on
-getting the job done and we are happy to employ other technologies which
-fit. Heck, we even use and support Microsoft's products! Our areas
-of expertise cover general Unix consultancy, support for public domain
-and GNUish software, PC LAN -> Unix integration, Internet, WWW and local
-and wide-area network design, implementation and security. We have a
-collective masochistic streak and actually enjoy hacking on sendmail
-configuration. We are an AUSTEL-licenced telecommunications and data
-cabler and hold a NSW security industry licence.
-
-We know Windows NT, LANMAN, PC-NFS and others. We use, recommend and
-support Samba and have done so since 1994.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-PERTH - AUSTRALIA
-
-Bruce Cook - Synonet Corporation.
-E-mail: bcook@wantree.com.au
-Mobile: 015 999 330 (International +61 15 999 330)
-Experience: Samba on FreeBSD, Linux, Solaris (Sparc), Sunos-4
- Microsoft networking using NT/NTAS, Win95, WFW311, DOS
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-PERTH - AUSTRALIA
-
-Geoff Allan Phone: +61 8 9325 9922
-Office Information Fax: +61 8 9325 9938
-Perth, Western Australia Mobile: 0412 903 659
-Email: geoffa@officeinfo.com.au
-
-Office Information has been in existence since 1991. We are (amongst
-other things) systems integrators with experts in Unix, Linux, Novell,
-NT and the other DOS & Windows platforms. We also have a number of
-Clients for whom we have installed and supported Samba.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-QUEENSLAND - AUSTRALIA
-
-Plugged In Software Pty Ltd
-PO Box 4130
-4/242 Hawken Drive
-St. Lucia South, Qld 4067
-Australia
-http://www.plugged.net.au
-info@plugged.net.au
-+61 7 3876 7140
-+61 7 3876 7142 (fax)
-Point of Contact: David Wood
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-SYDNEY - AUSTRALIA
-
-Philip Rhoades
-Pricom Pty Ltd
-http://www.pricom.com.au = http://203.12.131.20
-GPO Box 3411 Sydney NSW 2001 Australia
-Ph: +61:0411:185652
-Fax: +61:2:9959-3481
-E-mail: philr@mail.austasia.net
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-SYDNEY - AUSTRALIA
-
-John Terpstra - Aquasoft (jht@aquasoft.com.au)
-Business: +612 9524 4040
-Home: +612 9540 3154
-Mobile: +612 414 334422 (aka 0414 334422)
-Samba Experience: Member of Samba-Team. Long term contributor to Samba
- Samba on BSD/OS, Solaris (Sparc & x86), ISC Unix, SCO Unix
- NCR SVR4, Linux, UnixWare, IBM, HP, DEC, Others.
- Training Instructor in Windows NT, wide area networking
- over TCP/IP. Providing paid-for support for Public Domain
- Software and Linux.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-SYDNEY - AUSTRALIA
-
-We are a Unix & Windows developer with a consulting & support component.
-In business since 1981 with experience on Sun, hp, sgi, IBM rs6000 plus
-Windows, NT and Win95, Using Samba since September 94.
-CodeSmiths, 22 Darley Road, MANLY 2095 NSW; 977 1979; fax: 977 2116
-philm@esi.com.au (Australia; New South Wales; SYDNEY; North East)
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-SYDNEY - AUSTRALIA
-
-Pacific ESI has used and installed Samba since 1.6 on a range
-of machines running SunOS, BSD/OS, SCO/UNIX, HP/UX, and Solaris,
-and WfWG and Windows95. The largest system worked on to date
-involved an Australia wide network of machines with PCs and SUNs
-at the various nodes. The in-house testing site is a wide area
-network with three sites, remotely connected with PPP and with
-SUN servers at each site to all of which are connected several
-PCs running mainly WfWG.
-
-Stefan Kjellberg Pacific Engineering Systems
-International
-info@eram.esi.com.au Voice:+61-2-9063377
-... Fax:+61-2-9063468
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-WELLINGTON - NEW ZEALAND
-
-David Gempton
-Computer Consultant
-UNIX & PC Networking specialist
-TTC Technology Training Consulting
-PO Box 5444
-Lambton Quay Wellington
-New Zealand
-Phone (025) 518-574
-Email: ttcdg@cyberspace.co.nz
-------------------------------------------------------------------------------
-
-
-
-
-
-
-CANADA
-======
-
-------------------------------------------------------------------------------
-ONTARIO - CANADA
-
-Strata Software Limited, Kanata Ontario CANADA
-Tel: +1 (613) 591-1922 Fax: +1 (613) 591-3485
-Email: sales@strataware.com WWW: http://www.strataware.com/
-
-Strata Software Limited is a software development and consulting group
-specializing in data communications (TCP/IP and OSI), X.400, X.500 and
-LDAP, and X.509-based security. We have Samba experience with Windows NT,
-Windows 95, and Windows for Workgroups clients with Linux, Unixware
-(SVR4), and HP-UX servers.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-ONTARIO - CANADA
-
-WW Works Inc.
-3201 Maderna Road
-Burlington, Ontario
-Canada L7M 2W4
-
-Contact: Wade Weppler
-(905) 332-5844
-FAX: (905) 332-5535
-
-Information Systems Sales and Consulting.
-Specializing in Turnkey Windows NT Network environments with emphasis on
-Legacy UNIX System integration using Samba.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-ONTARIO - CANADA
-
- Bilyana Aleksic |Email: baleksic@atitech.ca |
- | |
-ATI Technologies Inc. |Phone: 905-882-2600 x3179 |
-75 Tiverton Court |Fax : 905-475-3930 |
-Unionville, Ontario | |
-Canada, L3R 9S3 | |
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-ONTARIO - CANADA
-
-Sound Software Ltd.
-20 Abelard Avenue
-Brampton, Ontario Canada
-905 452 0504
-sales@telly.org
-www.telly.org
-
-Sound Software company is a Caldera Business Partner, providing support for
-Samba and other applications running under Caldera Linux.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-OTTAWA - CANADA
-
-Russell McOrmond
-Open Systems Internet Consultant
-Serving individuals and organizations in the Ottawa (Ontario, Canada) area.
-voice: (613) 235-7584 FAX: (613) 230-1258
-russell@flora.org , http://www.flora.org/russell/work/
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-QUEBEC - CANADA
-
-Dataden Computer Systems
-Attn: Danny Arseneau
-arseneau@parkmed.com
-895 2nd Avenue
-Ile Bizard, Quebec
-Canada, H9C 1K3
-Tel: (514)891-2293
-Fax: (514)696-0848
-
-Dataden is company that specializes in Unix--TCP/IP networking.
-We have over 15 years of experience. We have been installing,
-configuring and maintaining Samba for clients for 1-1/2 years now. We
-have samba installations on Linx, SunOS and DEC OSF. Our biggest site
-has 4 Suns and 3 Linux servers running Samba which are serving a network
-of about 50 PC's running WFWg and Win95.
-------------------------------------------------------------------------------
-
-
-
-
-
-
-
-
-EUROPE
-======
-
-------------------------------------------------------------------------------
-BRUSSELS - BELGIUM
-
-Phidani Software SPRL
-Rue de l'autonomie, 1
-1070 Brussels
-Belgium
-Tel : +32 (2) 5220663
-Fax: +32 (2) 5220930
-
-We provide commercial support in Belgium to large organisations
-(eg: N.A.T.O., Unisys, E.C.C. ...)
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-PRAHA (PRAGUE) - CZECH
-
-AGC Praha,
-David Doubrava
-Sokolovska 141
-PRAHA 8
-180 00
-
-Tel: +42 (2) 6600 2202 Fax: +42 (2) 683 02 55
-Email: ddoubrava@agc.cz WWW: http://corwin.agc.cz/
-
-I have Samba experience with Windows NT,
-Windows 95, and Windows for Workgroups clients with Linux and HP-UX
-servers.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-CAMBRIDGE - ENGLAND. Will travel / provide support world-wide.
-
-Luke Kenneth Casson Leighton
-Phone: +44 1223 570 262 or 570 264
-lkcl@cb1.com
-
-Configuration Experience:
-
-Clients: MSClient 3.0; WfWg; W95; NT 3.5 and 4.0 Workstation.
-Servers: Samba 1.9.15 and above (on-hands experience with Linux, SunOS
-4.1.3 and FreeBSD); NT 4.0 Server.
-
-Present Experience:
-
-Luke Leighton, a Samba Team member since October 1995, understands
-Browsing and WINS from having re-designed and re-written nmbd, and
-SMB/CIFS from attending the two CIFS conferences; by listening to
-discussions amongst the Samba Developers, and from answering user's
-queries on the Samba Digest.
-
-Support offered:
-
-If there are either areas of functionality that are missing or bugs
-that are affecting the performance of your company; if you require
-advice / training on the deployment and administration of SMB/CIFS
-Clients and Servers; if your company's policy only allows you to
-use samba if it is supported commercially... I am available for hire
-anywhere in the world.
-
-Long-term Project Aims:
-
-I would like to implement a CIFS proxying system suitable for Enterprise
-Networks (large Intranets: 10,000 to 150,000 simultaneous users) that is
-backwards compatible with all CIFS/SMB servers (MSClient 3.0 for DOS,
-through to NT 4.0).
-
-I would also like to implement an alternative SMB client for NT and 95.
-This would allow samba to offer secure and authenticated file and print
-access, to the extent that the laws of your country permit.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-CAMBRIDGE - ENGLAND
-
-Mark Ayliffe MBCS, Technical Consultant
-Protechnic Computers Limited http://www.prot.demon.co.uk
-7 Signet Court Tel +44 1223 314855
-Swann's Road Fax +44 1223 368168
-Cambridge CB5 8LA
-England
-
-
-Protechnic Computers Limited has experience of installing and
-maintaining Samba on the following platforms:
-
-HP/UX 9.0x, 10.1x & 10.2x
-DG/UX, Motorola and Intel
-Digital UNIX
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-CORNWALL - ENGLAND
-
-Starstream Communications Ltd
-Unit 9
-Moss Side Industrial Estate
-Callington
-Cornwall
-PL17 7DU
-United Kingdom
-
-Phone +44 1579 384072 Fax +44 1579 384267
-
-Contact : Terry Moore-Read terry@starstream.co.uk
-
-Website : http://www.ndu-star.demon.co.uk shortly moving to
-http://www.starstream.co.uk
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-FAREHAM - ENGLAND
-
-High Field Technology Ltd
-Little Park Farm Road, Segensworth West,
-Fareham, Hants PO15 5SJ, UK.
-sales@hft.co.uk tel +44 148 957 0111 fax +44 148 957 0555
-
-Company skills: Real time hardware and software systems
-
-Samba experience: BSD/OS, Linux, LynxOS <==> WFWG, NT
-
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-LEICESTERSHIRE - ENGLAND
-
-TECTONIC LIMITED
-WESTWOOD
-78 LOUGHBOROUGH ROAD
-QUORN
-LEICESTERSHIRE
-LE12 8DX
-
-TELEPHONE 01509-620922
-FAX 01509-620933
-
-Contact Samantha Hull
-
-We are unix orientated but also specialise in pc to unix communications, we
-know and understand pc-nfs, (hence our interest in samba).
-we support sunos, solaris 1.x and 2.x, hp-ux 9.0 and 10.0, osf (or dec unix,
-whichever you prefer), winnt, wfwg and win95.
-
-We are already talking to a couple of very large samba users here in the uk.
-Tectonic are in the process of creating the UK SAMBA USER GROUP and would
-appreciate any feedback or queries.
-
-For samba support, and for details on the UK SAMBA USER GROUP, please contact
-me at: sam@tectonic.demon.co.uk
-
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-LONDON - ENGLAND
-
-Mark H. Preston,
-Network Analyst, | Email : mpreston@sghms.ac.uk
-Computer Unit, | Tel : +44 (0)181 725-5434
-St. George's Hospital Med School, | Fax : +44 (0)181 725-3583
-London SW17 ORE. | WWW : http://www.sghms.ac.uk
-
-Samba Experience:
-Server: Solaris 2.3 & 2.4, Irix 5.2 & 5.3
-Client: WinNT, Win95, WfWg, Win3.1, Ms-LanMan, DHCP support
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-READING - ENGLAND
-
-Philip Hands | E-Mail: info@hands.com Tel:+44 118 9545656
-Philip Hands Computing Ltd. | Mobile: +44 802 242989 Fax:+44 118 9474655
-Unit 1, Cherry Close, Caversham, Reading RG4 8UP ENGLAND
-
-Samba experience:
- Server platforms: Linux,SVR4,SVR3.2 & Sequent ptx
- Clients: WfWg, W3.1, OS2 and MS-LanMan
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-PARIS - FRANCE
-
-Alcove
-7, rue Royer-Bendelé
-92230 Gennevilliers
- Email: alcove@alcove.fr
-http://www.alcove.fr Phone number: +33 01 40 85 80 06
- Fax number: +33 01 47 90 40 42
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-BERLIN - GERMANY
-
-Name: innominate GbR
-Address: Soldiner Str. 96, 13359 Berlin; Bundesland: Berlin;
-Country: Germany
-Phone: +49 30 49308195, +49 177 2649655 (mobil)
-Fax: +49 30 49308196
-EMail: innominate@poboxes.com
-
-Contact : Sascha Ottolski
-
-Type of support: vor Ort, Email, Fernzugriff ueber Internet/ISDN,
-
-Special
-expertise: Wir verfuegen ueber umfangreiche Erfahrung mit Samba, vor allem
- in Internet- und Intranetumgebungen. Neben Beratung, Dienstleistung
- und Schulung bieten wir auch individuell vorkonfigurierte
- Kommunikationsserver ("Lingo") auf der Basis von Linux an.
- Neben anderen Modulen (ISDN/Internet/Intranet/Email/Proxy
- u.a.) ist in Lingo ein Fileserver-Modul auf Samba-Basis inklusive
- einem mehrstufigen Firewallsystem enthalten.
- Außerdem verfuegt Lingo ueber eine grafische Administrations-
- oberflaeche, mit der z.B. das Hinzufuegen von neuen Benutzern
- von jedem Client per WWW-Browser moeglich ist.
-
-Sample prices: - Komplettpreise fuer Lingo nach Vereinbarung
- - 120 DM/Stunde fuer Dienstleistung
- - Schulung nach Vereinbarung
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-BERLIN - GERMANY
-
-Ing. Buero Buehler
-Dipl.-Ing. Frank Buehler
-Paul-Krause-Str. 5
-14129 Berlin
-Germany
-
-Phone: +49/(0)177/825 33 80 Fax: +49/(0)30/803-3039
-mailto:fb@hydmech.fb12.TU-Berlin.de
-
-We install and maintain small to middle sized Linux-Windows
-networks within the Berlin area and are available for consulting and
-questions about networking, Linux, database systems and electronics.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-BIELEFELD - GERMANY
-
-I am located in Bielefeld/Germany and have been doing Unix consultancy
-work for the past 8 years throughout Germany and the rest of Europe. I
-can be contacted by email at or via phone at +49 521
-9225922 or telefax at +49 521 9225924.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-BIELEFELD - GERMANY
-
-Name : media engineering gmbh
-Address: Bleichstr. 77a , D-33607 Bielefeld
-Phone : +49-521-1365640
-Fax : +49-521-1365642
-eMail : info@media-eng.bielefeld.com
-URL : http://www.media-eng.bielefeld.com/
-Contact: Dipl.Ing. Hartmut Holzgraefe
-
-Type of support: phone, eMail, inhouse, remote administration
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-DREIEICH - GERMANY
-
-A. G. Schindler
-c/o Alpha Zero One Gmbh
-Frankfurter Str. 141
-D - 63303 Dreieich
-Germany
-
-AZ1 is a company of Value Added Resellers (VARs) of Digital Equipment
-Corp. products and solution provider for Industry Applications.
-
-We're providing commercial support for Samba running on DEC hardware
-under Digital Unix (R), Digital OpenVMS (R) and Linux.
-
-Contract based and hotline support available. Fast response on-site
-support coming soon for the Franfurt / Main area.
-
-Pathworks or WinNT to Samba migrators welcome !
-
-Please contact us via: schindler@az1.de
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-GOETTINGEN - GERMANY
-
-Service Network GmbH
-Hannah Vogt Str. 1
-37085 Goettingen
-Germany
-Phone: +49-551-507775
-Fax: +49-551-507776
-http://www.sernet.de/
-samba@sernet.de
-
-SerNet is a company doing LAN consulting and training. We offer
-Internet access for our customers. We have experience with many
-different kinds of Unix, especially Linux, as well as NetWare and NT.
-Volker Lendecke, one of our our founders and a Samba Team member,
-has gained a lot of SMB/CIFS and NetWare experience writing smbfs and
-ncpfs, the Linux kernel file systems that enable Linux to access
-Windows NT and other SMB/CIFS servers, and NetWare Servers.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-GREIFSWALD - GERMANY
-
-Mr. Frank Rautenberg, Mr. Heiko Boesel, Mr. Jan Holz
-UniCon Computersysteme GmbH
-Ziegelhof 20
-D-17489 Greifswald
-email: samba@unicon-gmbh.com
-www: http://www.unicon-gmbh.com
-
-We use Samba and we provide support for our customers.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-MUENCHEN - GERMANY
-
-CONSYS GmbH
-Landsberger Str. 402
-81241 München
-Germany
-Phone: +49-89-5808181
-Fax: +49-89-588776
-http://www.consys.de/
-mailto:samba@consys.de
-
-
-CONSYS is a software company. We have experience especially with SCO Unix
-and other Unix systems, as well as with Windows 95 and NT.
-We are a Premium Partner of SCO and know and have used samba for four years.
-Our engineers know a lot about the installation of SCO Unix.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-SZEGED - HUNGARY
-
- Name: Geza Makay
- Institute: Jozsef Attila University of Szeged
- Mail: Bolyai Institute, Aradi vertanuk tere 1.
- H-6720, Szeged, Hungary
- Tel: (62) 454-091 (Hungary's code: 36)
- Fax/Message: (62) 326-246 (Hungary's code: 36)
- E-mail: makayg@math.u-szeged.hu
- World Wide Web: http://www.math.u-szeged.hu/
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-PALERMO - ITALY
-
-Francesco Cardinale
-E-Mail: cardinal@palermo.italtel.it
-Samba experience: SVR3.2, SOLARIS, ULTRIX, LINUX <--> DOS LAN-MAN, WFW
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-PISA - ITALY
-
-I3 ICUBE s.r.l.
-Via Pascoli 8
-56125 PISA (PI)
-ITALY
-tel: 050/503202
-fax: 050/504617
-contact person: Marco Bizzarri
-e-mail: m.bizzarri@icube.it
-www: http://www.icube.it/
-
-Our company offers commercial support to integrate eterogenous networks.
-We can provide support for the following architectures:
-
-Windows:
-Windows for Workgroup
-Windows 95
-Windows NT
-
-Unix:
-Linux
-Solaris
-Digital Unix
-
-Macintosh
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-LUXEMBOURG - EUROPE
-
-E.C.C. sa
-11, Rue Bettlange
-L-9657 HARLANGE
-Grand-Duche de Luxembourg
-Tel. +352 93615 (from 09/97: +352 993615)
-Fax +352 93569 (from 09/97: +352 993569)
-oontact person: Stefaan A Eeckels
-email: Stefaan.Eeckels@ecc.lumail
-
-We're located in Luxembourg, and recently provided support
-for Samba at Eurostat (the European Commision), who are using
-Samba to integrate Windows NT workstations in their Solaris
-/ Windows3.1 network. All in all, things run rather smoothly now.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-DELFT - NETHERLANDS
-
-BitWizard B.V.
-van Bronckhorststraat 12
-2612 XV Delft
-The Netherlands
-Tel: +31-15-2137459
-Email: samba@BitWizard.nl
-http: http://www.bitwizard.nl/
-
-Specific activities:
-
- - Linux support
- - GNU software support
- - Linux device driver writing
- - Data recovery
-
-BitWizard supports freely distributable software,
-especially quality products like "Samba".
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-GRONINGEN - THE NETHERLANDS
-
-Company: Le Reseau netwerksystemen BV
-Address: Bieslookstraat 31
-City: Groningen
-Zip: NL-9731 HH
-Country: The Netherlands
-
-We already offer commercial support on Linux and other Unices. Together with
-an application house we have developed a office automation environment which
-heavily depends on Samba. This environment consists of a Linux application
-server which is also the Samba server. A NT server for standard office
-applications. A firewall for Internet connectivity. And a large number of
-DOS/Win3.x/W95 clients that connect to the different machines. User's home
-directories are mounted through Sambe.
-
-We also support other Unices like Solaris, SunOS, HP-UX, Digital Unix and
-AIX.
-
-Sincerely,
-
-Arthur Donkers
-Le Reseau
-
-email : arthur@reseau.nl
-phone : (+31) 595 552431
-URL http://www.reseau.nl
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-NIJMEGEN - THE NETHERLANDS
-
-Xtended Internet (http://www.xtdnet.nl/)
-
-Broerdijk 27 Postbus 170 Tel: 31-24-360 39 19
-6523 GM Nijmegen 6500 AD Nijmegen Fax: 31-24-360 19 99
-The Netherlands The Netherlands info@xtdnet.nl
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-UTRECHT - NETHERLANDS
-
-Van den Hout Creative Communications
-Koos van den Hout
-Email : koos@kzdoos.xs4all.nl
-Phone : +31-30-2871002
-Fax : +31-30-2817051
-Samba experience: Setup and configuration for Linux, Solaris, web
-publishing related usage.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-ITALY
-
-InfoTecna di Cesana D. & C. s.n.c.
-Via Cesana e Villa, 29
-20046 Biassono (Mi)
-
-Tel: ++39 39 2324054
-Fax: ++39 39 2324054
-
-e-mail: infotecn@tin.it
-URL: http://space.tin.it/internet/dsbragio
-
-We provide Samba support along with generic Linux support. Specifically we
-have implemented a powerful Fax servicing system for Samba with Win95/NT
-clients. Details could be found at our URL, currently, only in Italian.
-------------------------------------------------------------------------------
-VETLANDA - SWEDEN
-
- IBS Industridata AB
- Box 95
- 574 21 VETLANDA
- SWEDEN
-
-Phone: +46-383-16065
-Fax: +46-8-287905
-E-mail: samba@ibs.se
-http://www.id.ibs.se/ibsid
-
-We have offices in about 20 cities in Sweden and can provide commercial
-support for Samba.
-------------------------------------------------------------------------------
-
-------------------------------------------------------------------------------
-
-
-
-
diff --git a/docs/textdocs/Tracing.txt b/docs/textdocs/Tracing.txt
deleted file mode 100644
index d8b38378228..00000000000
--- a/docs/textdocs/Tracing.txt
+++ /dev/null
@@ -1,93 +0,0 @@
-Contributor: Andrew Tridgell
-Date: Old
-Status: Questionable
-
-Subject: How to trace samba system calls for debugging purposes
-=============================================================================
-
-This file describes how to do a system call trace on Samba to work out
-what its doing wrong. This is not for the faint of heart, but if you
-are reading this then you are probably desperate.
-
-Actually its not as bad as the the above makes it sound, just don't
-expect the output to be very pretty :-)
-
-Ok, down to business. One of the big advantages of unix systems is
-that they nearly all come with a system trace utility that allows you
-to monitor all system calls that a program is making. This is
-extremely using for debugging and also helps when trying to work out
-why something is slower than you expect. You can use system tracing
-without any special compilation options.
-
-The system trace utility is called different things on different
-systems. On Linux systems its called strace. Under SunOS 4 its called
-trace. Under SVR4 style systems (including solaris) its called
-truss. Under many BSD systems its called ktrace.
-
-The first thing you should do is read the man page for your native
-system call tracer. In the discussion below I'll assume its called
-strace as strace is the only portable system tracer (its available for
-free for many unix types) and its also got some of the nicest
-features.
-
-Next, try using strace on some simple commands. For example, "strace
-ls" or "strace echo hello".
-
-You'll notice that it produces a LOT of output. It is showing you the
-arguments to every system call that the program makes and the
-result. Very little happens in a program without a system call so you
-get lots of output. You'll also find that it produces a lot of
-"preamble" stuff showing the loading of shared libraries etc. Ignore
-this (unless its going wrong!)
-
-For example, the only line that really matters in the "strace echo
-hello" output is:
-
-write(1, "hello\n", 6) = 6
-
-all the rest is just setting up to run the program.
-
-Ok, now you're famialiar with strace. To use it on Samba you need to
-strace the running smbd daemon. The way I tend ot use it is to first
-login from my Windows PC to the Samba server, then use smbstatus to
-find which process ID that client is attached to, then as root I do
-"strace -p PID" to attach to that process. I normally redirect the
-stderr output from this command to a file for later perusal. For
-example, if I'm using a csh style shell:
-
- strace -f -p 3872 >& strace.out
-
-or with a sh style shell:
-
- strace -f -p 3872 > strace.out 2>&1
-
-Note the "-f" option. This is only available on some systems, and
-allows you to trace not just the current process, but any children it
-forks. This is great for finding printing problems caused by the
-"print command" being wrong.
-
-Once you are attached you then can do whatever it is on the client
-that is causing problems and you will capture all the system calls
-that smbd makes.
-
-So how do you interpret the results? Generally I search thorugh the
-output for strings that I know will appear when the problem
-happens. For example, if I am having touble with permissions on a file
-I would search for that files name in the strace output and look at
-the surrounding lines. Another trick is to match up file descriptor
-numbers and "follow" what happens to an open file until it is closed.
-
-Beyond this you will have to use your initiative. To give you an idea
-of wehat you are looking for here is a piece of strace output that
-shows that /dev/null is not world writeable, which causes printing to
-fail with Samba:
-
-[pid 28268] open("/dev/null", O_RDWR) = -1 EACCES (Permission denied)
-[pid 28268] open("/dev/null", O_WRONLY) = -1 EACCES (Permission denied)
-
-the process is trying to first open /dev/null read-write then
-read-only. Both fail. This means /dev/null has incorrect permissions.
-
-Have fun!
-
-(please send updates/fixes to this file to samba-bugs@samba.anu.edu.au)
diff --git a/docs/textdocs/UNIX-SMB.txt b/docs/textdocs/UNIX-SMB.txt
deleted file mode 100644
index 88a7324dd73..00000000000
--- a/docs/textdocs/UNIX-SMB.txt
+++ /dev/null
@@ -1,231 +0,0 @@
-Contributor: Andrew Tridgell
-Date: April 1995
-
-Subject: Discussion of NetBIOS in a Unix World
-============================================================================
-
-This is a short document that describes some of the issues that
-confront a SMB implementation on unix, and how Samba copes with
-them. They may help people who are looking at unix<->PC
-interoperability.
-
-It was written to help out a person who was writing a paper on unix to
-PC connectivity.
-
-
-Usernames
-=========
-
-The SMB protocol has only a loose username concept. Early SMB
-protocols (such as CORE and COREPLUS) have no username concept at
-all. Even in later protocols clients often attempt operations
-(particularly printer operations) without first validating a username
-on the server.
-
-Unix security is based around username/password pairs. A unix box
-should not allow clients to do any substantive operation without some
-sort of validation.
-
-The problem mostly manifests itself when the unix server is in "share
-level" security mode. This is the default mode as the alternative
-"user level" security mode usually forces a client to connect to the
-server as the same user for each connected share, which is
-inconvenient in many sites.
-
-In "share level" security the client normally gives a username in the
-"session setup" protocol, but does not supply an accompanying
-password. The client then connects to resources using the "tree
-connect" protocol, and supplies a password. The problem is that the
-user on the PC types the username and the password in different
-contexts, unaware that they need to go together to give access to the
-server. The username is normally the one the user typed in when they
-"logged onto" the PC (this assumes Windows for Workgroups). The
-password is the one they chose when connecting to the disk or printer.
-
-The user often chooses a totally different username for their login as
-for the drive connection. Often they also want to access different
-drives as different usernames. The unix server needs some way of
-divining the correct username to combine with each password.
-
-Samba tries to avoid this problem using several methods. These succeed
-in the vast majority of cases. The methods include username maps, the
-service%user syntax, the saving of session setup usernames for later
-validation and the derivation of the username from the service name
-(either directly or via the user= option).
-
-File Ownership
-==============
-
-The commonly used SMB protocols have no way of saying "you can't do
-that because you don't own the file". They have, in fact, no concept
-of file ownership at all.
-
-This brings up all sorts of interesting problems. For example, when
-you copy a file to a unix drive, and the file is world writeable but
-owned by another user the file will transfer correctly but will
-receive the wrong date. This is because the utime() call under unix
-only succeeds for the owner of the file, or root, even if the file is
-world writeable. For security reasons Samba does all file operations
-as the validated user, not root, so the utime() fails. This can stuff
-up shared development diectories as programs like "make" will not get
-file time comparisons right.
-
-There are several possible solutions to this problem, including
-username mapping, and forcing a specific username for particular
-shares.
-
-Passwords
-=========
-
-Many SMB clients uppercase passwords before sending them. I have no
-idea why they do this. Interestingly WfWg uppercases the password only
-if the server is running a protocol greater than COREPLUS, so
-obviously it isn't just the data entry routines that are to blame.
-
-Unix passwords are case sensitive. So if users use mixed case
-passwords they are in trouble.
-
-Samba can try to cope with this by either using the "password level"
-option which causes Samba to try the offered password with up to the
-specified number of case changes, or by using the "password server"
-option which allows Samba to do it's validation via another machine
-(typically a WinNT server).
-
-Samba supports the password encryption method used by SMB
-clients. Note that the use of password encryption in Microsoft
-networking leads to password hashes that are "plain text equivalent".
-This means that it is *VERY* important to ensure that the Samba
-smbpasswd file containing these password hashes is only readable
-by the root user. See the documentation ENCRYPTION.txt for more
-details.
-
-
-Locking
-=======
-
-The locking calls available under a DOS/Windows environment are much
-richer than those available in unix. This means a unix server (like
-Samba) choosing to use the standard fcntl() based unix locking calls
-to implement SMB locking has to improvise a bit.
-
-One major problem is that dos locks can be in a 32 bit (unsigned)
-range. Unix locking calls are 32 bits, but are signed, giving only a 31
-bit range. Unfortunately OLE2 clients use the top bit to select a
-locking range used for OLE semaphores.
-
-To work around this problem Samba compresses the 32 bit range into 31
-bits by appropriate bit shifting. This seems to work but is not
-ideal. In a future version a separate SMB lockd may be added to cope
-with the problem.
-
-It also doesn't help that many unix lockd daemons are very buggy and
-crash at the slightest provocation. They normally go mostly unused in
-a unix environment because few unix programs use byte range
-locking. The stress of huge numbers of lock requests from dos/windows
-clients can kill the daemon on some systems.
-
-The second major problem is the "opportunistic locking" requested by
-some clients. If a client requests opportunistic locking then it is
-asking the server to notify it if anyone else tries to do something on
-the same file, at which time the client will say if it is willing to
-give up it's lock. Unix has no simple way of implementing
-opportunistic locking, and currently Samba has no support for it.
-
-Deny Modes
-==========
-
-When a SMB client opens a file it asks for a particular "deny mode" to
-be placed on the file. These modes (DENY_NONE, DENY_READ, DENY_WRITE,
-DENY_ALL, DENY_FCB and DENY_DOS) specify what actions should be
-allowed by anyone else who tries to use the file at the same time. If
-DENY_READ is placed on the file, for example, then any attempt to open
-the file for reading should fail.
-
-Unix has no equivalent notion. To implement this Samba uses either lock
-files based on the files inode and placed in a separate lock
-directory or a shared memory implementation. The lock file method
-is clumsy and consumes processing and file resources,
-the shared memory implementation is vastly prefered and is turned on
-by default for those systems that support it.
-
-Trapdoor UIDs
-=============
-
-A SMB session can run with several uids on the one socket. This
-happens when a user connects to two shares with different
-usernames. To cope with this the unix server needs to switch uids
-within the one process. On some unixes (such as SCO) this is not
-possible. This means that on those unixes the client is restricted to
-a single uid.
-
-Note that you can also get the "trapdoor uid" message for other
-reasons. Please see the FAQ for details.
-
-Port numbers
-============
-
-There is a convention that clients on sockets use high "unprivilaged"
-port numbers (>1000) and connect to servers on low "privilaged" port
-numbers. This is enforced in Unix as non-root users can't open a
-socket for listening on port numbers less than 1000.
-
-Most PC based SMB clients (such as WfWg and WinNT) don't follow this
-convention completely. The main culprit is the netbios nameserving on
-udp port 137. Name query requests come from a source port of 137. This
-is a problem when you combine it with the common firewalling technique
-of not allowing incoming packets on low port numbers. This means that
-these clients can't query a netbios nameserver on the other side of a
-low port based firewall.
-
-The problem is more severe with netbios node status queries. I've
-found that WfWg, Win95 and WinNT3.5 all respond to netbios node status
-queries on port 137 no matter what the source port was in the
-request. This works between machines that are both using port 137, but
-it means it's not possible for a unix user to do a node status request
-to any of these OSes unless they are running as root. The answer comes
-back, but it goes to port 137 which the unix user can't listen
-on. Interestingly WinNT3.1 got this right - it sends node status
-responses back to the source port in the request.
-
-
-Protocol Complexity
-===================
-
-There are many "protocol levels" in the SMB protocol. It seems that
-each time new functionality was added to a Microsoft operating system,
-they added the equivalent functions in a new protocol level of the SMB
-protocol to "externalise" the new capabilities.
-
-This means the protocol is very "rich", offering many ways of doing
-each file operation. This means SMB servers need to be complex and
-large. It also means it is very difficult to make them bug free. It is
-not just Samba that suffers from this problem, other servers such as
-WinNT don't support every variation of every call and it has almost
-certainly been a headache for MS developers to support the myriad of
-SMB calls that are available.
-
-There are about 65 "top level" operations in the SMB protocol (things
-like SMBread and SMBwrite). Some of these include hundreds of
-sub-functions (SMBtrans has at least 120 sub-functions, like
-DosPrintQAdd and NetSessionEnum). All of them take several options
-that can change the way they work. Many take dozens of possible
-"information levels" that change the structures that need to be
-returned. Samba supports all but 2 of the "top level" functions. It
-supports only 8 (so far) of the SMBtrans sub-functions. Even NT
-doesn't support them all.
-
-Samba currently supports up to the "NT LM 0.12" protocol, which is the
-one preferred by Win95 and WinNT3.5. Luckily this protocol level has a
-"capabilities" field which specifies which super-duper new-fangled
-options the server suports. This helps to make the implementation of
-this protocol level much easier.
-
-There is also a problem with the SMB specications. SMB is a X/Open
-spec, but the X/Open book is far from ideal, and fails to cover many
-important issues, leaving much to the imagination. Microsoft recently
-renamed the SMB protocol CIFS (Common Internet File System) and have
-published new specifications. These are far superior to the old
-X/Open documents but there are still undocumented calls and features.
-This specification is actively being worked on by a CIFS developers
-mailing list hosted by Microsft.
-
diff --git a/docs/textdocs/WinNT.txt b/docs/textdocs/WinNT.txt
deleted file mode 100644
index 772ef74a4c0..00000000000
--- a/docs/textdocs/WinNT.txt
+++ /dev/null
@@ -1,69 +0,0 @@
-Contributor: Various
-Updated: June 27, 1997
-Status: Current
-
-Subject: Samba and Windows NT Password Handling
-=============================================================================
-
-There are some particular issues with Samba and Windows NT.
-
-Passwords:
-==========
-One of the most annoying problems with WinNT is that NT refuses to
-connect to a server that is in user level security mode and that
-doesn't support password encryption unless it first prompts the user
-for a password.
-
-This means even if you have the same password on the NT box and the
-Samba server you will get prompted for a password. Entering the
-correct password will get you connected only if Windows NT can
-communicate with Samba using a compatible mode of password security.
-
-All versions of Windows NT prior to 4.0 Service Pack 3 could negotiate
-plain text (clear text) passwords. Windows NT 4.0 Service Pack 3 changed
-this default behaviour so it now will only handle encrypted passwords.
-The following registry entry change will re-enable clear text password
-handling:
-
-Run regedt32.exe and locate the hive key entry:
-HKEY_LOCAL_MACHINE\system\CurrentControlSet\Services\rdr\parameters\
-
-Add the following value:
- EnablePlainTextPassword:REG_DWORD=1
-
-
-The other major ramification of this feature of NT is that it can't
-browse a user level non-encrypted server unless it already has a
-connection open. This is because there is no spot for a password
-prompt in the browser window. It works fine if you already have a
-drive mounted (for example, one auto mounted on startup).
-=====================================================================
-
-Printing:
-=========
-When you mount a printer using the print manager in NT you may find
-the following info from Matthew Harrell
-useful:
-
-------------
- I noticed in your change-log you noted that some people were
-still unable to use print manager under NT. If this is the same problem
-that I encountered, it's caused by the length of time it takes NT to
-determine if the printer is ready.
-
-The problem occurs when you double-click on a printer to connect it to
-the NT machine. Because it's unable to determine if the printer is ready
-in the short span of time it has, it assumes it isn't and gives some
-strange error about not having enough resources (I forget what the error
-is). A solution to this that seems to work fine for us is to click
-once on the printer, look at the bottom of the window and wait until
-it says it's ready, then clilck on "OK".
-
-By the way, this problem probably occurs in our group because the
-Samba server doesn't actually have the printers - it queues them to
-remote printers either on other machines or using their own network
-cards. Because of this "middle layer", it takes an extra amount of
-time for the NT machine to get verification that the printer queue
-actually exists.
-
-I hope this helped in some way...
diff --git a/docs/textdocs/security_level.txt b/docs/textdocs/security_level.txt
deleted file mode 100644
index fac446fda8e..00000000000
--- a/docs/textdocs/security_level.txt
+++ /dev/null
@@ -1,96 +0,0 @@
-Contributor: Andrew Tridgell
-Updated: June 27, 1997
-Status: Current
-
-Subject: Description of SMB security levels.
-===========================================================================
-
-Samba supports the following options to the global smb.conf parameter
-"security =":
- share, user, server
-
-Of the above, "security = server" means that Samba reports to clients that
-it is running in "user mode" but actually passes off all authentication
-requests to another "user mode" server. This requires an additional
-parameter "password server =" that points to the real authentication server.
-That real authentication server can be another Samba server or can be a
-Windows NT server, the later natively capable of encrypted password support.
-
-Below is a more complete description of security levels.
-===========================================================================
-
-A SMB server tells the client at startup what "security level" it is
-running. There are two options "share level" and "user level". Which
-of these two the client receives affects the way the client then tries
-to authenticate itself. It does not directly affect (to any great
-extent) the way the Samba server does security. I know this is
-strange, but it fits in with the client/server approach of SMB. In SMB
-everything is initiated and controlled by the client, and the server
-can only tell the client what is available and whether an action is
-allowed.
-
-I'll describe user level security first, as its simpler. In user level
-security the client will send a "session setup" command directly after
-the protocol negotiation. This contains a username and password. The
-server can either accept or reject that username/password
-combination. Note that at this stage the server has no idea what
-share the client will eventually try to connect to, so it can't base
-the "accept/reject" on anything other than:
-
-- the username/password
-- the machine that the client is coming from
-
-If the server accepts the username/password then the client expects to
-be able to mount any share (using a "tree connection") without
-specifying a password. It expects that all access rights will be as
-the username/password specified in the "session setup".
-
-It is also possible for a client to send multiple "session setup"
-requests. When the server responds it gives the client a "uid" to use
-as an authentication tag for that username/password. The client can
-maintain multiple authentication contexts in this way (WinDD is an
-example of an application that does this)
-
-
-Ok, now for share level security. In share level security (the default
-with samba) the client authenticates itself separately for each
-share. It will send a password along with each "tree connection"
-(share mount). It does not explicitly send a username with this
-operation. The client is expecting a password to be associated with
-each share, independent of the user. This means that samba has to work
-out what username the client probably wants to use. It is never
-explicitly sent the username. Some commercial SMB servers such as NT actually
-associate passwords directly with shares in share level security, but
-samba always uses the unix authentication scheme where it is a
-username/password that is authenticated, not a "share/password".
-
-Many clients send a "session setup" even if the server is in share
-level security. They normally send a valid username but no
-password. Samba records this username in a list of "possible
-usernames". When the client then does a "tree connection" it also adds
-to this list the name of the share they try to connect to (useful for
-home directories) and any users listed in the "user =" smb.conf
-line. The password is then checked in turn against these "possible
-usernames". If a match is found then the client is authenticated as
-that user.
-
-Finally "server level" security. In server level security the samba
-server reports to the client that it is in user level security. The
-client then does a "session setup" as described earlier. The samba
-server takes the username/password that the client sends and attempts
-to login to the "password server" by sending exactly the same
-username/password that it got from the client. If that server is in
-user level security and accepts the password then samba accepts the
-clients connection. This allows the samba server to use another SMB
-server as the "password server".
-
-You should also note that at the very start of all this, where the
-server tells the client what security level it is in, it also tells
-the client if it supports encryption. If it does then it supplies the
-client with a random "cryptkey". The client will then send all
-passwords in encrypted form. You have to compile samba with encryption
-enabled to support this feature, and you have to maintain a separate
-smbpasswd file with SMB style encrypted passwords. It is
-cryptographically impossible to translate from unix style encryption
-to SMB style encryption, although there are some fairly simple management
-schemes by which the two could be kept in sync.
diff --git a/examples/README b/examples/README
deleted file mode 100644
index 2dbc630e48c..00000000000
--- a/examples/README
+++ /dev/null
@@ -1,6 +0,0 @@
-This directory contains example config files and related material for
-Samba.
-
-Send additions to: samba-bugs@samba.anu.edu.au
-
-
diff --git a/examples/dce-dfs/README b/examples/dce-dfs/README
deleted file mode 100644
index 4aaba8bb33e..00000000000
--- a/examples/dce-dfs/README
+++ /dev/null
@@ -1,4 +0,0 @@
-this is a sample configuration file from Jim Doyle who
-did the DCE/DFS patches for Samba. It shows how to make DCE/DFS shares
-available.
-
diff --git a/examples/dce-dfs/smb.conf b/examples/dce-dfs/smb.conf
deleted file mode 100644
index f5f155b8e6c..00000000000
--- a/examples/dce-dfs/smb.conf
+++ /dev/null
@@ -1,42 +0,0 @@
-[global]
- printing = bsd
- printcap name = /etc/printcap
- load printers = no
- guest account = guest
- log file = /usr/local/samba/var/log.%m
- log level = 8
- password level = 8
-
-[homes]
- comment = Home Directories
- browseable = no
- read only = no
- create mode = 0750
-
-[test]
- comment = test stuff
- path = /dept/mis/home/testacct
- valid users = testacct
- public = no
- writable = yes
-
-[namespace]
- comment = DCE-DFS Global Root
- path = /...
- public = no
- writable = yes
-
-[oecdfs]
- comment = Corporate Cell
- path = /.../corp.boston.oec.com/fs
- browseable = no
- read only = no
- create mode = 0750
-
-[develdfs]
- comment = Technology Development Cell
- path = /.../devel.boston.oec.com/fs
- browseable = no
- read only = no
- create mode = 0750
-
diff --git a/examples/misc/extra_smbstatus b/examples/misc/extra_smbstatus
deleted file mode 100644
index 363e7f67af5..00000000000
--- a/examples/misc/extra_smbstatus
+++ /dev/null
@@ -1,50 +0,0 @@
-Here's something that Paul Blackman sent me that may be useful:
-
--------------------
-I created this script to do a few things that smbstatus doesn't at the
-moment. Perhaps you might want to include these. Sorry I haven't
-added things at source level, script was quick&easy.
-
-*******
-#!/bin/csh
-if ($1 == "-p") then
- smbstatus -p |sort -u
-else if ($1 == "-c") then
- echo There are `smbstatus -p |sort -u |grep -n -v z |grep -c :` unique smbd processes running.
- else if ($1 == "-l") then
- echo `date '+ %d/%m/%y %H:%M:%S'` `smbstatus -p |sort -u |grep -n -v z |grep -c :` >>$2
-else if ($1 == "-cs") then
- echo There are `smbstatus |awk '$1==share {n++;} END {print n}' share=$2` concurrent connections to share: $2
-else if ($1 == "-csl") then
- echo `date '+ %d/%m/%y %H:%M:%S'` `smbstatus |awk '$1==share {n++;} END {print n}' share=$2` >>$3
-else
- echo "'smbstat -c' ==> Count unique smbd processes."
- echo "'smbstat -p' ==> List unique smbd processes."
- echo "'smbstat -l logfile' ==> Append a log entry for the number of"
- echo " concurrent and unique processes to logfile."
- echo "'smbstat -cs sharename'"
- echo " ==> Count processes connected to sharename (assumed unique)"
- echo "'smbstat -csl sharename logfile'"
- echo " ==> Append a log entry for the number of concurrent"
- echo " processes connected to sharename (assumed unique)"
-endif
-******
-
-Run this script from cron eg.
-
-0,5,10,15,20,25,30,35,40,50,55 * * * * /usr/local/samba/bin/smbstat -l /usr/local/samba/var/smbdcount.log
-
-and you get a good idea of usage over time.
-
-Cheers,
-~^ MIME OK ^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~
- o | Paul Blackman ictinus@lake.canberra.edu.au
- o | Co-operative Research ------------------------
- o _ | Centre For Freshwater Ecology. Ph. (Aus) 06 2012518
- -- (") o | University of Canberra, Australia. Fax. " 06 2015038
- \_|_-- |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- | | "Spend a little love and get high"
- _/ \_ | - Lenny Kravitz
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-~~~~ SAMBA Web Pages: http://samba.canberra.edu.au/pub/samba/samba.html ~~~~~
-
diff --git a/examples/misc/wall.perl b/examples/misc/wall.perl
deleted file mode 100644
index 9303658ce14..00000000000
--- a/examples/misc/wall.perl
+++ /dev/null
@@ -1,69 +0,0 @@
-#!/usr/local/bin/perl
-#
-#@(#) smb-wall.pl Description:
-#@(#) A perl script which allows you to announce whatever you choose to
-#@(#) every PC client currently connected to a Samba Server...
-#@(#) ...using "smbclient -M" message to winpopup service.
-#@(#) Default usage is to message every connected PC.
-#@(#) Alternate usage is to message every pc on the argument list.
-#@(#) Hacked up by Keith Farrar
-#
-# Cleanup and corrections by
-# Michal Jaegermann
-# Message to send can be now also fed (quietly) from stdin; a pipe will do.
-#=============================================================================
-
-$smbstatus = "/usr/local/bin/smbstatus";
-$smbshout = "/usr/local/bin/smbclient -M";
-
-if (@ARGV) {
- @clients = @ARGV;
- undef @ARGV;
-}
-else { # no clients specified explicitly
- open(PCLIST, "$smbstatus |") || die "$smbstatus failed!.\n$!\n";
- while() {
- last if /^Locked files:/;
- split(' ', $_, 6);
- # do not accept this line if less then six fields
- next unless $_[5];
- # if you have A LOT of clients you may speed things up by
- # checking pid - no need to look further if this pid was already
- # seen; left as an exercise :-)
- $client = $_[4];
- next unless $client =~ /^\w+\./; # expect 'dot' in a client name
- next if grep($_ eq $client, @clients); # we want this name once
- push(@clients, $client);
- }
- close(PCLIST);
-}
-
-if (-t) {
- print <<'EOT';
-
-Enter message for Samba clients of this host
-(terminated with single '.' or end of file):
-EOT
-
- while (<>) {
- last if /^\.$/;
- push(@message, $_);
- }
-}
-else { # keep quiet and read message from stdin
- @message = <>;
-}
-
-foreach(@clients) {
-## print "To $_:\n";
- if (open(SENDMSG,"|$smbshout $_")) {
- print SENDMSG @message;
- close(SENDMSG);
- }
- else {
- warn "Cannot notify $_ with $smbshout:\n$!\n";
- }
-}
-
-exit 0;
-
diff --git a/examples/printer-accounting/README b/examples/printer-accounting/README
deleted file mode 100644
index b7ab42acb96..00000000000
--- a/examples/printer-accounting/README
+++ /dev/null
@@ -1,63 +0,0 @@
-These are just a few examples of what you can do for printer accounting;
-they are really just hacks to show a manager how may pages were being
-printed out on his new hp5n :)
-
-acct-all will run acct-sum and read the log files to generate some
-stats.
-
-Here is a sample output of the raw stats :
-
-1996-06-10.15:02:15 pkelly master.fcp.oypi.com 538 0
-1996-06-10.15:06:40 pkelly master.fcp.oypi.com 537 0
-1996-06-10.15:32:12 ted master.fcp.oypi.com 547 0
-1996-06-11.09:06:15 violet master.fcp.oypi.com 2667 0
-1996-06-11.09:48:02 violet master.fcp.oypi.com 66304 5
-1996-06-11.09:50:04 violet master.fcp.oypi.com 116975 9
-1996-06-11.09:57:20 violet master.fcp.oypi.com 3013 1
-1996-06-11.10:13:17 pkelly master.fcp.oypi.com 3407 1
-1996-06-11.12:37:06 craig master.fcp.oypi.com 13639 2
-1996-06-11.12:42:23 pkelly master.fcp.oypi.com 13639 2
-1996-06-11.12:45:11 marlene master.fcp.oypi.com 515 0
-1996-06-11.14:17:10 lucie master.fcp.oypi.com 1405 1
-1996-06-11.14:36:03 laura master.fcp.oypi.com 45486 5
-1996-06-11.15:08:21 violet master.fcp.oypi.com 1923 1
-1996-06-11.15:09:42 laura master.fcp.oypi.com 4821 1
-1996-06-11.15:12:28 laura master.fcp.oypi.com 46277 5
-1996-06-11.15:19:38 violet master.fcp.oypi.com 3503 1
-1996-06-11.15:21:49 lucie master.fcp.oypi.com 493 0
-1996-06-11.15:43:36 al master.fcp.oypi.com 3067 1
-
-And the output after the acct-sum is done on a full set of files
-in /var/log/lp/*
-
-master[1072] /var/log/lp$ /etc/conf/acct-all
-
-Sun Jul 21 23:03:16 EDT 1996
-
-Pages are approximate ...
-
-User Jobs Pages Size
-al 1 1 2 KB
-craig 1 2 13 KB
-jack 68 235 1995 KB
-laura 88 328 3050 KB
-lucie 221 379 3529 KB
-marlene 12 151 1539 KB
-melanie 83 365 3691 KB
-michelle 68 219 1987 KB
-mike 2 10 81 KB
-neil 111 225 2753 KB
-operator 44 137 1132 KB
-pkelly 368 984 11154 KB
-root 8 0 29 KB
-ted 158 257 2337 KB
-tony 244 368 2455 KB
-violet 419 1002 10072 KB
-
-
-Printer Jobs Pages
-hp2p 3 4
-hp5 915 2135
-lp 978 2524
-
-
diff --git a/examples/printer-accounting/acct-all b/examples/printer-accounting/acct-all
deleted file mode 100644
index dc8f175b3cb..00000000000
--- a/examples/printer-accounting/acct-all
+++ /dev/null
@@ -1,9 +0,0 @@
-#!/bin/sh
-
-echo ""
-date
-echo ""
-echo "Pages are approximate ..."
-echo ""
-/etc/conf/acct-sum /var/log/lp/*
-echo ""
diff --git a/examples/printer-accounting/acct-sum b/examples/printer-accounting/acct-sum
deleted file mode 100644
index ffbfc8d8801..00000000000
--- a/examples/printer-accounting/acct-sum
+++ /dev/null
@@ -1,29 +0,0 @@
-#!/usr/bin/perl
-
-while (<>) {
- ($date, $user, $machine, $size, $pages) = split(' ');
-
- $Printer{$ARGV}++;
- $PrinterPages{$ARGV} += $pages;
-
- $Jobs{$user}++;
- $Size{$user}+= $size;
- $Pages{$user}+= $pages;
-}
-
-printf "%-15s %5s %8s %8s\n", qw(User Jobs Pages Size);
-foreach $user (sort keys %Jobs) {
- printf "%-15s %5d %8d %8d \KB\n",
- $user, $Jobs{$user}, $Pages{$user}, $Size{$user}/1024;
-}
-
-
-print "\n\n";
-printf "%-15s %5s %8s %8s\n", qw(Printer Jobs Pages);
-foreach $prn (sort keys %Printer) {
- ($name = $prn) =~ s=.*/==;
- printf "%-15s %5d %8d\n",
- $name, $Printer{$prn}, $PrinterPages{$prn};
-}
-
-
diff --git a/examples/printer-accounting/hp5-redir b/examples/printer-accounting/hp5-redir
deleted file mode 100644
index 98c2b72edd2..00000000000
--- a/examples/printer-accounting/hp5-redir
+++ /dev/null
@@ -1,43 +0,0 @@
-#!/usr/bin/perl
-#
-# $Source: /data/src/mirror/cvs/samba/examples/printer-accounting/hp5-redir,v $
-# $Id: hp5-redir,v 1.1 1996/07/23 03:30:56 samba-bugs Exp $
-#
-# 0 == stdin == docuement
-# 1 == stdout == printer
-# 2 == stderr == logging
-#
-# With redirection to another valid /etc/printcap entry
-#
-
-umask(002);
-
-# -w132 -l66 -i0 -n pkelly -h master.fcp.oypi.com /var/log/lp-acct
-require "getopts.pl";
-&Getopts("w:l:i:n:h:");
-
-chomp($date = `date '+%Y-%m-%d.%T'`);
-
-($dev,$ino,$mode,$nlink,$uid,$gid,$rdev,$size,
- $atime,$mtime,$ctime,$blksize,$blocks)
- = stat(STDIN);
-
-# send to the real printer now.
-open(P, "|lpr -Pmgmt0") || die "Can't print to hp5-real ($!)\n";
-$cnt = 0;
-while (sysread(STDIN, $buf, 10240)) {
- print P $buf;
- # this is ugly, but it gives the approx in pages. We
- # don't print graphics, so ... There must be a better way :)
- $cnt += ($buf =~ /^L/g);
-}
-close(P);
-
-$acct = shift;
-if (open(ACCT, ">>$acct")) {
- print ACCT "$date $opt_n $opt_h $size $cnt\n";
- close(ACCT);
-} else {
- warn "Err: Can't account for it ($!)\n";
- warn "Log: $date $opt_n $opt_h $size $cnt\n";
-}
diff --git a/examples/printer-accounting/lp-acct b/examples/printer-accounting/lp-acct
deleted file mode 100644
index 3fe45f877fd..00000000000
--- a/examples/printer-accounting/lp-acct
+++ /dev/null
@@ -1,38 +0,0 @@
-#!/usr/bin/perl
-#
-# $Source: /data/src/mirror/cvs/samba/examples/printer-accounting/lp-acct,v $
-# $Id: lp-acct,v 1.1 1996/07/23 03:30:56 samba-bugs Exp $
-#
-# 0 == stdin == docuement
-# 1 == stdout == printer
-# 2 == stderr == logging
-#
-# Regular, with no redirection
-#
-
-umask(002);
-
-# -w132 -l66 -i0 -n pkelly -h master.fcp.oypi.com /var/log/lp-acct
-require "getopts.pl";
-&Getopts("w:l:i:n:h:");
-
-chomp($date = `date '+%Y-%m-%d.%T'`);
-
-($dev,$ino,$mode,$nlink,$uid,$gid,$rdev,$size,
- $atime,$mtime,$ctime,$blksize,$blocks)
- = stat(STDIN);
-
-$cnt = 0;
-while (sysread(STDIN, $buf, 10240)) {
- print $buf;
- $cnt += ($buf =~ /^L/g);
-}
-
-$acct = shift;
-if (open(ACCT, ">>$acct")) {
- print ACCT "$date $opt_n $opt_h $size $cnt\n";
- close(ACCT);
-} else {
- warn "Err: Can't account for it ($!)\n";
- warn "Log: $date $opt_n $opt_h $size $cnt\n";
-}
diff --git a/examples/printer-accounting/printcap b/examples/printer-accounting/printcap
deleted file mode 100644
index 976005a097c..00000000000
--- a/examples/printer-accounting/printcap
+++ /dev/null
@@ -1,22 +0,0 @@
-# HP5N - Accounting entry
-#
-# This file calls the filter, hp5-redir to do the numbers and then
-# is redirected to the real entry, mgmt0, which is a remote HP5N
-# on the LAN with it's own IP number.
-#
-hp5:lp=/dev/lp1:\
- :sd=/usr/spool/lpd/hp5-acct:\
- :lf=/var/log/lp-err:\
- :af=/var/log/lp/hp5:\
- :if=/usr/local/bin/lp/hp5-redir:\
- :sh:sf:\
- :mx#0:
-
-# HP5N - Real printer location
-mgmt0:\
- :rm=hp5.fcp.oypi.com:\
- :rp=hp5.fcp.oypi.com:\
- :sd=/usr/spool/lpd/mgmt0:\
- :sh:sf:\
- :mx#0:
-
diff --git a/examples/printing/smbprint b/examples/printing/smbprint
deleted file mode 100755
index 079f20aac41..00000000000
--- a/examples/printing/smbprint
+++ /dev/null
@@ -1,77 +0,0 @@
-#!/bin/sh -x
-
-# This script is an input filter for printcap printing on a unix machine. It
-# uses the smbclient program to print the file to the specified smb-based
-# server and service.
-# For example you could have a printcap entry like this
-#
-# smb:lp=/dev/null:sd=/usr/spool/smb:sh:if=/usr/local/samba/smbprint
-#
-# which would create a unix printer called "smb" that will print via this
-# script. You will need to create the spool directory /usr/spool/smb with
-# appropriate permissions and ownerships for your system.
-
-# Set these to the server and service you wish to print to
-# In this example I have a WfWg PC called "lapland" that has a printer
-# exported called "printer" with no password.
-
-#
-# Script further altered by hamiltom@ecnz.co.nz (Michael Hamilton)
-# so that the server, service, and password can be read from
-# a /usr/var/spool/lpd/PRINTNAME/.config file.
-#
-# In order for this to work the /etc/printcap entry must include an
-# accounting file (af=...):
-#
-# cdcolour:\
-# :cm=CD IBM Colorjet on 6th:\
-# :sd=/var/spool/lpd/cdcolour:\
-# :af=/var/spool/lpd/cdcolour/acct:\
-# :if=/usr/local/etc/smbprint:\
-# :mx=0:\
-# :lp=/dev/null:
-#
-# The /usr/var/spool/lpd/PRINTNAME/.config file should contain:
-# server=PC_SERVER
-# service=PR_SHARENAME
-# password="password"
-#
-# E.g.
-# server=PAULS_PC
-# service=CJET_371
-# password=""
-
-#
-# Debugging log file, change to /dev/null if you like.
-#
-logfile=/tmp/smb-print.log
-# logfile=/dev/null
-
-
-#
-# The last parameter to the filter is the accounting file name.
-# Extract the directory name from the file name.
-# Concat this with /.config to get the config file.
-#
-eval acct_file=\${$#}
-spool_dir=`dirname $acct_file`
-config_file=$spool_dir/.config
-
-# Should read the following variables set in the config file:
-# server
-# service
-# password
-eval `cat $config_file`
-
-#
-# Some debugging help, change the >> to > if you want to same space.
-#
-echo "server $server, service $service" >> $logfile
-
-(
-# NOTE You may wish to add the line `echo translate' if you want automatic
-# CR/LF translation when printing.
-# echo translate
- echo "print -"
- cat
-) | /usr/local/samba/bin/smbclient "\\\\$server\\$service" $password -U $server -N -P >> $logfile
diff --git a/examples/printing/smbprint.sysv b/examples/printing/smbprint.sysv
deleted file mode 100644
index 3e1cec47f50..00000000000
--- a/examples/printing/smbprint.sysv
+++ /dev/null
@@ -1,52 +0,0 @@
-#!/bin/sh
-#
-# @(#) smbprint.sysv version 1.0 Ross Wakelin
-#
-# Version 1.0 13 January 1995
-# modified from the original smbprint (bsd) script
-#
-# this script is a System 5 printer interface script. It
-# uses the smbclient program to print the file to the specified smb-based
-# server and service.
-#
-# To add this to your lp system, copy this file into your samba directory
-# (the example here is /opt/samba), modify the server and service variables
-# and then execute the following command (as root)
-#
-# lpadmin -punixprintername -v/dev/null -i/opt/samba/smbprint
-#
-# where unixprintername is the name that the printer will be known as
-# on your unix box.
-#
-# the script smbprint will be copied into your printer administration
-# directory (/usr/lib/lp or /etc/lp) as a new interface
-# (interface/unixprintername)
-# Then you have to enable unixprintername and accept unixprintername
-#
-# This script will then be called by the lp service to print the files
-# This script will have 6 or more parameters passed to it by the lp service.
-# The first five will contain details of the print job, who queued it etc,
-# while parameters 6 onwards are a list of files to print. We just
-# cat these at the samba client.
-#
-# Set these to the server and service you wish to print to
-# In this example I have a WfWg PC called "lapland" that has a printer
-# exported called "printer" with no password.
-#
-# clear out the unwanted parameters
-shift;shift;shift;shift;shift
-# now the argument list is just the files to print
-
-server=admin
-service=hplj2
-password=""
-
-(
-# NOTE You may wish to add the line `echo translate' if you want automatic
-# CR/LF translation when printing.
- echo translate
- echo "print -"
- cat $*
-) | /opt/samba/smbclient "\\\\$server\\$service" $password -N -P > /dev/null
-exit $?
-
diff --git a/examples/redhat/Instructions b/examples/redhat/Instructions
deleted file mode 100644
index c88f06e47d9..00000000000
--- a/examples/redhat/Instructions
+++ /dev/null
@@ -1,25 +0,0 @@
-January 8, 1997
-
-John H Terpstra
-
-Subject:
-========
-Preparation of RedHat RPM packages.
-
-Process:
-========
-1. Copy the official Samba-latest.tar.gz archive to /usr/src/redhat/SOURCES
-2. Un-gnuzip the file to the plain tar archive format
-3. Untar the archive to access the samba/examples/redhat files
-4. Copy the samba-make.patch file to /usr/src/redhat/SOURCES
-5. Copy samba-RHXXX.spec file to /usr/src/redhat/SPECS
- Note: Use the XXX that is your RedHat Linux Version Number
-6. Delete the extracted archive (see item 3)
-7. Go to the /usr/src/redhat/SPECS directory
-8. Execute: rpm -ba -v samba-RHxxx.spec
-9. Copy the SRPM file from the /usr/src/redhat/SRPMS directory
- and copy the RPMS file from the /usr/src/redhat/RPMS directory
- to the distribution point from which the finished packages will
- be uploaded to the samba ftp archive.
-
-Finito!!
diff --git a/examples/redhat/makeldirs.sh b/examples/redhat/makeldirs.sh
deleted file mode 100755
index 1ca312dfc18..00000000000
--- a/examples/redhat/makeldirs.sh
+++ /dev/null
@@ -1,10 +0,0 @@
-#!/bin/sh
-RPMDIR=$1
-mkdir $RPMDIR
-for i in etc etc/logrotate.d bin sbin usr usr/bin usr/sbin var var/spool var/log var/lock var/lock/samba
-do
- if [ ! -x $RPMDIR/$i ]; then
- mkdir $RPMDIR/$i
- fi
- echo Mkdir $RPMDIR/$i ... Done
-done
diff --git a/examples/redhat/makerpms.sh b/examples/redhat/makerpms.sh
deleted file mode 100755
index df54884a74b..00000000000
--- a/examples/redhat/makerpms.sh
+++ /dev/null
@@ -1,10 +0,0 @@
-#!/bin/sh
-# First we move all our gear into place - a noble move!
-RPMDIR=`rpm --showrc | awk '/^rpmdir/ { print $3}'`
-SPECDIR=`rpm --showrc | awk '/^specdir/ { print $3}'`
-SRCDIR=`rpm --showrc | awk '/^sourcedir/ { print $3}'`
-
-cp -a *.spec $SPECDIR
-cp -a *.patch smb.* samba.log $SRCDIR
-cd $SPECDIR
-rpm --clean -ba samba.spec
diff --git a/examples/redhat/samba-axp.patch b/examples/redhat/samba-axp.patch
deleted file mode 100644
index 662a0361484..00000000000
--- a/examples/redhat/samba-axp.patch
+++ /dev/null
@@ -1,21 +0,0 @@
-*** samba-1.9.16p11/source/Makefile.RPM
---- samba-1.9.16p11/source/Makefile
-***************
-*** 179,186 ****
- # Use this for Linux without shadow passwords
- # contributed by Andrew.Tridgell@anu.edu.au
- # AXPROC defines DEC Alpha Processor
-! # FLAGSM = -DLINUX -DAXPROC
-! FLAGSM = -DLINUX
- LIBSM =
-
- # Use this for Linux with shadow passwords and quota
---- 179,186 ----
- # Use this for Linux without shadow passwords
- # contributed by Andrew.Tridgell@anu.edu.au
- # AXPROC defines DEC Alpha Processor
-! FLAGSM = -DLINUX -DAXPROC
-! # FLAGSM = -DLINUX
- LIBSM =
-
- # Use this for Linux with shadow passwords and quota
diff --git a/examples/redhat/samba-make.patch b/examples/redhat/samba-make.patch
deleted file mode 100644
index 81797baf0e9..00000000000
--- a/examples/redhat/samba-make.patch
+++ /dev/null
@@ -1,121 +0,0 @@
-*** samba-1.9.17a1/source/Makefile.orig Sun May 11 22:44:55 1997
---- samba-1.9.17a1/source/Makefile Sun May 11 22:51:53 1997
-***************
-*** 5,20 ****
-
- # The base manpages directory to put the man pages in
- # Note: $(MANDIR)/man1, $(MANDIR)/man5 and $(MANDIR)/man8 must exist.
-! MANDIR = /usr/local/man
-
- # The directories to put things in. If you use multiple
- # architectures or share the samba binaries across NFS then
- # you will probably want to change this layout.
-! BASEDIR = /usr/local/samba
-! BINDIR = /usr/local/bin
-! SBINDIR = $(BASEDIR)/bin
-! LIBDIR = $(BASEDIR)/lib
-! VARDIR = $(BASEDIR)/var
-
- # The permissions to give the executables
- INSTALLPERMS = 0755
---- 5,20 ----
-
- # The base manpages directory to put the man pages in
- # Note: $(MANDIR)/man1, $(MANDIR)/man5 and $(MANDIR)/man8 must exist.
-! MANDIR = /usr/man
-
- # The directories to put things in. If you use multiple
- # architectures or share the samba binaries across NFS then
- # you will probably want to change this layout.
-! BASEDIR = /usr
-! BINDIR = $(BASEDIR)/bin
-! SBINDIR = $(BASEDIR)/sbin
-! LIBDIR = /etc
-! VARDIR = /var/log
-
- # The permissions to give the executables
- INSTALLPERMS = 0755
-***************
-*** 23,35 ****
- # add -DSYSLOG for syslog support
- # RPM_OPT_FLAGS is needed when building an RPM distribution package
- # for RedHat Linux.
-! # FLAGS1 = $(RPM_OPT_FLAGS)
-! FLAGS1 = -O
- LIBS1 =
-
- # You will need to use a ANSI C compiler. This means under SunOS 4 you can't
- # use cc, instead you will have to use gcc.
-! # CC = gcc
-
- # This may help with some versions of make
- SHELL = /bin/sh
---- 23,35 ----
- # add -DSYSLOG for syslog support
- # RPM_OPT_FLAGS is needed when building an RPM distribution package
- # for RedHat Linux.
-! FLAGS1 = $(RPM_OPT_FLAGS)
-! # FLAGS1 = -O
- LIBS1 =
-
- # You will need to use a ANSI C compiler. This means under SunOS 4 you can't
- # use cc, instead you will have to use gcc.
-! CC = gcc
-
- # This may help with some versions of make
- SHELL = /bin/sh
-***************
-*** 48,54 ****
- LMHOSTSFILE = $(LIBDIR)/lmhosts
-
- # the directory where lock files go
-! LOCKDIR = $(VARDIR)/locks
-
- # set this to the default group you want your machine to appear in
- # for browsing. This can also be set in nmbd (see nmbd(8))
---- 48,54 ----
- LMHOSTSFILE = $(LIBDIR)/lmhosts
-
- # the directory where lock files go
-! LOCKDIR = /var/lock/samba
-
- # set this to the default group you want your machine to appear in
- # for browsing. This can also be set in nmbd (see nmbd(8))
-***************
-*** 71,78 ****
-
- # This is for PAM authentication. RedHat Linux uses PAM.
- # If you use PAM, then uncomment the following lines:
-! # PAM_FLAGS = -DUSE_PAM
-! # PAM_LIBS = -ldl -lpam
-
- # This is for AFS authentication. If you use AFS then set AFS_BASE
- # according to your system layout, and uncomment the other lines as well.
---- 71,78 ----
-
- # This is for PAM authentication. RedHat Linux uses PAM.
- # If you use PAM, then uncomment the following lines:
-! PAM_FLAGS = -DUSE_PAM
-! PAM_LIBS = -ldl -lpam
-
- # This is for AFS authentication. If you use AFS then set AFS_BASE
- # according to your system layout, and uncomment the other lines as well.
-***************
-*** 181,188 ****
- # contributed by Andrew.Tridgell@anu.edu.au
- # AXPROC defines DEC Alpha Processor
- # FLAGSM = -DLINUX -DAXPROC
-! # FLAGSM = -DLINUX
-! # LIBSM =
-
- # Use this for Linux with shadow passwords and quota
- # contributed by xeno@mix.hive.no
---- 181,188 ----
- # contributed by Andrew.Tridgell@anu.edu.au
- # AXPROC defines DEC Alpha Processor
- # FLAGSM = -DLINUX -DAXPROC
-! FLAGSM = -DLINUX
-! LIBSM =
-
- # Use this for Linux with shadow passwords and quota
- # contributed by xeno@mix.hive.no
diff --git a/examples/redhat/samba.log b/examples/redhat/samba.log
deleted file mode 100644
index 2837b45e896..00000000000
--- a/examples/redhat/samba.log
+++ /dev/null
@@ -1,17 +0,0 @@
-/var/log/samba {
- postrotate
- /usr/bin/killall -HUP smbd
- endrotate
-}
-
-/var/log/samba.nmb {
- postrotate
- /usr/bin/killall -HUP nmbd
- endrotate
-}
-
-/var/log/samba.smb {
- postrotate
- /usr/bin/killall -HUP smbd
- endrotate
-}
diff --git a/examples/redhat/samba.spec b/examples/redhat/samba.spec
deleted file mode 100644
index 5b058de5bca..00000000000
--- a/examples/redhat/samba.spec
+++ /dev/null
@@ -1,154 +0,0 @@
-Summary: SMB client and server
-Name: samba
-Version: 1.9.17
-Release: 1
-Copyright: GPL
-Group: Networking
-Source: ftp://samba.anu.edu.au/pub/samba/samba-1.9.17.tar.gz
-Patch: samba-make.patch
-Patch2: samba-axp.patch
-Packager: John H Terpstra [Samba-Team]
-Requires: pamconfig
-BuildRoot: /tmp/samba-root
-
-%description
-Samba provides an SMB server which can be used to provide network
-services to SMB (sometimes called "Lan Manager") clients, including
-various versions of MS Windows, OS/2, and other Linux machines.
-Samba also provides some SMB clients, which complement the built-in
-SMB filesystem in Linux.
-
-Samba uses NetBIOS over TCP/IP (NetBT) protocols and does NOT need
-NetBEUI (Microsoft Raw NetBIOS frame) protocol.
-
-%prep
-%setup
-%patch -p1
-
-%ifarch axp alpha
-%patch2 -p1
-%endif
-
-%build
-cd source
-make RPM_OPT_FLAGS="$RPM_OPT_FLAGS"
-
-%install
-rm -rf $RPM_BUILD_ROOT
-mkdir -p $RPM_BUILD_ROOT
-
-mkdir -p $RPM_BUILD_ROOT/etc
-mkdir -p $RPM_BUILD_ROOT/etc/logrotate.d
-mkdir -p $RPM_BUILD_ROOT/etc/rc.d/init.d
-mkdir -p $RPM_BUILD_ROOT/etc/rc.d/rc0.d
-mkdir -p $RPM_BUILD_ROOT/etc/rc.d/rc1.d
-mkdir -p $RPM_BUILD_ROOT/etc/rc.d/rc2.d
-mkdir -p $RPM_BUILD_ROOT/etc/rc.d/rc3.d
-mkdir -p $RPM_BUILD_ROOT/etc/rc.d/rc5.d
-mkdir -p $RPM_BUILD_ROOT/etc/rc.d/rc6.d
-mkdir -p $RPM_BUILD_ROOT/usr/bin
-mkdir -p $RPM_BUILD_ROOT/usr/sbin
-mkdir -p $RPM_BUILD_ROOT/usr/man/man1
-mkdir -p $RPM_BUILD_ROOT/usr/man/man5
-mkdir -p $RPM_BUILD_ROOT/usr/man/man7
-mkdir -p $RPM_BUILD_ROOT/usr/man/man8
-
-cd source
-cd ..
-for i in nmblookup smbclient smbpasswd smbrun smbstatus testparm testprns
-do
-install -m755 -s source/$i $RPM_BUILD_ROOT/usr/bin
-done
-
-for i in addtosmbpass mksmbpasswd.sh smbtar
-do
-install -m755 source/$i $RPM_BUILD_ROOT/usr/bin
-done
-
-for i in smbd nmbd
-do
-install -m755 -s source/$i $RPM_BUILD_ROOT/usr/sbin
-done
-
-for i in smbclient.1 smbrun.1 smbstatus.1 smbtar.1 testparm.1 testprns.1
-do
-install -m644 docs/$i $RPM_BUILD_ROOT/usr/man/man1
-done
-
-install -m644 docs/smb.conf.5 $RPM_BUILD_ROOT/usr/man/man5
-install -m644 docs/samba.7 $RPM_BUILD_ROOT/usr/man/man7
-install -m644 docs/smbd.8 $RPM_BUILD_ROOT/usr/man/man8
-install -m644 docs/nmbd.8 $RPM_BUILD_ROOT/usr/man/man8
-install -m644 examples/simple/smb.conf $RPM_BUILD_ROOT/etc/smb.conf.sampl
-install -m644 examples/redhat/smb.conf $RPM_BUILD_ROOT/etc/smb.conf
-install -m644 examples/redhat/smbprint $RPM_BUILD_ROOT/usr/bin
-install -m755 examples/redhat/smb.init $RPM_BUILD_ROOT/etc/rc.d/init.d/smb
-ln -sf /etc/rc.d/init.d/smb $RPM_BUILD_ROOT/etc/rc.d/rc0.d/K35smb
-ln -sf /etc/rc.d/init.d/smb $RPM_BUILD_ROOT/etc/rc.d/rc1.d/K35smb
-ln -sf /etc/rc.d/init.d/smb $RPM_BUILD_ROOT/etc/rc.d/rc2.d/K35smb
-ln -sf /etc/rc.d/init.d/smb $RPM_BUILD_ROOT/etc/rc.d/rc3.d/S91smb
-ln -sf /etc/rc.d/init.d/smb $RPM_BUILD_ROOT/etc/rc.d/rc5.d/S91smb
-ln -sf /etc/rc.d/init.d/smb $RPM_BUILD_ROOT/etc/rc.d/rc6.d/K35smb
-
-mkdir -p $RPM_BUILD_ROOT/home/samba
-mkdir -p $RPM_BUILD_ROOT/var/lock/samba
-chmod 775 $RPM_BUILD_ROOT/home/samba
-install -m 644 examples/redhat/samba.log $RPM_BUILD_ROOT/etc/logrotate.d/samba
-
-%clean
-rm -rf $RPM_BUILD_ROOT
-
-%post
-/sbin/pamconfig --add --service=samba --password=none --sesslist=none
-
-if [ ! -f /var/log/samba ]; then
- touch /var/log/samba
- chmod 600 /var/log/samba
-fi
-
-%postun
-if [ "$1" = 0 ] ; then
- /sbin/pamconfig --remove --service=samba --password=none --sesslist=none
-fi
-
-%files
-%attr(-,root,root) %doc docs/*.txt docs/INSTALL.sambatar docs/MIRRORS docs/PROJECTS
-%attr(-,root,root) %doc docs/README.DCEDFS docs/README.jis docs/README.sambatar
-%attr(-,root,root) %doc docs/SMBTAR.notes docs/THANKS docs/announce docs/history
-%attr(-,root,root) %doc docs/samba.faq docs/samba.lsm docs/wfw_slip.htm
-%attr(-,root,root) %doc examples
-%attr(-,root,root) /usr/sbin/smbd
-%attr(-,root,root) /usr/bin/addtosmbpass
-%attr(-,root,root) /usr/bin/mksmbpasswd.sh
-%attr(-,root,root) /usr/bin/smbclient
-%attr(-,root,root) /usr/sbin/nmbd
-%attr(-,root,root) /usr/bin/testparm
-%attr(-,root,root) /usr/bin/testprns
-%attr(-,root,root) /usr/bin/smbrun
-%attr(-,root,root) /usr/bin/smbstatus
-%attr(-,root,root) /usr/bin/nmblookup
-%attr(-,root,root) /usr/bin/smbpasswd
-%attr(-,root,root) /usr/bin/smbtar
-%attr(-,root,root) /usr/bin/smbprint
-%attr(-,root,root) %config /etc/smb.conf
-%attr(-,root,root) %config /etc/smb.conf.sampl
-%attr(-,root,root) %config /etc/rc.d/init.d/smb
-%attr(-,root,root) %config /etc/rc.d/rc3.d/S91smb
-%attr(-,root,root) %config /etc/rc.d/rc5.d/S91smb
-%attr(-,root,root) %config /etc/rc.d/rc0.d/K35smb
-%attr(-,root,root) %config /etc/rc.d/rc1.d/K35smb
-%attr(-,root,root) %config /etc/rc.d/rc6.d/K35smb
-%attr(-,root,root) %config /etc/rc.d/rc2.d/K35smb
-%attr(-,root,root) %config /etc/logrotate.d/samba
-%attr(-,root,root) /usr/man/man1/smbstatus.1
-%attr(-,root,root) /usr/man/man1/smbclient.1
-%attr(-,root,root) /usr/man/man1/smbrun.1
-%attr(-,root,root) /usr/man/man1/smbtar.1
-%attr(-,root,root) /usr/man/man1/testparm.1
-%attr(-,root,root) /usr/man/man1/testprns.1
-%attr(-,root,root) /usr/man/man5/smb.conf.5
-%attr(-,root,root) /usr/man/man7/samba.7
-%attr(-,root,root) /usr/man/man8/smbd.8
-%attr(-,root,root) /usr/man/man8/nmbd.8
-%attr(-,root,nobody) %dir /home/samba
-%attr(-,root,root) %dir /var/lock/samba
diff --git a/examples/redhat/smb.conf b/examples/redhat/smb.conf
deleted file mode 100644
index d615580710a..00000000000
--- a/examples/redhat/smb.conf
+++ /dev/null
@@ -1,196 +0,0 @@
-; The global setting for a RedHat default install
-; smbd re-reads this file regularly, but if in doubt stop and restart it:
-; /etc/rc.d/init.d/smb stop
-; /etc/rc.d/init.d/smb start
-;======================= Global Settings =====================================
-[global]
-
-; workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4
- workgroup = WORKGROUP
-
-; comment is the equivalent of the NT Description field
- comment = RedHat Samba Server
-
-; volume = used to emulate a CDRom label (can be set on a per share basis)
- volume = RedHat4
-
-; printing = BSD or SYSV or AIX, etc.
- printing = bsd
- printcap name = /etc/printcap
- load printers = yes
-
-; Uncomment this if you want a guest account
-; guest account = pcguest
- log file = /var/log/samba-log.%m
-; Put a capping on the size of the log files (in Kb)
- max log size = 50
-
-; Options for handling file name case sensitivity and / or preservation
-; Case Sensitivity breaks many WfW and Win95 apps
-; case sensitive = yes
- short preserve case = yes
- preserve case = yes
-
-; Security and file integrity related options
- lock directory = /var/lock/samba
- locking = yes
- strict locking = yes
-; fake oplocks = yes
- share modes = yes
-; Security modes: USER uses Unix username/passwd, SHARE uses WfW type passwords
-; SERVER uses a Windows NT Server to provide authentication services
- security = user
-; Use password server option only with security = server
-; password server =
-
-; Configuration Options ***** Watch location in smb.conf for side-effects *****
-; Where %m is any SMBName (machine name, or computer name) for which a custom
-; configuration is desired
-; include = /etc/smb.conf.%m
-
-; Performance Related Options
-; Before setting socket options read the smb.conf man page!!
- socket options = TCP_NODELAY
-; Socket Address is used to specify which socket Samba
-; will listen on (good for aliased systems)
-; socket address = aaa.bbb.ccc.ddd
-; Use keep alive only if really needed!!!!
-; keep alive = 60
-
-; Domain Control Options
-; OS Level gives Samba the power to rule the roost. Windows NT = 32
-; Any value < 32 means NT wins as Master Browser, > 32 Samba gets it
-; os level = 33
-; specifies Samba to be the Domain Master Browser
-; domain master = yes
-; Use with care only if you have an NT server on your network that has been
-; configured at install time to be a primary domain controller.
-; domain controller =
-; Domain logon control can be a good thing! See [netlogon] share section below!
-; domain logons = yes
-; run a specific logon batch file per workstation (machine)
-; logon script = %m.bat
-; run a specific logon batch file per username
-; logon script = %u.bat
-; Windows Internet Name Serving Support Section
-; WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
-; the default is NO.
-; wins support = yes
-; WINS Server - Tells the NMBD components of Samba to be a WINS Client
-; Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
-; wins server = w.x.y.z
-; WINS Proxy - Tells Samba to answer name resolution queries on behalf of a non
-; WINS Client capable client, for this to work there must be at least one
-; WINS Server on the network. The default is NO.
-; wins proxy = yes
-
-;============================ Share Declarations ==============================
-[homes]
- comment = Home Directories
- browseable = no
- read only = no
- preserve case = yes
- short preserve case = yes
- create mode = 0750
-
-; Un-comment the following and create the netlogon directory for Domain Logons
-; [netlogon]
-; comment = Samba Network Logon Service
-; path = /home/netlogon
-; Case sensitivity breaks logon script processing!!!
-; case sensitive = no
-; guest ok = yes
-; locking = no
-; read only = yes
-; browseable = yes ; say NO if you want to hide the NETLOGON share
-; admin users = @wheel
-
-; NOTE: There is NO need to specifically define each individual printer
-[printers]
- comment = All Printers
- path = /var/spool/samba
- browseable = no
- printable = yes
-; Set public = yes to allow user 'guest account' to print
- public = no
- writable = no
- create mode = 0700
-
-;[tmp]
-; comment = Temporary file space
-; path = /tmp
-; read only = no
-; public = yes
-
-; A publicly accessible directory, but read only, except for people in
-; the staff group
-[public]
- comment = Public Stuff
- path = /home/samba
- public = yes
- writable = yes
- printable = no
- write list = @users
-
-; Other examples.
-;
-; A private printer, usable only by fred. Spool data will be placed in fred's
-; home directory. Note that fred must have write access to the spool directory,
-; wherever it is.
-;[fredsprn]
-; comment = Fred's Printer
-; valid users = fred
-; path = /homes/fred
-; printer = freds_printer
-; public = no
-; writable = no
-; printable = yes
-;
-; A private directory, usable only by fred. Note that fred requires write
-; access to the directory.
-;[fredsdir]
-; comment = Fred's Service
-; path = /usr/somewhere/private
-; valid users = fred
-; public = no
-; writable = yes
-; printable = no
-;
-; a service which has a different directory for each machine that connects
-; this allows you to tailor configurations to incoming machines. You could
-; also use the %u option to tailor it by user name.
-; The %m gets replaced with the machine name that is connecting.
-;[pchome]
-; comment = PC Directories
-; path = /usr/pc/%m
-; public = no
-; writeable = yes
-;
-;
-; A publicly accessible directory, read/write to all users. Note that all files
-; created in the directory by users will be owned by the default user, so
-; any user with access can delete any other user's files. Obviously this
-; directory must be writable by the default user. Another user could of course
-; be specified, in which case all files would be owned by that user instead.
-;[public]
-; path = /usr/somewhere/else/public
-; public = yes
-; only guest = yes
-; writable = yes
-; printable = no
-;
-;
-; The following two entries demonstrate how to share a directory so that two
-; users can place files there that will be owned by the specific users. In this
-; setup, the directory should be writable by both users and should have the
-; sticky bit set on it to prevent abuse. Obviously this could be extended to
-; as many users as required.
-;[myshare]
-; comment = Mary's and Fred's stuff
-; path = /usr/somewhere/shared
-; valid users = mary fred
-; public = no
-; writable = yes
-; printable = no
-; create mask = 0765
-
diff --git a/examples/redhat/smb.init b/examples/redhat/smb.init
deleted file mode 100755
index ab047e55b4a..00000000000
--- a/examples/redhat/smb.init
+++ /dev/null
@@ -1,32 +0,0 @@
-#!/bin/sh
-
-# Source function library.
-. /etc/rc.d/init.d/functions
-
-# Source networking configuration.
-. /etc/sysconfig/network
-
-# Check that networking is up.
-[ ${NETWORKING} = "no" ] && exit 0
-
-# See how we were called.
-case "$1" in
- start)
- echo -n "Starting SMB services: "
- daemon smbd -D
- daemon nmbd -D
- echo
- touch /var/lock/subsys/smb
- ;;
- stop)
- echo -n "Shutting down SMB services: "
- killproc smbd
- killproc nmbd
- rm -f /var/lock/subsys/smb
- echo ""
- ;;
- *)
- echo "Usage: smb {start|stop}"
- exit 1
-esac
-
diff --git a/examples/redhat/smbprint b/examples/redhat/smbprint
deleted file mode 100755
index 51b15706add..00000000000
--- a/examples/redhat/smbprint
+++ /dev/null
@@ -1,77 +0,0 @@
-#!/bin/sh -x
-
-# This script is an input filter for printcap printing on a unix machine. It
-# uses the smbclient program to print the file to the specified smb-based
-# server and service.
-# For example you could have a printcap entry like this
-#
-# smb:lp=/dev/null:sd=/usr/spool/smb:sh:if=/usr/local/samba/smbprint
-#
-# which would create a unix printer called "smb" that will print via this
-# script. You will need to create the spool directory /usr/spool/smb with
-# appropriate permissions and ownerships for your system.
-
-# Set these to the server and service you wish to print to
-# In this example I have a WfWg PC called "lapland" that has a printer
-# exported called "printer" with no password.
-
-#
-# Script further altered by hamiltom@ecnz.co.nz (Michael Hamilton)
-# so that the server, service, and password can be read from
-# a /var/spool/lpd/PRINTNAME/.config file.
-#
-# In order for this to work the /etc/printcap entry must include an
-# accounting file (af=...):
-#
-# cdcolour:\
-# :cm=CD IBM Colorjet on 6th:\
-# :sd=/var/spool/lpd/cdcolour:\
-# :af=/var/spool/lpd/cdcolour/acct:\
-# :if=/usr/local/etc/smbprint:\
-# :mx=0:\
-# :lp=/dev/null:
-#
-# The /usr/var/spool/lpd/PRINTNAME/.config file should contain:
-# server=PC_SERVER
-# service=PR_SHARENAME
-# password="password"
-#
-# E.g.
-# server=PAULS_PC
-# service=CJET_371
-# password=""
-
-#
-# Debugging log file, change to /dev/null if you like.
-#
-# logfile=/tmp/smb-print.log
-logfile=/dev/null
-
-
-#
-# The last parameter to the filter is the accounting file name.
-# Extract the directory name from the file name.
-# Concat this with /.config to get the config file.
-#
-eval acct_file=\${$#}
-spool_dir=`dirname $acct_file`
-config_file=$spool_dir/.config
-
-# Should read the following variables set in the config file:
-# server
-# service
-# password
-eval `cat $config_file`
-
-#
-# Some debugging help, change the >> to > if you want to same space.
-#
-echo "server $server, service $service" >> $logfile
-
-(
-# NOTE You may wish to add the line `echo translate' if you want automatic
-# CR/LF translation when printing.
-# echo translate
- echo "print -"
- cat
-) | /usr/bin/smbclient "\\\\$server\\$service" $password -U $server -N -P >> $logfile
diff --git a/examples/simple/README b/examples/simple/README
deleted file mode 100644
index 9628aa8260d..00000000000
--- a/examples/simple/README
+++ /dev/null
@@ -1,2 +0,0 @@
-This is the "original" sample config file.
-
diff --git a/examples/simple/smb.conf b/examples/simple/smb.conf
deleted file mode 100644
index 786bf49057c..00000000000
--- a/examples/simple/smb.conf
+++ /dev/null
@@ -1,167 +0,0 @@
-; Configuration file for smbd.
-; ============================================================================
-; For the format of this file and comprehensive descriptions of all the
-; configuration option, please refer to the man page for smb.conf(5).
-;
-; The following configuration should suit most systems for basic usage and
-; initial testing. It gives all clients access to their home directories and
-; allows access to all printers specified in /etc/printcap.
-;
-; Things you need to check:
-; --------------------------
-;
-; 1: Check the path to your printcap file. If you are using a system that does
-; not use printcap (eg., Solaris), create a file containing lines of the
-; form
-;
-; printername|printername|printername|
-;
-; where each "printername" is the name of a printer you want to provide
-; access to. Then alter the "printcap =" entry to point to the new file.
-;
-; If using Solaris, the following command will generate a suitable printcap
-; file:
-;
-; lpc status | grep ":" | sed s/:/\|/ > myprintcap
-;
-; 2: Make sure the "print command" entry is correct for your system. This
-; command should submit a file (represented by %s) to a printer
-; (represented by %p) for printing and should REMOVE the file after
-; printing.
-;
-; One most systems the default will be OK, as long as you get "printing ="
-; right.
-;
-; It is also a good idea to use an absolute path in the print command
-; as there is no guarantee the search path will be set correctly.
-;
-; 3: Make sure the "printing =" option is set correctly for your system.
-; Possible values are "sysv", "bsd" or "aix".
-;
-; 4: Make sure the "lpq command" entry is correct for your system. The default
-; may not work for you.
-;
-; 5: Make sure that the user specified in "guest account" exists. Typically
-; this will be a user that cannot log in and has minimal privileges.
-; Often the "nobody" account doesn't work (very system dependant).
-;
-; 6: You should consider the "security =" option. See a full description
-; in the main documentation and the smb.conf(5) manual page
-;
-; 7: Look at the "hosts allow" option, unless you want everyone on the internet
-; to be able to access your files.
-;
-[global]
- printing = bsd
- printcap name = /etc/printcap
- load printers = yes
- guest account = pcguest
-; This next option sets a separate log file for each client. Remove
-; it if you want a combined log file.
- log file = /usr/local/samba/log.%m
-
-; You will need a world readable lock directory and "share modes=yes"
-; if you want to support the file sharing modes for multiple users
-; of the same files
-; lock directory = /usr/local/samba/var/locks
-; share modes = yes
-
-[homes]
- comment = Home Directories
- browseable = no
- read only = no
- create mode = 0750
-
-[printers]
- comment = All Printers
- browseable = no
- printable = yes
- public = no
- writable = no
- create mode = 0700
-
-; you might also want this one, notice that it is read only so as not to give
-; people without an account write access.
-;
-; [tmp]
-; comment = Temporary file space
-; path = /tmp
-; read only = yes
-; public = yes
-
-;
-; Other examples.
-;
-; A private printer, usable only by fred. Spool data will be placed in fred's
-; home directory. Note that fred must have write access to the spool directory,
-; wherever it is.
-;[fredsprn]
-; comment = Fred's Printer
-; valid users = fred
-; path = /homes/fred
-; printer = freds_printer
-; public = no
-; writable = no
-; printable = yes
-;
-; A private directory, usable only by fred. Note that fred requires write
-; access to the directory.
-;[fredsdir]
-; comment = Fred's Service
-; path = /usr/somewhere/private
-; valid users = fred
-; public = no
-; writable = yes
-; printable = no
-;
-; A publicly accessible directory, but read only, except for people in
-; the staff group
-;[public]
-; comment = Public Stuff
-; path = /usr/somewhere/public
-; public = yes
-; writable = no
-; printable = no
-; write list = @staff
-;
-; a service which has a different directory for each machine that connects
-; this allows you to tailor configurations to incoming machines. You could
-; also use the %u option to tailor it by user name.
-; The %m gets replaced with the machine name that is connecting.
-;[pchome]
-; comment = PC Directories
-; path = /usr/pc/%m
-; public = no
-; writeable = yes
-;
-;
-; A publicly accessible directory, read/write to all users. Note that all files
-; created in the directory by users will be owned by the default user, so
-; any user with access can delete any other user's files. Obviously this
-; directory must be writable by the default user. Another user could of course
-; be specified, in which case all files would be owned by that user instead.
-;[public]
-; path = /usr/somewhere/else/public
-; public = yes
-; only guest = yes
-; writable = yes
-; printable = no
-;
-;
-; The following two entries demonstrate how to share a directory so that two
-; users can place files there that will be owned by the specific users. In this
-; setup, the directory should be writable by both users and should have the
-; sticky bit set on it to prevent abuse. Obviously this could be extended to
-; as many users as required.
-;[myshare]
-; comment = Mary's and Fred's stuff
-; path = /usr/somewhere/shared
-; valid users = mary fred
-; public = no
-; writable = yes
-; printable = no
-; create mask = 0765
-
-
-
-
diff --git a/examples/svr4-startup/README b/examples/svr4-startup/README
deleted file mode 100644
index 8ed9f744770..00000000000
--- a/examples/svr4-startup/README
+++ /dev/null
@@ -1,24 +0,0 @@
-Hi and thanks for this great software.
-
-Solaris (and other sysv) machines have a standardized way of
-starting and shutting down services (you may well know that already).
-
-Here's a piece of code one could place under /etc/init.d
-and create appropriate link from, say
-
- /etc/rc2.d/S99samba.server
-
-to make smbd start and stop automatically with system bootups and
-shutdowns. Each one should edit the lines containing the
-daemon calls to agree with his/her installation (the code below
-works with the defaults) and workgroup setup (we use the -G and -n
-options).
-
-
-I hope this will be of use --- at least it is for me.
-
-Yours,
-
-Timo Knuutila
-knuutila@cs.utu.fi
-
diff --git a/examples/svr4-startup/samba.server b/examples/svr4-startup/samba.server
deleted file mode 100755
index 0a47fdb10ce..00000000000
--- a/examples/svr4-startup/samba.server
+++ /dev/null
@@ -1,38 +0,0 @@
-#!/bin/sh
-#ident "@(#)samba.server 1.0 96/06/19 TK" /* SVr4.0 1.1.13.1*/
-#
-# Please send info on modifications to knuutila@cs.utu.fi
-#
-# This file should have uid root, gid sys and chmod 744
-#
-if [ ! -d /usr/bin ]
-then # /usr not mounted
- exit
-fi
-
-killproc() { # kill the named process(es)
- pid=`/usr/bin/ps -e |
- /usr/bin/grep -w $1 |
- /usr/bin/sed -e 's/^ *//' -e 's/ .*//'`
- [ "$pid" != "" ] && kill $pid
-}
-
-# Start/stop processes required for samba server
-
-case "$1" in
-
-'start')
-#
-# Edit these lines to suit your installation (paths, workgroup, host)
-#
- /opt/samba/bin/smbd -D -s/opt/samba/smb.conf
- /opt/samba/bin/nmbd -D -l/opt/samba/log -s/opt/samba/smb.conf
- ;;
-'stop')
- killproc nmbd
- killproc smbd
- ;;
-*)
- echo "Usage: /etc/init.d/samba.server { start | stop }"
- ;;
-esac
diff --git a/examples/thoralf/smb.conf b/examples/thoralf/smb.conf
deleted file mode 100644
index f9f147474a8..00000000000
--- a/examples/thoralf/smb.conf
+++ /dev/null
@@ -1,152 +0,0 @@
-; Configuration file for smbd (Samba 1.9.15p8)
-; created by Thoralf Freitag. Send comments to:
-; or
-;
-; last edit 24.04.1995 01:11
-;
-;
-
-[global]
-
- protocol = NT1
- ;long filenames for win95
- mangle case = yes
- ;lower and upper letters
- mangled names = yes
- default case = lower
- case sensitive = no
- preserve case = yes
- short preserve case = yes
-
- printing = bsd
- printcap name = /etc/printcap
- lpq cache time = 0
- workgroup = WORKGROUP
- admin users = su
- ;su is allowed to do all !!!
- guest account = ftp
- ;guest is same as user ftp
- default service = reference
- ;is possibly helpful to browsing under win 95
- os level = 2
- log file = /var/adm/log.smb
- max log size = 10
- debug level = 1
- share modes = yes
- lock directory = /var/adm
-
-[JP_360_raw]
- comment = Networkprinter queue for Olivetti JP 360 (untreated RAW format)
- browseable = yes
- available = yes
- public = no
- force user = root
- writable = no
- printable = yes
- printer name = samba
- ;samba is an alias name for an raw_printer in your /etc/printcap
- path = /samba/tmp
- create mode = 0700
-
-[JP_360_mono]
- comment = Networkprinter queue for Olivetti JP 360 Mono (with apsfilter)
- browseable = yes
- available = yes
- public = no
- force user = root
- writable = no
- printable = yes
- printer name = lp
- ;lp means the standard printer in your /etc/printcap
- path = /samba/tmp
- create mode = 0700
-
-[JP_360_color]
- comment = Networkprinter queue for Olivetti JP 360 Color (with apsfilter)
- browseable = yes
- available = yes
- public = no
- force user = root
- writable = no
- printable = yes
- printer name = lp4
- ;my printer need this to print with his color cartridge
- ;--> the lpd is drive to the printer as an color printer
- path = /samba/tmp
- create mode = 0700
-
-[tmp]
- comment = the garbage dump
- browseable = yes
- available = yes
- public = yes
- read only = no
- printable = no
- path = /samba/tmp
- create mask = 0777
-
-[transfer]
- comment = the market place
- browseable = yes
- available = yes
- public = yes
- read only = no
- printable = no
- path = /samba/transfer
- create mask = 0777
-
-[homes]
- comment = home directories
- browseable = no
- ;ONLY the home-dirs are visible, not the service itself
- available = yes
- guest ok = no
- read only = no
- printable = no
- create mode = 0700
-
-[install]
- comment = all of the many install files
- browsable = yes
- available = yes
- public = no
- username = @root, @users
- writable = yes
- read list = @users
- printable = no
- path = /samba/install
- create mode = 0755
-
-[doc-help]
- comment = documentations, helpfiles, FAQ's
- browsable = yes
- available = yes
- public = no
- username = @root, @users
- writable = yes
- read list = @users
- printable = no
- path = /samba/doc
- create mode = 0755
-
-[cd_rom_2]
- comment = the CD in the CD-ROM drive on PANDORA
- browsable = yes
- available = yes
- public = yes
- writable = no
- printable = no
- path = /cdrom
-
-[reference]
- ;the default, if invalid accesses
- comment = PANDORA: Samba LAN manager
- browsable = yes
- ;only as an hint
- available = no
- ;however no access possible
- public = yes
- writable = no
- printable = no
- path = /samba/tmp
-
diff --git a/examples/tridge/README b/examples/tridge/README
deleted file mode 100644
index 11c72f20b3a..00000000000
--- a/examples/tridge/README
+++ /dev/null
@@ -1,8 +0,0 @@
-This is the configuration I use at home. I have 2 client PCs, one
-running Win95, one running alternately WfWg and NTAS3.5. My server is
-a 486dx2-66 Linux box.
-
-Note that I use the %a and %m macros to load smb.conf extensions
-particular to machines and architectures. This gives me a lot of
-flexibility in how I handle each of the machines.
-
diff --git a/examples/tridge/smb.conf b/examples/tridge/smb.conf
deleted file mode 100644
index a2f269f3b76..00000000000
--- a/examples/tridge/smb.conf
+++ /dev/null
@@ -1,101 +0,0 @@
-[global]
- config file = /usr/local/samba/smb.conf.%m
- status = yes
- security = user
- encrypt passwords = yes
- server string = Tridge (%v,%h)
- load printers = yes
- log level = 1
- log file = /usr/local/samba/var/log.%m
- guest account = pcguest
- hosts allow = 192.0.2. localhost
- password level = 2
- auto services = tridge susan
- message command = csh -c '/usr/bin/X11/xedit -display :0 %s;rm %s' &
- read prediction = yes
- socket options = TCP_NODELAY
- valid chars = ö:Ö å:Å ä:Ä
- share modes = yes
- locking = yes
- strict locking = yes
- keepalive = 30
- include = /usr/local/samba/lib/smb.conf.%m
- include = /usr/local/samba/lib/smb.conf.%a
-
-
-[uniprint]
- comment = University Printing
- path = /home/susan/print
- user = susan
- postscript = yes
- print ok = yes
- print command = xmenu -heading "%s" OK&
-
-[testprn]
- comment = Test printer
- path = /tmp
- user = susan
- print ok = yes
- print command = cp %s /tmp/smb.%U.prn
- lpq command = cat /tmp/xxyz
-
-[amd]
- comment = amd area
- path = /mount
- force user = tridge
- read only = no
-
-[homes]
- browseable = no
- guest ok = no
- read only = no
- create mask = 0755
-
-[printers]
- browseable = no
- comment = Printer in Printcap
- guest ok = no
- path = /tmp
- read only = no
- print ok = yes
-
-[dos]
- browseable = yes
- comment = Dos Files
- force group = samba
- create mode = 0775
- path = /home/tridge/dos
- copy = homes
-
-[msoffice]
- browseable = yes
- comment = Microsoft Office
- force group = samba
- create mode = 0775
- path = /data/msoffice
- read only = yes
-
-[root]
- comment = Root Dir
- copy = dos
- path = /
- dont descend = /proc ./proc /etc
-
-[tmp]
- comment = tmp files
- copy = dos
- path = /tmp
- read only = no
-
-
-[cdrom]
- comment = Tridge's CdRom
- path = /mount/cdrom
- read only = yes
- locking = no
-
-[data]
- comment = Data Partition
- path = /data
- read only = yes
- guest ok = yes
diff --git a/examples/tridge/smb.conf.WinNT b/examples/tridge/smb.conf.WinNT
deleted file mode 100644
index f490f830ca7..00000000000
--- a/examples/tridge/smb.conf.WinNT
+++ /dev/null
@@ -1,14 +0,0 @@
-#log level = 4
-#readraw = no
-#writeraw = no
-
-
-
-
-
-
-
-
-
-
-
diff --git a/examples/tridge/smb.conf.fjall b/examples/tridge/smb.conf.fjall
deleted file mode 100644
index 76f4d0e3cad..00000000000
--- a/examples/tridge/smb.conf.fjall
+++ /dev/null
@@ -1,21 +0,0 @@
-;log level = 4
-;readraw = no
-;writeraw = no
-;password level = 4
-;mangled map = (;1 )
-;protocol = lanman1
-;user = susan
-;getwd cache = no
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/examples/tridge/smb.conf.lapland b/examples/tridge/smb.conf.lapland
deleted file mode 100644
index f490f830ca7..00000000000
--- a/examples/tridge/smb.conf.lapland
+++ /dev/null
@@ -1,14 +0,0 @@
-#log level = 4
-#readraw = no
-#writeraw = no
-
-
-
-
-
-
-
-
-
-
-
diff --git a/examples/tridge/smb.conf.vittjokk b/examples/tridge/smb.conf.vittjokk
deleted file mode 100644
index 919ecd15420..00000000000
--- a/examples/tridge/smb.conf.vittjokk
+++ /dev/null
@@ -1,14 +0,0 @@
-;protocol = LANMAN2
-log level = 2
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/examples/validchars/msdos70.out b/examples/validchars/msdos70.out
deleted file mode 100644
index a722b83604f..00000000000
--- a/examples/validchars/msdos70.out
+++ /dev/null
@@ -1,257 +0,0 @@
-255: ok
-254: ok
-253: ok
-252: ok
-251: ok
-250: ok
-249: ok
-248: ok
-247: ok
-246: ok
-245: ok
-244: ok
-243: ok
-242: ok
-241: ok
-240: ok
-239: ok
-238: ok
-237: ok
-236: 237
-235: ok
-234: ok
-233: ok
-232: ok
-231: 232
-230: ok
-229: ok
-228: 229
-227: ok
-226: ok
-225: ok
-224: ok
-223: ok
-222: ok
-221: ok
-220: ok
-219: ok
-218: ok
-217: ok
-216: ok
-215: ok
-214: ok
-213: 73
-212: ok
-211: ok
-210: ok
-209: ok
-208: 209
-207: ok
-206: ok
-205: ok
-204: ok
-203: ok
-202: ok
-201: ok
-200: ok
-199: ok
-198: 199
-197: ok
-196: ok
-195: ok
-194: ok
-193: ok
-192: ok
-191: ok
-190: ok
-189: ok
-188: ok
-187: ok
-186: ok
-185: ok
-184: ok
-183: ok
-182: ok
-181: ok
-180: ok
-179: ok
-178: ok
-177: ok
-176: ok
-175: ok
-174: ok
-173: ok
-172: ok
-171: ok
-170: ok
-169: ok
-168: ok
-167: ok
-166: ok
-165: ok
-164: 165
-163: 233
-162: 224
-161: 214
-160: 181
-159: ok
-158: ok
-157: ok
-156: ok
-155: 157
-154: ok
-153: ok
-152: length 0
-151: 235
-150: 234
-149: 227
-148: 153
-147: 226
-146: ok
-145: 146
-144: ok
-143: ok
-142: ok
-141: 222
-140: 215
-139: 216
-138: 212
-137: 211
-136: 210
-135: 128
-134: 143
-133: 183
-132: 142
-131: 182
-130: 144
-129: 154
-128: ok
-127: ok
-126: ok
-125: ok
-124: open unlink 0
-123: ok
-122: 90
-121: 89
-120: 88
-119: 87
-118: 86
-117: 85
-116: 84
-115: 83
-114: 82
-113: 81
-112: 80
-111: 79
-110: 78
-109: 77
-108: 76
-107: 75
-106: 74
-105: 73
-104: 72
-103: 71
-102: 70
-101: 69
-100: 68
-99: 67
-98: 66
-97: 65
-96: ok
-95: ok
-94: ok
-93: open unlink 0
-92: open unlink 0
-91: open unlink 0
-90: ok
-89: ok
-88: ok
-87: ok
-86: ok
-85: ok
-84: ok
-83: ok
-82: ok
-81: ok
-80: ok
-79: ok
-78: ok
-77: ok
-76: ok
-75: ok
-74: ok
-73: ok
-72: ok
-71: ok
-70: ok
-69: ok
-68: ok
-67: ok
-66: ok
-65: ok
-64: ok
-63: open unlink 0
-62: open unlink 0
-61: open unlink 0
-60: open unlink 0
-59: open unlink 0
-58: open unlink 0
-57: ok
-56: ok
-55: ok
-54: ok
-53: ok
-52: ok
-51: ok
-50: ok
-49: ok
-48: ok
-47: open unlink 0
-46: open unlink 0
-45: ok
-44: open unlink 0
-43: open unlink 0
-42: open unlink 0
-41: ok
-40: ok
-39: ok
-38: ok
-37: ok
-36: ok
-35: ok
-34: open unlink 0
-33: ok
-32: open unlink 0
-31: open unlink 0
-30: open unlink 0
-29: open unlink 0
-28: open unlink 0
-27: open unlink 0
-26: open unlink 0
-25: open unlink 0
-24: open unlink 0
-23: open unlink 0
-22: open unlink 0
-21: open unlink 0
-20: open unlink 0
-19: open unlink 0
-18: open unlink 0
-17: open unlink 0
-16: open unlink 0
-15: open unlink 0
-14: open unlink 0
-13: open unlink 0
-12: open unlink 0
-11: open unlink 0
-10: open unlink 0
-9: open unlink 0
-8: open unlink 0
-7: open unlink 0
-6: open unlink 0
-5: open unlink 0
-4: open unlink 0
-3: open unlink 0
-2: open unlink 0
-1: open unlink 0
-
- valid chars = 73:213 213:73 73:73 33 35 36 37 38 39 40 41 45 48 49 50 51 52 53 54 55 56 57 64 97:65 98:66 99:67 100:68 101:69 102:70 103:71 104:72 105:73 106:74 107:75 108:76 109:77 110:78 111:79 112:80 113:81 114:82 115:83 116:84 117:85 118:86 119:87 120:88 121:89 122:90 94 95 96 123 125 126 127 135:128 132:142 134:143 130:144 145:146 148:153 129:154 156 155:157 158 159 164:165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 160:181 131:182 133:183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198:199 200 201 202 203 204 205 206 207 208:209 136:210 137:211 138:212 161:214 140:215 139:216 217 218 219 220 221 141:222 223 162:224 225 147:226 149:227 228:229 230 231:232 163:233 150:234 151:235 236:237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255
diff --git a/examples/validchars/nwdos70.out b/examples/validchars/nwdos70.out
deleted file mode 100644
index b0dbf628531..00000000000
--- a/examples/validchars/nwdos70.out
+++ /dev/null
@@ -1,257 +0,0 @@
-255: ok
-254: ok
-253: ok
-252: ok
-251: ok
-250: ok
-249: ok
-248: ok
-247: ok
-246: ok
-245: ok
-244: ok
-243: ok
-242: ok
-241: ok
-240: ok
-239: ok
-238: ok
-237: ok
-236: ok
-235: ok
-234: ok
-233: ok
-232: ok
-231: ok
-230: ok
-229: ok
-228: ok
-227: ok
-226: ok
-225: ok
-224: ok
-223: ok
-222: ok
-221: ok
-220: ok
-219: ok
-218: ok
-217: ok
-216: ok
-215: ok
-214: ok
-213: ok
-212: ok
-211: ok
-210: ok
-209: ok
-208: ok
-207: ok
-206: ok
-205: ok
-204: ok
-203: ok
-202: ok
-201: ok
-200: ok
-199: ok
-198: ok
-197: ok
-196: ok
-195: ok
-194: ok
-193: ok
-192: ok
-191: ok
-190: ok
-189: ok
-188: ok
-187: ok
-186: ok
-185: ok
-184: ok
-183: ok
-182: ok
-181: ok
-180: ok
-179: ok
-178: ok
-177: ok
-176: ok
-175: ok
-174: ok
-173: ok
-172: ok
-171: ok
-170: ok
-169: ok
-168: ok
-167: ok
-166: ok
-165: ok
-164: 165
-163: 85
-162: 79
-161: 73
-160: 65
-159: ok
-158: ok
-157: ok
-156: ok
-155: ok
-154: ok
-153: ok
-152: 89
-151: 85
-150: 85
-149: 79
-148: 153
-147: 79
-146: ok
-145: 146
-144: ok
-143: ok
-142: ok
-141: 73
-140: 73
-139: 73
-138: 69
-137: 69
-136: 69
-135: 128
-134: 143
-133: 65
-132: 142
-131: 65
-130: 69
-129: 154
-128: ok
-127: ok
-126: ok
-125: ok
-124: open unlink 0
-123: ok
-122: 90
-121: 89
-120: 88
-119: 87
-118: 86
-117: 85
-116: 84
-115: 83
-114: 82
-113: 81
-112: 80
-111: 79
-110: 78
-109: 77
-108: 76
-107: 75
-106: 74
-105: 73
-104: 72
-103: 71
-102: 70
-101: 69
-100: 68
-99: 67
-98: 66
-97: 65
-96: ok
-95: ok
-94: ok
-93: open unlink 0
-92: open unlink 0
-91: open unlink 0
-90: ok
-89: ok
-88: ok
-87: ok
-86: ok
-85: ok
-84: ok
-83: ok
-82: ok
-81: ok
-80: ok
-79: ok
-78: ok
-77: ok
-76: ok
-75: ok
-74: ok
-73: ok
-72: ok
-71: ok
-70: ok
-69: ok
-68: ok
-67: ok
-66: ok
-65: ok
-64: ok
-63: open unlink 0
-62: open unlink 0
-61: open unlink 0
-60: open unlink 0
-59: open unlink 0
-58: open unlink 0
-57: ok
-56: ok
-55: ok
-54: ok
-53: ok
-52: ok
-51: ok
-50: ok
-49: ok
-48: ok
-47: open unlink 0
-46: open unlink 0
-45: ok
-44: open unlink 0
-43: open unlink 0
-42: open unlink 0
-41: ok
-40: ok
-39: ok
-38: ok
-37: ok
-36: ok
-35: ok
-34: open unlink 0
-33: ok
-32: length 0
-31: open unlink 0
-30: open unlink 0
-29: open unlink 0
-28: open unlink 0
-27: open unlink 0
-26: open unlink 0
-25: open unlink 0
-24: open unlink 0
-23: open unlink 0
-22: open unlink 0
-21: open unlink 0
-20: open unlink 0
-19: open unlink 0
-18: open unlink 0
-17: open unlink 0
-16: open unlink 0
-15: open unlink 0
-14: open unlink 0
-13: open unlink 0
-12: open unlink 0
-11: open unlink 0
-10: open unlink 0
-9: open unlink 0
-8: open unlink 0
-7: open unlink 0
-6: open unlink 0
-5: open unlink 0
-4: open unlink 0
-3: open unlink 0
-2: open unlink 0
-1: open unlink 0
-
- valid chars = 69:130 130:69 69:69 65:131 131:65 65:65 65:133 133:65 65:65 69:136 136:69 69:69 69:137 137:69 69:69 69:138 138:69 69:69 73:139 139:73 73:73 73:140 140:73 73:73 73:141 141:73 73:73 79:147 147:79 79:79 79:149 149:79 79:79 85:150 150:85 85:85 85:151 151:85 85:85 89:152 152:89 89:89 65:160 160:65 65:65 73:161 161:73 73:73 79:162 162:79 79:79 85:163 163:85 85:85 33 35 36 37 38 39 40 41 45 48 49 50 51 52 53 54 55 56 57 64 97:65 98:66 99:67 100:68 101:69 102:70 103:71 104:72 105:73 106:74 107:75 108:76 109:77 110:78 111:79 112:80 113:81 114:82 115:83 116:84 117:85 118:86 119:87 120:88 121:89 122:90 94 95 96 123 125 126 127 135:128 132:142 134:143 144 145:146 148:153 129:154 155 156 157 158 159 164:165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255
diff --git a/examples/validchars/readme b/examples/validchars/readme
deleted file mode 100644
index 6487fbd766a..00000000000
--- a/examples/validchars/readme
+++ /dev/null
@@ -1,101 +0,0 @@
-Note: All files in this directory are DOS formatted (CRLF line terminator).
-
-!!! VIRUS WARNING !!! I do not know if VALIDCHR.COM is virus free !!!
-I think that my system is virus free here because I do not run any games
-or other copied software. I only run Shareware/Freeware etc. from CD-ROMs
-or from registered disks, however I do not use viral scanners because
-I have not registered any (I consider `having no sex' is better than
-`testing for AIDS on a regular basis', if you know what I mean).
-
-This is VALIDCHR, a little DOS program I wrote to create
-an apropriate `valid chars =' config parameter.
-It is freeware and is thought to be distributed freely with Samba.
-
-WARNING:
- Your SMB driver may use another character map as the one VALIDCHR
- sees. The only way you can tell this is that some file names fail.
- Under Win95 everything is fine, though.
-
-Usage:
- c:
- mkdir junk_dir
- cd junk_dir
- a:validchr > a:output.log
- cd ..
- rmdir junk_dir
-
-Siedeffects:
- Files named *.TST may be deleted.
-
-Verification:
- For diagnostic purpose you can run VALIDCHR on a Samba mounted drive.
- Then you can use unix diff to compare the output of the network and
- the hard drive. These two outputs usually differ! However there
- should be few differences. I get following on Win95 (c: visa e:)
- 104c104
- < 152: length 0
- ---
- > 152: 95
- (diff line for `valid chars =' deleted because it's uninteresting)
- You can see, `y diaresis' can be mapped on the network drive while
- it cannot be mapped on the hard drive. Everything else is identical.
- However this gives a hint that one can improve the mapping.
-
-Bugs:
- Yes, probably some.
-
-
-VALIDCHR must be run on the system which character mapping should be probed.
-It must be run on the hard drive for this. VALIDCHR ALTERS THE CURRENT
-DIRECTORY AND REMOVES SOME FILES, SO ALWAYS RUN IT IN A junk DIRECTORY !!!
-You should redirect the output of VALIDCHR. At the end of the output is a
-line like
- valid chars = x:y y:x x:x ... a:b c ...
-which is suitable for your smb.conf file. (you should remove the DOS CR
-character, because DOS uses CRLF while Unix uses LF only.)
-
-Note that some mappings at the beginning of the `valid chars =' line like
-A:B B:A B:B
-might look a little bit strange to you, however sometimes character A
-has to be mapped to character B independently of a default mapping
-to uppercase or lowercase while character B must not be touched. I found
-this out the hard way ... Consider it a crude workaround, because Samba
-lacks the possibility to map characters in one direction only!
-
-VALIDCHR usually issues one warning for character 32.
-You may ignore these and any other warnings.
-
-VALIDCHR does not test for character NUL (this is the directory end marker).
-
-validchr.c is the source code to validchr.com
- You may do anything with the source code (copy, change, sell, burn)
-validchr.com is a Borland C compiled binary.
- Beware, it may contain a virus (if my system contains one).
-nwdos70.out is the output of an VALIDCHR-run under Novell DOS 7.0
- while no codepage (no display.sys) was active.
-msdos70.out is the output of an VALIDCHR-run under MS-DOS 7.0 (Win95 DOS)
- while codepage 850 was active.
-
-I have no other MS-DOS systems at home currently.
-(I have access to MS-DOS 3.0, 3.2, 3.3, 5.0 and 6.22, however I have no time
- to run VALIDCHR there)
-
-Some words to the output
-(for people not fammiliar with programming language C):
-
-probed_char: [text] mapped_char
-
-probed_char is the character probed to be written to disk
-text may be empty or contain:
- open File could not be opened.
- close File could not be closed (should not happen)
- length File name was shortened (usually occurs on SPC)
- unlink File cannot be unlinked (usually when open fails)
-mapped_char is the character which is used by MS-DOS in the directory
- This is usually the uppercase character.
- The mapped character is 0 if something failed (you may say
- that the character is not supported)
-
-The last line in the output is documented in the smb.conf manual page ;)
-
-tino@augsburg.net
diff --git a/examples/validchars/validchr.c b/examples/validchars/validchr.c
deleted file mode 100644
index 415546cb841..00000000000
--- a/examples/validchars/validchr.c
+++ /dev/null
@@ -1,123 +0,0 @@
-/* by tino@augsburg.net
- */
-
-#include
-#include
-
-#include
-
-unsigned char
-test(void)
-{
- DIR *dir;
- struct dirent *dp;
- unsigned char c;
-
- if ((dir=opendir("."))==0)
- {
- perror("open .");
- return 0;
- }
- c = 0;
- while ((dp=readdir(dir))!=0)
- {
- size_t len;
-
- len = strlen(dp->d_name);
- if (len<4)
- continue;
- if (strcmp(dp->d_name+len-4, ".TST"))
- continue;
- if (len!=5)
- {
- fprintf(stderr, "warning: %s\n", dp->d_name);
- printf(" length");
- continue;
- }
- if (c)
- printf(" double%d\n", c);
- c = dp->d_name[0];
- }
- if (closedir(dir))
- perror("close .");
- return c;
-}
-
-int
-main(void)
-{
- char name[256];
- unsigned char map[256], upper[256], lower[256];
- int i, j, c;
- FILE *fd;
-
- if (test())
- {
- printf("There are *.TST files, please remove\n");
- return 0;
- }
- for (i=0; ++i<256; )
- {
- lower[i] = i;
- upper[i] = 0;
- }
- for (i=256; --i; )
- {
- map[i] = i;
- strcpy(name, "..TST");
- name[0] = i;
- printf("%d:", i);
- if ((fd=fopen(name, "w"))==0)
- printf(" open");
- else
- fclose(fd);
- c = test();
- if (unlink(name))
- printf(" unlink");
- if (c==i)
- printf(" ok");
- else
- printf(" %d", c);
- printf("\n");
- if (c!=i)
- {
- upper[c]++;
- lower[c] = i;
- }
- map[i] = c;
- }
-
- /* Uppercase characters are detected above on:
- * The character is mapped to itself and there is a
- * character which maps to it.
- * Lowercase characters are the lowest character pointing to another one.
- * Else it is a one way character.
- *
- * For this reason we have to process the list
- * 1) for 'one way' characters
- * 'one way' is something which is no upper and no lower character.
- * This is an awful, crude and ugly hack due to missing Samba support.
- * 2) for true uppercase/lowercase characters
- * 3) for standalone characters
- * Note that there might be characters which do not fall into 1 to 3.
- */
- printf("\n valid chars =");
- for (i=0; ++i<256; )
- if (map[i] && map[i]!=i && lower[map[i]]!=i)
- {
- if (!upper[i])
- printf(" %d:%d %d:%d %d:%d", /*1*/
- map[i], i, i, map[i], map[i], map[i]);
- else
- fprintf(stderr, "ignoring map %d->%d because of %d->%d\n",
- lower[i], i, i, map[i]);
- }
- for (i=0; ++i<256; )
- if (map[i] && map[i]==i)
- if (upper[i])
- printf(" %d:%d", lower[i], i); /*2*/
- else
- printf(" %d", i); /*3*/
- printf("\n");
- return 0;
-}
diff --git a/examples/validchars/validchr.com b/examples/validchars/validchr.com
deleted file mode 100644
index ce159568369..00000000000
Binary files a/examples/validchars/validchr.com and /dev/null differ
diff --git a/source/.cvsignore b/source/.cvsignore
deleted file mode 100644
index 9b7ea034be9..00000000000
--- a/source/.cvsignore
+++ /dev/null
@@ -1,12 +0,0 @@
-Makefile.RPM
-makefile
-makefile.sunos5
-nmbd
-nmblookup
-smbclient
-smbd
-smbpasswd
-smbrun
-smbstatus
-testparm
-testprns
diff --git a/source/Makefile.RPM b/source/Makefile.RPM
deleted file mode 100644
index ca17cce64ef..00000000000
--- a/source/Makefile.RPM
+++ /dev/null
@@ -1,663 +0,0 @@
-###########################################################################
-# Makefile for Samba SMB client/server for unix
-# Copyright Andrew Tridgell 1992-1996
-###########################################################################
-
-# The base manpages directory to put the man pages in
-# Note: $(MANDIR)/man1, $(MANDIR)/man5 and $(MANDIR)/man8 must exist.
-MANDIR = /usr/man
-
-# The directories to put things in. If you use multiple
-# architectures or share the samba binaries across NFS then
-# you will probably want to change this layout.
-BASEDIR = /usr
-BINDIR = $(BASEDIR)/bin
-SBINDIR = $(BASEDIR)/sbin
-LIBDIR = /etc
-VARDIR = /var
-
-# The permissions to give the executables
-INSTALLPERMS = 0755
-
-# Add any optimisation or debugging flags here
-# add -DSYSLOG for syslog support
-# RPM_OPT_FLAGS is needed when building an RPM distribution package
-# for RedHat Linux.
-FLAGS1 = $(RPM_OPT_FLAGS)
-#FLAGS1 = -O
-LIBS1 =
-
-# You will need to use a ANSI C compiler. This means under SunOS 4 you can't
-# use cc, instead you will have to use gcc.
-CC = gcc
-
-# This may help with some versions of make
-SHELL = /bin/sh
-
-# The following can be useful for compiling on multiple architectures
-# just uncommment them putting the right directory in.
-# srcdir=./
-# VPATH=$(srcdir)
-
-# set these to where to find various files
-# These can be overridden by command line switches (see smbd(8))
-# or in smb.conf (see smb.conf(5))
-SMBLOGFILE = $(VARDIR)/log/log.smb
-NMBLOGFILE = $(VARDIR)/log/log.nmb
-CONFIGFILE = $(LIBDIR)/smb.conf
-LMHOSTSFILE = $(LIBDIR)/lmhosts
-
-# the directory where lock files go
-LOCKDIR = $(VARDIR)/lock/samba
-
-# set this to the default group you want your machine to appear in
-# for browsing. This can also be set in nmbd (see nmbd(8))
-WORKGROUP = WORKGROUP
-
-# set this to the name of the default account, which is the one
-# to use when no username or password is specified. This can be overridden
-# in the runtime configuration file (see smb.conf(5))
-# NOTE: The account "nobody" may not be a good one as
-# on many unixes it may not be able to print. Thus you
-# might have to create a separate guest account that can print.
-GUESTACCOUNT = nobody
-
-# where you are going to have the smbrun binary. This defaults to the
-# install directory. This binary is needed for correct printing
-# and magic script execution. This should be an absolute path!
-# Also not that this should include the name "smbrun" on the end (the
-# name of the executable)
-SMBRUN = $(BINDIR)/smbrun
-
-# This is for PAM authentication. RedHat Linux uses PAM.
-# If you use PAM, then uncomment the following lines:
-PAM_FLAGS = -DUSE_PAM
-PAM_LIBS = -ldl -lpam
-
-# This is for AFS authentication. If you use AFS then set AFS_BASE
-# according to your system layout, and uncomment the other lines as well.
-# AFS_BASE = /usr/afsws
-# AFS_FLAGS = -DAFS_AUTH -I$(AFS_BASE)/include
-# AFS_LIBDIR = $(AFS_BASE)/lib
-# NOTE: You may need to add -laudit in the line below
-# AFS_LIBS = -L$(AFS_LIBDIR) -L$(AFS_LIBDIR)/afs -lkauth -lprot -lubik \
-# -lauth -lrxkad -lsys -ldes -lrx -llwp -lcom_err \
-# $(AFS_LIBDIR)/afs/util.a
-
-# This is for DCE/DFS enablement. Uncomment this so that smbd can
-# operate as an authenticated user identity to operate on files that
-# live in the DCE Distributed Filesystem.
-# DCE_BASE = /opt/dcelocal
-# DCE_FLAGS = -I$(DCE_BASE)/include
-# DCE_LIBDIR = -L$(DCE_BASE)/lib
-# DCE_LIBS =
-
-# This is for SMB encrypted (lanman) passwords.
-# you may wish to add -DREPLACE_GETPASS if your getpass() is limited
-# to 8 chars
-# DES_BASE=/usr/local/libdes
-# DES_FLAGS= -I$(DES_BASE)
-# DES_LIB= -L$(DES_BASE) -ldes
-# PASSWD_FLAGS=-DUSE_LIBDES -DSMB_PASSWD=\"$(BINDIR)/smbpasswd\" -DSMB_PASSWD_FILE=\"$(BASEDIR)/private/smbpasswd\"
-
-######################################
-# VTP-Support
-#
-# uncomment the following two lines to enable VTP-Support
-#VTP_FLAGS = -DWITH_VTP
-#VTP_OBJ = vt_mode.o
-######################################
-
-######################################
-# WHICH AWK? awk is used for automatic prototype generation. GNU awk works
-# where inferior awks don't. Sun is one manufacturer who supplies both
-# a broken awk called 'awk' and a fixed one called 'nawk'. mkproto.awk will
-# only work with the latter, and even that isn't as good as free GNU awk.
-#
-# Leave this uncommented; the OS-specific stuff will override it if required
-AWK = awk
-######################################
-
-#####################################
-# WHICH OPERATING SYSTEM?
-# UNCOMMENT ONE OF THE SECTIONS BELOW
-# MAKE SURE ONLY *ONE* IS UNCOMMENTED
-#
-# The following are additional flags that may apply
-# -DNETGROUP if your machine supports yp netgroups
-# -DSHADOW_PWD if you are using shadow passwords
-# -DGETPWANAM if you wish to use getpwanam() call
-# -DPWDAUTH if you have and want to use the pwdauth() call
-# -DUFC_CRYPT if you want the fast crypt routine
-# -DALLOW_CHANGE_PASSWORD if you want users to be able to set their password
-# remotely (only works on some systems)
-# -DQUOTAS for quota support in disk_free(). This probably only works
-# on some systems.
-# -DFAST_SHARE_MODES=1 if you want the fast shared memory instead of the
-# slow description files for share mode locking. This
-# requires the mmap() and lockf() system calls.
-#
-# NOTE: GETPWANAM & PWDAUTH are mutually exclusive, if you
-# Define one, you should NOT define the other.
-#####################################
-
-#####################################
-# for the JAPANESE EXTENSION
-# select filename's code set for KANJI/KANA in UNIX,
-# apply the following flag
-# -DKANJI=\"\"
-# is select character code set for JAPAN.
-# sjis: if your machine support SJIS
-# euc: if your machine support EUC
-# jis7: if your machine support JIS7
-# jis8: if your machine support JIS8
-# junet: if your machine support jis7 + junet rule
-# hex: if your machine only support 7 bits ascii filename only
-# convert to hexdecimal code preseeding ':'.
-# see also README.jis
-######################################
-
-
-# This is for SUNOS 4. Use the SUNOS5 entry for Solaris 2.
-# Note that you cannot use Suns "cc" compiler
-# as it's not an Ansi-C compiler. Get gcc or acc.
-# Note that if you have adjunct passwords you may need the GETPWANAM
-# or PWDAUTH option. There have been reports that using PWDAUTH may crash
-# your pwdauthd server so GETPWANAM is preferable (and probably faster)
-# contributed by Andrew.Tridgell@anu.edu.au
-# FLAGSM = -DSUNOS4
-# LIBSM =
-# AWK = nawk
-
-# Use this for Linux with shadow passwords
-# contributed by Andrew.Tridgell@anu.edu.au
-# add -DLINUX_BIGCRYPT is you have shadow passwords but don't have the
-# right libraries and includes
-# FLAGSM = -DLINUX -DSHADOW_PWD
-# LIBSM = -lshadow
-
-# Use this for Linux without shadow passwords
-# contributed by Andrew.Tridgell@anu.edu.au
-# AXPROC defines DEC Alpha Processor
-# FLAGSM = -DLINUX -DAXPROC
-FLAGSM = -DLINUX
-LIBSM =
-
-# Use this for Linux with quotas and without shadow passwords
-# contributed by Andrew.Tridgell@anu.edu.au
-# AXPROC defines DEC Alpha Processor
-# FLAGSM = -DLINUX -DAXPROC -DQUOTAS
-# FLAGSM = -DLINUX -DQUOTAS
-# LIBSM =
-
-# Use this for Linux with quota and glibc2
-# contributed by xeno@mix.hive.no
-# Tested on the 2.0.30 kernel and ext2fs filesystem.
-# FLAGSM = -DLINUX -DQUOTAS -DNO_ASMSIGNALH -DGLIBC2
-# LIBSM = -L/lib/libc5-compat -lcrypt
-
-# This is for SUNOS5.4 and later (also known as Solaris 2.4 and later)
-# contributed by Andrew.Tridgell@anu.edu.au
-# FLAGSM = -DSUNOS5 -DSHADOW_PWD -DNETGROUP
-# LIBSM = -lsocket -lnsl
-# AWK = nawk
-
-# This is for SUNOS 5.2 and 5.3 (also known as Solaris 2.2 and 2.3)
-# contributed by hdsi@newtech.net
-# FLAGSM = -DSUNOS5 -DSHADOW_PWD -DNETGROUP -DNO_STRFTIME
-# LIBSM = -lsocket -lnsl
-# AWK = nawk
-
-# This is for UXP/DS
-# contributed by dsfrost@oai6.yk.fujitsu.co.jp
-# FLAGSM = -DSVR4 -DSHADOW_PWD
-# LIBSM = -lsocket -lnsl
-
-# This is for SVR4
-# Contributed by mark@scot1.ucsalf.ac.uk
-# FLAGSM = -DSVR4 -DSHADOW_PWD -DALLOW_CHANGE_PASSWORD
-# LIBSM = -lsocket -lnsl -lc -L/usr/ucblib -lucb
-
-
-# This is for the Motorola 88xxx/9xx range of machines
-# Contributed by RPE@monnet.com
-# FLAGSM = -DSVR4 -DSHADOW_PWD -DGETTIMEOFDAY1
-# LIBSM = -lsocket -lnsl -lc -L/usr/ucblib -lucb
-
-
-# This is for UNIXWARE
-# FLAGSM = -Xa -DSVR4 -DSHADOW_PWD
-# LIBSM = -lsocket -lnsl -lc -L/usr/ucblib -lucb
-
-
-# This is for ULTRIX. Add -DULTRIX_AUTH for Ultrix enhanced security.
-# contributed by iversen@dsfys1.fi.uib.no
-# FLAGSM = -DULTRIX
-# LIBSM =
-
-
-# This is for OSF1 (Alpha)
-# contributed by errath@balu.kfunigraz.ac.at
-# NOTE: You may need -warning_unresolved if you get unresolved symbols
-# FLAGSM = -DOSF1
-# LIBSM =
-
-# This is for OSF1 with DCE/DFS
-# contributed by Jim Doyle
-# FLAGSM = -DOSF1 -DDFS_AUTH -DSIGCLD_IGNORE -DNO_SIGNAL_TEST
-# LIBSM = -ldce -lpthreads -lmach -lc_r
-
-# This is for OSF1 (Alpha) with NIS and Fast Crypt
-# contributed by David Gardiner
-# FLAGSM = -DOSF1 -DNETGROUP -DUFC_CRYPT
-# LIBSM =
-
-
-# This is for OSF1 (Alpha) V2.0 Enhanced Security
-# contributed by Udo Linauer
-# FLAGSM = -DOSF1 -DOSF1_ENH_SEC
-# LIBSM = -lsecurity
-
-
-# This is for AIX
-# contributed by tomc@osi.curtin.edu.au
-# FLAGSM = -DAIX
-# LIBSM =
-
-# This is for AIX 3.2.5 with DCE/DFS
-# contributed by Jim Doyle
-# FLAGSM = -DAIX -DDFS_AUTH -DSIGCLD_IGNORE -DNO_SIGNAL_TEST
-# LIBSM = -lc_r -ldce -lpthreads
-# CC = cc_r
-
-# This is for BSDI
-# contributed by tomh@metrics.com
-# versions of BSDI prior to 2.0 may need to add -DUSE_F_FSIZE for
-# disk usage stats to be correct
-# FLAGSM = -DBSDI
-# LIBSM =
-
-
-# This is for NetBSD. Add -DNETBSD_1_0 if you are using 1.0
-# contributed by noses@oink.rhein.de
-# FLAGSM = -DNETBSD -DSHADOW_PWD
-# LIBSM = -lcrypt
-
-
-# This is for SEQUENT.
-# Contributed by fwk@ix.netcom.com (Frank Keeney) and
-# rpwillia@Pentagon-EMH6.army.mil (Ray Williams)
-# tested on DYNIX/ptx(R) V2.1.0
-# FLAGSM = -DSEQUENT -DSHADOW_PWD -DHAVE_TIMEZONE
-# LIBSM = -lrpc -lsocket -lPW -linet -lnsl -lseq -lsec
-
-
-# This is for SEQUENT PTX 4.1.x
-# Contributed by bressler@iftccu.ca.boeing.com (Rick Bressler)
-# based on Keeny and Williams contribution.
-# tested on DYNIX/ptx(R) V4.1.3
-# FLAGSM = -DSEQUENT -DSHADOW_PWD -DHAVE_TIMEZONE -DPTX4
-# LIBSM = -lrpc -lsocket -lPW -lnsl -lseq -lsec
-
-
-# This is for HP-UX. Note that some systems don't like the -Aa switch.
-# contributed by Pasi.Kaara@atk.tpo.fi
-# You will need -DREPLACE_GETPASS if you use smb encryption
-# FLAGSM = -DHPUX -Aa -D_HPUX_SOURCE -D_POSIX_SOURCE
-# LIBSM =
-
-# This is for HP-UX with DCE/DFS
-# contributed by Jim Doyle
-# FLAGSM = -DHPUX -Aa -D_HPUX_SOURCE -D_POSIX_SOURCE -DDFS_AUTH -D_REENTRANT -I/usr/include/reentrant
-# LIBSM = -ldce -lM -lc_r
-
-# HP-UX 10.x Trusted System
-# Contributed by David-Michael Lincke (dlincke@sgcl1.unisg.ch)
-# FLAGSM = +O3 -Ae -DHPUX -DHPUX_10_TRUSTED
-# LIBSM = -lsec
-
-
-# This is for SGI.
-# contributed by lpc@solomon.technet.sg (Michael Chua)
-# FOR SGI IRIX 4.x.x, use the following line
-# FLAGSM = -DSGI -DHAVE_TIMEZONE
-# LIBSM = -lsun
-
-# FOR SGI IRIX 5.x.x, use this line instead
-# FLAGSM = -DSGI5 -DSHADOW_PWD -DHAVE_TIMEZONE
-# LIBSM =
-
-
-# This is for FreeBSD
-# contributed by kuku@acds.physik.rwth-aachen.de
-# NOTE: You may need to add -DBSD44 if you have password problems
-# FLAGSM = -DFreeBSD
-# LIBSM = -lcrypt
-
-
-# This is for NEXTSTEP Release 2.X
-# No Posix.
-# contributed by brad@cac.washington.edu (Brad Greer)
-# FLAGSM = -DNEXT2
-# LIBSM =
-
-# This is for NEXTSTEP Release 3.0 and greater (including OPENSTEP for Mach).
-# contributed by brad@cac.washington.edu (Brad Greer)
-# additional configuration by pmarcos@next.com (Paul Marcos)
-# For compiling n-way fat executables, you should append the appropriat -arch
-# flags to the FLAGSM variable. Valid flags are:
-# -arch m68k
-# -arch i386
-# -arch hppa
-# -arch sparc
-# To compile 4-way fat, you would append
-# -arch m68k -arch i386 -arch hppa -arch sparc
-# FLAGSM = -DNEXT3_0
-# LIBSM =
-
-
-# NOTE: ISC is also known as "INTERACTIVE"
-# This is for Sunsoft ISC SVR3V4 running in POSIX mode
-# contributed by pim@cti-software.nl (Pim Zandbergen)
-# FLAGSM = -posix -D_SYSV3 -DISC -DSHADOW_PWD
-# LIBSM = -lsec -lcrypt -linet
-
-# This is for Sunsoft ISC SVR3V4 running in iBCS2 mode
-# contributed by pim@cti-software.nl (Pim Zandbergen)
-# FLAGSM = -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_SYSV3\
-# -DISC -DSHADOW_PWD -DREPLACE_GETWD -DREPLACE_RENAME
-# LIBSM = -lsec -lcrypt -linet -lcposix
-
-
-# This is for A/UX 3.0
-# Contributed by root@dolphin.csudh.edu (Jon S. Stevens)
-# FLAGSM = -DAUX
-# LIBSM =
-
-# This is for Altos Series 386/1000
-# Contributed by cal@zls.com
-# FLAGSM = -DALTOS -DHAS_RDCHK
-# LIBSM = -lsocket -lxenix
-
-
-#Note: The SCO entries require the libcrypt library. You can get it via
-#anonymous ftp from ftp.sco.com:/SLS/lng225b.* or ftp.uu.net:/vendors/sco
-#
-# Use this for SCO with shadow passwords. Tested on "Open enterprise 3.0"
-# SCO changes from Heinz Mauelshagen (mauelsha@ez.da.telekom.de)
-# FLAGSM = -DSCO -DSHADOW_PWD -DNETGROUP
-# LIBSM = -lyp -lrpc -lyp -lsec -lsocket -lcrypt_i -lintl
-
-# Use this for SCO with shadow passwords, without YP.
-# Tested on "Open Enterprise Server 3.0" (John Owens john@micros.com)
-# Also, use "CC = cc" above.
-# FLAGSM = -DSCO -DSHADOW_PWD
-# LIBSM = -lsec -lsocket -lcrypt_i
-
-# Use this for SCO with TCB passwords (default).
-# Tested on "Open enterprise 3.0". Contributed by lance@fox.com.
-# CC = cc
-# FLAGSM = -DSCO -DSecureWare
-# LIBSM = -lprot_s -lcrypt -lsocket -lm -lc_s
-
-# Use this for SCO Unix 3.2v2 (ODT 1.1) with TCB passwords (default).
-# Contributed by Stephen.Rothwell@pd.necisa.oz.au
-# N.B. this needs gcc
-# FLAGSM = -DSCO -DSecureWare -DSCO3_2_2
-# LIBSM = -lprot -lcrypt_i -lsocket -lm -lintl
-
-# This is for the european distribution of SCO.
-# Contributed by Urmet.Janes@gwhite.goodwin.ee
-# FLAGSM = -DSCO -DSHADOW_PWD
-# LIBSM = -lsec -lsocket /usr/lib/libcrypt_i.a -lintl
-
-# Use this for SCO OpenServer 5 with TCB passwords (default).
-# contributed by Scott Michel
-# you may also like to add the -dy switch (recommended by Marnus van
-# Niekerk, mvn@pixie.co.za)
-# CC = cc -Xc
-# FLAGSM = -DSCO -DSecureWare -DEVEREST -DUSE_MMAP
-# LIBSM = -lprot -lcurses -lcrypt -lsocket -lPW -lm -lx -lc_s -lc
-
-
-# This is for intergraph.
-# contributed by cjkiick@flinx.b11.ingr.com
-# modified by ttj@sknsws61.sjo.statkart.no
-# FLAGSM = -DCLIX -D_INGR_EXTENSIONS=1
-# LIBSM = -lbsd -lc_s
-
-# This is for DGUX.
-# Contributed by ross@augie.insci.com (Ross Andrus)
-# FLAGSM = -DDGUX
-# LIBSM =
-
-# This is for Apollo Domain/OS sr10.3 (systype = BSD4.3)
-# Added 1994-07-08 Stephen C. Steel
-# additional patches by jmi@csd.cri.dk (John Mills)
-# you may need the "-A ansi" switch to cc
-# FLAGSM = -DAPOLLO -D_INCLUDE_BSD_SOURCE -D_INCLUDE_XOPEN_SOURCE
-# LIBSM =
-
-
-# RiscIX.
-# contributed by Jim Barry and
-# Charles Gay-Jones
-# FLAGSM = -DRiscIX -DNOSTRDUP
-# LIBSM =
-
-
-# This is for System V with some berkely extensions (Motorola 88k R32V3.2).
-# contributed by tonyb@plaza.ds.adp.com (Tony D. Birnseth)
-# FLAGSM = -DM88K_R3
-# LIBSM = -lgen -lbsd -lnsl
-
-
-# This is for DNIX.
-# contributed by Peter Olsson
-# NOTE: You may need an updated libc.a from your vendor as older
-# versions have broken mktime calls and no initgroups() call
-# NOTE2: You may need -lpasswd if you use shadow passwords
-# NOTE3: Please read the file DNIX.txt in the docs directory. It
-# contains important information about uid handling under DNIX, you may
-# need to patch your C library.
-# FLAGSM = -DDNIX -I/usr/include/bsd
-# LIBSM = -ln
-
-
-# This is for Cray, Unicos 8.0
-# contributed by velo@sesun3.epfl.ch (Martin Ouwehand)
-# FLAGSM = -DCRAY -U__STDC__ -DQUOTAS
-# LIBSM =
-
-# This is for Convex
-# contributed by Victor Balashov
-# and Ulrich Hahn
-# FLAGSM= -DCONVEX -DSHADOW_PWD
-# LIBSM=
-
-# This is for SMP_DC.OSx v1.1-94c079 on Pyramid S series
-# contributed by jeffrey@itm.org
-# FLAGSM = -DSOLARIS -DSHADOW_PWD -DBSD_COMP
-# LIBSM = -lsocket -lnsl
-
-# This is for QNX 4.22
-# Contributed by eldo@invisa.satlink.net (Eldo Loguzzo)
-# FLAGSM = -DQNX -DGUEST_SESSSETUP=1
-# LIBSM =
-
-
-# This is for SONY NEWS, NEWS-OS 4.2.x
-# contributed by sky@sm.sony.co.jp (Katushi Sato)
-# FLAGSM = -DNEWS42 -DKANJI=\"sjis\"
-# LIBSM =
-
-
-# This is for SONY NEWS, NEWS-OS 6.1.x
-# contributed by kobo@sm.sony.co.jp (Yoichi Kobori)
-# FLAGSM = -Xa -DSVR4 -DNEWS61 -DSHADOW_PWD -DNETGROUP -DGETTIMEOFDAY1 -DKANJI=\"euc\"\ -D_SONYILS_H
-# LIBSM = -lsocket -lnsl
-
-
-# This is for OS/2 using EMX 0.9b
-# Contributed by jasonr@pec.co.nz (Jason Rumney)
-# FLAGSM = -DOS2
-# LIBSM = -Zexe -lsocket
-
-
-# This is for LYNX 2.3.0 (gcc v2.6)
-# Contributed by woelfel@hpe.fzk.de (Manfred Woelfel)
-# FLAGSM = -DLYNX -DUFC_CRYPT -mposix
-# LIBSM = -lbsd
-
-
-# This is for MachTen (a unix like system for Macintoshes)
-# contributed by Trevor Strohman (trev@figment.tenon.com)
-# FLAGSM = -DMACHTEN
-# LIBSM =
-
-
-# RISCOs 5.0B
-# contributed by John Agnew
-# FLAGSM = -systype svr4 -std -DSVR4
-# LIBSM = -lsocket -lnsl -lc -L/usr/ucblib -lucb
-
-
-# This is for B.O.S. (Bull Operating System)
-# Contributed by koine@fileita.it
-# FLAGSM = -DBOS -DNO_RESOURCEH -DUSE_WAITPID
-# LIBSM = -linet
-
-
-# This for Amiga using GCC and ixemul.library 43.0 or later.
-# contributed by Rask Ingemann Lambertsen
-# The binaries will support both AmiTCP and AS225R2 compatible
-# protocol stacks because of the use of ixnet.library.
-# Other protocol stacks will be supported automatically if
-# support for them is added to ixnet.library.
-# The binaries will have automatic stack extension :-)
-# smbd must be run from inetd :-(
-# FLAGSM = -DAMIGA -Dfork=vfork -mstackextend
-# LIBSM =
-
-
-
-######################################################################
-# DON'T EDIT BELOW THIS LINE
-######################################################################
-
-CFLAGS1 = $(FLAGS1) -DSMBLOGFILE=\"$(SMBLOGFILE)\" -DNMBLOGFILE=\"$(NMBLOGFILE)\"
-CFLAGS2 = -DCONFIGFILE=\"$(CONFIGFILE)\" -DLMHOSTSFILE=\"$(LMHOSTSFILE)\"
-CFLAGS3 = -DLOCKDIR=\"$(LOCKDIR)\" -DSMBRUN=\"$(SMBRUN)\"
-CFLAGS4 = -DWORKGROUP=\"$(WORKGROUP)\" -DGUEST_ACCOUNT=\"$(GUESTACCOUNT)\"
-CFLAGS5 = $(CFLAGS1) $(CFLAGS2) $(CFLAGS3) $(CFLAGS4) $(FLAGSM) $(AFS_FLAGS)
-CFLAGS = $(CFLAGS5) $(PAM_FLAGS) $(DCE_FLAGS) $(DES_FLAGS) $(PASSWD_FLAGS) $(VTP_FLAGS)
-LIBS = $(LIBS1) $(LIBSM) $(PAM_LIBS) $(DCE_LIBS) $(DES_LIB)
-
-SPROGS = smbd nmbd
-PROGS1 = smbclient testparm testprns smbrun smbstatus smbpasswd
-PROGS = $(PROGS1) nmblookup
-SCRIPTS = smbtar addtosmbpass
-
-all : CHECK $(SPROGS) $(PROGS)
-
-CHECK :
- @$(SHELL) $(srcdir)checkos.sh $(FLAGSM)
- @echo "Using CFLAGS = $(CFLAGS)"
- @echo "Using LIBS = $(LIBS)"
-
-INCLUDES1 = version.h local.h includes.h smb.h
-INCLUDES2 = trans2.h
-INCLUDES = $(INCLUDES1) $(INCLUDES2)
-
-UTILOBJ1 = util.o system.o charset.o kanji.o fault.o smbencrypt.o charcnv.o
-UTILOBJ2 = $(UTILOBJ1) md4.o loadparm.o params.o pcap.o username.o time.o
-UTILOBJ = $(UTILOBJ2) interface.o replace.o
-PARAMOBJ = $(UTILOBJ) ufc.o smbpass.o access.o shmem.o
-SMBDOBJ1 = $(PARAMOBJ) trans2.o pipes.o message.o dir.o printing.o locking.o
-SMBDOBJ2 = ipc.o reply.o mangle.o chgpasswd.o password.o quotas.o uid.o
-SMBDOBJ = predict.o $(SMBDOBJ1) $(SMBDOBJ2) $(VTP_OBJ)
-NMBDOBJ1 = nmblib.o namepacket.o nameresp.o nmbsync.o nameannounce.o nameelect.o
-NMBDOBJ2 = namedbresp.o namedbwork.o namedbserver.o namedbsubnet.o namedbname.o
-NMBDOBJ3 = nameservresp.o nameservreply.o namelogon.o namebrowse.o namework.o nameserv.o clientutil.o
-NMBDOBJ = $(UTILOBJ) $(NMBDOBJ1) $(NMBDOBJ2) $(NMBDOBJ3)
-.SUFFIXES:
-.SUFFIXES: .c .o .h
-
-.c.o: $(INCLUDES)
- @echo Compiling $*.c
- @$(CC) $(CFLAGS) -c $(srcdir)$*.c
-
-smbd: server.o $(SMBDOBJ)
- @echo Linking smbd
- @$(CC) $(CFLAGS) -o smbd server.o $(SMBDOBJ) $(LIBS) $(AFS_LIBS)
-
-smbrun: smbrun.o
- @echo Linking smbrun
- @$(CC) $(CFLAGS) -o smbrun smbrun.o $(LIBS)
-
-nmblookup: nmblookup.o namequery.o nmblib.o $(UTILOBJ)
- @echo Linking nmblookup
- @$(CC) $(CFLAGS) -o nmblookup nmblookup.o namequery.o nmblib.o $(UTILOBJ) $(LIBS)
-
-nmbd: nmbd.o $(NMBDOBJ)
- @echo Linking nmbd
- @$(CC) $(CFLAGS) -o nmbd nmbd.o $(NMBDOBJ) $(LIBS)
-
-smbclient: client.o clitar.o getsmbpass.o namequery.o nmblib.o $(UTILOBJ)
- @echo Linking smbclient
- @$(CC) $(CFLAGS) -o smbclient client.o clitar.o getsmbpass.o namequery.o nmblib.o $(UTILOBJ) $(LIBS)
-
-smbstatus: status.o $(PARAMOBJ)
- @echo Linking smbstatus
- @$(CC) $(CFLAGS) -o smbstatus status.o $(PARAMOBJ) $(LIBS)
-
-testparm: testparm.o $(PARAMOBJ)
- @echo Linking testparm
- @$(CC) $(CFLAGS) -o testparm testparm.o $(PARAMOBJ) $(LIBS)
-
-testprns: testprns.o $(PARAMOBJ)
- @echo Linking testprns
- @$(CC) $(CFLAGS) -o testprns testprns.o $(PARAMOBJ) $(LIBS)
-
-smbpasswd: smbpasswd.o getsmbpass.o $(PARAMOBJ)
- @echo Linking smbpasswd
- @$(CC) $(CFLAGS) -o smbpasswd smbpasswd.o getsmbpass.o $(PARAMOBJ) $(LIBS)
-
-install: installbin installman installscripts
-
-installbin: all
- @$(SHELL) $(srcdir)installbin.sh $(INSTALLPERMS) $(BASEDIR) $(SBINDIR) $(LIBDIR) $(VARDIR) $(SPROGS)
- @$(SHELL) $(srcdir)installbin.sh $(INSTALLPERMS) $(BASEDIR) $(BINDIR) $(LIBDIR) $(VARDIR) $(PROGS)
-
-installscripts:
- @$(SHELL) $(srcdir)installscripts.sh $(INSTALLPERMS) $(BINDIR) $(SCRIPTS)
-
-# revert to the previously installed version
-revert:
- @$(SHELL) $(srcdir)revert.sh $(SBINDIR) $(SPROGS) $(SCRIPTS)
- @$(SHELL) $(srcdir)revert.sh $(BINDIR) $(PROGS) $(SCRIPTS)
-
-installman:
- @$(SHELL) $(srcdir)installman.sh $(MANDIR) $(srcdir)
-
-uninstall: uninstallman uninstallbin uninstallscripts
-
-uninstallman:
- @$(SHELL) $(srcdir)uninstallman.sh $(MANDIR) $(srcdir)
-
-uninstallbin:
- @$(SHELL) $(srcdir)uninstallbin.sh $(INSTALLPERMS) $(BASEDIR) $(SBINDIR) $(LIBDIR) $(VARDIR) $(SPROGS)
- @$(SHELL) $(srcdir)uninstallbin.sh $(INSTALLPERMS) $(BASEDIR) $(BINDIR) $(LIBDIR) $(VARDIR) $(PROGS)
-
-uninstallscripts:
- @$(SHELL) $(srcdir)uninstallscripts.sh $(INSTALLPERMS) $(BINDIR) $(SCRIPTS)
-
-clean:
- rm -f core *.o *~ $(PROGS) $(SPROGS)
-
-proto:
- @$(SHELL) $(srcdir)checkos.sh $(FLAGSM)
- $(AWK) -f mkproto.awk *.c > proto.h
-
-realclean: clean
-
diff --git a/source/change-log b/source/change-log
deleted file mode 100644
index 42a27fe6f68..00000000000
--- a/source/change-log
+++ /dev/null
@@ -1,1878 +0,0 @@
-SUPERCEDED Change Log for Samba
-^^^^^^^^^^
-
-Unless otherwise attributed, all changes were made by
-Andrew.Tridgell@anu.edu.au. All bugs to samba-bugs@samba.anu.edu.au.
-
-NOTE: THIS LOG IS IN CHRONOLOGICAL ORDER
-
-NOTE: From now on the cvs.log file will be used to give a complete log of
-changes to samba. This change-log is now obsolete.
-
-1.5.00 announced to mailing list
-
-1.5.01 1/12/93
- - configuration through makefile only
- - fixed silly bug that made the client not accept dir's from
- the server
- - tested and updated include files for ultrix, aix and solaris
- - several things fixed thanks to pierson@ketje.enet.dec.com
- who provided invaluable help and advice.
-
-1.5.02 1/12/93
- - added username option to services file so connection
- as non guest from lanmanager is possible
- - made server abort when it can't read/write on a socket
- - added logging to client
-
-1.5.03 2/12/93
- - printing now works
- - fixed a minor bug to do with hidden and system attributes
-
-1.5.04 2/12/93
- - added reduce_name() call to fill in security hole.
- - cleanup up debug stuff a little
-
-1.5.05 2/12/93
- - fixed bug in reduce_name that affects services with base paths
- that have a soft link in them.
-
-1.5.06 3/12/93
- - used the reserved server field in the search status to hold the
- directory pointer. This allows lots of directories to be open
- at once by clients without stuffing things up.
- - preserved all the client reserved bytes in the search status
- in case they actually use them. Hopefully this will fix the annoying
- empty directory dir bug. (it does)
-
-1.5.07 3/12/93
- - fixed silly bug that caused volume ids to appear twice
- - fixed a wrote-too-few bug in smb_send()
-
-1.5.08 3/12/93
- - did the SMBsearch properly. It can now handle recursive searches.
- In order to keep the required dir info I encode the dirptr and
- the current dir offset (from telldir) into 5 bytes by using a table
- on the last 7 bits of the first byte. The first bit is always on
- as this byte must by != 0
- This is all put in the "server reserved" search field.
-
-1.5.09 5/12/93
- - added a prototype nameserver. It's broken but can at least interpret
- incoming packets.
- - minor fixes to the server and client
-
-
-1.5.10 5/12/93
- - fixed silly unsigned/signed char bug that made dosshell noot see all files
- - added nmbd to Makefile
-
-1.5.11 6/12/93
- - made the volume label appear as the service name, rather than "Remote"
- - made the nmbd actually work (a little) for lanman for dos
-
-1.5.12 7/12/93
- - fixed broadcasting in the nameserver
- - the smbd now correctly sets the pid and uid
- - nmbd now seems to work enough to satisfy the MS client.
-
-
-1.5.13 7/12/93
- - fixed a silly bug that truncated filenames
- - added -B option to nameserver to specify bcast address
- - added -R option to nameserver to prevent name registering
- - fixed minor read() bug. Does this fix the "cmp" bug?
-
-1.5.14 8/12/93
- - fixed a bug in send_login() in the client. Thanks to
- tim.hudson@gslmail.mincom.oz.au for pointing this out.
- - changed name_mangle() to pad to minimum of 32 bytes with spaces
- - changed the returned buffer size in reply_connect() to not
- count the 4 byte length field. This fixes the "can execute" bug
- and the "comp" bug
- - once again re-wrote the directory pointer handling code.
- now "tree" works correctly
-
-1.5.15 9/12/93
- - fixed name mangle bug introduced in 1.5.14 which stopped
- nameserver from working
-
-1.5.16 9/12/93
- - arrgh. another silly bug in name_mangle() causes the client to die.
-
-
-1.5.17 13/12/93
- - some cosmetic cleanups to the code
- - changed make_connection not to lower case the password (thanks
- to bryan@alex.com)
- - fixed accept() bug not initialising in_addrlen (thanks to
- bogstad@cs.jhu.edu)
- - fixed cd bug in client.c (thanks to joergs@toppoint.de)
- - lots of fixes to the nameserver to read_socket and
- associated routines. It should now correctly reply to the originating
- address and use the correct broadcast.
- (thanks to troyer@saifr00.ateng.az.honeywell.com)
- - SVR4 patches from mark@scot1.ucsalf.ac.uk
- - changed the default BUFFER_SIZE to 0xFFFF
-
-1.5.18 15/12/93
- - minor fix to reply_printqueue() to zero data buffer array.
- - added print command to client.
- - fixed minor bug in cmd_put() in client where a handle could
- be closed without being previously opened.
- - minor cleanups to the client
- - minor solaris fixes from lonnie@itg.ti.com
- - SYSV, shadow password and dfree() fixes from mark@scot1.ucsalf.ac.uk
- - fixed reply_delete() to not delete read-only files
- - fixed infinite loop in reply_delete on "del ."
- Thanks to mark@scot1.ucsalf.ac.uk for pointing this out.
- - posix mode definitions and changes from mark@scot1.ucsalf.ac.uk
-
-
-1.5.19 18/12/93
- - another very minor fix to dfree().
- - minor change to SVR4 makefile entry from rossw@march.co.uk
- - changed reply_open not to open directories, this fixes the
- "copy .." bug pointed out by mark@scot1.ucsalf.ac.uk
- - changed dos_mode() so it doesn't return hidden and system info
- on directories.
- - changed get_dir_entry() not to descend into proc/self under linux
- control this with the DONT_DESCEND define in includes.h
- - changed smb_setlen() to add in the SMB id. (thanks
- to troyer@saifr00.ateng.az.honeywell.com)
- - fixed minor bug in reply_dir() so it won't return a ACCESS_DENIED
- when searching a directory that is unreadable
- - removed second stat() from get_dir_entry() (speed up)
- - made null searches close the dirptr (fixes big filesystem problem)
- - fixed clean_name for cd .. (from magnus@axiom.se)
-
-
-1.5.20 28/12/93
- - added debug statement in case of SMBcreate with volid set (leefi@microsoft.com)
- - fixed a bug in dptr_close() so it sets the next_key to a better
- value, this fixes a annoying dir bug
- - LOTS of changes from jeremy@netcom.com (Jeremy Allison). This
- makes it possible to at least connect to a NT server with the client
- and also fixes up much of the socket/process code. This also includes
- stuff for compiling on a sun386
- - got the client working with the Syntax server (a commercial
- smb-based server). This required a few minor changes so the xmit
- sizes were negotiated properly.
- - added support for OSF1, tested on a DEC3000/400 alpha.
- - fixed the ifconf support under ultrix
-
-1.5.21 31/12/93
- - minor cosmetic change to reduce_name()
- - changes for HPUX from ppk@atk.tpo.fi (Pasi Kaara)
- - minor fix to nameserver
- - revamped configuration file format. It now takes a Windows-style
- (.INI style) configuration file. See the file services for
- full details of the format. New files: loadparm.c, loadparm.h,
- params.c, params.h, testparm.c. Several changes to smb.h, local.h,
- server.c, Makefile. The services structure is no longer visible
- to the rest of the system. (Karl Auer)
- - added ability to specify a print command on a per service basis
- and globally via the configuration file. Also allows guest account
- to be specified in the configuration file. Made appropriate changes
- to server.c so that these data items are obtained from the config
- module rather than from hardcoded strings (though the hardcoded
- strings are still the source of the defaults). (Karl Auer)
- - renamed old-style configuration file to services.old (Karl Auer)
- - changed README to reflect new configuration details. (Karl Auer)
- - removed an item from the bugs wishlist (now supplied!) (Karl Auer)
- - protected smb.h against multiple compilation. (Karl Auer)
- - protected local.h against multiple compilation. (Karl Auer)
- - made config stuff do dynamic allocation
- - added "homes" capability
- - added create_mask to each service in config
-
-1.5.22 3/1/94
- - added "root dir" option for extra security
- - added -n option to client (useful for OS/2)
- - changed operation of -n to nameserver to be more useful
- - patches from Jeremy Allison (jeremy@netcom.com)
- fixing bug in set_message(), fixing up wait3() for SYSV,
- making cd check the path in the client, allowing fetching to stdin
- in client, and enhancing prompt in client to include directory.
- - made the -D become_daemon() actually detach from the tty. This
- may need tuning for different flavors of unix.
- - added "dont descend" option to each service to prevent infinite
- loops on recursive filesystems.
- - updated README to add "running as a daemon" and a simple
- smb.conf file.
- - HP/UX fixes from ppk@atk.tpo.fi
- - made lock calls only if opened with write enabled, as pointed out
- by gadams@ddrive.demon.co.uk
-
-1.5.23 4/1/94
- - minor fix to logging of data in receive_smb(). It used to
- miss the last 4 bytes of packets.
- - added the pid,uid and mid fields to the negotiation phase of
- the client.
- - made client able to print from stdin
- - added password on command line for client
- - created a sample printcap input filter "smbprint"
- - several fixes to client to work with OS/2
- - added mput, mget, prompt and lcd to client
-
-1.5.24 5/1/94
- - a resend of 1.5.23 as I managed to not include the new
- prompt, mput and mget code.
-
-1.5.25 7/1/94
- - change -B on nameserver so it can override the broadcast address
- - minor changes to printing in client so OS/2 server can handle it.
- - fixed reply_access() where OK was not being initialised
- - added "max xmit" to global parameters.
- - changed create to open with O_RDWR instead of O_WRONLY
- - added printmode command to client
- - made help return extra help on a specified command in client
- - fixed return code in chkpath
- - added "recurse" and "lowercase" options to client
- - fixed some error codes from server
- - added -I option to client
- - fix for become_daemon() for HPUX from ppk@atk.tpo.fi
- - added "hosts allow" and "hosts deny" to server
- - added keepalives to server
- - added "access" feature to testparam
- - NetBSD patches from sreiz@aie.nl
-
-1.5.26 8/1/94
- - changed semantics of hosts access code to do more sensible defaults
- when either of "hosts allow" or "hosts deny" is blank
- - added the SO_KEEPALIVE option to configurations of sockets in the
- server
- - made some of the SVAL fns into macros to keep fussy compilers from
- complaining
- - fixed several null pointer bugs in check_access(). These bugs
- made 1.5.25 unuseable for many people.
- - fixed null pointer reference of lp_dontdescend()
- - reload services file after each new connection.
-
-1.5.27 11/1/94
- - fixed opening mode for reply_open() in server
- - patches from Jeremy Allison (jeremy@netcom.com) to support the
- "core+" protocol. The patches also inclued some other features, such
- as a new read_with_timeout() call (used by SMBreadbraw), and auto
- detection of the need to create a socket.
- - changed the default KEEPALIVE value to 0, as it caused
- problems with Lanmanager.
- - added tar capability to client when getting files
- - altered unix_mode() to return x bits for directories
- - fixed bug in trim_string()
-
-1.5.28 12/1/94
- - cleaned up the debug levels a little so debug level 1 is a practical
- level for general use
- - fixed a bug in add_a_service() where a freed pointer was referenced. Thanks
- to bryan@alex.com for finding the bug.
- - fixed bug in time structure handling in server and client. Thanks to
- bryan@alex.com for pointing out the bug.
-
-
-1.5.29 15/1/94
- - fixed a silly bug in reply_open(). Thanks to
- jeremy@netcom.com for pointing this out.
- - fixed debug levels in client to be more sensible
- - added raw read to client
- - added -B option to client
- - fixed several bugs in the client, mostly to do with the tar option
- - added -E option to client
-
-1.5.30 16/1/94
- - added lots of prototypes so compilers don't complain
- - fixed minor bug in reply_rename() (thanks to ppk@atk.tpo.fi)
- - added more support for LANMAN1.0 protocol.
- - added SESSION SETUP AND X call
- - added READ AND X call
- - added TREE CONNECT AND X call
- - added support for setbuffer for HPUX (thanks to ppk@atk.tpo.fi)
-
-1.5.31 29/1/94
- - added support for user level security in smbclient eg:
- smbclient "\\SERVER\SHARE" -U USERNAME%PASSWORD
- - added error message decode as per SMB File Sharing
- protocol extensions. (thanks to merik@blackadder.dsh.oz.au)
- - added selection masks to smbclient that recurse down directory
- tree. eg: mget *.* with recurse and mask *.c on will retrieve all
- *.c files in the tree.
- - patches for FreeBSD from kuku@acds.physik.rwth-aachen.de
- - changed reduce_name() to trim ./ from front of strings and / from
- back
- - fixed a nasty bug in trim_string().
- - numerous small changes to lots of stuff that I didn't
- document while I was doing them. Sorry :-(
- - slightly updated sockspy
-
- - The following was done by Karl Auer (Karl.Auer@anu.edu.au)
- - added processing in configuration file of a [printers] section. Allows
- connection to any printer specified in /etc/printcap (or the file
- specified in the global parameter 'printcap name').
- - added full processing of 'available' flag to configuration file. A
- service can now be 'turned off' by specifying 'available = no'. Of
- dubious utility.
- - added 'printcap =' parameter to [global] section in the configuration
- file. This allows the normal /etc/printcap to be bypassed when
- checking printer names for dynamic printer connections via [printers].
- - added 'printer name =' parameters to both the [global] section and
- services sections of the configuration file. This allows the printer
- name only to be set, without having to specify an entire print
- command.
- - added some synonyms: 'writable' and 'write ok' have the opposite sense
- to 'read only'. 'public' may be used instead of 'guest ok'. 'printer'
- may be used instead of 'printer name'. 'printable' is the same as
- 'print ok'. 'root' may be used instead of 'root dir' or 'root
- directory'.
- - added lots more detail to the sample configuration file to take
- account of the above.
- - many minor fixes to internal documentation in the configuration
- sources.
- - also - Man pages!
-
-
-1.5.32 3/2/94
- - addition of smbd, smbclient and testparm man pages
- from Karl Auer
- - zombie process fix from lendecke@namu01.gwdg.de
- - added capability to nmbd to serve names available
- via gethostbyname().
-
-1.5.33 3/2/94
- - fixed up getting of netmask so it works on more unix variants
- - added -N option to nmbd
- - changed GMT diff calculation. need to check it's right for
- lots of OSes
- - fixed a bug in read_and_X() and chain_reply() chaining now
- seems to work correctly
-
-1.5.34 4/2/94
- - fixed bug in client that meant it couldn't get/put files from WfWg
- - fixed a bug in the server that caused lpr to return -1 under sunos
- - fixed a few errors in the hosts allow section of the
- smb.conf.5 manual page and added examples
-
-1.5.35 6/2/1994
- - minor bugfix in reduce_name().
- - changed width of "size" in client during a dir
- - patches for NEXT (among other things) from lendecke@namu01.gwdg.de
- - added -a switch to server, and made default action to append
- to log file
- - added deadtime options to [global] section for timing out
- dead connections to the smbd.
- - HPUX changes from Pasi.Kaara@atk.tpo.fi
- - made use of unsigned char more consistent
- - changed the way of getting the default username and host in the
- client
- - made LANMAN1 default to on in the client, off in server.
- Use -DLANMAN1=1 to make it on in both.
- - lots of casts and cleanups for various operating systems
- - changes to the Makefile from Karl to auto-instal the man pages
- - added a short history of the project to the distribution
-
-1.5.36 15/2/94
- - fixed minor bug in Debug() (thanks to Pasi.Kaara@atk.tpo.fi)
- - fixed bug in server.c so -a wasn't accepted.
- - minor fixes to the client
- - added hosts file to name server (-H option)
- - added -G option for groups to nameserver
- - cleanups and additions from Jeremy Allison, taking us
- closer to LANMAN1.0. In particular the locking code was cleaned up
- considerably.
-
-1.5.37 16/2/94
- - fixed bug introduced in 1.5.36 which disabled SMBcreate
-
-1.5.38 18/2/94
- - fixed get_broadcast() for ultrix (fix from iversen@dsfys1.fi.uib.no)
- - added automatic group registration
- - fixed bug in registration code
- - made nmbd work better with WfWg, and probably others
- - updated the man pages to include the new nmbd options.
- - minor updates to the README
- - fixed double log_out() in send_packet().
- - fixed bug in smbclient so that "dir" didn't work correctly
- with pathworks
- - possibly fixed bug in server that led to "abort retry ignore" from
- pathworks client when doing a "dir".
- - changed behaviour of smbclient login slightly, to try a
- blank password in SMBtcon if the right password fails, and a
- session setup has succeeded. Some clients seem to use a blank
- one if a session setup has succeeded.
- - ISC patches from imb@asstdc.scgt.oz.au
- - the client now tries to do name registration using a unicast.
- Let me know if this helps anyone.
- - tried to add a "contributed" line to each OS in the Makefile.
-
-1.5.39 18/2/94
- - fixed silly C code that only worked with some compilers
- - fixed another silly bug in nameserv.c that caused it to seg fault
-
-1.5.40 21/2/94
- - removed the from (IP) message so people don't worry about 0.0.0.0,
- it's redundant anyway.
- - changed the client so the crypt key isn't printed
- - changed the structure of switch_message() to use a list of functions.
- This improves the debug info.
- - made SMBopen ignore supplied attribute as per X/Open spec
- - made SMBopen fail if file doesn't exist in all cases. Let me know
- if this breaks something. It is implied in the X/Open spec. This
- fixes the pkzip bug.
- - added dptr_demote() to replace dptr_close() to try and fix
- pathworks dir bug. This has the potential disadvantage of
- leaving lots of open file descriptors.
- - changed mask_match to disallow two .s in a name
-
-1.5.41 2/3/94
- - added "dfree command" global option to smbd to support an
- external "disk free" executable (typically a script). This gets
- around the problem of getting disk free info reliably on lots
- of systems.
- - added ffirst and fclose to client
- - simple SYSVR4 patch from mark@scot1.ucsalf.ac.uk
- - added better uid/gid reporting for debugging purposes
- - several changes to the logon procedure for the client, so hopefully
- it will connect correctly to a wider range of servers.
- - server should no longer crash if it can't open the debug
- file (thanks to MGK@newton.npl.co.uk)
- - added the THANKS file.
-
-1.5.42 6/3/94
- - lots of changes from Jeremy Allison, implementing more of
- the LANMAN1.0 protocol, and fixing a few bugs.
- - fixed delete bug, so hopefully wildcards are correct now
- - pcap changes from Martin Kiff so non-aliased printers in
- /etc/printcap are recognised
- - wrote announce file ready for 1.6
- - re-wrote browse code in client (still doesn't work)
- - updates to man-pages from Karl Auer
- - made raw packet dumps mode 0600 and only if -dA is given
- - changed socket code to use utility functions in util.c
-
-1.6.00 17/3/94
- - made server always return to original directory (rather than /)
- - fixed bug in params.c that caused a seg fault if no parms in a
- section
- - minor clean ups for clean compile under solaris
- - solaris fix for running from inetd from Karl Auer
- - fixes for dfree() under solaris
- - minor changes that might help BSDI
- - changes to the Makefile, manual-pages and sample config file from
- Karl Auer
- - fixed dfree for Ultrix
-
-1.6.01 19/3/94
- - fixed setatr bug that allowed directories to be unusable
-
-1.6.02 27/3/94
- - added timestamps to connection message in log
- - added idle timeout of 10 minutes to name server
- - made HAVE_SYSCONF==0 the default in includes.h
- - made the client not register by default
- - ISC patches from imb@asstdc.scgt.oz.au
- - GetWd() cache code from Martin Kiff
- - rewrote the locking code in terms of fcntl() calls.
- - fixed "can't delete directory" bug
- - added code to close old dirptrs for duplicate searches
- - removed exchange_uids() and the access() call and replaced them.
-
-1.6.03 28/3/94
- - tried to clean up the time handling a little (local vs gmt time)
- - added debug level global to server config
- - added protocol level global to server config
- - added SMBecho command to server
- - included Karl Auers SMBGuide in the distribution.
-
-1.6.04 31/3/94
- - fixed time zeroing bug in smb_close and smb_setatr
- - re-wrote the username/password handling to be more flexible
- - added "guest only" service setting to smb.conf
- - updated man pages for new username/password handling
- - fixed parse bug in reply_tconX
- - improved error return code from tcon
- - several changes to fix printing from WfWg
-
-1.6.05 2/4/94
- - changed the name of the whole package to Samba
- - removed SMBexit call from client to stop exiting error message
- - added interpret_addr() call to replace inet_addr() so
- a hostname can be used whenever a IP is required
-
-1.6.06 8/4/94
- - added random tid choice to reduce problem of clients not
- detecting a server disconnection.
- - made client not report spurious time from CORE or COREPLUS server.
- - minor HPUX fix from gunjkoa@dep.sa.gov.au
- - turned off GETWD_CACHE until we track down a minor bug in it
-
-1.6.07: 10/4/94
- - added helpful error messages to connection failure in client.
- - fixed problem with mput in client
- - changed server to allow guest-only sesssetup messages with any
- password. Control this with GUEST_SESSION_SETUP in local.h.
- - minor change to session setup handling in make_connection()
- - added check for right number of \s in the client.
- - made the server not exit on last close if the deadtime is != 0
- - added malloc and realloc wrappers. enable them with -DWRAP_MALLOC=1
- - if smbd is started with a debug level of 10 or greater it creates
- a log file ending in the process number
-
-1.6.08: 18/4/94
- - updated the THANKS file
- - changes from marcel@fanout.et.tudelft.nl (Marcel Mol) for AMPM
- times and error report on connect().
- - made the get_myname() routine discard any part after the first '.'
- - added a wrapper for free from Martin Kiff
- - added simpleminded code to handle trapdoor uid systems (untested)
- - added Martin Kiffs "paranoid" getwd code.
- - added default MAXPATHLEN if undefined of 1024
- - made get_broadcast() continue to get netmask if it can't get
- broadcast (suggestion from Hannu Martikk)
- - replaced fchmod() calls with chmod() to satisfy some unixes
-
-
-
-1.6.09: 4/5/94
- - changed perror() calls to strerror() in server.c
- - fix for dfree on OSF1 from
- Maximilian Errath (errath@balu.kfunigraz.ac.at)
- - fixed server time reporting for protocol >= LANMAN1
- - fixed TimeDiff() for machines without TIMEZONE or TIMELOCAL
- (thanks to Vesa S{rkel{ )
- - added SYSV defs to AIX and HPUX to fix "memory" problem
- (actually a signal problem).
- - added version to client banner in log file
- - Ultrix patches from Vesa S{rkel{
- - added ! command to client for executing shell commands
- - fixed ERRnofids bug in server
- - fixed name_equal bug
- (thanks to cjkiick@flinx.b11.ingr.com (Chris Kiick))
- - wrapped gethostbyname() with Get_Hostbyname() to prevent
- case sensitive problems on name lookups
- - limit printer tmp filename to 14 chars
- (from Paul Thomas Mahoney )
- - added ability to understand 64 bit file times
- (thanks to davidb@ndl.co.uk (David Boreham))
- - added Gwt_Pwnam() wrapper to cover server case-sensitivity
- problems (suggestion from J.M.OConnor@massey.ac.nz (John O'Connor))
- - changed the setuid() calls to try and work for more systems
- without breaking the ones it currently works for
- - added version number to usage()
- (suggestion from peter@prospect.anprod.csiro.au)
- - added "security=" option for share or user level security
- - allowed multiple usernames in "user=" field
- - changed display method for recursive dorectory listings
- - switched client to use long filenames where supported
- - added speed reporting to client transfers
- - several NT fixes to server from jra@vantive.com (Jeremy Allison)
- - ISC fixes from ptm@xact.demon.co.uk (Paul Mahoney)
- - fix to README from grif@cs.ucr.edu (Michael A. Griffith)
- - default netmask and broadcast from Ian A Young
- - changed default of is_locked() on fcntl() error.
- - fixed bug in read_with_timeout() that could cause a runaway
- smbd process.
- - fixed findnext bug for long filenames in client
- - changed default protocol level to LANMAN1
- - change default reported security level to SHARE.
- - changed password_ok() so that if pwdauth() fails it tries
- with standard crypt.
- - added "translate" command to the client to do CR/LF translation
- for printing, and add a form feed at the end.
- (thanks to mh2620@sarek.sbc.com (Mark A. Horstman ) )
- - added "locking=yes/no" toggle for each service
- - SCO unix patches from Heinz Mauelshagen (mauelsha@ez.da.telekom.de)
-
-1.6.10: 7/5/94
- - fixed important bug in readbraw/writebraw
- - added -A option to client
- - fixed delete bug on long filenames (untested). Thanks to
- Stefan Wessels
- - neatened up the byte swapping code
-
-1.6.11: 3/6/94
- - fixed bug in client in receive_trans2_response() that caused
- some strange behaviour with LANMAN2.
- - fixed some offset/alignment problems with lockingX (thanks to
- Jeremy Allison)
- - allow locking on O_RDONLY files. Thanks to Martin N Dey
- - fixed del bug in client thanks to paulzn@olivetti.nl (Paul van der Zwan)
- - fixed multiple user= bug thanks to MDGrosen@spectron.COM (Mark Grosen)
- - added translate ability for all files. Thanks to mh2620@sarek.sbc.com (Mark A. Horstman )
- - mask out negative lock offsets. Thanks to bgm@atml.co.uk (Barry G Merrick)
- - more attempts to get the structure alignment better for some machines
- - cleaned up the machine dependencies a little
- - ISC fixes from Paul Thomas Mahoney
- - enabled printing with a SMBclose and SMBwrite for NT
- thanks to jkf@frisky.Franz.COM (Sean Foderaro)
- - SGI changes from Michael Chua
- - CLIX patches from cjkiick@ingr.com
- - NEXT2 and NEXT3_0 patches from Brad Greer (brad@cac.washington.edu)
- - BSDI changes from tomh@metrics.com (Tom Haapanen)
- - SCO patches from John Owens (john@micros.com)
- - fix psz bug in pcap.c (thanks to Karl Auer)
- - added widelinks option (global and per service). Suggestion from
- Karl Auer. Defaults to True.
- - made locking able to be global or local (default is give by global)
- - added check_name() to dir listings
- - added "packet size" option to globals. default to 32767. This
- "fixes" a WfWg bug (thanks to Karl Auer)
- - fixes for getattrE and setattrE and minor fix in util.c from Jeremy Allison.
- - Karl updated the man pages o be current
- - disabled writebraw and readbraw until a possible bug can be investigated further
-
-1.7.00: 14/7/94
- - added session_users list, to overcome problem of missing usernames in SMBTconX.
- - added term support to the client
- - added "default service"
- - fork for print so user is not root
- - added name mangling to 8.3 (rudimentary)
- - fixed bug in in_group()
- - changed to use gid in place of egid
- - fixed client connection to OS/2 (1.3 + lanman2.2) and long filenames
- - added patches from mcochran@wellfeet.com (Marc Cochran)
- these implement scope ids and fix some udp bugs. It means
- the -L option to nmbd now works.
- - made nmbd respond to incoming port rather than only 137
- - made wide links refuse .. components
- - fixed "dir foo." bug to stop it showing "foo.???"
- - improved name mangling (added stack)
- - added valid FNUM check to most calls
- - fixed important do_put bug in the client
- - added magic scripts to the server
- - re-enabled getwd_cache code
- - added optional agressive password checking
- - removed dptr_closepath from SMBsearch to try and stop "dos for loop"
- bug
- - DGUX patches from ross@augie.insci.com (ross andrus)
- - updated the README and THANKS file.
- - added node status request to -L option of nmbd
- - stripped trailing spaces in mask_match() (thanks to mike hench hench@cae.uwm.edu)
- - added COREPLUS style print queue reporting and "lpq command"
- in globals.
- - cleaned up date handling and fixed byte order dependancy on dates
- in SMBgetattrE.
- - cleaned up the password handling and added "password level" with
- the possability of checking all case combinations up to N upper
- case chars.
- - changed to use recvfrom only on udp ports (fixed read raw!)
- - added TCB password support for SCO (thanks to lance@fox.com)
- - updated README, THANKS and announce files.
- - fixed timezone reporting to be signed (thanks to noses@oink.rhein.de)
- - disabled max packet as it could cause problems with WfWg (no longer
- needed now readraw is "fixed")
- - changed from creat() to open() in mktemp and mknew.
- - changed umask handling
- - sped up nmbd by making it cache names
- - changed idle timeout on nmbd to 2 mins
- - Netbsd changes from noses@oink.rhein.de
- - released alpha2
- - added name timeout to nmbd
- - changed bind port retry in nmbd
- - added Limitations sections to README
- - fixed two . in is_83()
- - fixed compilations warnings in util.c (thanks to njw@cpsg.com.au)
- - made [homes] honour multiple user list
- - fixed mask match bug introduced in alpha1
- - added "mangled stack" option for stack size
- - added mangled stack promotion
- - released alpha3
- - netbsd-1.0 fix for statfs().
- - added null_string to util.c to reduce memory usage
- - changed the way directory structures are put together
- - added smbrun for system() requests
- - changed maxmux to 0 in hope of avoiding mpx commands problem
- - fixed zero response length for session keepalives
- - removed called name from session users list
- - added F_RDLCK support to try and handle locks on readonly files
- - made directory creation honour the lowercase flag in client (thanks
- to charlie@edina.demon.co.uk)
- - made checksum for mangling independant of extension if extension is
- lowercase
- - added ability to rename files with different extension, preserving
- root name
- - released alpha4
- - better command line error checking in client
- - changed all debug statements to new format
- - fixed delete error code reporting
- - released alpha5
- - added mangled name support to wildcard delete in server
- - fixed mask bug in SMBsearch
- - cleaned up prototypes
- - released alpha6
- - fixed important bug in session_setup which made WfWg freeze
- (maxmux was 0 - this bug was introduced in alpha4)
- - released alpha7
- - two printing bug fixes thanks to bgm@atml.co.uk (Barry G Merrick)
- - uid fix to smbrun (thanks to larry@witch.mitra.com)
- - man page updates from Karl Auer
- - FAQ file from Karl Auer
- - released alpha8
- - fixed read-only flag in dos_mode() for non writeable services
- - fixed error code reporting in open() and openX().
- - minor secureware fix from (thanks to lance@fox.com)
- - released alpha9
- - casting cleanups for memcpy().
- - cleaned up error code names to be more consistant
-
-1.7.01: 17/7/94
- - minor man page fix from baeder@cadence.com (Scott Baeder)
- - changed usage() error message in client
- - made nmbd not exit if can't register own name
- - made nmbd only register if running as a daemon
- - fixed stdout problem in smbrun by closing stdin/stdout/stderr
- - minor fix to lmhosts parsing
-
-
-1.7.02: 20/7/94
- - made nmbd not call get_broadcast if both -B and -N are used (thanks
- to Chris Woodrow )
- - disabled GETWD_CACHE again
- - fixed INCLUDES list in Makefile to add version.h (thanks to
- jimw@PE-Nelson.COM (Jim Watt))
- - made checkname do a become user if it hasn't already done so.
- - added consistancy check to become_user().
- - removed mask extension expansion from SMBsearch
- - small change to chkpth
- - fix to snum select for lpq status (thanks to Rafi Sadowsky
- rafi@tavor.openu.ac.il)
- - changed daemon to is_daemon for NetBSD (thanks to noses@oink.rhein.de)
- - removed STAFS3 stuff for NETBSD_1_0
-
-
-1.7.03: 29/7/94
- - updated docs for new distribution structure
- - made getatr return 0 size for directories (thanks to Bernd Esser
- esser@pib1.physik.uni-bonn.de)
- - added valid dos filename checks from Stefan Wessels
- (swessels@cs.up.ac.za)
- - added trimming of . in hostnames to -S mode of nmbd
- - removed become_user() and OPEN_CNUM calls. Now make them
- in switch_message instead which simplifies a lot of code.
- - added GETFNUM macro to make chain_fnum more consistant and
- reliable.
- - added flags to protocol structures to simplify CAN_WRITE and AS_USER
- checking
- - added getwd cache boolean option to globals
- - added fclose() to lpq status routine thanks to
- dgb900@durras.anu.edu.au (David Baldwin)
- - added "only user" option, to limit connection usernames to those
- in the user= line
- - changed to badpath from badfile in chkpath despite specs (following
- what WfWg does). This fixes "file not found" error in copy command.
- Thanks to rwa@aber.ac.uk for pointing out the bug
- - changes for apollo from Stephen C. Steel
- - more changes for Apollo from jmi@csd.cri.dk (John Mills)
- - released alpha release
- - added FTRUNCATE_CAN_EXTEND=0 as default to fix problem with word6.
- Possibly not needed on many OSes? Thanks to Charlie Hussey
- charlie@edina.demon.co.uk
- - started adding max connections code
- - much improved group handling contributed by
- Ian Heath (ih@ecs.soton.ac.uk)
-
-1.7.04: 29/7/94
- - fixed one line bug in SMBopenX that got error code wrong.
-
-1.7.05: 2/8/94
- - added UNIXERROR() macro to get error code from unix errno.
- - fixed lpq status for MSTCPB3
- - added @ option for user= line to lookup groups in group file
- - added become_user optimisation and process timeout (thanks to
- Jeanette Pauline Middelink (middelin@calvin.iaf.nl)
- - added malloc optimisation in readbraw
- - released alpha
- - patches for OSF1 enhanced security from Udo Linauer
- - made level 2 a more useful debug level (less guff)
- - added "max connections" and "lock dir" options to allow
- limiting of the number of connections to a service at one time.
- - released alpha2
- - updated man pages
- - released alpha3
- - added read prediction code for better read performance
- - released alpha4
- - minor tuning to receive_smb()
- - changed the order of mangled stack checking
- - bug fix in read_predict().
- - released alpha5
- - minor search optimisation
- - fixed keep alive bug in writebraw and in readbraw in the client
- - released alpha6
- - disabled writeraw by default pending a bug fix
- - added profiling code (off by default)
- - minor delete tuning
-
-
-1.7.06: 4/8/94
- - OSF1 crypt fix thanks to Udo Linauer
- - ifdef'd EDQUOT in case you don't have it (thanks to Paul Blackman )
- - tidied up UNIXERROR stuff to work on more systems.
- - made Makefile more sophisticated and added "make revert"
-
-1.7.07: 4/8/94
- - fixed one line fatal bug in receive_smb. Thanks to bruce@pixar.com
-
-1.7.08: 2/9/94
- - initgroups call for SCO from lance@fox.com
- - code cleanups from cap@isac.hces.com (Simon Casady)
- - use full pathname in print command construction
- - ISC includes fix from Martin Tomes
- - added GID_TYPE define to cope with ultrix. Thanks to
- brad@cac.washington.edu
- - added umask call to main in server
- - fixed several minor problems with the max connections
- code. Thanks to lehmann@klizix.mpi-stuttgart.mpg.de (Arno Lehmann).
- - fixed filetime in writeclose. Thanks to Andreas Bahrdt
- <100321.2431@compuserve.com>
- - df fix for large disks from Andreas Bahrdt
- - getpwanam support from horn@mickey.jsc.nasa.gov
- - clean name change from Bernd Esser
-
- - released alpha1
- - more locking changes to fix Excel problem
- - released alpha3
- - another minor locking change
- - smarter masking in the locking code. Excel now apparently works.
- - minor FAQ updates
- - changed max connections refusal error to access denied.
- - added queue command to client to show the print queue
- - changed some print queue reporting stuff
-
-1.8.0: 14/10/94
- - added international chars to valid_dos_char(). Thanks
- to Daniel.Grandjean@dgr.epfl.ch
- - volume label fix
- - released alpha1
- - important off by 4 fix in the server
- - readbraw size adaption in the client
- - released alpha2
- - wait3 cast for NeXt fixed. Thanks to dbrandon@politics.tamu.edu.
- - man page fix for max xmit. Thanks to mmoore@wexford (Mike Moore)
- - is_8_3() fixes from Jochen Roderburg
- - list_match() fix from jkf@soton.ac.uk
- - statfs3 fix for BSDI from dan@supra.com
- - changed file open/close/read in server in preparation for mmap()
- based IO.
- - added mmap() support for reading files in the server. Optional
- at compile time. Thanks to suggestion from Roger Binns
- - mmap bug fixes
- - added __SAMBA__ name in nmbd
- - major changes for support of lanman2 and long filenames from
- Jeremy Allison (jeremy@netcom.com)
- - lseek optimisation. Thanks to Linus Torvalds.
- - released alpha4
- - date patches for lanman2 from Jeremy Allison
- - added protocol aliases to handle WfWg (untested)
- - allow for zero params or data in reply_trans2
- - small lanman2 patches from jeremy
- - more prototype additions for clean compilation
- - postscript patches from tim@fsg.com
- - more lanman2 patches from Jeremy
- - added null ioctl support
- - kanji patches from fujita@ainix.isac.co.jp
- - released alpha6
- - disallowed null password access (thanks to Birger Kraegelin krg@iitb.fhg.de)
- - Makefile fix for ultrix from andrew@d2bsys.demon.co.uk (Andrew Stirling)
- - added per-service mangled names
- - totally re-vamped loadparm.c
- - added "mangling char" parameter
- - released alpha7
- - added "default case = lower|upper" service option
- - change mangling char to a service parameter
- - ultrix enhanced security patch from steven@gopher.dosli.govt.nz
- - more changes to loadparm.c
- - printer name always set in [printers]
- - string_free() fix thanks to jef_iwaniw@pts.mot.com
- - changed group handling to be faster and work for large numbers
- of groups
- - added dynamic gid_t type determination
- - released alpha8
- - fixed become_user() problem for services with invalid
- directories
- - added "invalid users" list on per service basis
- - fixed pointer problems in alpha8 (thanks to murnaghant@a1uproar.yuppy.rdgmts.MTS.dec.com)
- - fixed some date setting problems
- - trans2 fixes from jeremy to stop infinite directory listings of
- long filenames
- - "standard input" lpq patch from root@tlspu.demon.co.uk (Adrian Hungate)
- - changed password checking to check session list and validated ids
- before user list
- - split off password functions into password.c
- - added hosts equiv and rhosts code (thanks to Tim Murnaghan )
- - released alpha11
- - added "newer" command to the client
- - attempt at aix trapdoor uid workaround
- - released alpha12
- - minor trans2 bugfix
- - added ufc crypt (fast crypt) support. Thanks to suggestion from
- forrest d whitcher
- - socket() fix for getting bcast and netmask thanks to
- Brian.Onn@Canada.Sun.COM
- - added beginnings of IPC and named pipe support in the server
- - changed file structure a bit, creating reply.c
- - finished print queue support for lanman1
- - changed default protocol to LANMAN2
- - released alpha13
- - logged IPC connects at a higher debug level
- - added netgroup support to hosts equiv search
- - disallowed root access though hosts.equiv (thanks to Colin.Dean@Smallworld.co.uk)
- - kanji and password handling fixes from fujita@ainix.isac.co.jp
- - several bug fixes for lanman and other things from
- esser@pib1.physik.uni-bonn.de (Bernd Esser)
- - updated man pages, README and announce files.
- - released 1.8.00alpha1
- - reply_close() time change fix from Andreas Bahrdt <100321.2431@compuserve.com>
- - added valid users list to compliment invalid users list.
- - aix fixes from tomc@osi.curtin.edu.au (Tom Crawley)
- - changed testparm output format
- - support for getting time from the server (nearly untested)
- - fixed device type error for wild device ????
- - fixed groups problem when in 0 groups
- - more IPC fixups
- - added support for "net view \\server" command to list
- available services (like browsing)
- - released 1.8.00alpha2
- - changed port choice for nmbd -L
- - added -L option to client to view share list on a host
- - bug fixes for NetShareEnum code
- - added "server string" option
- - changed default print file name to include remote machine name.
- - added hooks for browsing in nmbd
- - added browsing to nmbd
- - freebsd fixed from Steve Sims SimsS@Infi.Net
- - got rid of tell()
- - added subnet browsing with the S option in lmhosts
- - made smbd prime nmbd with a 1 byte dgram
- - added REUSADDR to open_socket_in() thanks to peter@ifm.liu.se
-
-
-1.8.01: 18/10/94
-
- - auto add group "LANGROUP" if no group specified in nmbd
- - made nmbd more responsive at startup
- - lots of cleanups and consistancy checks
- - added -C option to nmbd to set "machine comment".
- - fixed postscript option
- - force print_file in print_open()
- - restructured the browsing a little
- - casesignames fix for lanman-dos
- - auto-load home directory from session setup
- - changed to StrnCpy() for safety
- - fixed "out of file descriptors" bug in the client (a WfWg bug?)
-
-
-1.8.02: 22/10/94
- - fixed uppercase username problem
- - added "hide dot files" option
- - changed auto debug log in nmbd
- - added LMHOSTS to Makefile
- - added M flag in lmhosts to specify own netbios name
- - added "load printers" option to auto-load all printers
- - substitution of %p in lpq command
- - substitution of %h and %v in server string and -C option of
- nmbd
- - string substitions substitute all occurances of a pattern
- - added casesignames global option
- - fix for man pages thanks to David Gardiner
- - changed debug options a bit
- - added default for lpq command and lpr command
- - changed default shell path to /bin/sh
- - forced lpq under api to run as root - should speed things up
- - added "group" option to force group of a connection
- - added "read list" and "write list" options
- - added max mux option - seems to fix NT browsing?
- - added "mangled map" option thanks to
- Martin.Tomes@uk.co.eurotherm.controls
- - separated mangling functions into mangle.c
- - allowed all dos chars in mangled names
- - apollo changes from Helmut Buchsbaum
- - password changing code from Bob Nance
- it doesn't quite work yet, but it's a start (disabled by default)
-
-
-1.8.03: 25/10/94
- - made auto loaded services browsable as per default service
- so you can hide homes but keep home directories.
- - changed check_name() to handle "direct to network" printing
- - auto 3 minute deadtime if all connections are closed. This
- prevents restart when polling the print queue.
- - fix for newer command in client from Rich-Hoesly@uai.com
- - changed connection recording method
- - added the program smbstatus
- - changed timeout mechanism
- - "null passwords" option from Pim Zandbergen
- - made new files with casesignames=False set their case to the default
- case.
- - fixed problem of uppercasing first letter of printers in printcap
- - debug level fixes in trans2 from jimw@PE-Nelson.COM (Jim Watt)
- - made null printer default to lp
-
-1.8.04: 27/10/94
- - added OS2.txt from riiber@oslonett.no
- - another "auto services" fix. A silly strtok() bug :-(
- - fixed the status locking and max connections (broken in 1.8.03)
- - released alpha1
- - added gets_slash so lines can be continued in smb.conf and
- lmhosts
- - browse list bugfix
- - default to "load printers=yes"
- - rewrote pcap.c
- - intergraph bugfix from tarjeij@ulrik.uio.no
- - changed properties flags in nmbd (to fix NT print browsing)
- - allowed very long lines in printcap parsing.
-
-1.8.05: 28/10/94
- - lanman2 fix from Jeremy
-
-1.9.00: 22/1/95
- - only add home if not already there.
- - added ulogoffX support
- - PTR_DIFF() cleanups
- - fixed a bug that caused STATUS..LCK to grow very large
- - changed mangling to handle names ending in . a little better
- - added "strip dot" option
- - SGI and setgroups() fix from bill@sg25.npt.nuwc.navy.mil
- - fixed password preservation in password_ok() (again?)
- - unink fix from emer@vssad.enet.dec.com (Joel S. Emer)
- - changed username part of spool filename to max 10 chars (from 6)
- - magic script fix from beverly@datacube.com (Beverly Brown)
- - reply_special() fix from Peter Brouwer
- - stopped nmbd from listening on 138. It didn't seem to help much.
- - clix fixes from ttj@sknsws61.sjo.statkart.no
- - fixed select behaviour under Linux
- - man page fix from Robin Cutshaw
- - ISC block size fix from ralf@rbsoft.sdata.de (Ralf Beck)
- - ISC fixes from Martin.Tomes@controls.eurotherm.co.uk
- - attrib bit fix in smbclient (pointed out by Rich-Hoesly@uai.com)
- - japanese extensions from fujita@ainix.isac.co.jp (Takashi
- Fujita) and ouki@gssm.otuska.tsukuba.ac.jp.
- - SCO patches from Stephen.Rothwell@pd.necisa.oz.au
- - changed the system commands to redirect stderr
- - changed default printername to service name for all print ops
- - added ability to delete print queue entries
- - added warning if you try to print without -P in smbclient
- - INTERACTIVE patches from cardinal@settimo.italtel.it
- - patch to handle spaces in group names from GJC@vax1.village.com
- (GEORGE J. CARRETTE)
- - lockingX fix from stefank@esi.COM.AU (Stefan Kjellberg)
- - some fairly radical changes to filename handling. We can now
- handle mixed case filenames properly
- - released alpha2
- - added sysv printing support and improved bsd support
- - changed the user that does print queues and lprm jobs
- - return code support in the client from doylen@nbslib.isc-br.com (Doyle Nickless)
- - added "strict locking" option. Defaults to no.
-
- - added -I switch to nmbd
- - fixed DEV bug thanks to Dirk.DeWachter@rug.ac.be
- - use pw_encrypt() for shadow passords in Linux (from begemot@begemot.iko.kharkov.ua (Dmitry Gorodchanin))
- - disabled read prediction by default
- - added varient handling code to ipc.c for printQ and printDel.
- - released alpha5
- - AUX patches from root@dolphin.csudh.edu
- - struct timeval fix from gkb1@york.ac.uk
- - patches to merge ISC and INTERACTIVE from pim@cti-software.nl
- - changed to "printing ="
- - fixed problem with long print queues.
- - fixed node status request in nmbd to go to non bcast
- - made default path in services /tmp if not specified
- - added %u in passwd program
- - fixed up the password changing code for Linux
- - no guest sess setup when user level security
- - changed timeouts to kill dirptrs so cdroms can be unmounted
- - added auto-reload of smb.conf if changed
- - added SIGHUP to reload the config files
- - added -M option to nmbd to search for a master browser
- - added support for continue bit in trans2findnext
- - changed to dynamic strings in some more structures
- - changed default deadtime to 30 minutes
- - cleaned up the memory swapping code a bit
- - updated the man pages somewhat
- - added %m and %u in the "path=" of services
- - released alpha6
- - simple testing and fixups for solaris, sunos, aix, ultrix and
- osf/1 (this is all I have access to).
- - fixed chdir bug
- - added hashing to cnum selection
- - released alpha7
- - fixed printing bug
- - reduced chance of "hung" smbd with dead client
- - fixed do_match() bug (recently introduced)
- - released alpha8
- - nameserver fix from W.J.M.vGeest@et.tudelft.nl (W.J.M. van Geest)
- - rewrote readbraw to try and overlap reads with writes
- - client optimisations
- - rewrote getwd cache and enabled it by default
- - added partial smb packet reads (hopefully faster writes)
- - added log file and log level options (with subs)
- - added "read size" option
- - tried setting some more socket options
- - can use subs in "config file=" and will auto-reload
- - added "include" options, with some subs
- - finally got print manager working with NT
- - auto-respond in nmbd to non-broadcast (auto WINS server, no -A
- needed)
- - released alpha10
- - auto-delet unused services when reloading
- - fixed auto-deletion
- - fixed long names in printing
- - fixed double loading of services file
- - added printer file name support
- - reformatted man pages for better www conversion
- - renamed to 1.9.00.
- - added support for RNetServerGetInfo and NetWkstaGetInfo API's
- - updated the docs a bit
- - released alpha1
- - added -M -
- - changed nmbd announce interval to 10 mins in outgoing packets
- - hopefully fixed idle timeout reconnects
- - strupper all command lines in nmbd
- - added %a substitution for "remote architecture"
- - added "Samba" protocol (same as lanman2)
- - added "security = SERVER"
- - released alpha2
- - lowercase password fix
- - fixed connect path length bug (thanks to JOHN YTSENG
- )
- - added subs on "password server".
- - fixed printing filename bug from smbclient
- - disk quotas and hpux printing support from Dirk.DeWachter@rug.ac.be
- - Makefile patches from pappinm@ayr_srv2.nth.dpi.qld.gov.au
- - AFS patches from Mike Allard (mgrmja@nextwork.rose-hulman.edu)
- - fixed grp name = server name problem
- - man page updates from Charlie Brady (charlieb@budge.apana.org.au)
- - fixed file search bug by adding "finished" flag
- - added "max log size". Suggestion from Mark Hastings
- - released alpha3
- - changed the read/write routines to handle partial read/writes
- - released alpha4
- - changed "guest account" to per-service
- - changed so "guest ok" allows access to the guest account,
- not the "user=" line
- - changed default readsize to 2048
- - try bind to 137 in nmbd if possible
- - added server lookup to -L option in smbclient (gets list of servers)
- - added -M switch to smbclient for sending winpopup messages
- - released alpha5
- - FAQ updates from Paul Blackman ictinus@lake.canberra.edu.au
-
-1.9.01: 23/1/95
- - changed comment in print Q info to service rather than server comment
- - fixed smbclient -L to NT when in user level security mode
- - hopefully finally fixed NT print manager problems
- - added informative messages during smbclient -M
- - added node status replies to nmbd
- - changed the lock offset fixup calculation to be more friendly
- to dumb lockd daemons.
- - added sigbus and sigsegv handlers to catch any silly errors and
- print a message
- - added message receipt to smbd and "message command =" option
-
-1.9.02: 25/1/95
- - added argv/argc mangling for people who start the server the
- wrong way.
- - some man page updates
- - added "revalidate" option
- - added hosts allow/deny access check to messaging access
- - added timeouts in the client
- - added check for existance of smbrun binary
- - man page updates from Colin.Dean@Smallworld.co.uk
- - freebsd patches from dfr@render.com
- - added mask sanity check in SMBsearch
- - added more useful substitutions (%S, %P, %I and %T)
- - added "exec =" option to execute commands on each connection
-
-1.9.03: 13/3/95
- - added "socket options" option
- - close base fd's (0,1 and 2)
- - use dup(0) for inetd operation
- - better detection of is_daemon
- - hopefully finally fixed silly put bug that gave the wrong
- date on files.
- - fixed segv in readbraw bug
- - added improved checing for invalid (or null) print file name
- - several patches from ad@papyrus.hamburg.com (Andreas Degert)
- - fixed slow logout bug in smbclient
- - fixed automounter problems
- - added subs on lock dir
- - BSDI patch from John.Terpstra@Aquasoft.com.au
- - added separate nmb and smb logfile entries in the Makefile
- - fixed return code error in open calls
- - added simple status display of printer in lpq parsing
- - rewrote the directory handling to avoid seekdir (added dir.c)
- - added uid=65535 check (thanks to grant@gear.torque.net)
- - enhanced transfer_file() to add header (used in readbraw)
- - reply_special bugfix from ferret@pc8871.seqeb.gov.au
- - added HAVE_PATHCONF
- - RiscIX patches from Jim Barry and
- Charles Gay-Jones
- - CLIX patches from ttj@sknsws61.sjo.statkart.no
- - fixed aix lpq parser from kvintus@acd.com
- - added substitutions to "include="
- - M88K_S3 patches from tonyb@plaza.ds.adp.com (Tony D. Birnseth)
- - fixed mangled stack problem
- - added code to handle broken readdir() setups on solaris
- - initgroups() fix from jarit@to.icl.fi
- - dgux dfree fix from listwork@cloud9.net
- - dnix support from Peter Olsson
- - getgrgid() patch from tpg@bailey.com (Tom Gall)
- - Makefile patch from obrien@Sea.Legent.com (David O'Brien)
- - password changing fixes from Dirk.DeWachter@rug.ac.be
- - minor man page updates
- - tried to enhance the read prediction code a little bit
-
-1.9.04: 16/3/95
- - a bit better handling of global include lists
- - fixed GSTRING bug in loadparm.c (affected "socket options =")
- - fixed broken lpq parsing code (recent bug).
- Thanks to Dirk.DeWachter@rug.ac.be
-
-1.9.05: 20/3/95
- - improved mget in client to take multiple arguments and default
- to *.*
- - socket option fixes for both nmbd and smbd
- - changed the byteorder handling scheme to be more portable (and
- faster)
- - lint cleanups from kast@kcs.planet.net (Robert Kast)
- - added crude segv, sigbus and sighup recovery to nmbd
- - rewrote lanman2_match to be closer to NT and WfWg behaviour
- - Cray support from velo@sesun3.epfl.ch (Martin Ouwehand)
- - "admin users" patch from Tim Leamy
- - released alpha1
- - added samba.7 man page
- - no chdir when doing non AS_USER protocols
- - become_guest() returns true in trapdoor uid system
- - added more sophisticated segv/sigbus reporting (Linux only)
- - released alpha2
- - minor code cleanups (output of -Wall)
- - smbprint fix from James Dryfoos
- - improved testparm a little
- - updated INSTALL.txt a little
-
-
-1.9.06: 21/3/95
- - added %S substitution to users, valid users and invalid
- users. This is useful for [homes].
- - split off printing routines into printing.c and more dir
- commands into dir.c
- - postexec patch from jpm@gin.Mens.DE (Jan-Piet Mens)
- - smbstatus updates from jpm@gin.Mens.DE (Jan-Piet Mens)
- - reload sighup after use
- - fixed name ptr offset bug
- - added %f in print commands
- - fixed byte ordering in nmbd which caused browsing to fail in
- 1.9.05
-
-1.9.07: 22/3/95
- - important directory listing fix
- - allowed path= in [homes] section
- - printer status patches from Dirk.DeWachter@rug.ac.be
-
-1.9.08: 24/3/95
- - fixed . and .. in root dir for lanman2
- - better default comment in [homes]
- - added time stamping to directory entries
- - check directory access at connection time
- - rlimit code from loebach@homer.atria.com (Thomas M. Loebach)
- - fixed home dir default comment
- - totally rewrote dptr handling to overcome a persistant bug
- - added [globals] as well as [global]
-
-1.9.09: 30/3/95
- - fixed static string bug in nmbd
- - better null password handling
- - split CFLAGS in Makefile
- - fixed typo in smbclient messaging
- - made home dir not inherit path from [global]
- - standard input printing patch from xiao@ic.ac.uk
- - added O_CREAT to all print opens (bug in Win95)
- - use /proc for process_exists under Linux and solaris
- - fixed another segv problem in readbraw
- - fixed volume label problem
- - lots of changes to try and support the NT1 protocol
- - released alpha1
- - fixed session setup bug with NT in NT1 protocol
- - released alpha2
- - fixed "get" bug in smbclient that affected NT3.5
- - added SO_KEEPALIVE as a default socket option in smbd
- - changed some error codes to match those that NT 3.5 produces
- - updated trans2 with some new calls for Win95 and WinNT (better
- long file support)
- - released alpha3
- - fixed "nmbd -D -b" timeouts
- - added IS_LONG_NAME flag to getattr in NT1
- - added the NT qfileinfo trans2 commands
- - merged qpathinfo with qfileinfo
- - changed idling technique to try and be more friendly to
- clients
- - merged setfileinfo with setpathinfo and updated them with the NT fns
- - improved read prediction a lot
- - added read prediction to readbraw
- - improved fault reporting (last packet dump)
-
-1.9.10: 30/3/95
- - fixed read prediction+readbraw bug for read/write files
-
-1.9.11: 9/4/95
- - fixed trans2 qpathinfo bug
- - fixed bug with % in service name when doing print queue requests
- - default readsize now 16K
- - minor read prediction changes
- - fixed status initialisation in print queue reporting
- - fixed const compile problem for hpux
- - minor SMBread fix from Volker Lendecke
- - removed space after -P in print commands (for fussy systems)
- - disabled level2 of setfilepathinfo
- - changed to a single read dir model, saving all dir names in
- the Dir structure
- - disabled NT protocols in the client due to reported problems
- - fixed QUERY_FS_VOLUME_INFO which caused Win95 to hang on drive
- properties
- - minor lseek bug fix
- - fixed up keepalives
- - new timezone handling code (hopefully better!)
- from steve@qv3pluto.LeidenUniv.nl
- - BSDI interface patch from jrb@csi.compuserve.com
- - gettimeofday changes from Roger Binns
- - added smbrun option
- - added "root preexec" and "root postexec" options
-
-1.9.12: 12/4/95
- - hopefully fixed some recently introduced NT problems
- - fixed a unlink error code problem
- - minor testparm fix
- - fixed silly error messages about comments in config files
- - added "valid chars" option for other languages
-
-1.9.13: 28/4/95
- - patches from David O'Brien (obrien@Sea.Legent.com) improving the
- netgroup suport, and adding the "map archive" option, as well as
- other minor cleanups.
- - tried to add info level 3 and 4 support for OS/2
- - default deadtime set to 0 as in docs
- - cleaned up the trans2 code a little
- - cleaned up the Makefile a little
- - added charset.c and charset.h
- - expanded "valid chars" option to handle case mapping
- - lots of changes to try and get timezones right
- - released alpha1
- - win95 fixups
- - released alpha2
- - added %H substitution (gives home directory)
- - nameserv.c cleanups and minor bug fixes
- - redid the browse hook logic
- - fixed daylight saving time offset for logfile messages
- - added name cacheing to nmbd
- - added send counts to node status in nmbd
- - added STRICT_TIMEZONES compile time option (very computationally
- expensive)
- - removed the partial read code
- - cleaned up the permission checking a lot
- - added share modes (DENY_READ, DENY_WRITE, DENY_ALL, DENY_NONE,
- DENY_FCB and DENY_DOS)
- - added "share modes" option
- - cleaned up the file open calls
- - released alpha4
- - fixed important one line bug in open_file()
- - trans2 client fix from lendecke@namu01.gwdg.de
- - netgroup patche from David O'Brien (obrien@Sea.Legent.com)
- - case sensitive fix from lenneis@statrix2.wu-wien.ac.at (Joerg Lenneis)
- - got long filenames working from Win95 dos prompt
- - added "workgroup=" option
- - added "username map" option including multiple maps, group maps etc
- - fixed password server for NT1 protocol and made it more robust
- - changed unix_mode() to add IWUSR to read-only directories. This
- is much closer to what clients expect.
- - added preservation of unused permission bits when a chmod() is
- called from a client.
- - made static those fns that could be
- - fixed typo in access.c (thanks to Andrew J Cole
- )
- - added %d substitution for process id
- (thanks to lenneis@statrix2.wu-wien.ac.at (Joerg Lenneis))
- - changed share error code to ERRbadshare
- - added locked files list to smbstatus if share modes is enabled
- - changed DENY_DOS to allow read by other tasks
- - added shared_pending checks to server
- - preserverd all possible permission bits during a chmod, and
- fixed a trans2 chmod bug
- - open /dev/null to use up first 3 fds, in an attempt to stop rogue
- library routines from causing havoc
- - fixed NT username problem when in server security
- - added "force user" and "force group" options
- - cleaned up some of the IPC calls a bit
- - added writeraw to the client and cleaned up write raw in the server
- - osf1 big-crypt bugfix from Udo Linauer
- - hopefully better disk-full checking
- - next uid bugfix from patrick@graphics.cornell.edu
- - changed share modes so lock directory doesn't need to be world
- writeable
- - enabled write-raw by default
- - added server_info() in client
- - added level checks in some ipc calls
- - added defines for the important timeouts in local.h
- - added print queue deletion to smbclient (untested)
- - removed the sysconf() calls
- - optimised writebraw a bit
- - fixed some file deletion problems
- - added total_data check for extended attribs in trans2 (for OS/2)
- - fixed broadcast reply bug in nmbd
- - added careful core dumping code
- - added faster password level searches (suggestion
- by lydick@cvpsun104.csc.ti.com (Dan Lydick))
-
-
-1.9.14: 22/9/95
- - fixed up level 3 and 4 trans2 requests for OS/2
- - minor optimisations in a few places
- - cleaned up the closing of low fds a bit
- - added SO_REUSEADDR to socket as a daemon
- - override aDIR bit for directories in dos_chmod()
- - SGI5 fixes from ymd@biosym.com (Yuri Diomin)
- - bsize sanity check and removed sunos force to 1k
- - force the create mode to be at least 0700
- - SCO and freebsd include changes from Peter Olsson
-
- - check with FQDN in access.c (thanks to Arne Ansper )
- - default broadcast for dnix from Peter Olsson
- - solaris patches from Ronald Guilmette
- - added EXDEV handling
- - small AFS Makefile patch from mgrlhc@nextwork.rose-hulman.edu
- - hopefully fixed the Win95 dates to work in other than my
- timezone
- - attempted alignment fixups (to speed up memcpy)
- - added some DCE/DFS support (thanks to Jim Doyle )
- - added fix so that root doesn't have special privilages to open
- readonly files for writing (but admin users do). This fixes the MS
- office install problem.
- - fixed trans2 response bug in client
- - got dual names working for NT
- - enabled lock_and_read in NT protocol
- - added %L macro for "local machine"
- - changed dfree reporting to use "sectors per unit"
- - fixed "not enough memory" bug in MS print manger by limiting
- share name length in share enum.
- - "short preserve case" option from Rabin Ezra (rabin@acm.org)
- - added archive option to client
- - changed openX in client to be able to open hidden and system files
- - added "sync always" option
- - rewrote writebmpx and readbmpx
- - added auto string_sub_basic to all loadparm strings
- - lots of nmbd fixups (add registration, refresh etc)
- - released alpha1
- - added smbtar patches from Ricky Poulten (poultenr@logica.co.uk)
- - added a lpq cache and the "lpq cache time" option
- - released alpha 2
- - sun includes fix from Kimmo Suominen
- - change nmbd -L lookup type to workstation from server
- - added min print space option
- - added user and group names to smbstatus (thanks to
- davide.migliavacca@inferentia.it)
- - fixed %f in print command bug (thanks to huver@amgraf.com)
- - added wildcard support to SMBmv
- - misc patches from David Elm (delm@hookup.net)
- - changed default of "share modes" to yes
- - changed default of "status" to yes
- - aix qconfig parsing from Jean-Pierre.Boulard@univ-rennes1.fr
- - more long_date fixups
- - added wildcards to nmbd
- - extensive changes to ipc.c and miscellaneous other changes
- from ad@papyrus.hamburg.com (Andreas Degert). Should especially
- help OS/2 users
- - added name release to nmbd
- - relesed alpha4
- - fixed "SOLARIS" to SUNOS5 in Makefile
- - several minor fixups to get it to compile on aix, osf1, ultrix,
- solaris and sunos
- - released alpha5
- - minor bug fixes and cleanups in ipc.c
- - fixed "only user" bug
- - changed lpq to report guest queue entries as sesssetup_user to
- allow for deletion by windows
- - released alpha6
- - added __SAMBA__ as type 0 in nmbd (was type 20)
- - fixed null print job bug
- - added 8 char warnings to testparm and smbclient
- - changed to 8 char limit for names in pcap.c
- - added linked list of config files to detect all date changes
- that require a reload
- - simplified pcap guessing heuristics
- - added space trimming to the name mapping
- - updated Get_Pwnam to add allow_change field for username mapping
- - fixed MemMove bug (thanks to mass@tanner.com (Massimo
- Sivilotti))
- - released alpha7
- - rewrote MemMove to be a little more efficient
- - ipc va_arg bug fix from djg@tas.com (Dave Gesswein)
- - added check for illegal chars in long filenames
- - fixed name cache init bug in nmbd
- - Convex patches from Victor Balashov
- - timestring() bugfix from staale@spacetec.no
- - changed %H to give path of forced user if one is set
- - added quoting to smbclient to allow spaces in filenames
- - convex and other patches from Ulrich Hahn
-
- - released alpha8
- - fixed rename directory bug
- - nmbd wins fix from Maximilian Errath
- - client and AFS changes + password.c reorganisation + "more" and
- "pwd" commands in client from Todd j. Derr (tjd@smi.med.pitt.edu)
- - fixed several nmbd bugs
- - released alpha9
- - fixed another "cd" bug in smbclient
- - password encryption from Jeremy Allison
- - added "passwd chat" option and chat interpretation code
- - added "smb passwd file" option
- - released alpha10
- - cleaned up chgpasswd.c a little
- - portability changes to the encryption handling code
- - added password encryption to smbclient
- - fixed a share level security encryption bug
- - added "ENCRYPTION.txt" document
- - released alpha11
- - added code to detect a password server loop
- - fixed typo in chkpath in client.c that broken cd (again)
- - LINUX_BIGCRYPT from marsj@ida.liu.se
- - AFS password fixup from jbushey@primenet.com (Jeffrey G. Bushey)
- - iso/8859-1 charcnv patches from Dan.Oscarsson@malmo.trab.se
- - strtok/user_in_list fix from roderich@nodebonn.muc.bmw.de
- - NETGROUP patches from J.W.Schilperoort@research.ptt.nl
- - trim_string patch from J.W.Schilperoort@research.ptt.nl
- - fixed problem with files with no extension getting mixed up
- - ipc bugfix for print job deletion from Rainer Leberle
- - released alpha12
- - pwlen fix in NETGROUP from Andrew J Cole
- - lots of uid and encryption changes from Jeremy Allison. WinDD
- should now work.
- - released alpha13
- - fixed max_xmit bug in client
- - select fix in server (fixed critical drive errors under ISC)
- - released alpha14
- - wildcard fix from Jeremy
- - changes to make IPC code more robust
- - small select loop change to reduce cleaning of share files
- - vtp, altos and mktime patches from Christian A. Lademann
-
- - EEXIST bugfix in server.c
- - changed mangled map to apply in all cases
- - released alpha15
- - fixed fcb open permissions (should mean apps know when a file is
- read only)
- - released alpha16
- - client help formatting fix and docs fix from Peter Jones
-
- - added a directory cache
- - use /proc whenever possible for pid detection
- - TCSANOW fix in getsmbpasswd from roderich@nodebonn.muc.bmw.de
- - fixed default printing mode for sysv systems
- - make client always expand mask
- - more minor IPC fixups
- - pyramid makefile entry from jeffrey@itm.org
- - client fixups for passlen, maxvcs and session redirect from
- Charles Hoch
- - finally fixed important IPC bug (varargs bug with int16)
- - quota patches from Dirk.DeWachter@rug.ac.be
- - print queue cache changes (per service) and print queue priority
- additions from Dirk.DeWachter@rug.ac.be
- - new japanese patches (incomplete) from
- fujita@ainix.isac.co.jp (Takashi Fujita)
- - moved a lot more functions into system.c via wrappers
- - changed a lot of the connection refused error codes to be more
- informative (or at least different)
- - released alpha17
- - changed error return code from cannor chdir() in make_connection
- - fixed realloc() bug in printing.c
- - fixed invalid username bug in sesssetupX
- - released alpha18
- - made default service change name to asked for service (idea
- from Ian McEwan )
- - fixed "guest only" bug
- - sambatar patches from Ricky
- - printing.c patches from Dirk.DeWachter@rug.ac.be
- - rewrote become_user()
- - sunos5 patch from Niels.Baggesen@uni-c.dk
- - more japanese extensions patches from fujita@ainix.isac.co.jp
- - released alpha20
- - added force_user to conn struct
-
-
-1.9.15: 14/11/95
- - removed bcast override from workgroup announce in nmbd
- - aix patch, added NO_SYSMOUNTH, from
- lionel leston <102624.346@compuserve.com>
- - quick fix in lp_string() to try and stop some core dumps
- - added uid cache in connections structure
- to make user level security faster
- - changed dos_mode() to show read-only on read-only shares only if
- user w bit not set
- - added check to stop exit_server() looping
- - core dump fix in string_sub()
- - fix client bug for long dirs in NT1 mode.
- Thanks to Erwin Authried (erwin@ws1.atv.tuwien.ac.at)
- - switched to a safer (but probably slower) readbraw implementation
- - released p1
- - readbraw fix from Stefaan.Eeckels@eunet.lu
- - fixed groups bug when user is in 1 group
- - fixed NT1 dir bug
- - changed default protocol in client to NT1
- - changed trans2 to not return both names in long listing if long
- name is 8.3
- - made stat of "" return RONLY if not writeable drive
- - wrapped strcpy() to stop nulls propogating (hack)
- - made rename and unlink look at share locks on file
- - clitar memory leak fix from jjm@jjm.com
- - added -p option to smbstatus to list smbd processes
- - added rename to the client
- - released p2
- - fixed SMBmv for case where the destination exists
- - man page patch from michal@ellpspace.math.ualberta.ca (Michal Jaegermann)
- - once again redid the time handling, but finally explained what
- is going on, this is written up in TIME.txt. The "kludge-GMT" used
- by NT is a bastard and led to a lot of the confusion
- - kanji patch from fujita@ainix.isac.co.jp (Takashi Fujita)
- - is08859-1 patches from eauth@mail.cso.co.at
- - starting rewriting nmbd, new nmbd is nmbd2, old one still around
- for time being
- - released p3
- - rewrote more of nmbd2 to use new structures
- - CLIX patches from Jason.J.Faultless@bechtel.btx400.co.uk
- - DirCacheFlush() bugfix from Michael Joosten
- . This bug explains a lot of the crashes.
- - fixed a bug in ChDir() that caused reversion to / in some
- situations
- - ipc fix from Magnus Hyllander
- - released p4
- - smbpasswd fix from Jeremy
- - compilation fixes from Magnus Hyllander
- - added NetServerEnum to ipc.c (needed for master browser stuff)
- - Makefile fix from Gunther Mayer
- - cleanups for clean compile on several OSes
- - added browse mastering code
- - started integration with smb.conf for nmbd2
- - released p5
- - fixed death_time (should be t+ttl*3)
- - fixed non-removal of dead servers
- - added smbstatus -u patch from oskarh@spornet.is (Oskar Hannesson)
- - NETGROUP fix from J.W.Schilperoort@research.kpn.com
- - select and NO_SETGROUPS patches from lennylim@netcom.com (Lenny
- Lim)
- - added LINKS_READ_ONLY define in dos_mode() for LM/X
- compatability
- - "dir a.c" bug fixed thanks to roderich@nodebonn.muc.bmw.de
- (Roderich Schupp)
- - job cancel fix in client from peo@mtek.chalmers.se
- - changed nmbd2 to nmbd
- - fixed "dir a*" under trans2 lookups
- - added StrnCaseCmp()
- - updated docs a bit for new browsing stuff
- - updated INSTALL.txt
- - hopefully fixed server level security with WfWg
-
-1.9.15 (patches):
- - major/minor fix for solaris from Jeroen Schipper
-
- - fixed critical bug in directory listings
- - released p1
- - fixed one of the causes of "out of memory" while browsing
- - fixed manpage install script (Paul Blackman)
- - added DNS failures to name cache
- - fixed writebmpx bug (affects OS/2)
- - misc OS/2 fixes, mostly for EA handling
- - added SMBcopy
- - added "max ttl" option
- - arch detection patch from Bas Laarhoven
- - released p2
- - another OS/2 fix - the level 4 getpathinfo for EAs
- - added "alternate permissions" option
- - changed client to parse destination names into name + domain
- - fixed problem with PrimaryGroup and lmhosts loading
- - added domain master ability to nmbd
- - added "domain master" option
- - added "domain controller" option and code
- - pwd fix to client from Erik Devriendt (de@te6.siemens.be)
- - fixed problem in smbmv that led to ar not working in mks
- - added transs2
- - released p3
- - updated email addresses
- - fix for innetgr from Olaf Seibert (rhialto@polder.ubc.kun.nl)
- - client translate fix from bandc@dircon.co.uk
- - netbsd bcast fix from from Olaf Seibert (rhialto@polder.ubc.kun.nl)
- - syslog code from Alex Nash
- - strip dot fix from Arne Ansper
- - added addtosmbpass + man page from
- michal@ellpspace.math.ualberta.ca (Michal Jaegermann)
- - pcap fix for AIX from Jon Christiansen
- - fixed servertype bug in remote announcements
- - fixed up illegal name checks (should also be faster)
- - kanji patches from fujita@ainix.isac.co.jp (Takashi Fujita)
- - fixed bug handling non-encrypted passwords
- - released p4
- - fixed makefile for addtosmbpass
- - DCE/DFS fixes from John Brezak (brezak@ch.hp.com)
- - client patch for partial command matching from Andrew Wiseman
-
- - made is_8_3() handle full paths
- - rewrote open_file_shared() with help from Charles Hoch
-
- - changed syslog to handle interactive programs
- - fixed syslog problem with full path in argv[0]
- - illegal name fixup for kanji from fujita@ainix.isac.co.jp
- - fixed server level security to allow fallback to encryption
- - changed reply_read() and reply_lockread() to ignore clients
- smb_bufsize in order to handle broken lanman clients
- - fixed NT wildcard problem with old style programs
- - man page patches from "John M. Sellens"
-
- - partially documented the "character set" option
- - changed default for MAXDIR to 64
- - changed default DPTR idle time to 120
- - released p5
- - QNX patches from eldo@invisa.satlink.net (Eldo Loguzzo)
- - made nmbd use the "max log size" option and changed log handling
- code a bit
- - sunos patches, remote protocol (%R) addition and arch detection
- changes to stop compiler warning from Timothy Hunt
- - fixed become_user() bug that led to incorrect permissions in
- some situations.
- - released p6
- - is_8_3() fix from Charles Hoch
- - nmblib bugfix from gmk@mhcnet.att.com (George Kull)
- - aix pcap fix from Jon Christiansen
- - added explicit sig_pipe() in server.c
- - added domain logins option (not fully implemented)
- - added HAVE_GMTOFF code
- - got rid of PM_MAXLINE
- - minor client fix from goggi@eflir (Garðar Georg Nielsen)
- - added SIGCLD_IGNORE for HPUX (from Tor Lillqvist
- )
- - OSF/1 lpq patch from scooter@GENE.COM (Scooter Morris)
- - NeXT patches from pmarcos@next.com (Paul Marcos)
- - dstdiff patch to stop infinite loop from Erwin Authried (eauth@cso.co.at)
- - password server option can now take a list of password servers
- - patches to let samba run on OS/2 from Jason Rumney
- - added domain logon and logon script suport
- - SCO openserver 5 patches from Scott Michel
- - Makefile changes from Marty Leisner
- - chgpasswd changes from Roman Dumych
- for SVR4
- - GUEST_SESSSETUP change from David.Chappell@mail.cc.trincoll.edu
- - released p7
- - moved SO_REUSEADDR before bind() (thanks to Thomas Bellman
- )
- - added more flexible GUEST_SESSSETUP to local.h and restored
- pre-p7 behaviour as default
- - released p8
-
-1.9.16:
- - Makefile fix from Marty Leisner
- - added %g and %G substitutions
- - changed IDLE_CLOSED_TIMEOUT to 60
- - fixed the "admin user" status in domain logons
- - hpux 10 "trusted security" patches from David-Michael Lincke
- (dlincke@sgcl1.unisg.ch)
- - added nmb lookups to client from Adrian Hill
- - svr4 pause/resume printing patch from Brendan O'Dea (bod@tyndall.com.au)
- - fixed master announcement thanks to Luke Leighton
- - changed srcdir usage in Makefile to be friendly to more systems
- - NT4 alignment patches from Jeremy Allison (jra@vantive.com)
- - updated share mode code for new spec
- - minor client bugfix (for smbclient '\\\')
- - fix for level 260 when magling disabled. From Martin Tomes
-
- - SMBtranss2 fix for OS/2 from Jeremy Allison
- - profiles fixup from Timm Wetzel
- - man page updates from Dirk.DeWachter@rug.ac.be
- - nmbsync fix from Andy Whitcroft
- - Lynx patches from Manfred Woelfel
- - new smbtar stuff from Ricky
- - changed to share mode DENY_NONE for tar
- - fixed -D option of smbclient when in tar mode
- - added aARCH to open modes
- - added code to cope with select/read errors
- - fixed blank browse entries after smb.conf reread
- - integrated new browse stuff from Luke into ipc.c
- - added workgroup list to smbclient -L
- - improved archive attribute handling in close_file() and
- write_file()
- - smbtar fixes from Martin.Kraemer@mch.sni.de
- - Linux quota patch from xeno@mix.hsv.no
- - try to work around NT passlen2 problem in session setup
- - released alpha1
-
-NOTE: From now on the cvs.log file will be used to give a complete log of
-changes to samba. This change-log is now obsolete.
-
-
-==========
-todo:
-
-
-64 bit longs and IP addresses may give problems with unsigned longs?
-
-set archive bit whenever file is modified??
-
-fix man page dates
-
-reply only to own workgroup in server enum
-
-patch to compile with g++ and possibly solaris c++
-
-nmbd needs to keep browse list uptodate by talking to the master if it loses
-an election as others may still think its a valid backup and use it to get
-lists.
-
-leftover lock files can end up belonging to non-smbd processes after a reboot.
-
-hosts allow in nmbd
-
-hosts allow cache
-
-add password command in smbclient
-
-drag long filename to samba under os/2 gives short name
-
-document max ttl option
-
-dup/close 0 for getopt?
-
-implement SMBmove ??
-
-add option to print more info about locked files (full path, share name
-etc)
-
-very slow listing CD, perhaps because of order of stat and readdir or add
-masking to opendir?
-
-protocol drop back in client to avoid openX etc.
-
-handle exported fat drives to a long filename capable client
-
-add check for existance of lpq commands etc (use stat?)
-
-get rid of the silly +4 and -4 by removing NBT stuff
-
-write-only shares
-
-document cnvchar stuff
-
-allow smbd to serve user and group lists to win95
-
-document homes behaviour with WinDD
-
-add "hide file = *.o" "hide dir = .Foo*" "show file = xx*" type options.
-
-ALLOW_PASSWORD_CHANGE only compiles/works on some systems
-
-weird foooooooo/open.exe bug on NT
-
-%a detection can't detect Win95 versus WinNT
-
-reverse mangled maps, so (*.html *.htm) works for new files.
-
-install problems with w95. could be some sort of race?
-
-more efficient Files[] structure to handle thousands of open files
-
-lpd stuff:
- Tony Aiuto (tony@ics.com)
-
-make max disk size local
-
diff --git a/source/client/client.c b/source/client/client.c
deleted file mode 100644
index c7e00c45150..00000000000
--- a/source/client/client.c
+++ /dev/null
@@ -1,4870 +0,0 @@
-/*
- Unix SMB/Netbios implementation.
- Version 1.9.
- SMB client
- Copyright (C) Andrew Tridgell 1994-1997
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-*/
-
-#ifdef SYSLOG
-#undef SYSLOG
-#endif
-
-#include "includes.h"
-
-#ifndef REGISTER
-#define REGISTER 0
-#endif
-
-pstring cur_dir = "\\";
-pstring cd_path = "";
-pstring service="";
-pstring desthost="";
-extern pstring myname;
-pstring password = "";
-pstring username="";
-pstring workgroup="";
-char *cmdstr="";
-BOOL got_pass = False;
-BOOL connect_as_printer = False;
-BOOL connect_as_ipc = False;
-extern struct in_addr ipzero;
-
-char cryptkey[8];
-BOOL doencrypt=False;
-
-extern pstring user_socket_options;
-
-/* 30 second timeout on most commands */
-#define CLIENT_TIMEOUT (30*1000)
-#define SHORT_TIMEOUT (5*1000)
-
-/* value for unused fid field in trans2 secondary request */
-#define FID_UNUSED (0xFFFF)
-
-int name_type = 0x20;
-
-int max_protocol = PROTOCOL_NT1;
-
-
-time_t newer_than = 0;
-int archive_level = 0;
-
-extern pstring debugf;
-extern int DEBUGLEVEL;
-
-BOOL translation = False;
-
-
-static BOOL send_trans_request(char *outbuf,int trans,
- char *name,int fid,int flags,
- char *data,char *param,uint16 *setup,
- int ldata,int lparam,int lsetup,
- int mdata,int mparam,int msetup);
-static BOOL receive_trans_response(char *inbuf,int trans,
- int *data_len,int *param_len,
- char **data,char **param);
-static int interpret_long_filename(int level,char *p,file_info *finfo);
-static void dir_action(char *inbuf,char *outbuf,int attribute,file_info *finfo,BOOL recurse_dir,void (*fn)(),BOOL longdir);
-static int interpret_short_filename(char *p,file_info *finfo);
-static BOOL call_api(int prcnt,int drcnt,
- int mprcnt,int mdrcnt,
- int *rprcnt,int *rdrcnt,
- char *param,char *data,
- char **rparam,char **rdata);
-
-
-/* clitar bits insert */
-extern int blocksize;
-extern BOOL tar_inc;
-extern BOOL tar_reset;
-/* clitar bits end */
-
-
-int cnum = 0;
-int pid = 0;
-int gid = 0;
-int uid = 0;
-int mid = 0;
-int myumask = 0755;
-
-int max_xmit = BUFFER_SIZE;
-
-extern pstring scope;
-
-BOOL prompt = True;
-
-int printmode = 1;
-
-BOOL recurse = False;
-BOOL lowercase = False;
-
-BOOL have_ip = False;
-
-struct in_addr dest_ip;
-
-#define SEPARATORS " \t\n\r"
-
-BOOL abort_mget = True;
-
-extern int Protocol;
-
-BOOL readbraw_supported = False;
-BOOL writebraw_supported = False;
-
-pstring fileselection = "";
-
-extern file_info def_finfo;
-
-/* timing globals */
-int get_total_size = 0;
-int get_total_time_ms = 0;
-int put_total_size = 0;
-int put_total_time_ms = 0;
-
-
-extern int Client;
-
-#define USENMB
-
-#ifdef KANJI
-extern int coding_system;
-#define CNV_LANG(s) (coding_system == DOSV_CODE?s:dos_to_unix(s, False))
-#define CNV_INPUT(s) (coding_system == DOSV_CODE?s:unix_to_dos(s, True))
-static BOOL
-setup_term_code (char *code)
-{
- int new;
- new = interpret_coding_system (code, UNKNOWN_CODE);
- if (new != UNKNOWN_CODE) {
- coding_system = new;
- return True;
- }
- return False;
-}
-#else
-#define CNV_LANG(s) dos2unix_format(s,False)
-#define CNV_INPUT(s) unix2dos_format(s,True)
-#endif
-
-/****************************************************************************
-setup basics in a outgoing packet
-****************************************************************************/
-void setup_pkt(char *outbuf)
-{
- SSVAL(outbuf,smb_pid,pid);
- SSVAL(outbuf,smb_uid,uid);
- SSVAL(outbuf,smb_mid,mid);
- if (Protocol > PROTOCOL_COREPLUS)
- {
- SCVAL(outbuf,smb_flg,0x8);
- SSVAL(outbuf,smb_flg2,0x1);
- }
-}
-
-/****************************************************************************
-write to a local file with CR/LF->LF translation if appropriate. return the
-number taken from the buffer. This may not equal the number written.
-****************************************************************************/
-static int writefile(int f, char *b, int n)
-{
- int i;
-
- if (!translation)
- return(write(f,b,n));
-
- i = 0;
- while (i < n)
- {
- if (*b == '\r' && (i<(n-1)) && *(b+1) == '\n')
- {
- b++;i++;
- }
- if (write(f, b, 1) != 1)
- {
- break;
- }
- b++;
- i++;
- }
-
- return(i);
-}
-
-/****************************************************************************
- read from a file with LF->CR/LF translation if appropriate. return the
- number read. read approx n bytes.
-****************************************************************************/
-static int readfile(char *b, int size, int n, FILE *f)
-{
- int i;
- int c;
-
- if (!translation || (size != 1))
- return(fread(b,size,n,f));
-
- i = 0;
- while (i < n)
- {
- if ((c = getc(f)) == EOF)
- {
- break;
- }
-
- if (c == '\n') /* change all LFs to CR/LF */
- {
- b[i++] = '\r';
- n++;
- }
-
- b[i++] = c;
- }
-
- return(i);
-}
-
-
-/****************************************************************************
-read from a file with print translation. return the number read. read approx n
-bytes.
-****************************************************************************/
-static int printread(FILE *f,char *b,int n)
-{
- int i;
-
- i = readfile(b,1, n-1,f);
-#if FORMFEED
- if (feof(f) && i>0)
- b[i++] = '\014';
-#endif
-
- return(i);
-}
-
-/****************************************************************************
-check for existance of a dir
-****************************************************************************/
-static BOOL chkpath(char *path,BOOL report)
-{
- fstring path2;
- pstring inbuf,outbuf;
- char *p;
-
- strcpy(path2,path);
- trim_string(path2,NULL,"\\");
- if (!*path2) *path2 = '\\';
-
- bzero(outbuf,smb_size);
- set_message(outbuf,0,4 + strlen(path2),True);
- SCVAL(outbuf,smb_com,SMBchkpth);
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- p = smb_buf(outbuf);
- *p++ = 4;
- strcpy(p,path2);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (report && CVAL(inbuf,smb_rcls) != 0)
- DEBUG(2,("chkpath: %s\n",smb_errstr(inbuf)));
-
- return(CVAL(inbuf,smb_rcls) == 0);
-}
-
-
-/****************************************************************************
-send a message
-****************************************************************************/
-static void send_message(char *inbuf,char *outbuf)
-{
- int total_len = 0;
-
- char *p;
- int grp_id;
-
- /* send a SMBsendstrt command */
- bzero(outbuf,smb_size);
- set_message(outbuf,0,0,True);
- CVAL(outbuf,smb_com) = SMBsendstrt;
- SSVAL(outbuf,smb_tid,cnum);
-
- p = smb_buf(outbuf);
- *p++ = 4;
- strcpy(p,username);
- p = skip_string(p,1);
- *p++ = 4;
- strcpy(p,desthost);
- p = skip_string(p,1);
-
- set_message(outbuf,0,PTR_DIFF(p,smb_buf(outbuf)),False);
-
- send_smb(Client,outbuf);
-
-
- if (!receive_smb(Client,inbuf,SHORT_TIMEOUT) || CVAL(inbuf,smb_rcls) != 0)
- {
- printf("SMBsendstrt failed. (%s)\n",smb_errstr(inbuf));
- return;
- }
-
- grp_id = SVAL(inbuf,smb_vwv0);
-
- printf("Connected. Type your message, ending it with a Control-D\n");
-
- while (!feof(stdin) && total_len < 1600)
- {
- int maxlen = MIN(1600 - total_len,127);
- pstring msg;
- int l=0;
- int c;
-
- bzero(msg,smb_size);
-
- for (l=0;l= 1600)
- printf("the message was truncated to 1600 bytes ");
- else
- printf("sent %d bytes ",total_len);
-
- printf("(status was %d-%d)\n",CVAL(inbuf,smb_rcls),SVAL(inbuf,smb_err));
-
- CVAL(outbuf,smb_com) = SMBsendend;
- set_message(outbuf,1,0,False);
- SSVAL(outbuf,smb_vwv0,grp_id);
-
- send_smb(Client,outbuf);
-
-
- if (!receive_smb(Client,inbuf,SHORT_TIMEOUT) || CVAL(inbuf,smb_rcls) != 0)
- {
- printf("SMBsendend failed (%s)\n",smb_errstr(inbuf));
- return;
- }
-}
-
-
-
-/****************************************************************************
-check the space on a device
-****************************************************************************/
-static void do_dskattr(void)
-{
- pstring inbuf,outbuf;
-
- bzero(outbuf,smb_size);
- set_message(outbuf,0,0,True);
- CVAL(outbuf,smb_com) = SMBdskattr;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- DEBUG(0,("Error in dskattr: %s\n",smb_errstr(inbuf)));
-
- DEBUG(0,("\n\t\t%d blocks of size %d. %d blocks available\n",
- SVAL(inbuf,smb_vwv0),
- SVAL(inbuf,smb_vwv1)*SVAL(inbuf,smb_vwv2),
- SVAL(inbuf,smb_vwv3)));
-}
-
-/****************************************************************************
-show cd/pwd
-****************************************************************************/
-static void cmd_pwd(void)
-{
- DEBUG(0,("Current directory is %s",CNV_LANG(service)));
- DEBUG(0,("%s\n",CNV_LANG(cur_dir)));
-}
-
-
-/****************************************************************************
-change directory - inner section
-****************************************************************************/
-static void do_cd(char *newdir)
-{
- char *p = newdir;
- pstring saved_dir;
- pstring dname;
-
- /* Save the current directory in case the
- new directory is invalid */
- strcpy(saved_dir, cur_dir);
- if (*p == '\\')
- strcpy(cur_dir,p);
- else
- strcat(cur_dir,p);
- if (*(cur_dir+strlen(cur_dir)-1) != '\\') {
- strcat(cur_dir, "\\");
- }
- dos_clean_name(cur_dir);
- strcpy(dname,cur_dir);
- strcat(cur_dir,"\\");
- dos_clean_name(cur_dir);
-
- if (!strequal(cur_dir,"\\"))
- if (!chkpath(dname,True))
- strcpy(cur_dir,saved_dir);
-
- strcpy(cd_path,cur_dir);
-}
-
-/****************************************************************************
-change directory
-****************************************************************************/
-static void cmd_cd(char *inbuf,char *outbuf)
-{
- fstring buf;
-
- if (next_token(NULL,buf,NULL))
- do_cd(buf);
- else
- DEBUG(0,("Current directory is %s\n",CNV_LANG(cur_dir)));
-}
-
-
-/****************************************************************************
- display info about a file
- ****************************************************************************/
-static void display_finfo(file_info *finfo)
-{
- time_t t = finfo->mtime; /* the time is assumed to be passed as GMT */
- DEBUG(0,(" %-30s%7.7s%10d %s",
- CNV_LANG(finfo->name),
- attrib_string(finfo->mode),
- finfo->size,
- asctime(LocalTime(&t))));
-}
-
-
-/****************************************************************************
- do a directory listing, calling fn on each file found. Use the TRANSACT2
- call for long filenames
- ****************************************************************************/
-static int do_long_dir(char *inbuf,char *outbuf,char *Mask,int attribute,void (*fn)(),BOOL recurse_dir)
-{
- int max_matches = 512;
- int info_level = Protocol 200)
- {
- DEBUG(0,("ERROR: Looping in FIND_NEXT??\n"));
- break;
- }
-
- if (First)
- {
- setup = TRANSACT2_FINDFIRST;
- SSVAL(param,0,attribute); /* attribute */
- SSVAL(param,2,max_matches); /* max count */
- SSVAL(param,4,8+4+2); /* resume required + close on end + continue */
- SSVAL(param,6,info_level);
- SIVAL(param,8,0);
- strcpy(param+12,mask);
- }
- else
- {
- setup = TRANSACT2_FINDNEXT;
- SSVAL(param,0,ff_dir_handle);
- SSVAL(param,2,max_matches); /* max count */
- SSVAL(param,4,info_level);
- SIVAL(param,6,ff_resume_key); /* ff_resume_key */
- SSVAL(param,10,8+4+2); /* resume required + close on end + continue */
- strcpy(param+12,mask);
-
- DEBUG(5,("hand=0x%X resume=%d ff_lastname=%d mask=%s\n",
- ff_dir_handle,ff_resume_key,ff_lastname,mask));
- }
- /* ??? original code added 1 pad byte after param */
-
- send_trans_request(outbuf,SMBtrans2,NULL,FID_UNUSED,0,
- NULL,param,&setup,
- 0,12+strlen(mask)+1,1,
- BUFFER_SIZE,10,0);
-
- if (!receive_trans_response(inbuf,SMBtrans2,
- &resp_data_len,&resp_param_len,
- &resp_data,&resp_param))
- {
- DEBUG(3,("FIND%s gave %s\n",First?"FIRST":"NEXT",smb_errstr(inbuf)));
- break;
- }
-
- /* parse out some important return info */
- p = resp_param;
- if (First)
- {
- ff_dir_handle = SVAL(p,0);
- ff_searchcount = SVAL(p,2);
- ff_eos = SVAL(p,4);
- ff_lastname = SVAL(p,8);
- }
- else
- {
- ff_searchcount = SVAL(p,0);
- ff_eos = SVAL(p,2);
- ff_lastname = SVAL(p,6);
- }
-
- if (ff_searchcount == 0)
- break;
-
- /* point to the data bytes */
- p = resp_data;
-
- /* we might need the lastname for continuations */
- if (ff_lastname > 0)
- {
- switch(info_level)
- {
- case 260:
- ff_resume_key =0;
- StrnCpy(mask,p+ff_lastname,resp_data_len-ff_lastname);
- /* strcpy(mask,p+ff_lastname+94); */
- break;
- case 1:
- strcpy(mask,p + ff_lastname + 1);
- ff_resume_key = 0;
- break;
- }
- }
- else
- strcpy(mask,"");
-
- /* and add them to the dirlist pool */
- dirlist = Realloc(dirlist,dirlist_len + resp_data_len);
-
- if (!dirlist)
- {
- DEBUG(0,("Failed to expand dirlist\n"));
- break;
- }
-
- /* put in a length for the last entry, to ensure we can chain entries
- into the next packet */
- {
- char *p2;
- for (p2=p,i=0;i<(ff_searchcount-1);i++)
- p2 += interpret_long_filename(info_level,p2,NULL);
- SSVAL(p2,0,resp_data_len - PTR_DIFF(p2,p));
- }
-
- /* grab the data for later use */
- memcpy(dirlist+dirlist_len,p,resp_data_len);
- dirlist_len += resp_data_len;
-
- total_received += ff_searchcount;
-
- if (resp_data) free(resp_data); resp_data = NULL;
- if (resp_param) free(resp_param); resp_param = NULL;
-
- DEBUG(3,("received %d entries (eos=%d resume=%d)\n",
- ff_searchcount,ff_eos,ff_resume_key));
-
- First = False;
- }
-
- if (!fn)
- for (p=dirlist,i=0;i= PROTOCOL_LANMAN1)
- CVAL(outbuf,smb_com) = SMBffirst;
- else
-#endif
- CVAL(outbuf,smb_com) = SMBsearch;
-
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- SSVAL(outbuf,smb_vwv0,num_asked);
- SSVAL(outbuf,smb_vwv1,attribute);
-
- p = smb_buf(outbuf);
- *p++ = 4;
-
- if (first)
- strcpy(p,mask);
- else
- strcpy(p,"");
- p += strlen(p) + 1;
-
- *p++ = 5;
- if (first)
- SSVAL(p,0,0);
- else
- {
- SSVAL(p,0,21);
- p += 2;
- memcpy(p,status,21);
- }
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- received = SVAL(inbuf,smb_vwv0);
-
- DEBUG(5,("dir received %d\n",received));
-
- DEBUG(6,("errstr=%s\n",smb_errstr(inbuf)));
-
- if (received <= 0) break;
-
- first = False;
-
- dirlist = Realloc(dirlist,(num_received + received)*DIR_STRUCT_SIZE);
-
- if (!dirlist)
- return 0;
-
- p = smb_buf(inbuf) + 3;
-
- memcpy(dirlist+num_received*DIR_STRUCT_SIZE,
- p,received*DIR_STRUCT_SIZE);
-
- memcpy(status,p + ((received-1)*DIR_STRUCT_SIZE),21);
-
- num_received += received;
-
- if (CVAL(inbuf,smb_rcls) != 0) break;
- }
-
-#if FFIRST
- if (!first && Protocol >= PROTOCOL_LANMAN1)
- {
- bzero(outbuf,smb_size);
- CVAL(outbuf,smb_com) = SMBfclose;
-
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- p = smb_buf(outbuf);
- *p++ = 4;
-
- strcpy(p,"");
- p += strlen(p) + 1;
-
- *p++ = 5;
- SSVAL(p,0,21);
- p += 2;
- memcpy(p,status,21);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- DEBUG(0,("Error closing search: %s\n",smb_errstr(inbuf)));
- }
-#endif
-
- if (!fn)
- for (p=dirlist,i=0;i= PROTOCOL_LANMAN2)
- {
- if (do_long_dir(inbuf,outbuf,Mask,attribute,fn,recurse_dir) > 0)
- return;
- }
-
- expand_mask(Mask,False);
- do_short_dir(inbuf,outbuf,Mask,attribute,fn,recurse_dir);
- return;
-}
-
-/*******************************************************************
- decide if a file should be operated on
- ********************************************************************/
-static BOOL do_this_one(file_info *finfo)
-{
- if (finfo->mode & aDIR) return(True);
-
- if (newer_than && finfo->mtime < newer_than)
- return(False);
-
- if ((archive_level==1 || archive_level==2) && !(finfo->mode & aARCH))
- return(False);
-
- return(True);
-}
-
-
-/*****************************************************************************
- Convert a character pointer in a call_api() response to a form we can use.
- This function contains code to prevent core dumps if the server returns
- invalid data.
-*****************************************************************************/
-static char *fix_char_ptr(unsigned int datap, unsigned int converter, char *rdata, int rdrcnt)
-{
-if( datap == 0 ) /* turn NULL pointers */
- { /* into zero length strings */
- return "";
- }
-else
- {
- unsigned int offset = datap - converter;
-
- if( offset >= rdrcnt )
- {
- DEBUG(1,("bad char ptr: datap=%u, converter=%u, rdata=%u, rdrcnt=%d>", datap, converter, (unsigned)rdata, rdrcnt));
- return "";
- }
- else
- {
- return &rdata[offset];
- }
- }
-}
-
-/****************************************************************************
-interpret a short filename structure
-The length of the structure is returned
-****************************************************************************/
-static int interpret_short_filename(char *p,file_info *finfo)
-{
- finfo->mode = CVAL(p,21);
-
- /* this date is converted to GMT by make_unix_date */
- finfo->ctime = make_unix_date(p+22);
- finfo->mtime = finfo->atime = finfo->ctime;
- finfo->size = IVAL(p,26);
- strcpy(finfo->name,p+30);
-
- return(DIR_STRUCT_SIZE);
-}
-
-/****************************************************************************
-interpret a long filename structure - this is mostly guesses at the moment
-The length of the structure is returned
-The structure of a long filename depends on the info level. 260 is used
-by NT and 2 is used by OS/2
-****************************************************************************/
-static int interpret_long_filename(int level,char *p,file_info *finfo)
-{
- if (finfo)
- memcpy(finfo,&def_finfo,sizeof(*finfo));
-
- switch (level)
- {
- case 1: /* OS/2 understands this */
- if (finfo)
- {
- /* these dates are converted to GMT by make_unix_date */
- finfo->ctime = make_unix_date2(p+4);
- finfo->atime = make_unix_date2(p+8);
- finfo->mtime = make_unix_date2(p+12);
- finfo->size = IVAL(p,16);
- finfo->mode = CVAL(p,24);
- strcpy(finfo->name,p+27);
- }
- return(28 + CVAL(p,26));
-
- case 2: /* this is what OS/2 uses mostly */
- if (finfo)
- {
- /* these dates are converted to GMT by make_unix_date */
- finfo->ctime = make_unix_date2(p+4);
- finfo->atime = make_unix_date2(p+8);
- finfo->mtime = make_unix_date2(p+12);
- finfo->size = IVAL(p,16);
- finfo->mode = CVAL(p,24);
- strcpy(finfo->name,p+31);
- }
- return(32 + CVAL(p,30));
-
- /* levels 3 and 4 are untested */
- case 3:
- if (finfo)
- {
- /* these dates are probably like the other ones */
- finfo->ctime = make_unix_date2(p+8);
- finfo->atime = make_unix_date2(p+12);
- finfo->mtime = make_unix_date2(p+16);
- finfo->size = IVAL(p,20);
- finfo->mode = CVAL(p,28);
- strcpy(finfo->name,p+33);
- }
- return(SVAL(p,4)+4);
-
- case 4:
- if (finfo)
- {
- /* these dates are probably like the other ones */
- finfo->ctime = make_unix_date2(p+8);
- finfo->atime = make_unix_date2(p+12);
- finfo->mtime = make_unix_date2(p+16);
- finfo->size = IVAL(p,20);
- finfo->mode = CVAL(p,28);
- strcpy(finfo->name,p+37);
- }
- return(SVAL(p,4)+4);
-
- case 260: /* NT uses this, but also accepts 2 */
- if (finfo)
- {
- int ret = SVAL(p,0);
- int namelen;
- p += 4; /* next entry offset */
- p += 4; /* fileindex */
-
- /* these dates appear to arrive in a weird way. It seems to
- be localtime plus the serverzone given in the initial
- connect. This is GMT when DST is not in effect and one
- hour from GMT otherwise. Can this really be right??
-
- I suppose this could be called kludge-GMT. Is is the GMT
- you get by using the current DST setting on a different
- localtime. It will be cheap to calculate, I suppose, as
- no DST tables will be needed */
-
- finfo->ctime = interpret_long_date(p); p += 8;
- finfo->atime = interpret_long_date(p); p += 8;
- finfo->mtime = interpret_long_date(p); p += 8; p += 8;
- finfo->size = IVAL(p,0); p += 8;
- p += 8; /* alloc size */
- finfo->mode = CVAL(p,0); p += 4;
- namelen = IVAL(p,0); p += 4;
- p += 4; /* EA size */
- p += 2; /* short name len? */
- p += 24; /* short name? */
- StrnCpy(finfo->name,p,namelen);
- return(ret);
- }
- return(SVAL(p,0));
- }
-
- DEBUG(1,("Unknown long filename format %d\n",level));
- return(SVAL(p,0));
-}
-
-
-
-
-/****************************************************************************
- act on the files in a dir listing
- ****************************************************************************/
-static void dir_action(char *inbuf,char *outbuf,int attribute,file_info *finfo,BOOL recurse_dir,void (*fn)(),BOOL longdir)
-{
-
- if (!((finfo->mode & aDIR) == 0 && *fileselection &&
- !mask_match(finfo->name,fileselection,False,False)) &&
- !(recurse_dir && (strequal(finfo->name,".") ||
- strequal(finfo->name,".."))))
- {
- if (recurse_dir && (finfo->mode & aDIR))
- {
- pstring mask2;
- pstring sav_dir;
- strcpy(sav_dir,cur_dir);
- strcat(cur_dir,finfo->name);
- strcat(cur_dir,"\\");
- strcpy(mask2,cur_dir);
-
- if (!fn)
- DEBUG(0,("\n%s\n",CNV_LANG(cur_dir)));
-
- strcat(mask2,"*");
-
- if (longdir)
- do_long_dir(inbuf,outbuf,mask2,attribute,fn,True);
- else
- do_dir(inbuf,outbuf,mask2,attribute,fn,True);
-
- strcpy(cur_dir,sav_dir);
- }
- else
- {
- if (fn && do_this_one(finfo))
- fn(finfo);
- }
- }
-}
-
-
-/****************************************************************************
- receive a SMB trans or trans2 response allocating the necessary memory
- ****************************************************************************/
-static BOOL receive_trans_response(char *inbuf,int trans,
- int *data_len,int *param_len,
- char **data,char **param)
-{
- int total_data=0;
- int total_param=0;
- int this_data,this_param;
-
- *data_len = *param_len = 0;
-
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
- show_msg(inbuf);
-
- /* sanity check */
- if (CVAL(inbuf,smb_com) != trans)
- {
- DEBUG(0,("Expected %s response, got command 0x%02x\n",
- trans==SMBtrans?"SMBtrans":"SMBtrans2", CVAL(inbuf,smb_com)));
- return(False);
- }
- if (CVAL(inbuf,smb_rcls) != 0)
- return(False);
-
- /* parse out the lengths */
- total_data = SVAL(inbuf,smb_tdrcnt);
- total_param = SVAL(inbuf,smb_tprcnt);
-
- /* allocate it */
- *data = Realloc(*data,total_data);
- *param = Realloc(*param,total_param);
-
- while (1)
- {
- this_data = SVAL(inbuf,smb_drcnt);
- this_param = SVAL(inbuf,smb_prcnt);
- if (this_data)
- memcpy(*data + SVAL(inbuf,smb_drdisp),
- smb_base(inbuf) + SVAL(inbuf,smb_droff),
- this_data);
- if (this_param)
- memcpy(*param + SVAL(inbuf,smb_prdisp),
- smb_base(inbuf) + SVAL(inbuf,smb_proff),
- this_param);
- *data_len += this_data;
- *param_len += this_param;
-
- /* parse out the total lengths again - they can shrink! */
- total_data = SVAL(inbuf,smb_tdrcnt);
- total_param = SVAL(inbuf,smb_tprcnt);
-
- if (total_data <= *data_len && total_param <= *param_len)
- break;
-
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
- show_msg(inbuf);
-
- /* sanity check */
- if (CVAL(inbuf,smb_com) != trans)
- {
- DEBUG(0,("Expected %s response, got command 0x%02x\n",
- trans==SMBtrans?"SMBtrans":"SMBtrans2", CVAL(inbuf,smb_com)));
- return(False);
- }
- if (CVAL(inbuf,smb_rcls) != 0)
- return(False);
- }
-
- return(True);
-}
-
-
-/****************************************************************************
- get a directory listing
- ****************************************************************************/
-static void cmd_dir(char *inbuf,char *outbuf)
-{
- int attribute = aDIR | aSYSTEM | aHIDDEN;
- pstring mask;
- fstring buf;
- char *p=buf;
-
- strcpy(mask,cur_dir);
- if(mask[strlen(mask)-1]!='\\')
- strcat(mask,"\\");
-
- if (next_token(NULL,buf,NULL))
- {
- if (*p == '\\')
- strcpy(mask,p);
- else
- strcat(mask,p);
- }
- else {
- strcat(mask,"*");
- }
-
- do_dir(inbuf,outbuf,mask,attribute,NULL,recurse);
-
- do_dskattr();
-}
-
-
-
-/****************************************************************************
- get a file from rname to lname
- ****************************************************************************/
-static void do_get(char *rname,char *lname,file_info *finfo1)
-{
- int handle=0,fnum;
- uint32 nread=0;
- char *p;
- BOOL newhandle = False;
- char *inbuf,*outbuf;
- file_info finfo;
- BOOL close_done = False;
- BOOL ignore_close_error = False;
- char *dataptr=NULL;
- int datalen=0;
-
- struct timeval tp_start;
- GetTimeOfDay(&tp_start);
-
- if (finfo1)
- finfo = *finfo1;
- else
- finfo = def_finfo;
-
- if (lowercase)
- strlower(lname);
-
-
- inbuf = (char *)malloc(BUFFER_SIZE + SAFETY_MARGIN);
- outbuf = (char *)malloc(BUFFER_SIZE + SAFETY_MARGIN);
-
- if (!inbuf || !outbuf)
- {
- DEBUG(0,("out of memory\n"));
- return;
- }
-
- bzero(outbuf,smb_size);
- set_message(outbuf,15,1 + strlen(rname),True);
-
- CVAL(outbuf,smb_com) = SMBopenX;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- SSVAL(outbuf,smb_vwv0,0xFF);
- SSVAL(outbuf,smb_vwv2,1);
- SSVAL(outbuf,smb_vwv3,(DENY_NONE<<4));
- SSVAL(outbuf,smb_vwv4,aSYSTEM | aHIDDEN);
- SSVAL(outbuf,smb_vwv5,aSYSTEM | aHIDDEN);
- SSVAL(outbuf,smb_vwv8,1);
-
- p = smb_buf(outbuf);
- strcpy(p,rname);
- p = skip_string(p,1);
-
- /* do a chained openX with a readX? */
-#if 1
- if (finfo.size > 0)
- {
- DEBUG(3,("Chaining readX wth openX\n"));
- SSVAL(outbuf,smb_vwv0,SMBreadX);
- SSVAL(outbuf,smb_vwv1,smb_offset(p,outbuf));
- bzero(p,200);
- p -= smb_wct;
- SSVAL(p,smb_wct,10);
- SSVAL(p,smb_vwv0,0xFF);
- SSVAL(p,smb_vwv5,MIN(max_xmit-500,finfo.size));
- SSVAL(p,smb_vwv9,MIN(BUFFER_SIZE,finfo.size));
- smb_setlen(outbuf,smb_len(outbuf)+11*2+1);
- }
-#endif
-
- if(!strcmp(lname,"-"))
- handle = fileno(stdout);
- else
- {
- handle = creat(lname,0644);
- newhandle = True;
- }
- if (handle < 0)
- {
- DEBUG(0,("Error opening local file %s\n",lname));
- free(inbuf);free(outbuf);
- return;
- }
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- if (CVAL(inbuf,smb_rcls) == ERRSRV &&
- SVAL(inbuf,smb_err) == ERRnoresource &&
- reopen_connection(inbuf,outbuf))
- {
- do_get(rname,lname,finfo1);
- return;
- }
- DEBUG(0,("%s opening remote file %s\n",smb_errstr(inbuf),CNV_LANG(rname)));
- if(newhandle)
- close(handle);
- free(inbuf);free(outbuf);
- return;
- }
-
- strcpy(finfo.name,rname);
-
- if (!finfo1)
- {
- finfo.mode = SVAL(inbuf,smb_vwv3);
- /* these times arrive as LOCAL time, using the DST offset
- corresponding to that time, we convert them to GMT */
- finfo.mtime = make_unix_date3(inbuf+smb_vwv4);
- finfo.atime = finfo.ctime = finfo.mtime;
- finfo.size = IVAL(inbuf,smb_vwv6);
- }
-
- DEBUG(3,("file %s attrib 0x%X\n",CNV_LANG(finfo.name),finfo.mode));
-
- fnum = SVAL(inbuf,smb_vwv2);
-
- /* we might have got some data from a chained readX */
- if (SVAL(inbuf,smb_vwv0) == SMBreadX)
- {
- p = (smb_base(inbuf)+SVAL(inbuf,smb_vwv1)) - smb_wct;
- datalen = SVAL(p,smb_vwv5);
- dataptr = smb_base(inbuf) + SVAL(p,smb_vwv6);
- }
- else
- {
- dataptr = NULL;
- datalen = 0;
- }
-
-
- DEBUG(2,("getting file %s of size %d bytes as %s ",
- CNV_LANG(finfo.name),
- finfo.size,
- lname));
-
- while (nread < finfo.size && !close_done)
- {
- int method = -1;
- static BOOL can_chain_close = True;
-
- p=NULL;
-
- DEBUG(3,("nread=%d max_xmit=%d fsize=%d\n",nread,max_xmit,finfo.size));
-
- /* 3 possible read types. readbraw if a large block is required.
- readX + close if not much left and read if neither is supported */
-
- /* we might have already read some data from a chained readX */
- if (dataptr && datalen>0)
- method=3;
-
- /* if we can finish now then readX+close */
- if (method<0 && can_chain_close && (Protocol >= PROTOCOL_LANMAN1) &&
- ((finfo.size - nread) <
- (max_xmit - (2*smb_size + 13*SIZEOFWORD + 300))))
- method = 0;
-
- /* if we support readraw then use that */
- if (method<0 && readbraw_supported)
- method = 1;
-
- /* if we can then use readX */
- if (method<0 && (Protocol >= PROTOCOL_LANMAN1))
- method = 2;
-
- switch (method)
- {
- /* use readX */
- case 0:
- case 2:
- if (method == 0)
- close_done = True;
-
- /* use readX + close */
- bzero(outbuf,smb_size);
- set_message(outbuf,10,0,True);
- CVAL(outbuf,smb_com) = SMBreadX;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- if (close_done)
- {
- CVAL(outbuf,smb_vwv0) = SMBclose;
- SSVAL(outbuf,smb_vwv1,smb_offset(smb_buf(outbuf),outbuf));
- }
- else
- CVAL(outbuf,smb_vwv0) = 0xFF;
-
- SSVAL(outbuf,smb_vwv2,fnum);
- SIVAL(outbuf,smb_vwv3,nread);
- SSVAL(outbuf,smb_vwv5,MIN(max_xmit-200,finfo.size - nread));
- SSVAL(outbuf,smb_vwv6,0);
- SIVAL(outbuf,smb_vwv7,0);
- SSVAL(outbuf,smb_vwv9,MIN(BUFFER_SIZE,finfo.size-nread));
-
- if (close_done)
- {
- p = smb_buf(outbuf);
- bzero(p,9);
-
- CVAL(p,0) = 3;
- SSVAL(p,1,fnum);
- SIVALS(p,3,-1);
-
- /* now set the total packet length */
- smb_setlen(outbuf,smb_len(outbuf)+9);
- }
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- DEBUG(0,("Error %s reading remote file\n",smb_errstr(inbuf)));
- break;
- }
-
- if (close_done &&
- SVAL(inbuf,smb_vwv0) != SMBclose)
- {
- /* NOTE: WfWg sometimes just ignores the chained
- command! This seems to break the spec? */
- DEBUG(3,("Rejected chained close?\n"));
- close_done = False;
- can_chain_close = False;
- ignore_close_error = True;
- }
-
- datalen = SVAL(inbuf,smb_vwv5);
- dataptr = smb_base(inbuf) + SVAL(inbuf,smb_vwv6);
- break;
-
- /* use readbraw */
- case 1:
- {
- static int readbraw_size = BUFFER_SIZE;
-
- extern int Client;
- bzero(outbuf,smb_size);
- set_message(outbuf,8,0,True);
- CVAL(outbuf,smb_com) = SMBreadbraw;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
- SSVAL(outbuf,smb_vwv0,fnum);
- SIVAL(outbuf,smb_vwv1,nread);
- SSVAL(outbuf,smb_vwv3,MIN(finfo.size-nread,readbraw_size));
- SSVAL(outbuf,smb_vwv4,0);
- SIVALS(outbuf,smb_vwv5,-1);
- send_smb(Client,outbuf);
-
- /* Now read the raw data into the buffer and write it */
- if(read_smb_length(Client,inbuf,0) == -1) {
- DEBUG(0,("Failed to read length in readbraw\n"));
- exit(1);
- }
-
- /* Even though this is not an smb message, smb_len
- returns the generic length of an smb message */
- datalen = smb_len(inbuf);
-
- if (datalen == 0)
- {
- /* we got a readbraw error */
- DEBUG(4,("readbraw error - reducing size\n"));
- readbraw_size = (readbraw_size * 9) / 10;
-
- if (readbraw_size < max_xmit)
- {
- DEBUG(0,("disabling readbraw\n"));
- readbraw_supported = False;
- }
-
- dataptr=NULL;
- continue;
- }
-
- if(read_data(Client,inbuf,datalen) != datalen) {
- DEBUG(0,("Failed to read data in readbraw\n"));
- exit(1);
- }
- dataptr = inbuf;
- }
- break;
-
- case 3:
- /* we've already read some data with a chained readX */
- break;
-
- default:
- /* use plain read */
- bzero(outbuf,smb_size);
- set_message(outbuf,5,0,True);
- CVAL(outbuf,smb_com) = SMBread;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- SSVAL(outbuf,smb_vwv0,fnum);
- SSVAL(outbuf,smb_vwv1,MIN(max_xmit-200,finfo.size - nread));
- SIVAL(outbuf,smb_vwv2,nread);
- SSVAL(outbuf,smb_vwv4,finfo.size - nread);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- DEBUG(0,("Error %s reading remote file\n",smb_errstr(inbuf)));
- break;
- }
-
- datalen = SVAL(inbuf,smb_vwv0);
- dataptr = smb_buf(inbuf) + 3;
- break;
- }
-
- if (writefile(handle,dataptr,datalen) != datalen)
- {
- DEBUG(0,("Error writing local file\n"));
- break;
- }
-
- nread += datalen;
- if (datalen == 0)
- {
- DEBUG(0,("Error reading file %s. Got %d bytes\n",CNV_LANG(rname),nread));
- break;
- }
-
- dataptr=NULL;
- datalen=0;
- }
-
-
-
- if (!close_done)
- {
- bzero(outbuf,smb_size);
- set_message(outbuf,3,0,True);
- CVAL(outbuf,smb_com) = SMBclose;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- SSVAL(outbuf,smb_vwv0,fnum);
- SIVALS(outbuf,smb_vwv1,-1);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (!ignore_close_error && CVAL(inbuf,smb_rcls) != 0)
- {
- DEBUG(0,("Error %s closing remote file\n",smb_errstr(inbuf)));
- if(newhandle)
- close(handle);
- free(inbuf);free(outbuf);
- return;
- }
- }
-
- if(newhandle)
- close(handle);
-
- if (archive_level >= 2 && (finfo.mode & aARCH)) {
- bzero(outbuf,smb_size);
- set_message(outbuf,8,strlen(rname)+4,True);
- CVAL(outbuf,smb_com) = SMBsetatr;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
- SSVAL(outbuf,smb_vwv0,finfo.mode & ~(aARCH));
- SIVALS(outbuf,smb_vwv1,0);
- p = smb_buf(outbuf);
- *p++ = 4;
- strcpy(p,rname);
- p += strlen(p)+1;
- *p++ = 4;
- *p = 0;
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
- }
-
- {
- struct timeval tp_end;
- int this_time;
-
- GetTimeOfDay(&tp_end);
- this_time =
- (tp_end.tv_sec - tp_start.tv_sec)*1000 +
- (tp_end.tv_usec - tp_start.tv_usec)/1000;
- get_total_time_ms += this_time;
- get_total_size += finfo.size;
-
- DEBUG(1,("(%g kb/s) (average %g kb/s)\n",
- finfo.size / (1.024*this_time + 1.0e-4),
- get_total_size / (1.024*get_total_time_ms)));
- }
-
- free(inbuf);free(outbuf);
-}
-
-
-/****************************************************************************
- get a file
- ****************************************************************************/
-static void cmd_get(void)
-{
- pstring lname;
- pstring rname;
- char *p;
-
- strcpy(rname,cur_dir);
- strcat(rname,"\\");
-
- p = rname + strlen(rname);
-
- if (!next_token(NULL,p,NULL)) {
- DEBUG(0,("get \n"));
- return;
- }
- strcpy(lname,p);
- dos_clean_name(rname);
-
- next_token(NULL,lname,NULL);
-
- do_get(rname,lname,NULL);
-}
-
-
-/****************************************************************************
- do a mget operation on one file
- ****************************************************************************/
-static void do_mget(file_info *finfo)
-{
- pstring rname;
- pstring quest;
-
- if (strequal(finfo->name,".") || strequal(finfo->name,".."))
- return;
-
- if (abort_mget)
- {
- DEBUG(0,("mget aborted\n"));
- return;
- }
-
- if (finfo->mode & aDIR)
- sprintf(quest,"Get directory %s? ",CNV_LANG(finfo->name));
- else
- sprintf(quest,"Get file %s? ",CNV_LANG(finfo->name));
-
- if (prompt && !yesno(quest)) return;
-
- if (finfo->mode & aDIR)
- {
- pstring saved_curdir;
- pstring mget_mask;
- char *inbuf,*outbuf;
-
- inbuf = (char *)malloc(BUFFER_SIZE + SAFETY_MARGIN);
- outbuf = (char *)malloc(BUFFER_SIZE + SAFETY_MARGIN);
-
- if (!inbuf || !outbuf)
- {
- DEBUG(0,("out of memory\n"));
- return;
- }
-
- strcpy(saved_curdir,cur_dir);
-
- strcat(cur_dir,finfo->name);
- strcat(cur_dir,"\\");
-
- unix_format(finfo->name);
- {
- if (lowercase)
- strlower(finfo->name);
-
- if (!directory_exist(finfo->name,NULL) &&
- sys_mkdir(finfo->name,0777) != 0)
- {
- DEBUG(0,("failed to create directory %s\n",CNV_LANG(finfo->name)));
- strcpy(cur_dir,saved_curdir);
- free(inbuf);free(outbuf);
- return;
- }
-
- if (sys_chdir(finfo->name) != 0)
- {
- DEBUG(0,("failed to chdir to directory %s\n",CNV_LANG(finfo->name)));
- strcpy(cur_dir,saved_curdir);
- free(inbuf);free(outbuf);
- return;
- }
- }
-
- strcpy(mget_mask,cur_dir);
- strcat(mget_mask,"*");
-
- do_dir((char *)inbuf,(char *)outbuf,
- mget_mask,aSYSTEM | aHIDDEN | aDIR,do_mget,False);
- chdir("..");
- strcpy(cur_dir,saved_curdir);
- free(inbuf);free(outbuf);
- }
- else
- {
- strcpy(rname,cur_dir);
- strcat(rname,finfo->name);
- do_get(rname,finfo->name,finfo);
- }
-}
-
-/****************************************************************************
-view the file using the pager
-****************************************************************************/
-static void cmd_more(void)
-{
- fstring rname,lname,tmpname,pager_cmd;
- char *pager;
-
- strcpy(rname,cur_dir);
- strcat(rname,"\\");
- sprintf(tmpname,"%s/smbmore.%d",tmpdir(),(int)getpid());
- strcpy(lname,tmpname);
-
- if (!next_token(NULL,rname+strlen(rname),NULL)) {
- DEBUG(0,("more \n"));
- return;
- }
- dos_clean_name(rname);
-
- do_get(rname,lname,NULL);
-
- pager=getenv("PAGER");
- sprintf(pager_cmd,"%s %s",(pager? pager:PAGER), tmpname);
- system(pager_cmd);
- unlink(tmpname);
-}
-
-
-
-/****************************************************************************
-do a mget command
-****************************************************************************/
-static void cmd_mget(char *inbuf,char *outbuf)
-{
- int attribute = aSYSTEM | aHIDDEN;
- pstring mget_mask;
- fstring buf;
- char *p=buf;
-
- *mget_mask = 0;
-
- if (recurse)
- attribute |= aDIR;
-
- abort_mget = False;
-
- while (next_token(NULL,p,NULL))
- {
- strcpy(mget_mask,cur_dir);
- if(mget_mask[strlen(mget_mask)-1]!='\\')
- strcat(mget_mask,"\\");
-
- if (*p == '\\')
- strcpy(mget_mask,p);
- else
- strcat(mget_mask,p);
- do_dir((char *)inbuf,(char *)outbuf,mget_mask,attribute,do_mget,False);
- }
-
- if (! *mget_mask)
- {
- strcpy(mget_mask,cur_dir);
- if(mget_mask[strlen(mget_mask)-1]!='\\')
- strcat(mget_mask,"\\");
- strcat(mget_mask,"*");
- do_dir((char *)inbuf,(char *)outbuf,mget_mask,attribute,do_mget,False);
- }
-}
-
-/****************************************************************************
-make a directory of name "name"
-****************************************************************************/
-static BOOL do_mkdir(char *name)
-{
- char *p;
- char *inbuf,*outbuf;
-
- inbuf = (char *)malloc(BUFFER_SIZE + SAFETY_MARGIN);
- outbuf = (char *)malloc(BUFFER_SIZE + SAFETY_MARGIN);
-
- if (!inbuf || !outbuf)
- {
- DEBUG(0,("out of memory\n"));
- return False;
- }
-
- bzero(outbuf,smb_size);
- set_message(outbuf,0,2 + strlen(name),True);
-
- CVAL(outbuf,smb_com) = SMBmkdir;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
-
- p = smb_buf(outbuf);
- *p++ = 4;
- strcpy(p,name);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- DEBUG(0,("%s making remote directory %s\n",
- smb_errstr(inbuf),CNV_LANG(name)));
-
- free(inbuf);free(outbuf);
- return(False);
- }
-
- free(inbuf);free(outbuf);
- return(True);
-}
-
-
-/****************************************************************************
- make a directory
- ****************************************************************************/
-static void cmd_mkdir(char *inbuf,char *outbuf)
-{
- pstring mask;
- fstring buf;
- char *p=buf;
-
- strcpy(mask,cur_dir);
-
- if (!next_token(NULL,p,NULL))
- {
- if (!recurse)
- DEBUG(0,("mkdir \n"));
- return;
- }
- strcat(mask,p);
-
- if (recurse)
- {
- pstring ddir;
- pstring ddir2;
- *ddir2 = 0;
-
- strcpy(ddir,mask);
- trim_string(ddir,".",NULL);
- p = strtok(ddir,"/\\");
- while (p)
- {
- strcat(ddir2,p);
- if (!chkpath(ddir2,False))
- {
- do_mkdir(ddir2);
- }
- strcat(ddir2,"\\");
- p = strtok(NULL,"/\\");
- }
- }
- else
- do_mkdir(mask);
-}
-
-
-/*******************************************************************
- write to a file using writebraw
- ********************************************************************/
-static int smb_writeraw(char *outbuf,int fnum,int pos,char *buf,int n)
-{
- extern int Client;
- pstring inbuf;
-
- bzero(outbuf,smb_size);
- bzero(inbuf,smb_size);
- set_message(outbuf,Protocol>PROTOCOL_COREPLUS?12:10,0,True);
-
- CVAL(outbuf,smb_com) = SMBwritebraw;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- SSVAL(outbuf,smb_vwv0,fnum);
- SSVAL(outbuf,smb_vwv1,n);
- SIVAL(outbuf,smb_vwv3,pos);
- SSVAL(outbuf,smb_vwv7,1);
-
- send_smb(Client,outbuf);
-
- if (!receive_smb(Client,inbuf,CLIENT_TIMEOUT) || CVAL(inbuf,smb_rcls) != 0)
- return(0);
-
- _smb_setlen(buf-4,n); /* HACK! XXXX */
-
- if (write_socket(Client,buf-4,n+4) != n+4)
- return(0);
-
- if (!receive_smb(Client,inbuf,CLIENT_TIMEOUT) || CVAL(inbuf,smb_rcls) != 0) {
- DEBUG(0,("Error writing remote file (2)\n"));
- return(0);
- }
- return(SVAL(inbuf,smb_vwv0));
-}
-
-
-
-/*******************************************************************
- write to a file
- ********************************************************************/
-static int smb_writefile(char *outbuf,int fnum,int pos,char *buf,int n)
-{
- pstring inbuf;
-
- if (writebraw_supported && n > (max_xmit-200))
- return(smb_writeraw(outbuf,fnum,pos,buf,n));
-
- bzero(outbuf,smb_size);
- bzero(inbuf,smb_size);
- set_message(outbuf,5,n + 3,True);
-
- CVAL(outbuf,smb_com) = SMBwrite;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- SSVAL(outbuf,smb_vwv0,fnum);
- SSVAL(outbuf,smb_vwv1,n);
- SIVAL(outbuf,smb_vwv2,pos);
- SSVAL(outbuf,smb_vwv4,0);
- CVAL(smb_buf(outbuf),0) = 1;
- SSVAL(smb_buf(outbuf),1,n);
-
- memcpy(smb_buf(outbuf)+3,buf,n);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0) {
- DEBUG(0,("%s writing remote file\n",smb_errstr(inbuf)));
- return(0);
- }
- return(SVAL(inbuf,smb_vwv0));
-}
-
-
-
-/****************************************************************************
- put a single file
- ****************************************************************************/
-static void do_put(char *rname,char *lname,file_info *finfo)
-{
- int fnum;
- FILE *f;
- int nread=0;
- char *p;
- char *inbuf,*outbuf;
- time_t close_time = finfo->mtime;
- char *buf=NULL;
- static int maxwrite=0;
-
- struct timeval tp_start;
- GetTimeOfDay(&tp_start);
-
- inbuf = (char *)malloc(BUFFER_SIZE + SAFETY_MARGIN);
- outbuf = (char *)malloc(BUFFER_SIZE + SAFETY_MARGIN);
-
- if (!inbuf || !outbuf)
- {
- DEBUG(0,("out of memory\n"));
- return;
- }
-
- bzero(outbuf,smb_size);
- set_message(outbuf,3,2 + strlen(rname),True);
-
- if (finfo->mtime == 0 || finfo->mtime == -1)
- finfo->mtime = finfo->atime = finfo->ctime = time(NULL);
-
- CVAL(outbuf,smb_com) = SMBcreate;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- SSVAL(outbuf,smb_vwv0,finfo->mode);
- put_dos_date3(outbuf,smb_vwv1,finfo->mtime);
-
- p = smb_buf(outbuf);
- *p++ = 4;
- strcpy(p,rname);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- DEBUG(0,("%s opening remote file %s\n",smb_errstr(inbuf),CNV_LANG(rname)));
-
- free(inbuf);free(outbuf);if (buf) free(buf);
- return;
- }
-
- f = fopen(lname,"r");
-
- if (!f)
- {
- DEBUG(0,("Error opening local file %s\n",lname));
- free(inbuf);free(outbuf);
- return;
- }
-
-
- fnum = SVAL(inbuf,smb_vwv0);
- if (finfo->size < 0)
- finfo->size = file_size(lname);
-
- DEBUG(1,("putting file %s of size %d bytes as %s ",lname,finfo->size,CNV_LANG(rname)));
-
- if (!maxwrite)
- maxwrite = writebraw_supported?MAX(max_xmit,BUFFER_SIZE):(max_xmit-200);
-
- while (nread < finfo->size)
- {
- int n = maxwrite;
- int ret;
-
- n = MIN(n,finfo->size - nread);
-
- buf = (char *)Realloc(buf,n+4);
-
- fseek(f,nread,SEEK_SET);
- if ((n = readfile(buf+4,1,n,f)) < 1)
- {
- DEBUG(0,("Error reading local file\n"));
- break;
- }
-
- ret = smb_writefile(outbuf,fnum,nread,buf+4,n);
-
- if (n != ret) {
- if (!maxwrite) {
- DEBUG(0,("Error writing file\n"));
- break;
- } else {
- maxwrite /= 2;
- continue;
- }
- }
-
- nread += n;
- }
-
-
-
- bzero(outbuf,smb_size);
- set_message(outbuf,3,0,True);
- CVAL(outbuf,smb_com) = SMBclose;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- SSVAL(outbuf,smb_vwv0,fnum);
- put_dos_date3(outbuf,smb_vwv1,close_time);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- DEBUG(0,("%s closing remote file %s\n",smb_errstr(inbuf),CNV_LANG(rname)));
- fclose(f);
- free(inbuf);free(outbuf);
- if (buf) free(buf);
- return;
- }
-
-
- fclose(f);
- free(inbuf);free(outbuf);
- if (buf) free(buf);
-
- {
- struct timeval tp_end;
- int this_time;
-
- GetTimeOfDay(&tp_end);
- this_time =
- (tp_end.tv_sec - tp_start.tv_sec)*1000 +
- (tp_end.tv_usec - tp_start.tv_usec)/1000;
- put_total_time_ms += this_time;
- put_total_size += finfo->size;
-
- DEBUG(1,("(%g kb/s) (average %g kb/s)\n",
- finfo->size / (1.024*this_time + 1.0e-4),
- put_total_size / (1.024*put_total_time_ms)));
- }
-}
-
-
-
-/****************************************************************************
- put a file
- ****************************************************************************/
-static void cmd_put(void)
-{
- pstring lname;
- pstring rname;
- fstring buf;
- char *p=buf;
- file_info finfo;
- finfo = def_finfo;
-
- strcpy(rname,cur_dir);
- strcat(rname,"\\");
-
-
- if (!next_token(NULL,p,NULL))
- {
- DEBUG(0,("put \n"));
- return;
- }
- strcpy(lname,p);
-
- if (next_token(NULL,p,NULL))
- strcat(rname,p);
- else
- strcat(rname,lname);
-
- dos_clean_name(rname);
-
- {
- struct stat st;
- if (!file_exist(lname,&st)) {
- DEBUG(0,("%s does not exist\n",lname));
- return;
- }
- finfo.mtime = st.st_mtime;
- }
-
- do_put(rname,lname,&finfo);
-}
-
-/****************************************************************************
- seek in a directory/file list until you get something that doesn't start with
- the specified name
- ****************************************************************************/
-static BOOL seek_list(FILE *f,char *name)
-{
- pstring s;
- while (!feof(f))
- {
- if (fscanf(f,"%s",s) != 1) return(False);
- trim_string(s,"./",NULL);
- if (strncmp(s,name,strlen(name)) != 0)
- {
- strcpy(name,s);
- return(True);
- }
- }
-
- return(False);
-}
-
-
-/****************************************************************************
- set the file selection mask
- ****************************************************************************/
-static void cmd_select(void)
-{
- strcpy(fileselection,"");
- next_token(NULL,fileselection,NULL);
-}
-
-
-/****************************************************************************
- mput some files
- ****************************************************************************/
-static void cmd_mput(void)
-{
- pstring lname;
- pstring rname;
- file_info finfo;
- fstring buf;
- char *p=buf;
-
- finfo = def_finfo;
-
-
- while (next_token(NULL,p,NULL))
- {
- struct stat st;
- pstring cmd;
- pstring tmpname;
- FILE *f;
-
- sprintf(tmpname,"%s/ls.smb.%d",tmpdir(),(int)getpid());
- if (recurse)
- sprintf(cmd,"find . -name \"%s\" -print > %s",p,tmpname);
- else
- sprintf(cmd,"/bin/ls %s > %s",p,tmpname);
- system(cmd);
-
- f = fopen(tmpname,"r");
- if (!f) continue;
-
- while (!feof(f))
- {
- pstring quest;
-
- if (fscanf(f,"%s",lname) != 1) break;
- trim_string(lname,"./",NULL);
-
- again1:
-
- /* check if it's a directory */
- if (directory_exist(lname,&st))
- {
- if (!recurse) continue;
- sprintf(quest,"Put directory %s? ",lname);
- if (prompt && !yesno(quest))
- {
- strcat(lname,"/");
- if (!seek_list(f,lname))
- break;
- goto again1;
- }
-
- strcpy(rname,cur_dir);
- strcat(rname,lname);
- if (!chkpath(rname,False) && !do_mkdir(rname)) {
- strcat(lname,"/");
- if (!seek_list(f,lname))
- break;
- goto again1;
- }
-
- continue;
- }
- else
- {
- sprintf(quest,"Put file %s? ",lname);
- if (prompt && !yesno(quest)) continue;
-
- strcpy(rname,cur_dir);
- strcat(rname,lname);
- }
- dos_format(rname);
-
- /* null size so do_put knows to ignore it */
- finfo.size = -1;
-
- /* set the date on the file */
- finfo.mtime = st.st_mtime;
-
- do_put(rname,lname,&finfo);
- }
- fclose(f);
- unlink(tmpname);
- }
-}
-
-/****************************************************************************
- cancel a print job
- ****************************************************************************/
-static void do_cancel(int job)
-{
- char *rparam = NULL;
- char *rdata = NULL;
- char *p;
- int rdrcnt,rprcnt;
- pstring param;
-
- bzero(param,sizeof(param));
-
- p = param;
- SSVAL(p,0,81); /* DosPrintJobDel() */
- p += 2;
- strcpy(p,"W");
- p = skip_string(p,1);
- strcpy(p,"");
- p = skip_string(p,1);
- SSVAL(p,0,job);
- p += 2;
-
- if (call_api(PTR_DIFF(p,param),0,
- 6,1000,
- &rprcnt,&rdrcnt,
- param,NULL,
- &rparam,&rdata))
- {
- int res = SVAL(rparam,0);
-
- if (!res)
- printf("Job %d cancelled\n",job);
- else
- printf("Error %d calcelling job %d\n",res,job);
- return;
- }
- else
- printf("Server refused cancel request\n");
-
- if (rparam) free(rparam);
- if (rdata) free(rdata);
-
- return;
-}
-
-
-/****************************************************************************
- cancel a print job
- ****************************************************************************/
-static void cmd_cancel(char *inbuf,char *outbuf )
-{
- fstring buf;
- int job;
-
- if (!connect_as_printer)
- {
- DEBUG(0,("WARNING: You didn't use the -P option to smbclient.\n"));
- DEBUG(0,("Trying to cancel print jobs without -P may fail\n"));
- }
-
- if (!next_token(NULL,buf,NULL)) {
- printf("cancel ...\n");
- return;
- }
- do {
- job = atoi(buf);
- do_cancel(job);
- } while (next_token(NULL,buf,NULL));
-}
-
-
-/****************************************************************************
- get info on a file
- ****************************************************************************/
-static void cmd_stat(char *inbuf,char *outbuf)
-{
- fstring buf;
- pstring param;
- char *resp_data=NULL;
- char *resp_param=NULL;
- int resp_data_len = 0;
- int resp_param_len=0;
- char *p;
- uint16 setup = TRANSACT2_QPATHINFO;
-
- if (!next_token(NULL,buf,NULL)) {
- printf("stat \n");
- return;
- }
-
- bzero(param,6);
- SSVAL(param,0,4); /* level */
- p = param+6;
- strcpy(p,cur_dir);
- strcat(p,buf);
-
- send_trans_request(outbuf,SMBtrans2,NULL,FID_UNUSED,0,
- NULL,param,&setup,
- 0,6 + strlen(p)+1,1,
- BUFFER_SIZE,2,0);
-
- receive_trans_response(inbuf,SMBtrans2,
- &resp_data_len,&resp_param_len,
- &resp_data,&resp_param);
-
- if (resp_data) free(resp_data); resp_data = NULL;
- if (resp_param) free(resp_param); resp_param = NULL;
-}
-
-
-/****************************************************************************
- print a file
- ****************************************************************************/
-static void cmd_print(char *inbuf,char *outbuf )
-{
- int fnum;
- FILE *f = NULL;
- uint32 nread=0;
- pstring lname;
- pstring rname;
- char *p;
-
- if (!connect_as_printer)
- {
- DEBUG(0,("WARNING: You didn't use the -P option to smbclient.\n"));
- DEBUG(0,("Trying to print without -P may fail\n"));
- }
-
- if (!next_token(NULL,lname,NULL))
- {
- DEBUG(0,("print \n"));
- return;
- }
-
- strcpy(rname,lname);
- p = strrchr(rname,'/');
- if (p)
- {
- pstring tname;
- strcpy(tname,p+1);
- strcpy(rname,tname);
- }
-
- if ((int)strlen(rname) > 14)
- rname[14] = 0;
-
- if (strequal(lname,"-"))
- {
- f = stdin;
- strcpy(rname,"stdin");
- }
-
- dos_clean_name(rname);
-
- bzero(outbuf,smb_size);
- set_message(outbuf,2,2 + strlen(rname),True);
-
- CVAL(outbuf,smb_com) = SMBsplopen;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- SSVAL(outbuf,smb_vwv0,0);
- SSVAL(outbuf,smb_vwv1,printmode);
-
- p = smb_buf(outbuf);
- *p++ = 4;
- strcpy(p,rname);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- DEBUG(0,("%s opening printer for %s\n",smb_errstr(inbuf),CNV_LANG(rname)));
- return;
- }
-
- if (!f)
- f = fopen(lname,"r");
- if (!f)
- {
- DEBUG(0,("Error opening local file %s\n",lname));
- return;
- }
-
-
- fnum = SVAL(inbuf,smb_vwv0);
-
- DEBUG(1,("printing file %s as %s\n",lname,CNV_LANG(rname)));
-
- while (!feof(f))
- {
- int n;
-
- bzero(outbuf,smb_size);
- set_message(outbuf,1,3,True);
-
- /* for some strange reason the OS/2 print server can't handle large
- packets when printing. weird */
- n = MIN(1024,max_xmit-(smb_len(outbuf)+4));
-
- if (translation)
- n = printread(f,smb_buf(outbuf)+3,(int)(0.95*n));
- else
- n = readfile(smb_buf(outbuf)+3,1,n,f);
- if (n <= 0)
- {
- DEBUG(0,("read gave %d\n",n));
- break;
- }
-
- smb_setlen(outbuf,smb_len(outbuf) + n);
-
- CVAL(outbuf,smb_com) = SMBsplwr;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- SSVAL(outbuf,smb_vwv0,fnum);
- SSVAL(outbuf,smb_vwv1,n+3);
- CVAL(smb_buf(outbuf),0) = 1;
- SSVAL(smb_buf(outbuf),1,n);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- DEBUG(0,("%s printing remote file\n",smb_errstr(inbuf)));
- break;
- }
-
- nread += n;
- }
-
- DEBUG(2,("%d bytes printed\n",nread));
-
- bzero(outbuf,smb_size);
- set_message(outbuf,1,0,True);
- CVAL(outbuf,smb_com) = SMBsplclose;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- SSVAL(outbuf,smb_vwv0,fnum);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- DEBUG(0,("%s closing print file\n",smb_errstr(inbuf)));
- if (f != stdin)
- fclose(f);
- return;
- }
-
- if (f != stdin)
- fclose(f);
-}
-
-/****************************************************************************
-show a print queue - this is deprecated as it uses the old smb that
-has limited support - the correct call is the cmd_p_queue_4() after this.
-****************************************************************************/
-static void cmd_queue(char *inbuf,char *outbuf )
-{
- int count;
- char *p;
-
- bzero(outbuf,smb_size);
- set_message(outbuf,2,0,True);
-
- CVAL(outbuf,smb_com) = SMBsplretq;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- SSVAL(outbuf,smb_vwv0,32); /* a max of 20 entries is to be shown */
- SSVAL(outbuf,smb_vwv1,0); /* the index into the queue */
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- DEBUG(0,("%s obtaining print queue\n",smb_errstr(inbuf)));
- return;
- }
-
- count = SVAL(inbuf,smb_vwv0);
- p = smb_buf(inbuf) + 3;
- if (count <= 0)
- {
- DEBUG(0,("No entries in the print queue\n"));
- return;
- }
-
- {
- char status[20];
-
- DEBUG(0,("Job Name Size Status\n"));
-
- while (count--)
- {
- switch (CVAL(p,4))
- {
- case 0x01: sprintf(status,"held or stopped"); break;
- case 0x02: sprintf(status,"printing"); break;
- case 0x03: sprintf(status,"awaiting print"); break;
- case 0x04: sprintf(status,"in intercept"); break;
- case 0x05: sprintf(status,"file had error"); break;
- case 0x06: sprintf(status,"printer error"); break;
- default: sprintf(status,"unknown"); break;
- }
-
- DEBUG(0,("%-6d %-16.16s %-9d %s\n",
- SVAL(p,5),p+12,IVAL(p,7),status));
- p += 28;
- }
- }
-
-}
-
-
-/****************************************************************************
-show information about a print queue
-****************************************************************************/
-static void cmd_p_queue_4(char *inbuf,char *outbuf )
-{
- char *rparam = NULL;
- char *rdata = NULL;
- char *p;
- int rdrcnt, rprcnt;
- pstring param;
- int result_code=0;
-
- if (!connect_as_printer)
- {
- DEBUG(0,("WARNING: You didn't use the -P option to smbclient.\n"));
- DEBUG(0,("Trying to print without -P may fail\n"));
- }
-
- bzero(param,sizeof(param));
-
- p = param;
- SSVAL(p,0,76); /* API function number 76 (DosPrintJobEnum) */
- p += 2;
- strcpy(p,"zWrLeh"); /* parameter description? */
- p = skip_string(p,1);
- strcpy(p,"WWzWWDDzz"); /* returned data format */
- p = skip_string(p,1);
- strcpy(p,strrchr(service,'\\')+1); /* name of queue */
- p = skip_string(p,1);
- SSVAL(p,0,2); /* API function level 2, PRJINFO_2 data structure */
- SSVAL(p,2,1000); /* size of bytes of returned data buffer */
- p += 4;
- strcpy(p,""); /* subformat */
- p = skip_string(p,1);
-
- DEBUG(1,("Calling DosPrintJobEnum()...\n"));
- if( call_api(PTR_DIFF(p,param), 0,
- 10, 4096,
- &rprcnt, &rdrcnt,
- param, NULL,
- &rparam, &rdata) )
- {
- int converter;
- result_code = SVAL(rparam,0);
- converter = SVAL(rparam,2); /* conversion factor */
-
- DEBUG(2,("returned %d bytes of parameters, %d bytes of data, %d records\n", rprcnt, rdrcnt, SVAL(rparam,4) ));
-
- if (result_code == 0) /* if no error, */
- {
- int i;
- uint16 JobId;
- uint16 Priority;
- uint32 Size;
- char *UserName;
- char *JobName;
- char *JobTimeStr;
- time_t JobTime;
- char PrinterName[20];
-
- strcpy(PrinterName,strrchr(service,'\\')+1); /* name of queue */
- strlower(PrinterName); /* in lower case */
-
- p = rdata; /* received data */
- for( i = 0; i < SVAL(rparam,4); ++i)
- {
- JobId = SVAL(p,0);
- Priority = SVAL(p,2);
- UserName = fix_char_ptr(SVAL(p,4), converter, rdata, rdrcnt);
- strlower(UserName);
- Priority = SVAL(p,2);
- JobTime = make_unix_date3( p + 12);
- JobTimeStr = asctime(LocalTime( &JobTime));
- Size = IVAL(p,16);
- JobName = fix_char_ptr(SVAL(p,24), converter, rdata, rdrcnt);
-
-
- printf("%s-%u %s priority %u %s %s %u bytes\n",
- PrinterName, JobId, UserName,
- Priority, JobTimeStr, JobName, Size);
-
-#if 0 /* DEBUG code */
- printf("Job Id: \"%u\"\n", SVAL(p,0));
- printf("Priority: \"%u\"\n", SVAL(p,2));
-
- printf("User Name: \"%s\"\n", fix_char_ptr(SVAL(p,4), converter, rdata, rdrcnt) );
- printf("Position: \"%u\"\n", SVAL(p,8));
- printf("Status: \"%u\"\n", SVAL(p,10));
-
- JobTime = make_unix_date3( p + 12);
- printf("Submitted: \"%s\"\n", asctime(LocalTime(&JobTime)));
- printf("date: \"%u\"\n", SVAL(p,12));
-
- printf("Size: \"%u\"\n", SVAL(p,16));
- printf("Comment: \"%s\"\n", fix_char_ptr(SVAL(p,20), converter, rdata, rdrcnt) );
- printf("Document: \"%s\"\n", fix_char_ptr(SVAL(p,24), converter, rdata, rdrcnt) );
-#endif /* DEBUG CODE */
- p += 28;
- }
- }
- }
- else /* call_api() failed */
- {
- printf("Failed, error = %d\n", result_code);
- }
-
- /* If any parameters or data were returned, free the storage. */
- if(rparam) free(rparam);
- if(rdata) free(rdata);
-
- return;
-}
-
-/****************************************************************************
-show information about a print queue
-****************************************************************************/
-static void cmd_qinfo(char *inbuf,char *outbuf )
-{
- char *rparam = NULL;
- char *rdata = NULL;
- char *p;
- int rdrcnt, rprcnt;
- pstring param;
- int result_code=0;
-
- bzero(param,sizeof(param));
-
- p = param;
- SSVAL(p,0,70); /* API function number 70 (DosPrintQGetInfo) */
- p += 2;
- strcpy(p,"zWrLh"); /* parameter description? */
- p = skip_string(p,1);
- strcpy(p,"zWWWWzzzzWWzzl"); /* returned data format */
- p = skip_string(p,1);
- strcpy(p,strrchr(service,'\\')+1); /* name of queue */
- p = skip_string(p,1);
- SSVAL(p,0,3); /* API function level 3, just queue info, no job info */
- SSVAL(p,2,1000); /* size of bytes of returned data buffer */
- p += 4;
- strcpy(p,""); /* subformat */
- p = skip_string(p,1);
-
- DEBUG(1,("Calling DosPrintQueueGetInfo()...\n"));
- if( call_api(PTR_DIFF(p,param), 0,
- 10, 4096,
- &rprcnt, &rdrcnt,
- param, NULL,
- &rparam, &rdata) )
- {
- int converter;
- result_code = SVAL(rparam,0);
- converter = SVAL(rparam,2); /* conversion factor */
-
- DEBUG(2,("returned %d bytes of parameters, %d bytes of data, %d records\n", rprcnt, rdrcnt, SVAL(rparam,4) ));
-
- if (result_code == 0) /* if no error, */
- {
- p = rdata; /* received data */
-
- printf("Name: \"%s\"\n", fix_char_ptr(SVAL(p,0), converter, rdata, rdrcnt) );
- printf("Priority: %u\n", SVAL(p,4) );
- printf("Start time: %u\n", SVAL(p,6) );
- printf("Until time: %u\n", SVAL(p,8) );
- printf("Seperator file: \"%s\"\n", fix_char_ptr(SVAL(p,12), converter, rdata, rdrcnt) );
- printf("Print processor: \"%s\"\n", fix_char_ptr(SVAL(p,16), converter, rdata, rdrcnt) );
- printf("Parameters: \"%s\"\n", fix_char_ptr(SVAL(p,20), converter, rdata, rdrcnt) );
- printf("Comment: \"%s\"\n", fix_char_ptr(SVAL(p,24), converter, rdata, rdrcnt) );
- printf("Status: %u\n", SVAL(p,28) );
- printf("Jobs: %u\n", SVAL(p,30) );
- printf("Printers: \"%s\"\n", fix_char_ptr(SVAL(p,32), converter, rdata, rdrcnt) );
- printf("Drivername: \"%s\"\n", fix_char_ptr(SVAL(p,36), converter, rdata, rdrcnt) );
-
- /* Dump the driver data */
- {
- int count, x, y, c;
- char *ddptr;
-
- ddptr = rdata + SVAL(p,40) - converter;
- if( SVAL(p,40) == 0 ) {count = 0;} else {count = IVAL(ddptr,0);}
- printf("Driverdata: size=%d, version=%u\n", count, IVAL(ddptr,4) );
-
- for(x=8; x < count; x+=16)
- {
- for(y=0; y < 16; y++)
- {
- if( (x+y) < count )
- printf("%2.2X ", CVAL(ddptr,(x+y)) );
- else
- fputs(" ", stdout);
- }
- for(y=0; y < 16 && (x+y) < count; y++)
- {
- c = CVAL(ddptr,(x+y));
- if(isprint(c))
- fputc(c, stdout);
- else
- fputc('.', stdout);
- }
- fputc('\n', stdout);
- }
- }
-
- }
- }
- else /* call_api() failed */
- {
- printf("Failed, error = %d\n", result_code);
- }
-
- /* If any parameters or data were returned, free the storage. */
- if(rparam) free(rparam);
- if(rdata) free(rdata);
-
- return;
-}
-
-/****************************************************************************
-delete some files
-****************************************************************************/
-static void do_del(file_info *finfo)
-{
- char *p;
- char *inbuf,*outbuf;
- pstring mask;
-
- strcpy(mask,cur_dir);
- strcat(mask,finfo->name);
-
- if (finfo->mode & aDIR)
- return;
-
- inbuf = (char *)malloc(BUFFER_SIZE + SAFETY_MARGIN);
- outbuf = (char *)malloc(BUFFER_SIZE + SAFETY_MARGIN);
-
- if (!inbuf || !outbuf)
- {
- DEBUG(0,("out of memory\n"));
- return;
- }
-
- bzero(outbuf,smb_size);
- set_message(outbuf,1,2 + strlen(mask),True);
-
- CVAL(outbuf,smb_com) = SMBunlink;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- SSVAL(outbuf,smb_vwv0,0);
-
- p = smb_buf(outbuf);
- *p++ = 4;
- strcpy(p,mask);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- DEBUG(0,("%s deleting remote file %s\n",smb_errstr(inbuf),CNV_LANG(mask)));
-
- free(inbuf);free(outbuf);
-
-}
-
-/****************************************************************************
-delete some files
-****************************************************************************/
-static void cmd_del(char *inbuf,char *outbuf )
-{
- pstring mask;
- fstring buf;
- int attribute = aSYSTEM | aHIDDEN;
-
- if (recurse)
- attribute |= aDIR;
-
- strcpy(mask,cur_dir);
-
- if (!next_token(NULL,buf,NULL))
- {
- DEBUG(0,("del \n"));
- return;
- }
- strcat(mask,buf);
-
- do_dir((char *)inbuf,(char *)outbuf,mask,attribute,do_del,False);
-}
-
-
-/****************************************************************************
-remove a directory
-****************************************************************************/
-static void cmd_rmdir(char *inbuf,char *outbuf )
-{
- pstring mask;
- fstring buf;
- char *p;
-
- strcpy(mask,cur_dir);
-
- if (!next_token(NULL,buf,NULL))
- {
- DEBUG(0,("rmdir \n"));
- return;
- }
- strcat(mask,buf);
-
- bzero(outbuf,smb_size);
- set_message(outbuf,0,2 + strlen(mask),True);
-
- CVAL(outbuf,smb_com) = SMBrmdir;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
-
- p = smb_buf(outbuf);
- *p++ = 4;
- strcpy(p,mask);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- DEBUG(0,("%s removing remote directory file %s\n",smb_errstr(inbuf),CNV_LANG(mask)));
- return;
- }
-
-}
-
-/****************************************************************************
-rename some files
-****************************************************************************/
-static void cmd_rename(char *inbuf,char *outbuf )
-{
- pstring src,dest;
- fstring buf,buf2;
- char *p;
-
- strcpy(src,cur_dir);
- strcpy(dest,cur_dir);
-
- if (!next_token(NULL,buf,NULL) || !next_token(NULL,buf2,NULL))
- {
- DEBUG(0,("rename \n"));
- return;
- }
- strcat(src,buf);
- strcat(dest,buf2);
-
- bzero(outbuf,smb_size);
- set_message(outbuf,1,4 + strlen(src) + strlen(dest),True);
-
- CVAL(outbuf,smb_com) = SMBmv;
- SSVAL(outbuf,smb_tid,cnum);
- SSVAL(outbuf,smb_vwv0,aHIDDEN | aDIR | aSYSTEM);
- setup_pkt(outbuf);
-
- p = smb_buf(outbuf);
- *p++ = 4;
- strcpy(p,src);
- p = skip_string(p,1);
- *p++ = 4;
- strcpy(p,dest);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- DEBUG(0,("%s renaming files\n",smb_errstr(inbuf)));
- return;
- }
-
-}
-
-
-/****************************************************************************
-toggle the prompt flag
-****************************************************************************/
-static void cmd_prompt(void)
-{
- prompt = !prompt;
- DEBUG(2,("prompting is now %s\n",prompt?"on":"off"));
-}
-
-
-/****************************************************************************
-set the newer than time
-****************************************************************************/
-static void cmd_newer(void)
-{
- fstring buf;
- BOOL ok;
- struct stat sbuf;
-
- ok = next_token(NULL,buf,NULL);
- if (ok && (sys_stat(buf,&sbuf) == 0))
- {
- newer_than = sbuf.st_mtime;
- DEBUG(1,("Getting files newer than %s",
- asctime(LocalTime(&newer_than))));
- }
- else
- newer_than = 0;
-
- if (ok && newer_than == 0)
- DEBUG(0,("Error setting newer-than time\n"));
-}
-
-/****************************************************************************
-set the archive level
-****************************************************************************/
-static void cmd_archive(void)
-{
- fstring buf;
-
- if (next_token(NULL,buf,NULL)) {
- archive_level = atoi(buf);
- } else
- DEBUG(0,("Archive level is %d\n",archive_level));
-}
-
-/****************************************************************************
-toggle the lowercaseflag
-****************************************************************************/
-static void cmd_lowercase(void)
-{
- lowercase = !lowercase;
- DEBUG(2,("filename lowercasing is now %s\n",lowercase?"on":"off"));
-}
-
-
-
-
-/****************************************************************************
-toggle the recurse flag
-****************************************************************************/
-static void cmd_recurse(void)
-{
- recurse = !recurse;
- DEBUG(2,("directory recursion is now %s\n",recurse?"on":"off"));
-}
-
-/****************************************************************************
-toggle the translate flag
-****************************************************************************/
-static void cmd_translate(void)
-{
- translation = !translation;
- DEBUG(2,("CR/LF<->LF and print text translation now %s\n",
- translation?"on":"off"));
-}
-
-
-/****************************************************************************
-do a printmode command
-****************************************************************************/
-static void cmd_printmode(void)
-{
- fstring buf;
- fstring mode;
-
- if (next_token(NULL,buf,NULL))
- {
- if (strequal(buf,"text"))
- printmode = 0;
- else
- {
- if (strequal(buf,"graphics"))
- printmode = 1;
- else
- printmode = atoi(buf);
- }
- }
-
- switch(printmode)
- {
- case 0:
- strcpy(mode,"text");
- break;
- case 1:
- strcpy(mode,"graphics");
- break;
- default:
- sprintf(mode,"%d",printmode);
- break;
- }
-
- DEBUG(2,("the printmode is now %s\n",mode));
-}
-
-/****************************************************************************
-do the lcd command
-****************************************************************************/
-static void cmd_lcd(void)
-{
- fstring buf;
- pstring d;
-
- if (next_token(NULL,buf,NULL))
- sys_chdir(buf);
- DEBUG(2,("the local directory is now %s\n",GetWd(d)));
-}
-
-
-/****************************************************************************
-send a session request
-****************************************************************************/
-static BOOL send_session_request(char *inbuf,char *outbuf)
-{
- fstring dest;
- char *p;
- int len = 4;
- /* send a session request (RFC 8002) */
-
- strcpy(dest,desthost);
- p = strchr(dest,'.');
- if (p) *p = 0;
-
- /* put in the destination name */
- p = outbuf+len;
- name_mangle(dest,p,name_type); /* 0x20 is the SMB server NetBIOS type. */
- len += name_len(p);
-
- /* and my name */
- p = outbuf+len;
- name_mangle(myname,p,0);
- len += name_len(p);
-
- /* setup the packet length */
- _smb_setlen(outbuf,len);
- CVAL(outbuf,0) = 0x81;
-
- send_smb(Client,outbuf);
- DEBUG(5,("Sent session request\n"));
-
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- if (CVAL(inbuf,0) == 0x84) /* C. Hoch 9/14/95 Start */
- {
- /* For information, here is the response structure.
- * We do the byte-twiddling to for portability.
- struct RetargetResponse{
- unsigned char type;
- unsigned char flags;
- int16 length;
- int32 ip_addr;
- int16 port;
- };
- */
- extern int Client;
- int port = (CVAL(inbuf,8)<<8)+CVAL(inbuf,9);
- /* SESSION RETARGET */
- putip((char *)&dest_ip,inbuf+4);
-
- close_sockets();
- Client = open_socket_out(SOCK_STREAM, &dest_ip, port, LONG_CONNECT_TIMEOUT);
- if (Client == -1)
- return False;
-
- DEBUG(3,("Retargeted\n"));
-
- set_socket_options(Client,user_socket_options);
-
- /* Try again */
- return send_session_request(inbuf,outbuf);
- } /* C. Hoch 9/14/95 End */
-
-
- if (CVAL(inbuf,0) != 0x82)
- {
- int ecode = CVAL(inbuf,4);
- DEBUG(0,("Session request failed (%d,%d) with myname=%s destname=%s\n",
- CVAL(inbuf,0),ecode,myname,desthost));
- switch (ecode)
- {
- case 0x80:
- DEBUG(0,("Not listening on called name\n"));
- DEBUG(0,("Try to connect to another name (instead of %s)\n",desthost));
- DEBUG(0,("You may find the -I option useful for this\n"));
- break;
- case 0x81:
- DEBUG(0,("Not listening for calling name\n"));
- DEBUG(0,("Try to connect as another name (instead of %s)\n",myname));
- DEBUG(0,("You may find the -n option useful for this\n"));
- break;
- case 0x82:
- DEBUG(0,("Called name not present\n"));
- DEBUG(0,("Try to connect to another name (instead of %s)\n",desthost));
- DEBUG(0,("You may find the -I option useful for this\n"));
- break;
- case 0x83:
- DEBUG(0,("Called name present, but insufficient resources\n"));
- DEBUG(0,("Perhaps you should try again later?\n"));
- break;
- default:
- DEBUG(0,("Unspecified error 0x%X\n",ecode));
- DEBUG(0,("Your server software is being unfriendly\n"));
- break;
- }
- return(False);
- }
- return(True);
-}
-
-static struct {
- int prot;
- char *name;
-} prots[] = {
- {PROTOCOL_CORE,"PC NETWORK PROGRAM 1.0"},
- {PROTOCOL_COREPLUS,"MICROSOFT NETWORKS 1.03"},
- {PROTOCOL_LANMAN1,"MICROSOFT NETWORKS 3.0"},
- {PROTOCOL_LANMAN1,"LANMAN1.0"},
- {PROTOCOL_LANMAN2,"LM1.2X002"},
- {PROTOCOL_LANMAN2,"Samba"},
- {PROTOCOL_NT1,"NT LM 0.12"},
- {PROTOCOL_NT1,"NT LANMAN 1.0"},
- {-1,NULL}
-};
-
-
-/****************************************************************************
-send a login command
-****************************************************************************/
-static BOOL send_login(char *inbuf,char *outbuf,BOOL start_session,BOOL use_setup)
-{
- BOOL was_null = (!inbuf && !outbuf);
- int sesskey=0;
- time_t servertime = 0;
- extern int serverzone;
- int sec_mode=0;
- int crypt_len;
- int max_vcs=0;
- char *pass = NULL;
- pstring dev;
- char *p;
- int numprots;
- int tries=0;
-
- if (was_null)
- {
- inbuf = (char *)malloc(BUFFER_SIZE + SAFETY_MARGIN);
- outbuf = (char *)malloc(BUFFER_SIZE + SAFETY_MARGIN);
- }
-
-#if AJT
- if (strstr(service,"IPC$")) connect_as_ipc = True;
-#endif
-
- strcpy(dev,"A:");
- if (connect_as_printer)
- strcpy(dev,"LPT1:");
- if (connect_as_ipc)
- strcpy(dev,"IPC");
-
-
- if (start_session && !send_session_request(inbuf,outbuf))
- {
- if (was_null)
- {
- free(inbuf);
- free(outbuf);
- }
- return(False);
- }
-
- bzero(outbuf,smb_size);
-
- /* setup the protocol strings */
- {
- int plength;
-
- for (plength=0,numprots=0;
- prots[numprots].name && prots[numprots].prot<=max_protocol;
- numprots++)
- plength += strlen(prots[numprots].name)+2;
-
- set_message(outbuf,0,plength,True);
-
- p = smb_buf(outbuf);
- for (numprots=0;
- prots[numprots].name && prots[numprots].prot<=max_protocol;
- numprots++)
- {
- *p++ = 2;
- strcpy(p,prots[numprots].name);
- p += strlen(p) + 1;
- }
- }
-
- CVAL(outbuf,smb_com) = SMBnegprot;
- setup_pkt(outbuf);
-
- CVAL(smb_buf(outbuf),0) = 2;
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- show_msg(inbuf);
-
- if (CVAL(inbuf,smb_rcls) != 0 || ((int)SVAL(inbuf,smb_vwv0) >= numprots))
- {
- DEBUG(0,("SMBnegprot failed. myname=%s destname=%s - %s \n",
- myname,desthost,smb_errstr(inbuf)));
- if (was_null)
- {
- free(inbuf);
- free(outbuf);
- }
- return(False);
- }
-
- Protocol = prots[SVAL(inbuf,smb_vwv0)].prot;
-
-
- if (Protocol < PROTOCOL_NT1) {
- sec_mode = SVAL(inbuf,smb_vwv1);
- max_xmit = SVAL(inbuf,smb_vwv2);
- sesskey = IVAL(inbuf,smb_vwv6);
- serverzone = SVALS(inbuf,smb_vwv10)*60;
- /* this time is converted to GMT by make_unix_date */
- servertime = make_unix_date(inbuf+smb_vwv8);
- if (Protocol >= PROTOCOL_COREPLUS) {
- readbraw_supported = ((SVAL(inbuf,smb_vwv5) & 0x1) != 0);
- writebraw_supported = ((SVAL(inbuf,smb_vwv5) & 0x2) != 0);
- }
- crypt_len = smb_buflen(inbuf);
- memcpy(cryptkey,smb_buf(inbuf),8);
- DEBUG(3,("max mux %d\n",SVAL(inbuf,smb_vwv3)));
- max_vcs = SVAL(inbuf,smb_vwv4);
- DEBUG(3,("max vcs %d\n",max_vcs));
- DEBUG(3,("max blk %d\n",SVAL(inbuf,smb_vwv5)));
- } else {
- /* NT protocol */
- sec_mode = CVAL(inbuf,smb_vwv1);
- max_xmit = IVAL(inbuf,smb_vwv3+1);
- sesskey = IVAL(inbuf,smb_vwv7+1);
- serverzone = SVALS(inbuf,smb_vwv15+1)*60;
- /* this time arrives in real GMT */
- servertime = interpret_long_date(inbuf+smb_vwv11+1);
- crypt_len = CVAL(inbuf,smb_vwv16+1);
- memcpy(cryptkey,smb_buf(inbuf),8);
- if (IVAL(inbuf,smb_vwv9+1) & 1)
- readbraw_supported = writebraw_supported = True;
- DEBUG(3,("max mux %d\n",SVAL(inbuf,smb_vwv1+1)));
- max_vcs = SVAL(inbuf,smb_vwv2+1);
- DEBUG(3,("max vcs %d\n",max_vcs));
- DEBUG(3,("max raw %d\n",IVAL(inbuf,smb_vwv5+1)));
- DEBUG(3,("capabilities 0x%x\n",IVAL(inbuf,smb_vwv9+1)));
- }
-
- DEBUG(3,("Sec mode %d\n",SVAL(inbuf,smb_vwv1)));
- DEBUG(3,("max xmt %d\n",max_xmit));
- DEBUG(3,("Got %d byte crypt key\n",crypt_len));
- DEBUG(3,("Chose protocol [%s]\n",prots[SVAL(inbuf,smb_vwv0)].name));
-
- doencrypt = ((sec_mode & 2) != 0);
-
- if (servertime) {
- static BOOL done_time = False;
- if (!done_time) {
- DEBUG(1,("Server time is %sTimezone is UTC%+02.1f\n",
- asctime(LocalTime(&servertime)),
- -(double)(serverzone/3600.0)));
- done_time = True;
- }
- }
-
- get_pass:
-
- if (got_pass)
- pass = password;
- else
- pass = (char *)getpass("Password: ");
-
- /* use a blank username for the 2nd try with a blank password */
- if (tries++ && !*pass)
- *username = 0;
-
- if (Protocol >= PROTOCOL_LANMAN1 && use_setup)
- {
- fstring pword;
- int passlen = strlen(pass)+1;
- strcpy(pword,pass);
-
-#ifdef SMB_PASSWD
- if (doencrypt && *pass) {
- DEBUG(3,("Using encrypted passwords\n"));
- passlen = 24;
- SMBencrypt(pass,cryptkey,pword);
- }
-#else
- doencrypt = False;
-#endif
-
- /* if in share level security then don't send a password now */
- if (!(sec_mode & 1)) {strcpy(pword, "");passlen=1;}
-
- /* send a session setup command */
- bzero(outbuf,smb_size);
-
- if (Protocol < PROTOCOL_NT1) {
- set_message(outbuf,10,1 + strlen(username) + passlen,True);
- CVAL(outbuf,smb_com) = SMBsesssetupX;
- setup_pkt(outbuf);
-
- CVAL(outbuf,smb_vwv0) = 0xFF;
- SSVAL(outbuf,smb_vwv2,max_xmit);
- SSVAL(outbuf,smb_vwv3,2);
- SSVAL(outbuf,smb_vwv4,max_vcs-1);
- SIVAL(outbuf,smb_vwv5,sesskey);
- SSVAL(outbuf,smb_vwv7,passlen);
- p = smb_buf(outbuf);
- memcpy(p,pword,passlen);
- p += passlen;
- strcpy(p,username);
- } else {
- if (!doencrypt) passlen--;
- /* for Win95 */
- set_message(outbuf,13,0,True);
- CVAL(outbuf,smb_com) = SMBsesssetupX;
- setup_pkt(outbuf);
-
- CVAL(outbuf,smb_vwv0) = 0xFF;
- SSVAL(outbuf,smb_vwv2,BUFFER_SIZE);
- SSVAL(outbuf,smb_vwv3,2);
- SSVAL(outbuf,smb_vwv4,getpid());
- SIVAL(outbuf,smb_vwv5,sesskey);
- SSVAL(outbuf,smb_vwv7,passlen);
- SSVAL(outbuf,smb_vwv8,0);
- p = smb_buf(outbuf);
- memcpy(p,pword,passlen); p += SVAL(outbuf,smb_vwv7);
- strcpy(p,username);p = skip_string(p,1);
- strcpy(p,workgroup);p = skip_string(p,1);
- strcpy(p,"Unix");p = skip_string(p,1);
- strcpy(p,"Samba");p = skip_string(p,1);
- set_message(outbuf,13,PTR_DIFF(p,smb_buf(outbuf)),False);
- }
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- show_msg(inbuf);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- if (! *pass &&
- ((CVAL(inbuf,smb_rcls) == ERRDOS &&
- SVAL(inbuf,smb_err) == ERRnoaccess) ||
- (CVAL(inbuf,smb_rcls) == ERRSRV &&
- SVAL(inbuf,smb_err) == ERRbadpw)))
- {
- got_pass = False;
- DEBUG(3,("resending login\n"));
- goto get_pass;
- }
-
- DEBUG(0,("Session setup failed for username=%s myname=%s destname=%s %s\n",
- username,myname,desthost,smb_errstr(inbuf)));
- DEBUG(0,("You might find the -U, -W or -n options useful\n"));
- DEBUG(0,("Sometimes you have to use `-n USERNAME' (particularly with OS/2)\n"));
- DEBUG(0,("Some servers also insist on uppercase-only passwords\n"));
- if (was_null)
- {
- free(inbuf);
- free(outbuf);
- }
- return(False);
- }
-
- if (Protocol >= PROTOCOL_NT1) {
- char *domain,*os,*lanman;
- p = smb_buf(inbuf);
- os = p;
- lanman = skip_string(os,1);
- domain = skip_string(lanman,1);
- if (*domain || *os || *lanman)
- DEBUG(1,("Domain=[%s] OS=[%s] Server=[%s]\n",domain,os,lanman));
- }
-
- /* use the returned uid from now on */
- if (SVAL(inbuf,smb_uid) != uid)
- DEBUG(3,("Server gave us a UID of %d. We gave %d\n",
- SVAL(inbuf,smb_uid),uid));
- uid = SVAL(inbuf,smb_uid);
- }
-
- /* now we've got a connection - send a tcon message */
- bzero(outbuf,smb_size);
-
- if (strncmp(service,"\\\\",2) != 0)
- {
- DEBUG(0,("\nWarning: Your service name doesn't start with \\\\. This is probably incorrect.\n"));
- DEBUG(0,("Perhaps try replacing each \\ with \\\\ on the command line?\n\n"));
- }
-
-
- again2:
-
- {
- int passlen = strlen(pass)+1;
- fstring pword;
- strcpy(pword,pass);
-
-#ifdef SMB_PASSWD
- if (doencrypt && *pass) {
- passlen=24;
- SMBencrypt(pass,cryptkey,pword);
- }
-#endif
-
- /* if in user level security then don't send a password now */
- if ((sec_mode & 1)) {
- strcpy(pword, ""); passlen=1;
- }
-
- if (Protocol <= PROTOCOL_COREPLUS) {
- set_message(outbuf,0,6 + strlen(service) + passlen + strlen(dev),True);
- CVAL(outbuf,smb_com) = SMBtcon;
- setup_pkt(outbuf);
-
- p = smb_buf(outbuf);
- *p++ = 0x04;
- strcpy(p, service);
- p = skip_string(p,1);
- *p++ = 0x04;
- memcpy(p,pword,passlen);
- p += passlen;
- *p++ = 0x04;
- strcpy(p, dev);
- }
- else {
- set_message(outbuf,4,2 + strlen(service) + passlen + strlen(dev),True);
- CVAL(outbuf,smb_com) = SMBtconX;
- setup_pkt(outbuf);
-
- SSVAL(outbuf,smb_vwv0,0xFF);
- SSVAL(outbuf,smb_vwv3,passlen);
-
- p = smb_buf(outbuf);
- memcpy(p,pword,passlen);
- p += passlen;
- strcpy(p,service);
- p = skip_string(p,1);
- strcpy(p,dev);
- }
- }
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,CLIENT_TIMEOUT);
-
- /* trying again with a blank password */
- if (CVAL(inbuf,smb_rcls) != 0 &&
- (int)strlen(pass) > 0 &&
- !doencrypt &&
- Protocol >= PROTOCOL_LANMAN1)
- {
- DEBUG(2,("first SMBtconX failed, trying again. %s\n",smb_errstr(inbuf)));
- strcpy(pass,"");
- goto again2;
- }
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- DEBUG(0,("SMBtconX failed. %s\n",smb_errstr(inbuf)));
- DEBUG(0,("Perhaps you are using the wrong sharename, username or password?\n"));
- DEBUG(0,("Some servers insist that these be in uppercase\n"));
- if (was_null)
- {
- free(inbuf);
- free(outbuf);
- }
- return(False);
- }
-
-
- if (Protocol <= PROTOCOL_COREPLUS) {
- max_xmit = SVAL(inbuf,smb_vwv0);
-
- cnum = SVAL(inbuf,smb_vwv1);
- }
- else {
- max_xmit = MIN(max_xmit,BUFFER_SIZE-4);
- if (max_xmit <= 0)
- max_xmit = BUFFER_SIZE - 4;
-
- cnum = SVAL(inbuf,smb_tid);
- }
-
- DEBUG(3,("Connected with cnum=%d max_xmit=%d\n",cnum,max_xmit));
-
- if (was_null)
- {
- free(inbuf);
- free(outbuf);
- }
- return True;
-}
-
-
-/****************************************************************************
-send a logout command
-****************************************************************************/
-static void send_logout(void )
-{
- pstring inbuf,outbuf;
-
- bzero(outbuf,smb_size);
- set_message(outbuf,0,0,True);
- CVAL(outbuf,smb_com) = SMBtdis;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- send_smb(Client,outbuf);
- receive_smb(Client,inbuf,SHORT_TIMEOUT);
-
- if (CVAL(inbuf,smb_rcls) != 0)
- {
- DEBUG(0,("SMBtdis failed %s\n",smb_errstr(inbuf)));
- }
-
-
-#ifdef STATS
- stats_report();
-#endif
- exit(0);
-}
-
-
-
-/****************************************************************************
-call a remote api
-****************************************************************************/
-static BOOL call_api(int prcnt,int drcnt,
- int mprcnt,int mdrcnt,
- int *rprcnt,int *rdrcnt,
- char *param,char *data,
- char **rparam,char **rdata)
-{
- static char *inbuf=NULL;
- static char *outbuf=NULL;
-
- if (!inbuf) inbuf = (char *)malloc(BUFFER_SIZE + SAFETY_MARGIN);
- if (!outbuf) outbuf = (char *)malloc(BUFFER_SIZE + SAFETY_MARGIN);
-
- send_trans_request(outbuf,SMBtrans,"\\PIPE\\LANMAN",0,0,
- data,param,NULL,
- drcnt,prcnt,0,
- mdrcnt,mprcnt,0);
-
- return (receive_trans_response(inbuf,SMBtrans,
- rdrcnt,rprcnt,
- rdata,rparam));
-}
-
-/****************************************************************************
- send a SMB trans or trans2 request
- ****************************************************************************/
-static BOOL send_trans_request(char *outbuf,int trans,
- char *name,int fid,int flags,
- char *data,char *param,uint16 *setup,
- int ldata,int lparam,int lsetup,
- int mdata,int mparam,int msetup)
-{
- int i;
- int this_ldata,this_lparam;
- int tot_data=0,tot_param=0;
- char *outdata,*outparam;
- pstring inbuf;
- char *p;
-
- this_lparam = MIN(lparam,max_xmit - (500+lsetup*SIZEOFWORD)); /* hack */
- this_ldata = MIN(ldata,max_xmit - (500+lsetup*SIZEOFWORD+this_lparam));
-
- bzero(outbuf,smb_size);
- set_message(outbuf,14+lsetup,0,True);
- CVAL(outbuf,smb_com) = trans;
- SSVAL(outbuf,smb_tid,cnum);
- setup_pkt(outbuf);
-
- outparam = smb_buf(outbuf)+(trans==SMBtrans ? strlen(name)+1 : 3);
- outdata = outparam+this_lparam;
-
- /* primary request */
- SSVAL(outbuf,smb_tpscnt,lparam); /* tpscnt */
- SSVAL(outbuf,smb_tdscnt,ldata); /* tdscnt */
- SSVAL(outbuf,smb_mprcnt,mparam); /* mprcnt */
- SSVAL(outbuf,smb_mdrcnt,mdata); /* mdrcnt */
- SCVAL(outbuf,smb_msrcnt,msetup); /* msrcnt */
- SSVAL(outbuf,smb_flags,flags); /* flags */
- SIVAL(outbuf,smb_timeout,0); /* timeout */
- SSVAL(outbuf,smb_pscnt,this_lparam); /* pscnt */
- SSVAL(outbuf,smb_psoff,smb_offset(outparam,outbuf)); /* psoff */
- SSVAL(outbuf,smb_dscnt,this_ldata); /* dscnt */
- SSVAL(outbuf,smb_dsoff,smb_offset(outdata,outbuf)); /* dsoff */
- SCVAL(outbuf,smb_suwcnt,lsetup); /* suwcnt */
- for (i=0;i 0)
- {
- printf("\n\tSharename Type Comment\n");
- printf("\t--------- ---- -------\n");
- }
-
- if (sort)
- qsort(p,count,20,QSORT_CAST strcasecmp);
-
- for (i=0;i8) long_share_name=True;
-
- p += 20;
- }
-
- if (long_share_name) {
- printf("\nNOTE: There were share names longer than 8 chars.\nOn older clients these may not be accessible or may give browsing errors\n");
- }
- }
- }
-
- if (rparam) free(rparam);
- if (rdata) free(rdata);
-
- return(count>0);
-}
-
-
-/****************************************************************************
-get some server info
-****************************************************************************/
-static void server_info()
-{
- char *rparam = NULL;
- char *rdata = NULL;
- char *p;
- int rdrcnt,rprcnt;
- pstring param;
-
- bzero(param,sizeof(param));
-
- p = param;
- SSVAL(p,0,63); /* NetServerGetInfo()? */
- p += 2;
- strcpy(p,"WrLh");
- p = skip_string(p,1);
- strcpy(p,"zzzBBzz");
- p = skip_string(p,1);
- SSVAL(p,0,10); /* level 10 */
- SSVAL(p,2,1000);
- p += 6;
-
- if (call_api(PTR_DIFF(p,param),0,
- 6,1000,
- &rprcnt,&rdrcnt,
- param,NULL,
- &rparam,&rdata))
- {
- int res = SVAL(rparam,0);
- int converter=SVAL(rparam,2);
-
- if (res == 0)
- {
- p = rdata;
-
- printf("\nServer=[%s] User=[%s] Workgroup=[%s] Domain=[%s]\n",
- rdata+SVAL(p,0)-converter,
- rdata+SVAL(p,4)-converter,
- rdata+SVAL(p,8)-converter,
- rdata+SVAL(p,14)-converter);
- }
- }
-
- if (rparam) free(rparam);
- if (rdata) free(rdata);
-
- return;
-}
-
-
-/****************************************************************************
-try and browse available connections on a host
-****************************************************************************/
-static BOOL list_servers(char *wk_grp)
-{
- char *rparam = NULL;
- char *rdata = NULL;
- int rdrcnt,rprcnt;
- char *p,*svtype_p;
- pstring param;
- int uLevel = 1;
- int count = 0;
- BOOL ok = False;
- BOOL generic_request = False;
-
-
- if (strequal(wk_grp,"WORKGROUP")) {
- /* we won't specify a workgroup */
- generic_request = True;
- }
-
- /* now send a SMBtrans command with api ServerEnum? */
- p = param;
- SSVAL(p,0,0x68); /* api number */
- p += 2;
-
- strcpy(p,generic_request?"WrLehDO":"WrLehDz");
- p = skip_string(p,1);
-
- strcpy(p,"B16BBDz");
-
- p = skip_string(p,1);
- SSVAL(p,0,uLevel);
- SSVAL(p,2,0x2000); /* buf length */
- p += 4;
-
- svtype_p = p;
- p += 4;
-
- if (!generic_request) {
- strcpy(p, wk_grp);
- p = skip_string(p,1);
- }
-
- /* first ask for a list of servers in this workgroup */
- SIVAL(svtype_p,0,SV_TYPE_ALL);
-
- if (call_api(PTR_DIFF(p+4,param),0,
- 8,10000,
- &rprcnt,&rdrcnt,
- param,NULL,
- &rparam,&rdata))
- {
- int res = SVAL(rparam,0);
- int converter=SVAL(rparam,2);
- int i;
-
- if (res == 0) {
- char *p2 = rdata;
- count=SVAL(rparam,4);
-
- if (count > 0) {
- printf("\n\nThis machine has a browse list:\n");
- printf("\n\tServer Comment\n");
- printf("\t--------- -------\n");
- }
-
- for (i=0;i 0) {
- printf("\n\nThis machine has a workgroup list:\n");
- printf("\n\tWorkgroup Master\n");
- printf("\t--------- -------\n");
- }
-
- for (i=0;i list the contents of the current directory"},
- {"dir",cmd_dir," list the contents of the current directory"},
- {"lcd",cmd_lcd,"[directory] change/report the local current working directory"},
- {"cd",cmd_cd,"[directory] change/report the remote directory"},
- {"pwd",cmd_pwd,"show current remote directory (same as 'cd' with no args)"},
- {"get",cmd_get," [local name] get a file"},
- {"mget",cmd_mget," get all the matching files"},
- {"put",cmd_put," [remote name] put a file"},
- {"mput",cmd_mput," put all matching files"},
- {"rename",cmd_rename," rename some files"},
- {"more",cmd_more," view a remote file with your pager"},
- {"mask",cmd_select," mask all filenames against this"},
- {"del",cmd_del," delete all matching files"},
- {"rm",cmd_del," delete all matching files"},
- {"mkdir",cmd_mkdir," make a directory"},
- {"md",cmd_mkdir," make a directory"},
- {"rmdir",cmd_rmdir," remove a directory"},
- {"rd",cmd_rmdir," remove a directory"},
- {"pq",cmd_p_queue_4,"enumerate the print queue"},
- {"prompt",cmd_prompt,"toggle prompting for filenames for mget and mput"},
- {"recurse",cmd_recurse,"toggle directory recursion for mget and mput"},
- {"translate",cmd_translate,"toggle text translation for printing"},
- {"lowercase",cmd_lowercase,"toggle lowercasing of filenames for get"},
- {"print",cmd_print," print a file"},
- {"printmode",cmd_printmode," set the print mode"},
- {"queue",cmd_queue,"show the print queue"},
- {"qinfo",cmd_qinfo,"show print queue information"},
- {"cancel",cmd_cancel," cancel a print queue entry"},
- {"stat",cmd_stat," get info on a file (experimental!)"},
- {"quit",send_logout,"logoff the server"},
- {"q",send_logout,"logoff the server"},
- {"exit",send_logout,"logoff the server"},
- {"newer",cmd_newer," only mget files newer than the specified local file"},
- {"archive",cmd_archive,"\n0=ignore archive bit\n1=only get archive files\n2=only get archive files and reset archive bit\n3=get all files and reset archive bit"},
- {"tar",cmd_tar,"tar [IXbgNa] current directory to/from " },
- {"blocksize",cmd_block,"blocksize