From 05b2b2cdd4895b6d2a4d345192bfd4fed1e0ec25 Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Fri, 1 Jun 2001 11:50:38 +0000 Subject: syncing up with SAMBA_2_2 (This used to be commit 1bc58c21b15fcdb0a504d051f60e20c4e24441e6) --- docs/docbook/Makefile.in | 188 +-- docs/docbook/manpages/make_smbcodepage.1.sgml | 8 +- docs/docbook/manpages/make_unicodemap.1.sgml | 172 +++ docs/docbook/manpages/nmbd.8.sgml | 2 +- docs/docbook/manpages/rpcclient.1.sgml | 31 +- docs/docbook/manpages/smb.conf.5.sgml | 665 +++++++---- docs/docbook/manpages/smbcontrol.1.sgml | 2 +- docs/docbook/manpages/smbspool.8.sgml | 4 +- docs/docbook/manpages/smbstatus.1.sgml | 2 +- docs/docbook/projdoc/CVS-Access.sgml | 157 +++ docs/docbook/projdoc/Samba-PDC-HOWTO.sgml | 1552 ++++++++++++++++++++----- docs/docbook/projdoc/printer_driver2.sgml | 341 ++++-- docs/docbook/projdoc/samba-doc.sgml | 8 +- 13 files changed, 2381 insertions(+), 751 deletions(-) create mode 100644 docs/docbook/manpages/make_unicodemap.1.sgml create mode 100644 docs/docbook/projdoc/CVS-Access.sgml (limited to 'docs/docbook') diff --git a/docs/docbook/Makefile.in b/docs/docbook/Makefile.in index e3694896f2..0c043d77e3 100644 --- a/docs/docbook/Makefile.in +++ b/docs/docbook/Makefile.in @@ -36,7 +36,8 @@ MANPAGES=$(MANDIR)/findsmb.1 $(MANDIR)/smbclient.1 \ $(MANDIR)/smbpasswd.5 $(MANDIR)/testparm.1 $(MANDIR)/samba.7 \ $(MANDIR)/smbpasswd.8 $(MANDIR)/testprns.1 \ $(MANDIR)/smb.conf.5 $(MANDIR)/wbinfo.1 \ - $(MANDIR)/smbcacls.1 $(MANDIR)/smbsh.1 $(MANDIR)/winbindd.8 + $(MANDIR)/smbcacls.1 $(MANDIR)/smbsh.1 $(MANDIR)/winbindd.8 \ + $(MANDIR)/make_unicodemap.1 SGMLMANSRC=manpages/findsmb.1.sgml manpages/smbclient.1.sgml \ manpages/smbspool.8.sgml manpages/lmhosts.5.sgml \ @@ -50,12 +51,14 @@ SGMLMANSRC=manpages/findsmb.1.sgml manpages/smbclient.1.sgml \ manpages/smbpasswd.8.sgml manpages/testprns.1.sgml \ manpages/smb.conf.5.sgml \ manpages/wbinfo.1.sgml manpages/smbcacls.1.sgml \ - manpages/smbsh.1.sgml manpages/winbindd.8.sgml + manpages/smbsh.1.sgml manpages/winbindd.8.sgml \ + manpages/make_unicodemap.1.sgml HOWTOSRC=projdoc/DOMAIN_MEMBER.sgml projdoc/NT_Security.sgml \ projdoc/msdfs_setup.sgml projdoc/printer_driver2.sgml \ projdoc/UNIX_INSTALL.sgml projdoc/winbind.sgml projdoc/OS2-Client-HOWTO.sgml \ - projdoc/Samba-PDC-HOWTO.sgml projdoc/ENCRYPTION.sgml + projdoc/Samba-PDC-HOWTO.sgml projdoc/ENCRYPTION.sgml \ + projdoc/CVS-Access.sgml FAQSRC=faq/samba-pdc-faq.sgml @@ -71,7 +74,7 @@ man: $(MANPAGES) FAQ: $(FAQSRC) @echo Building SAMBA PDC FAQ... @(for i in $?; do \ - htmlfile=`basename $$i | sed "s/\.sgml/\.html/g"`; \ + htmlfile=`echo $$i | sed 's,.*/,,' | sed "s/\.sgml/\.html/g"`; \ echo "Making $$htmlfile"; \ $(JADE) -t sgml -V nochunks -d $(SGML_SHARE)/dsssl/docbook/html/docbook.dsl \ -f /tmp/jade.log $$i > ../htmldocs/$$htmlfile; \ @@ -82,13 +85,13 @@ FAQ: $(FAQSRC) HOWTO: $(HOWTOSRC) @echo Building HOWTO pages... @(for i in $?; do \ - htmlfile=`basename $$i | sed "s/\.sgml/\.html/g"`; \ + htmlfile=`echo $$i | sed 's,.*/,,' | sed "s/\.sgml/\.html/g"`; \ echo "Making $$htmlfile"; \ - cat $$i | $(PERL) scripts/make-article.pl > /tmp/`basename $$i`; \ + cat $$i | $(PERL) scripts/make-article.pl > /tmp/`echo $$i | sed 's,.*/,,'`; \ $(JADE) -t sgml -V nochunks -d $(SGML_SHARE)/dsssl/docbook/html/docbook.dsl \ - -f /tmp/jade.log /tmp/`basename $$i` > ../htmldocs/$$htmlfile; \ + -f /tmp/jade.log /tmp/`echo $$i | sed 's,.*/,,'` > ../htmldocs/$$htmlfile; \ cat /tmp/jade.log | grep -v DTDDECL; \ - /bin/rm -f /tmp/jade.log /tmp/`basename $$i`; \ + /bin/rm -f /tmp/jade.log /tmp/`echo $$i | sed 's,.*/,,'`; \ done) @@ -102,7 +105,6 @@ proj-doc: @(cd projdoc; $(JADE) -t sgml -i html -V nochunks -d ../stylesheets/ldp.dsl\#html samba-doc.sgml > ../samba-doc.html) @(cd scripts; ./ldp_print ../samba-doc.html) @mv -f samba-doc.pdf ../Samba-HOWTO-Collection.pdf - #@$(HTMLDOC) -f ../Samba-HOWTO-Collection.pdf samba-doc.html @/bin/mv -f samba-doc.html ../htmldocs/Samba-HOWTO-Collection.html @@ -113,7 +115,7 @@ proj-doc: man-html-all: $(SGMLMANSRC) @echo Building HTML formatted man pages... @(for i in $?; do \ - htmlfile=`basename $$i | sed "s/\.sgml/\.html/g"`; \ + htmlfile=`echo $$i | sed 's,.*/,,' | sed "s/\.sgml/\.html/g"`; \ echo "Making $$htmlfile"; \ $(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html -f /tmp/jade.log $$i > ../htmldocs/$$htmlfile; \ cat /tmp/jade.log | grep -v DTDDECL; \ @@ -124,7 +126,7 @@ man-html-all: $(SGMLMANSRC) man-all: $(SGMLMANSRC) @echo Building man pages... @(for i in $?; do \ - manfile=`basename $$i | sed "s/\.sgml//g"`; \ + manfile=`echo $$i | sed 's,.*/,,' | sed "s/\.sgml//g"`; \ echo "Making $$manfile"; \ $(ONSGMLS) -f /tmp/docbook2x.log $$i | $(SGMLSPL) \ $(SGML_SHARE)/docbook2X/docbook2man-spec.pl; \ @@ -143,210 +145,218 @@ man-all: $(SGMLMANSRC) $(MANDIR)/findsmb.1: manpages/findsmb.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbclient.1: manpages/smbclient.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbspool.8: manpages/smbspool.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/lmhosts.5: manpages/lmhosts.5.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbcontrol.1: manpages/smbcontrol.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbstatus.1: manpages/smbstatus.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/make_smbcodepage.1: manpages/make_smbcodepage.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` + +$(MANDIR)/make_unicodemap.1: manpages/make_unicodemap.1.sgml + @echo "Making $@" + @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` + @echo "Making HTML version of $@" + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbd.8: manpages/smbd.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbtar.1: manpages/smbtar.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/nmbd.8: manpages/nmbd.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbmnt.8: manpages/smbmnt.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbumount.8: manpages/smbumount.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/nmblookup.1: manpages/nmblookup.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbmount.8: manpages/smbmount.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/swat.8: manpages/swat.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/rpcclient.1: manpages/rpcclient.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbpasswd.5: manpages/smbpasswd.5.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/testparm.1: manpages/testparm.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/samba.7: manpages/samba.7.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbpasswd.8: manpages/smbpasswd.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/testprns.1: manpages/testprns.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smb.conf.5: manpages/smb.conf.5.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/wbinfo.1: manpages/wbinfo.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbcacls.1: manpages/smbcacls.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbsh.1 : manpages/smbsh.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/winbindd.8: manpages/winbindd.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` ## Clean Rule diff --git a/docs/docbook/manpages/make_smbcodepage.1.sgml b/docs/docbook/manpages/make_smbcodepage.1.sgml index 8a58b8614d..a36f9b968c 100644 --- a/docs/docbook/manpages/make_smbcodepage.1.sgml +++ b/docs/docbook/manpages/make_smbcodepage.1.sgml @@ -1,5 +1,5 @@ - + make_smbcodepage @@ -56,11 +56,11 @@ inputfile - This is the input file to process. In t - he 'c' case this will be a text + This is the input file to process. In + the c case this will be a text codepage definition file such as the ones found in the Samba source/codepages directory. In - the 'd' case this will be the + the d case this will be the binary format codepage definition file normally found in the lib/codepages directory in the Samba install directory path. diff --git a/docs/docbook/manpages/make_unicodemap.1.sgml b/docs/docbook/manpages/make_unicodemap.1.sgml new file mode 100644 index 0000000000..50a5446d60 --- /dev/null +++ b/docs/docbook/manpages/make_unicodemap.1.sgml @@ -0,0 +1,172 @@ + + + + + make_unicodemap + 1 + + + + + make_unicodemap + construct a unicode map file for Samba + + + + + make_unicodemap + codepage + inputfile + outputfile + + + + + + + DESCRIPTION + + + This tool is part of the Samba + suite. + + + + make_unicodemap compiles text unicode map + files into binary unicodef map files for use with the + internationalization features of Samba 2.2. + + + + + + + OPTIONS + + + + codepage + This is the codepage or UNIX character + set we are processing (a number, e.g. 850). + + + + + inputfile + This is the input file to process. This is a + text unicode map file such as the ones found in the Samba + source/codepages directory. + + + + + outputfile + This is the binary output file to produce. + + + + + + + + Samba Unicode Map Files + + + A text Samba unicode map file is a description that tells Samba + how to map characters from a specified DOS code page or UNIX character + set to 16 bit unicode. + + + A binary Samba unicode map file is a binary representation + of the same information, including a value that specifies what + codepage or UNIX character set this file is describing. + + + + + Files + + CP<codepage>.TXT + + + These are the input (text) unicode map files provided + in the Samba source/codepages + directory. + + + + A text unicode map file consists of multiple lines + containing two fields. These fields are : + + + + character - which is + the (hex) character mapped on this line. + + + unicode - which + is the (hex) 16 bit unicode character that the character + will map to. + + + + + unicode_map.<codepage> - These are + the output (binary) unicode map files produced and placed in + the Samba destination lib/codepage + directory. + + + + + + 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 make_unicodemap + program be installed under the + $prefix/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! + + + + + VERSION + + This man page is correct for version 2.2 of + the Samba suite. + + + + SEE ALSO + smbd(8), + smb.conf(5) + + + + + AUTHOR + + The original Samba software and related utilities + were created by Andrew Tridgell. Samba is now developed + by the Samba Team as an Open Source project similar + to the way the Linux kernel is developed. + + The original Samba man pages were written by Karl Auer. + The man page sources were converted to YODL format (another + excellent piece of Open Source software, available at + + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + release by Jeremy Allison. The conversion to DocBook for + Samba 2.2 was done by Gerald Carter + + + diff --git a/docs/docbook/manpages/nmbd.8.sgml b/docs/docbook/manpages/nmbd.8.sgml index 5194b1072b..8db2749bfa 100644 --- a/docs/docbook/manpages/nmbd.8.sgml +++ b/docs/docbook/manpages/nmbd.8.sgml @@ -37,7 +37,7 @@ nmbd is a server that understands and can reply to NetBIOS over IP name service requests, like - those produced by SMBD/CIFS clients such as Windows 95/98/ME, + those produced by SMB/CIFS clients such as Windows 95/98/ME, Windows NT, Windows 2000, and LanManager clients. It also participates in the browsing protocols which make up the Windows "Network Neighborhood" view. diff --git a/docs/docbook/manpages/rpcclient.1.sgml b/docs/docbook/manpages/rpcclient.1.sgml index c02f935d82..0d45a5dc20 100644 --- a/docs/docbook/manpages/rpcclient.1.sgml +++ b/docs/docbook/manpages/rpcclient.1.sgml @@ -107,8 +107,9 @@ -l logbasename - File name for log/debug files. .client will be - appended. The log file is never removed by the client. + File name for log/debug files. The extension + '.client' will be appended. The log file is never removed + by the client. @@ -161,9 +162,8 @@ -W domain Set the SMB domain of the username. This - overrides the default domain which is the domain of the - server specified with the -S option. - If the domain specified is the same as the server's NetBIOS name, + overrides the default domain which is the domain defined in + smb.conf. If the domain specified is the same as the server's NetBIOS name, it causes the client to log on using the server's local SAM (as opposed to the Domain SAM). @@ -179,8 +179,15 @@ LSARPC lsaquery - lookupsids - lookupnames + + lookupsids - Resolve a list + of SIDs to usernames. + + + lookupnames - Resolve s list + of usernames to SIDs. + + enumtrusts @@ -193,6 +200,10 @@ querygroup queryusergroups querygroupmem + queryaliasmem + querydispinfo + querydominfo + enumdomgroups @@ -244,6 +255,12 @@ + deldriver - Delete the + specified printer driver for all architectures. This + does not delete the actual driver files from the server, + only the entry from the server's list of drivers. + + enumdata - Enumerate all printer setting data stored on the server. On Windows NT clients, these values are stored in the registry, while Samba servers diff --git a/docs/docbook/manpages/smb.conf.5.sgml b/docs/docbook/manpages/smb.conf.5.sgml index e5357d24f3..70b4cc1c8e 100644 --- a/docs/docbook/manpages/smb.conf.5.sgml +++ b/docs/docbook/manpages/smb.conf.5.sgml @@ -325,7 +325,7 @@ 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/%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, @@ -586,8 +586,9 @@ each parameter for details. Note that some are synonyms. + add printer command + add share command add user script - addprinter command allow trusted domains announce as announce version @@ -595,6 +596,7 @@ bind interfaces only browse list change notify timeout + change share command character set client code page code page directory @@ -608,15 +610,13 @@ debuglevel default default service + delete printer command + delete share command delete user script - deleteprinter command dfree command dns proxy domain admin group - domain admin users - domain groups domain guest group - domain guest users domain logons domain master encrypt passwords @@ -670,9 +670,11 @@ nt pipe support nt smb support null passwords + obey pam restrictions oplock break wait time os level os2 driver map + pam password change panic action passwd chat passwd chat debug @@ -881,6 +883,119 @@ + + + add printer command (G) + With the introduction of MS-RPC based printing + support for Windows NT/2000 clients in Samba 2.2, The MS Add + Printer Wizard (APW) icon is now also available in the + "Printers..." folder displayed a share listing. The APW + allows for printers to be add remotely to a Samba or Windows + NT/2000 print server. + + For a Samba host this means that the printer must be + physically added to underlying printing system. The add + printer command defines a script to be run which + will perform the necessary operations for adding the printer + to the print system and to add the appropriate service definition + to the smb.conf file in order that it can be + shared by smbd(8) + . + + The add printer command is + automatically invoked with the following parameter (in + order: + + + printer name + share name + port name + driver name + location + Windows 9x driver location + + + + All parameters are filled in from the PRINTER_INFO_2 structure sent + by the Windows NT/2000 client with one exception. The "Windows 9x + driver location" parameter is included for backwards compatibility + only. The remaining fields in the structure are generated from answers + to the APW questions. + + Once the add printer command has + been executed, smbd will reparse the + smb.conf to determine if the share defined by the APW + exists. If the sharename is still invalid, then smbd + will return an ACCESS_DENIED error to the client. + + See also + delete printer command, printing, + show add + printer wizard + + Default: none + Example: addprinter command = /usr/bin/addprinter + + + + + + + + add share command (G) + Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + add share command is used to define an + external program or script which will add a new service definition + to smb.conf. In order to successfully + execute the add share command, smbd + requires that the administrator be connected using a root account (i.e. + uid == 0). + + + + When executed, smbd will automatically invoke the + add share command with four parameters. + + + + configFile - the location + of the global smb.conf file. + + + shareName - the name of the new + share. + + + pathName - path to an **existing** + directory on disk. + + + comment - comment string to associate + with the new share. + + + + + This parameter is only used for add file shares. To add printer shares, + see the add printer + command. + + + + See also change share + command, delete share + command. + + + Default: none + Example: add share command = /usr/local/bin/addshare + + + + + add user script (G) This is the full pathname to a script that will @@ -934,63 +1049,6 @@ - - addprinter command (G) - With the introduction of MS-RPC based printing - support for Windows NT/2000 clients in Samba 2.2, The MS Add - Printer Wizard (APW) icon is now also available in the - "Printers..." folder displayed a share listing. The APW - allows for printers to be add remotely to a Samba or Windows - NT/2000 print server. - - For a Samba host this means that the printer must be - physically added to underlying printing system. The - addprinter command defines a script to be run which - will perform the necessary operations for adding the printer - to the print system and to add the appropriate service definition - to the smb.conf file in order that it can be - shared by smbd(8) - . - - The addprinter command is - automatically invoked with the following parameter (in - order: - - - printer name - share name - port name - driver name - location - Windows 9x driver location - - - - All parameters are filled in from the PRINTER_INFO_2 structure sent - by the Windows NT/2000 client with one exception. The "Windows 9x - driver location" parameter is included for backwards compatibility - only. The remaining fields in the structure are generated from answers - to the APW questions. - - Once the addprinter command has - been executed, smbd will reparse the - smb.conf to determine if the share defined by the APW - exists. If the sharename is still invalid, then smbd - will return an ACCESS_DENIED error to the client. - - See also - deleteprinter command, printing, - show add - printer wizard - - Default: none - Example: addprinter command = /usr/bin/addprinter - - - - - admin users (S) This is a list of users who will be granted @@ -1264,7 +1322,60 @@ Would change the scan time to every 5 minutes. + + + + change share command (G) + Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + change share command is used to define an + external program or script which will modify an existing service definition + in smb.conf. In order to successfully + execute the change share command, smbd + requires that the administrator be connected using a root account (i.e. + uid == 0). + + + When executed, smbd will automatically invoke the + change share command with four parameters. + + + + configFile - the location + of the global smb.conf file. + + + shareName - the name of the new + share. + + + pathName - path to an **existing** + directory on disk. + + + comment - comment string to associate + with the new share. + + + + + This parameter is only used modify existing file shares definitions. To modify + printer shares, use the "Printers..." folder as seen when browsing the Samba host. + + + + See also add share + command, delete + share command. + + + Default: none + Example: change share command = /usr/local/bin/addshare + + + + character set (G) @@ -1545,6 +1656,11 @@ mode bits on created directories. See also the inherit permissions parameter. + Note that this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + a mask on access control lists also, they need to set the security mask. + Default: create mask = 0744 Example: create mask = 0775 @@ -1648,15 +1764,9 @@ debuglevel (G) - The value of the parameter (an integer) allows - the debug level (logging level) to be specified in the - 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 or level zero if none was specified. - - Example: debug level = 3 + Synonym for + log level. + @@ -1720,6 +1830,48 @@ + + delete printer command (G) + With the introduction of MS-RPC based printer + support for Windows NT/2000 clients in Samba 2.2, it is now + possible to delete printer at run time by issuing the + DeletePrinter() RPC call. + + For a Samba host this means that the printer must be + physically deleted from underlying printing system. The + deleteprinter command defines a script to be run which + will perform the necessary operations for removing the printer + from the print system and from smb.conf. + + + The delete printer command is + automatically called with only one parameter: + "printer name". + + + Once the delete printer command has + been executed, smbd will reparse the + smb.conf to associated printer no longer exists. + If the sharename is still valid, then smbd + will return an ACCESS_DENIED error to the client. + + See also + add printer command, printing, + show add + printer wizard + + Default: none + Example: deleteprinter command = /usr/bin/removeprinter + + + + + + + + + delete readonly (S) This parameter allows readonly files to be deleted. @@ -1733,6 +1885,53 @@ + + + delete share command (G) + Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + delete share command is used to define an + external program or script which will remove an existing service + definition from smb.conf. In order to successfully + execute the delete share command, smbd + requires that the administrator be connected using a root account (i.e. + uid == 0). + + + + When executed, smbd will automatically invoke the + delete share command with two parameters. + + + + configFile - the location + of the global smb.conf file. + + + shareName - the name of + the existing service. + + + + + This parameter is only used to remove file shares. To delete printer shares, + see the delete printer + command. + + + + See also delete share + command, change + share. + + + Default: none + Example: delete share command = /usr/local/bin/delshare + + + + + @@ -1797,46 +1996,6 @@ - - deleteprinter command (G) - With the introduction of MS-RPC based printer - support for Windows NT/2000 clients in Samba 2.2, it is now - possible to delete printer at run time by issuing the - DeletePrinter() RPC call. - - For a Samba host this means that the printer must be - physically deleted from underlying printing system. The - deleteprinter command defines a script to be run which - will perform the necessary operations for removing the printer - from the print system and from smb.conf. - - - The deleteprinter command is - automatically called with only one parameter: - "printer name". - - - Once the deleteprinter command has - been executed, smbd will reparse the - smb.conf to associated printer no longer exists. - If the sharename is still valid, then smbd - will return an ACCESS_DENIED error to the client. - - See also - addprinter command, printing, - show add - printer wizard - - Default: none - Example: deleteprinter command = /usr/bin/removeprinter - - - - - - - delete veto files (S) @@ -1962,6 +2121,11 @@ parameter. This parameter is set to 000 by default (i.e. no extra mode bits are added). + Note that this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + a mask on access control lists also, they need to set the directory security mask. + See the force directory mode parameter to cause particular mode bits to always be set on created directories. @@ -2002,17 +2166,15 @@ mask may be treated as a set of bits the user is not allowed to change. - If not set explicitly this parameter is set to the same - value as the directory - mask parameter. To allow a user to - modify all the user/group/world permissions on a directory, set - this parameter to 0777. + If not set explicitly this parameter is set to 0777 + meaning a user is allowed to modify all the user/group/world + permissions on a directory. Note that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. - Administrators of most normal systems will probably want to set - it to 0777. + Administrators of most normal systems will probably want to leave + it as the default of 0777. See also the force directory security mode, force security mode parameters. - Default: directory security mask = <same as - directory mask> - Example: directory security mask = 0777 + Default: directory security mask = 0777 + Example: directory security mask = 0700 @@ -2054,67 +2215,47 @@ domain admin group (G) - This is an EXPERIMENTAL parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list samba-ntdom available by - visiting the web page at - http://lists.samba.org/. - - - - - domain admin users (G) - This is an EXPERIMENTAL parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list samba-ntdom available by - visiting the web page at - http://lists.samba.org/. + This parameter is intended as a temporary solution + to enable users to be a member of the "Domain Admins" group when + a Samba host is acting as a PDC. A complete solution will be provided + by a system for mapping Windows NT/2000 groups onto UNIX groups. + Please note that this parameter has a somewhat confusing name. It + accepts a list of usernames and of group names in standard + smb.conf notation. + + + See also domain + guest group, domain + logons + + + Default: no domain administrators + Example: domain admin group = root @wheel + - - domain groups (G) - This is an EXPERIMENTAL parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list samba-ntdom available by - visiting the web page at - http://lists.samba.org/. - - domain guest group (G) - This is an EXPERIMENTAL parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list samba-ntdom available by - visiting the web page at - http://lists.samba.org/. - - - - - domain guest users (G) - This is an EXPERIMENTAL parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list samba-ntdom available by - visiting the web page at - http://lists.samba.org/. + This parameter is intended as a temporary solution + to enable users to be a member of the "Domain Guests" group when + a Samba host is acting as a PDC. A complete solution will be provided + by a system for mapping Windows NT/2000 groups onto UNIX groups. + Please note that this parameter has a somewhat confusing name. It + accepts a list of usernames and of group names in standard + smb.conf notation. + + + See also domain + admin group, domain + logons + + + Default: no domain guests + Example: domain guest group = nobody @guest + @@ -2431,6 +2572,12 @@ mode after the mask set in the create mask parameter is applied. + Note that by default this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + this mask on access control lists also, they need to set the restrict acl with + mask to true. + See also the parameter create mask for details on masking mode bits on files. @@ -2459,6 +2606,12 @@ mask in the parameter directory mask is applied. + Note that by default this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + this mask on access control lists also, they need to set the restrict acl with + mask to true. + See also the parameter directory mask for details on masking mode bits on created directories. @@ -2490,17 +2643,15 @@ mask may be treated as a set of bits that, when modifying security on a directory, the user has always set to be 'on'. - If not set explicitly this parameter is set to the same - value as the force - directory mode parameter. To allow - a user to modify all the user/group/world permissions on a - directory without restrictions, set this parameter to 000. + If not set explicitly this parameter is 000, which + allows a user to modify all the user/group/world permissions on a + directory without restrictions. Note that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. - Administrators of most normal systems will probably want to set - it to 0000. + Administrators of most normal systems will probably want to leave + it set as 0000. See also the directory security mask, @@ -2508,9 +2659,8 @@ force security mode parameters. - Default: force directory security mode = <same as - force directory mode> - Example: force directory security mode = 0 + Default: force directory security mode = 0 + Example: force directory security mode = 700 @@ -2568,17 +2718,15 @@ mask may be treated as a set of bits that, when modifying security on a file, the user has always set to be 'on'. - If not set explicitly this parameter is set to the same - value as the force - create mode parameter. To allow a user to - modify all the user/group/world permissions on a file, with no - restrictions set this parameter to 000. + If not set explicitly this parameter is set to 0, + and allows a user to modify all the user/group/world permissions on a file, + with no restrictions. Note that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. - Administrators of most normal systems will probably want to set - it to 0000. + Administrators of most normal systems will probably want to leave + this set to 0000. See also the force directory security mode, @@ -2586,9 +2734,8 @@ mask, security mask parameters. - Default: force security mode = <same as force - create mode> - Example: force security mode = 0 + Default: force security mode = 0 + Example: force security mode = 700 @@ -3340,9 +3487,15 @@ log level (G) - Synonym for - debug level. - + The value of the parameter (an integer) allows + the debug level (logging level) to be specified in the + smb.conf file. This is to give greater + flexibility in the configuration of the system. + + The default will be the log level specified on + the command line or level zero if none was specified. + + Example: log level = 3 @@ -4580,6 +4733,28 @@ + + + obey pam restrictions (G) + When Samba 2.2 is configure to enable PAM support + (i.e. --with-pam), this parameter will control whether or not Samba + should obey PAM's account and session management directives. The + default behavior is to use PAM for clear text authentication only + and to ignore any account or session management. Note that Samba + always ignores PAM for authentication in the case of encrypt passwords = yes + . The reason is that PAM modules cannot support the challenge/response + authentication mechanism needed in the presence of SMB password encryption. + + + Default: obey pam restrictions = no + + + + + + + only user (S) This is a boolean option that controls whether @@ -4608,24 +4783,6 @@ - - - ole locking compatibility (G) - This parameter allows an administrator to turn - off the byte range lock manipulation that is done within Samba to - give compatibility for OLE applications. Windows OLE applications - use byte range locking as a form of inter-process communication, by - locking ranges of bytes around the 2^32 region of a file range. This - can cause certain UNIX lock managers to crash or otherwise cause - problems. Setting this parameter to no means you - trust your UNIX lock manager to handle such cases correctly. - - Default: ole locking compatibility = yes - - - - - only guest (S) A synonym for @@ -4755,6 +4912,21 @@ + + pam password change (G) + With the addition of better PAM support in Samba 2.2, + this parameter, it is possible to use PAM's password change control + flag for Samba. If enabled, then PAM will be used for password + changes when requested by an SMB client, and the passwd chat must be + be changed to work with the pam prompts. + + + Default: pam password change = no + + + + panic action (G) @@ -4810,10 +4982,21 @@ password cleartext. In this case the old password cleartext is set to "" (the empty string). + Also, if the pam + password change parameter is set to true, then the + chat sequence should consist of three elements. The first element should + match the pam prompt for the old password, the second element should match + the pam prompt for the first request for the new password, and the final + element should match the pam prompt for the second request for the new password. + These matches are done case insentively. Under most conditions this change + is done as root so the prompt for the old password will never be matched. + + See also unix password sync, - passwd program and - passwd chat debug. + passwd program , + passwd chat debug and + pam password change. Default: passwd chat = *new*password* %n\n *new*password* %n\n *changed* @@ -5798,6 +5981,35 @@ + + restrict acl with mask (S) + This is a boolean parameter. If set to false (default), then + Creation of files with access control lists (ACLS) and modification of ACLs + using the Windows NT/2000 ACL editor will be applied directly to the file + or directory. + + If set to True, then all requests to set an ACL on a file will have the + parameters create mask, + force create mode + applied before setting the ACL, and all requests to set an ACL on a directory will + have the parameters directory + mask, force + directory mode applied before setting the ACL. + + + See also create mask, + force create mode, + directory mask, + force directory mode + + + Default: restrict acl with mask = no + + + + + + restrict anonymous (G) This is a boolean parameter. If it is true, then @@ -6176,17 +6388,15 @@ mask may be treated as a set of bits the user is not allowed to change. - If not set explicitly this parameter is set to the same - value as the create mask - parameter. To allow a user to modify all the - user/group/world permissions on a file, set this parameter to - 0777. + If not set explicitly this parameter is 0777, allowing + a user to modify all the user/group/world permissions on a file. + Note that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will - probably want to set it to 0777. + probably want to leave it set to 0777. See also the force directory security mode, @@ -6194,9 +6404,8 @@ security mask, force security mode parameters. - Default: security mask = <same as create mask> - - Example: security mask = 0777 + Default: security mask = 0777 + Example: security mask = 0770 diff --git a/docs/docbook/manpages/smbcontrol.1.sgml b/docs/docbook/manpages/smbcontrol.1.sgml index 44418ea85f..8e529d8b71 100644 --- a/docs/docbook/manpages/smbcontrol.1.sgml +++ b/docs/docbook/manpages/smbcontrol.1.sgml @@ -1,5 +1,5 @@ - + smbcontrol diff --git a/docs/docbook/manpages/smbspool.8.sgml b/docs/docbook/manpages/smbspool.8.sgml index b847aadd05..5b409bb9de 100644 --- a/docs/docbook/manpages/smbspool.8.sgml +++ b/docs/docbook/manpages/smbspool.8.sgml @@ -1,5 +1,5 @@ - + smbspool @@ -8,7 +8,7 @@ - nmblookup + smbspool send print file to an SMB printer diff --git a/docs/docbook/manpages/smbstatus.1.sgml b/docs/docbook/manpages/smbstatus.1.sgml index 6f2361d021..c2f638b88e 100644 --- a/docs/docbook/manpages/smbstatus.1.sgml +++ b/docs/docbook/manpages/smbstatus.1.sgml @@ -1,5 +1,5 @@ - + smbstatus diff --git a/docs/docbook/projdoc/CVS-Access.sgml b/docs/docbook/projdoc/CVS-Access.sgml new file mode 100644 index 0000000000..aea146b66a --- /dev/null +++ b/docs/docbook/projdoc/CVS-Access.sgml @@ -0,0 +1,157 @@ + + + + + + + Samba Team + + + + + (22 May 2001) + + +HOWTO Access Samba source code via CVS + + +Introduction + + +Samba is developed in an open environnment. Developers use CVS +(Concurrent Versioning System) to "checkin" (also known as +"commit") new source code. Samba's various CVS branches can +be accessed via anonymouns CVS using the instructions +detailed in this chapter. + + + +This document is a modified version of the instructions found at +http://samba.org/samba/cvs.html + + + + + + +CVS Access to samba.org + + +The machine samba.org runs a publicly accessible CVS +repository for access to the source code of several packages, +including samba, rsync and jitterbug. There are two main ways of +accessing the CVS server on this host. + + + +Access via CVSweb + + +You can access the source code via your +favourite WWW browser. This allows you to access the contents of +individual files in the repository and also to look at the revision +history and commit logs of individual files. You can also ask for a diff +listing between any two versions on the repository. + + + +Use the URL : http://samba.org/cgi-bin/cvsweb + + + + +Access via cvs + + +You can also access the source code via a +normal cvs client. This gives you much more control over you can +do with the repository and allows you to checkout whole source trees +and keep them uptodate via normal cvs commands. This is the +preferred method of access if you are a developer and not +just a casual browser. + + + +To download the latest cvs source code, point your +browser at the URL : http://www.cyclic.com/. +and click on the 'How to get cvs' link. CVS is free software under +the GNU GPL (as is Samba). Note that there are several graphical CVS clients +which provide a graphical interface to the sometimes mundane CVS commands. +Links to theses clients are also available from http://www.cyclic.com. + + + +To gain access via anonymous cvs use the following steps. +For this example it is assumed that you want a copy of the +samba source code. For the other source code repositories +on this system just substitute the correct package name + + + + + + Install a recent copy of cvs. All you really need is a + copy of the cvs client binary. + + + + + + + Run the command + + + + cvs -d :pserver:cvs@samba.org:/cvsroot login + + + + When it asks you for a password type cvs. + + + + + + + Run the command + + + + cvs -d :pserver:cvs@samba.org:/cvsroot co samba + + + + This will create a directory called samba containing the + latest samba source code (i.e. the HEAD tagged cvs branch). This + currently corresponds to the 3.0 development tree. + + + + CVS branches other HEAD can be obtained by using the -r + and defining a tag name. A list of branch tag names can be found on the + "Development" page of the samba web site. A common request is to obtain the + latest 2.2 release code. This could be done by using the following command. + + + + cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba + + + + + + Whenever you want to merge in the latest code changes use + the following command from within the samba directory: + + + + cvs update -d -P + + + + + + + + diff --git a/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml b/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml index 699ba54a09..0b86bcba63 100644 --- a/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml +++ b/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml @@ -8,15 +8,44 @@ VA Linux Systems/Samba Team
jerry@samba.org
+ DavidBannon + + Samba Team +
dbannon@samba.org
+ + - (15 Apr 2001) + (26 Apr 2001) -How to Configure Samba 2.2.x as a Primary Domain Controller +How to Configure Samba 2.2 as a Primary Domain Controller + + +Prerequisite Reading + + +Before you continue readingin this chapter, please make sure +that you are comfortable with configuring basic files services +in smb.conf and how to enable and administrate password +encryption in Samba. Theses two topics are covered in the +smb.conf(5) +manpage and the Encryption chapter +of this HOWTO Collection. + + + + + + + - - -DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba - +Domain Control for Windows 9x/ME + -This appendix was originally authored by John H Terpstra of the Samba Team -and is included here for posterity. +The following section contains much of the original +DOMAIN.txt file previously included with Samba. Much of +the material is based on what went into the book Special +Edition, Using Samba. (Richard Sharpe) + + +A domain and a workgroup are exactly the same thing in terms of network +browsing. The difference is that a distributable authentication +database is associated with a domain, for secure login access to a +network. Also, different access rights can be granted to users if they +successfully authenticate against a domain logon server (NT server and +other systems based on NT server support this, as does at least Samba TNG now). + -NOTE : -The term "Domain Controller" and those related to it refer to one specific -method of authentication that can underly an SMB domain. Domain Controllers -prior to Windows NT Server 3.1 were sold by various companies and based on -private extensions to the LAN Manager 2.1 protocol. Windows NT introduced +The SMB client logging on to a domain has an expectation that every other +server in the domain should accept the same authentication information. +Network browsing functionality of domains and workgroups is +identical and is explained in BROWSING.txt. It should be noted, that browsing +is total orthogonal to logon support. + + + +Issues related to the single-logon network model are discussed in this +document. Samba supports domain logons, network logon scripts, and user +profiles for MS Windows for workgroups and MS Windows 9X clients. + + + + +When an SMB client in a domain wishes to logon it broadcast requests for a +logon server. The first one to reply gets the job, and validates its +password using whatever mechanism the Samba administrator has installed. +It is possible (but very stupid) to create a domain where the user +database is not shared between servers, ie they are effectively workgroup +servers advertising themselves as participating in a domain. This +demonstrates how authentication is quite different from but closely +involved with domains. + + + +Another thing commonly associated with single-logon domains is remote +administration over the SMB protocol. Again, there is no reason why this +cannot be implemented with an underlying username database which is +different from the Windows NT SAM. Support for the Remote Administration +Protocol is planned for a future release of Samba. + + + +Network logon support as discussed in this section is aimed at Window for +Workgroups, and Windows 9X clients. + + + +Support for profiles is confirmed as working for Win95, NT 4.0 and NT 3.51. +It is possible to specify: the profile location; script file to be loaded +on login; the user's home directory; and for NT a kick-off time could also +now easily be supported. However, there are some differences between Win9X +profile support and WinNT profile support. These are discussed below. + + + +With NT Workstations, all this does not require the use or intervention of +an NT 4.0 or NT 3.51 server: Samba can now replace the logon services +provided by an NT server, to a limited and experimental degree (for example, +running "User Manager for Domains" will not provide you with access to +a domain created by a Samba Server). + + + +With Win95, the help of an NT server can be enlisted, both for profile storage +and for user authentication. For details on user authentication, see +security_level.txt. For details on profile storage, see below. + + + +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. + + + +Before launching into the configuration instructions, it is worthwhile looking +at how a Win9X client performs a logon: + + + + + + The client broadcasts (to the IP broadcast address of the subnet it is in) + a NetLogon request. This is sent to the NetBIOS address DOMAIN<00> at the + NetBIOS layer. The client chooses the first response it receives, which + contains the NetBIOS name of the logon server to use in the format of + \\SERVER. + + + + + + The client then connects to that server, logs on (does an SMBsessetupX) and + then connects to the IPC$ share (using an SMBtconX). + + + + + + The client then does a NetWkstaUserLogon request, which retrieves the name + of the user's logon script. + + + + + + The client then connects to the NetLogon share and searches for this + and if it is found and can be read, is retrieved and executed by the client. + After this, the client disconnects from the NetLogon share. + + + + + + The client then sends a NetUserGetInfo request to the server, to retrieve + the user's home share, which is used to search for profiles. Since the + response to the NetUserGetInfo request does not contain much more + the user's home share, profiles for Win9X clients MUST reside in the user + home directory. + + + + + + The client then connects to the user's home share and searches for the + user's profile. As it turns out, you can specify the users home share as + a sharename and path. For example, \\server\fred\.profile. + If the profiles are found, they are implemented. + + + + + + The client then disconnects from the user's home share, and reconnects to + the NetLogon share and looks for CONFIG.POL, the policies file. If this is + found, it is read and implemented. + + + + + + +Configuration Instructions: Network Logons + + +To use domain logons and profiles you need to do the following: + + + + + + + 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, how to use it, what it is, + 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 = no + + + + 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. + + + + + + + + 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 + something like: + + + +logon script = scripts\%U.bat + + + + + + 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. + + + + + + + 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. + + + + + + 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. + + + + + +security mode and master browsers + + +There are a few comments to make in order to tie up some +loose ends. There has been much debate over the issue of whether +or not it is ok to configure Samba as a Domain Controller in security +modes other than USER. The only security mode +which will not work due to technical reasons is SHARE +mode security. DOMAIN and SERVER +mode security is really just a variation on SMB user level security. + + + +Actually, this issue is also closer tied to the debate on whether +or not Samba must be the domain master browser for its workgroup +when operating as a DC. While it may technically be possible +to configure a server as such (after all, browsing and domain logons +are two distinctly different functions), it is not a good idea to +so. You should remember that the DC must register the DOMAIN#1b netbios +name. This is the name used by Windows clients to locate the DC. +Windows clients do not distinguish between the DC and the DMB. +For this reason, it is very wise to configure the Samba DC as the DMB. + + + +Now back to the issue of configuring a Samba DC to use a mode other +than "security = user". If a Samba host is configured to use +another SMB server or DC in order to validate user connection +requests, then it is a fact that some other machine on the network +(the "password server") knows more about user than the Samba host. +99% of the time, this other host is a domain controller. Now +in order to operate in domain mode security, the "workgroup" parameter +must be set to the name of the Windows NT domain (which already +has a domain controller, right?) + + + +Therefore configuring a Samba box as a DC for a domain that +already by definition has a PDC is asking for trouble. +Therefore, you should always configure the Samba DC to be the DMB +for its domain. + + + + + + + +Configuration Instructions: Setting up Roaming User Profiles + + + +NOTE! Roaming profiles support is different +for Win9X and WinNT. + + + + +Before discussing how to configure roaming profiles, it is useful to see how +Win9X and WinNT clients implement these features. + + + +Win9X clients send a NetUserGetInfo request to the server to get the user's +profiles location. However, the response does not have room for a separate +profiles location field, only the users home share. This means that Win9X +profiles are restricted to being in the user's home directory. + + + + +WinNT clients send a NetSAMLogon RPC request, which contains many fields, +including a separate field for the location of the user's profiles. +This means that support for profiles is different for Win9X and WinNT. + + + + + +Windows NT Configuration + + +To support WinNT clients, inn the [global] section of smb.conf set the +following (for example): + + + +logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath + + + +The default for this option is \\%N\%U\profile, namely +\\sambaserver\username\profile. The \\N%\%U service 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. + + + + +[lkcl 26aug96 - we have discovered a problem where Windows clients can +maintain a connection to the [homes] share in between logins. The +[homes] share must NOT therefore be used in a profile path.] + + + + + + + +Windows 9X Configuration + + +To support Win9X clients, you must use the "logon home" parameter. Samba has +now been fixed so that "net use/home" now works as well, and it, too, relies +on the "logon home" parameter. + + + +By using the logon home parameter, you are restricted to putting Win9X +profiles in the user's home directory. But wait! There is a trick you +can use. If you set the following in the [global] section of your +smb.conf file: + + + +logon home = \\%L\%U\.profiles + + + +then your Win9X clients will dutifully put their clients in a subdirectory +of your home directory called .profiles (thus making them hidden). + + + +Not only that, but 'net use/home' will also work, because of a feature in +Win9X. It removes any directory stuff off the end of the home directory area +and only uses the server and share portion. That is, it looks like you +specified \\%L\%U for "logon home". + + + + + + + +Win9X and WinNT Configuration + + +You can support profiles for both Win9X and WinNT clients by setting both the +"logon home" and "logon path" parameters. For example: + + + +logon home = \\%L\%U\.profiles +logon path = \\%L\profiles\%U + + + + +I have not checked what 'net use /home' does on NT when "logon home" is +set as above. + + + + + + + +Windows 9X Profile Setup + + +When a user first logs in on Windows 9X, 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. You will need to use the [global] +options "preserve case = yes", "short case preserve = yes" and +"case sensitive = no" in order to maintain capital letters in shortcuts +in any of the profile folders. + + + + +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 this file. + + + + + + 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. + + + + + + + On the Windows 95 machine, go to Control Panel | Network | + Client for Microsoft Networks | Preferences. Select 'Log on to + NT Domain'. Then, ensure that the Primary Logon is 'Client for + Microsoft Networks'. Press OK, and this time allow the computer + to reboot. + + + + + + +Under Windows 95, Profiles are downloaded from the Primary Logon. +If you have the Primary Logon as 'Client for Novell Networks', then +the profiles and logon script will be downloaded from your Novell +Server. If you have the Primary Logon as 'Windows Logon', then the +profiles will be loaded from the local machine - a bit against the +concept of roaming profiles, if you ask me. + + + +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, +but bear in mind that the user will be authenticated against this +domain and profiles downloaded from it, if that domain logon server +supports it), 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" +on the samba server 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 :-). +You will find that if the user creates further folders or short-cuts, +that the client will merge the profile contents downloaded with the +contents of the profile directory already on the local client, taking +the newest folders and short-cuts from each set. + + + +If you have made the folders / files read-only on the samba server, +then you will get errors from the w95 machine on logon and logout, as +it attempts to merge the local and the remote profile. Basically, if +you have any errors reported by the w95 machine, check the unix file +permissions and ownership rights on the profile directory contents, +on the samba server. + + + +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". + + + + + + instead of logging in under the [user, password, domain] dialog, + press escape. + + + + + + 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]. + + + + + + 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. + + + + + + search for the user's .PWL password-cacheing file in the c:\windows + directory, and delete it. + + + + + + + log off the windows 95 client. + + + + + + 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. + + + +If you have access to an NT server, then first set up roaming profiles +and / or netlogons on the NT server. Make a packet trace, or examine +the example packet traces provided with NT server, and see what the +differences are with the equivalent samba trace. + + + + + + +Windows NT Workstation 4.0 + + +When a user first logs in to a Windows NT Workstation, the profile +NTuser.DAT is created. The profile location can be now specified +through the "logon path" parameter. + + + + +[lkcl 10aug97 - i tried setting the path to +\\samba-server\homes\profile, and discovered that this fails because +a background process maintains the connection to the [homes] share +which does _not_ close down in between user logins. you have to +have \\samba-server\%L\profile, where user is the username created +from the [homes] share]. + + + + +There is a parameter that is now available for use with NT Profiles: +"logon drive". This should be set to "h:" or any other drive, and +should be used in conjunction with the new "logon home" parameter. + + + +The entry for the NT 4.0 profile is a _directory_ not a file. The NT +help on profiles mentions that a directory is also created with a .PDS +extension. The user, while logging in, must have write permission to +create the full profile path (and the folder with the .PDS extension) +[lkcl 10aug97 - i found that the creation of the .PDS directory failed, +and had to create these manually for each user, with a shell script. +also, i presume, but have not tested, that the full profile path must +be browseable just as it is for w95, due to the manner in which they +attempt to create the full profile path: test existence of each path +component; create path component]. + + + +In the profile directory, NT creates more folders than 95. It creates +"Application Data" and others, as well as "Desktop", "Nethood", +"Start Menu" and "Programs". The profile itself is stored in a file +NTuser.DAT. Nothing appears to be stored in the .PDS directory, and +its purpose is currently unknown. + + + +You can use the System Control Panel to copy a local profile onto +a samba server (see NT Help on profiles: it is also capable of firing +up the correct location in the System Control Panel for you). The +NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN +turns a profile into a mandatory one. + + + + +[lkcl 10aug97 - i notice that NT Workstation tells me that it is +downloading a profile from a slow link. whether this is actually the +case, or whether there is some configuration issue, as yet unknown, +that makes NT Workstation _think_ that the link is a slow one is a +matter to be resolved]. + + + +[lkcl 20aug97 - after samba digest correspondance, one user found, and +another confirmed, that profiles cannot be loaded from a samba server +unless "security = user" and "encrypt passwords = yes" (see the file +ENCRYPTION.txt) or "security = server" and "password server = ip.address. +of.yourNTserver" are used. either of these options will allow the NT +workstation to access the samba server using LAN manager encrypted +passwords, without the user intervention normally required by NT +workstation for clear-text passwords]. + + + +[lkcl 25aug97 - more comments received about NT profiles: the case of +the profile _matters_. the file _must_ be called NTuser.DAT or, for +a mandatory profile, NTuser.MAN]. + + + + + + + +Windows NT Server + + +There is nothing to stop you specifying any path that you like for the +location of users' profiles. Therefore, you could specify that the +profile be stored on a samba server, or any other SMB server, as long as +that SMB server supports encrypted passwords. + + + + + + +Sharing Profiles between W95 and NT Workstation 4.0 + + +Potentially outdated or incorrect material follows + +I think this is all bogus, but have not deleted it. (Richard Sharpe) + + + + +The default logon path is \\%N\U%. NT Workstation will attempt to create +a directory "\\samba-server\username.PDS" if you specify the logon path +as "\\samba-server\username" with the NT User Manager. Therefore, you +will need to specify (for example) "\\samba-server\username\profile". +NT 4.0 will attempt to create "\\samba-server\username\profile.PDS", which +is more likely to succeed. + + + +If you then want to share the same Start Menu / Desktop with W95, you will +need to specify "logon path = \\samba-server\username\profile" [lkcl 10aug97 +this has its drawbacks: i created a shortcut to telnet.exe, which attempts +to run from the c:\winnt\system32 directory. this directory is obviously +unlikely to exist on a Win95-only host]. + + + + +If you have this set up correctly, you will find separate user.DAT and +NTuser.DAT files in the same profile directory. + + + + +[lkcl 25aug97 - there are some issues to resolve with downloading of +NT profiles, probably to do with time/date stamps. i have found that +NTuser.DAT is never updated on the workstation after the first time that +it is copied to the local workstation profile directory. this is in +contrast to w95, where it _does_ transfer / update profiles correctly]. + + + + + + + + + + + + + +DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba + + + + Possibly Outdated Material + + + This appendix was originally authored by John H Terpstra of + the Samba Team and is included here for posterity. + + + + + +NOTE : +The term "Domain Controller" and those related to it refer to one specific +method of authentication that can underly an SMB domain. Domain Controllers +prior to Windows NT Server 3.1 were sold by various companies and based on +private extensions to the LAN Manager 2.1 protocol. Windows NT introduced Microsoft-specific ways of distributing the user authentication database. See DOMAIN.txt for examples of how Samba can participate in or create SMB domains based on shared authentication database schemes other than the @@ -858,13 +1773,8 @@ Windows NT SAM. Windows NT Server can be installed as either a plain file and print server (WORKGROUP workstation 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. -However only those servers which have licensed Windows NT code in them can be -a primary Domain Controller (eg Windows NT Server, Advanced Server for Unix.) diff --git a/docs/docbook/projdoc/printer_driver2.sgml b/docs/docbook/projdoc/printer_driver2.sgml index 7f0aebc45f..51471ae690 100644 --- a/docs/docbook/projdoc/printer_driver2.sgml +++ b/docs/docbook/projdoc/printer_driver2.sgml @@ -13,7 +13,7 @@ - (20 Apr 2001) + (3 May 2001) Printing Support in Samba 2.2.x @@ -55,17 +55,42 @@ SPOOLSS support includes: information + +There has been some initial confusion about what all this means +and whether or not it is a requirement for printer drivers to be +installed on a Samba host in order to support printing from Windows +clients. A bug existed in Samba 2.2.0 which made Windows NT/2000 clients +require that the Samba server possess a valid driver for the printer. +This is fixed in Samba 2.2.1 and once again, Windows NT/2000 clients +can use the local APW for installing drivers to be used with a Samba +served printer. This is the same behavior exhibited by Windows 9x clients. +As a side note, Samba does not use these drivers in any way to process +spooled files. They are utilized entirely by the clients. + + + +The following MS KB article, may be of some help if you are dealing with +Windows 2000 clients: How to Add Printers with No User +Interaction in Windows 2000 + + + +http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP + + Configuration + +[print$] vs. [printer$] + -WARNING!!! Previous versions of Samba -recommended using a share named [printer$]. This name was taken from the -printer$ service created by Windows 9x clients when a -printer was shared. Windows 9x printer servers always have +Previous versions of Samba recommended using a share named [printer$]. +This name was taken from the printer$ service created by Windows 9x +clients when a printer was shared. Windows 9x printer servers always have a printer$ service which provides read-only access via no password in order to support printer driver downloads. @@ -81,13 +106,13 @@ the client. -These parameters, including printer driver +These parameters, including printer driver file parameter, are being depreciated and should not be used in new installations. For more information on this change, -you should refer to the Migration section -of this document. +you should refer to the Migration section +of this document. - + Creating [print$] @@ -112,18 +137,22 @@ appropriate values for your site): guest ok = yes browseable = yes read only = yes + ; since this share is configured as read only, then we need + ; a 'write list'. Check the file system permissions to make + ; sure this account can copy files to the share. If this + ; is setup to a non-root account, then it should also exist + ; as a 'printer admin' write list = ntadmin The write list is used to allow administrative level user accounts to have write access in order to update files -on the share. See the -smb.conf(5) man page for more information on -configuring file shares. +on the share. See the smb.conf(5) +man page for more information on configuring file shares. -The requirement for -guest ok = yes depends upon how your +The requirement for guest +ok = yes depends upon how your site is configured. If users will be guaranteed to have an account on the Samba host, then this is a non-issue. @@ -165,27 +194,33 @@ for each architecture you wish to support. - ATTENTION! REQUIRED PERMISSIONS +ATTENTION! REQUIRED PERMISSIONS - In order to currently add a new driver to you Samba host, - one of two conditions must hold true: + +In order to currently add a new driver to you Samba host, +one of two conditions must hold true: + - - The account used to connect to the Samba host - must have a uid of 0 (i.e. a root account) + + The account used to connect to the Samba host + must have a uid of 0 (i.e. a root account) - The account used to connect to the Samba host - must be a member of the printer - admin list. - - - Of course, the connected account must still possess access - to add files to the subdirectories beneath [print$]. + The account used to connect to the Samba host + must be a member of the printer + admin list. + + + +Of course, the connected account must still possess access +to add files to the subdirectories beneath [print$]. Remember +that all file shares are set to 'read only' by default. + -Once you have created the required [print$] service and + +Once you have created the required [print$] service and associated subdirectories, simply log onto the Samba server using a root (or printer admin) account from a Windows NT 4.0 client. Navigate to the "Printers" folder @@ -198,9 +233,27 @@ that matches the printer shares defined on your Samba host. Setting Drivers for Existing Printers The initial listing of printers in the Samba host's -Printers folder will have no printer driver assigned to them. -The way assign a driver to a printer is to view the Properties -of the printer and either +Printers folder will have no real printer driver assigned +to them. By default, in Samba 2.2.0 this driver name was set to +NO PRINTER DRIVER AVAILABLE FOR THIS PRINTER. +Later versions changed this to a NULL string to allow the use +tof the local Add Printer Wizard on NT/2000 clients. +Attempting to view the printer properties for a printer +which has this default driver assigned will result in +the error message: + + +Device settings cannot be displayed. The driver +for the specified printer is not installed, only spooler +properties will be displayed. Do you want to install the +driver now? + + + +Click "No" in the error dialog and you will be presented with +the printer properties window. The way assign a driver to a +printer is to either + Use the "New Driver..." button to install @@ -271,7 +324,7 @@ Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,] comment:[] -$ rpcclient pogo -U root%bleaK.er \ +$ rpcclient pogo -U root%secret \ > -c "setdriver hp-print \"HP LaserJet 4000 Series PS\"" Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] Successfully set hp-print to driver HP LaserJet 4000 Series PS. @@ -292,7 +345,7 @@ Add Printer Wizard icon. The APW will be show only if The connected user is able to successfully execute an OpenPrinterEx(\\server) with administrative - priviledges (i.e. root or printer admin. + priviledges (i.e. root or printer admin). show @@ -302,8 +355,8 @@ Add Printer Wizard icon. The APW will be show only if In order to be able to use the APW to successfully add a printer to a Samba -server, the addprinter -command must have a defined value. The program +server, the add +printer command must have a defined value. The program hook must successfully add the printer to the system (i.e. /etc/printcap or appropriate files) and smb.conf if necessary. @@ -312,16 +365,16 @@ hook must successfully add the printer to the system (i.e. When using the APW from a client, if the named printer share does not exist, smbd will execute the add printer -program and reparse to the smb.conf +command and reparse to the smb.conf to attempt to locate the new printer share. If the share is still not defined, an error of "Access Denied" is returned to the client. Note that the -add printer program is executed undet the context +add printer program is executed under the context of the connected user, not necessarily a root account. -There is a complementing deleteprinter -command for removing entries from the "Printers..." +There is a complementing delete +printer command for removing entries from the "Printers..." folder. @@ -473,7 +526,7 @@ foreach (supported architecture for a given driver) will reveal that Windows NT always uses the NT driver - name. The is ok as Windows NT always requires that at least + name. This is ok as Windows NT always requires that at least the Windows NT version of the printer driver is present. However, Samba does not have the requirement internally. Therefore, how can you use the NT driver name if is has not @@ -489,67 +542,167 @@ foreach (supported architecture for a given driver) - <anchor id="MIGRATION">Migration to from Samba 2.0.x to - 2.2.x - - Given that printer driver management has changed - (we hope improved :) ) in 2.2.0 over prior releases, - migration from an existing setup to 2.2.0 can follow - several paths. +<anchor id="MIGRATION">Migration to from Samba 2.0.x to 2.2.x + + +Given that printer driver management has changed (we hope improved) in +2.2 over prior releases, migration from an existing setup to 2.2 can +follow several paths. + + + +Windows clients have a tendency to remember things for quite a while. +For example, if a Windows NT client has attached to a Samba 2.0 server, +it will remember the server as a LanMan printer server. Upgrading +the Samba host to 2.2 makes support for MSRPC printing possible, but +the NT client will still remember the previous setting. + + + +In order to give an NT client printing "amesia" (only necessary if you +want to use the newer MSRPC printing functionality in Samba), delete +the registry keys associated with the print server contained in +[HKLM\SYSTEM\CurrentControlSet\Control\Print]. The +spooler service on the client should be stopped prior to doing this: + + + +C:\WINNT\ > net stop spooler + + + +All the normal disclaimers about editing the registry go +here. Be careful, and know what you are doing. + + + +The spooler service should be restarted after you have finished +removing the appropriate registry entries by replacing the +stop command above with start. + + + +Windows 9x clients will continue to use LanMan printing calls +with a 2.2 Samba server so there is no need to perform any of these +modifications on non-NT clients. + - - Achtung! - The following smb.conf parameters are considered to be - depreciated and will be removed soon. Do not use them - in new installations + +Achtung! + + +The following smb.conf parameters are considered to be depreciated and will +be removed soon. Do not use them in new installations + - - printer driver file (G) - + + printer driver file (G) + - printer driver (S) - + printer driver (S) + - printer driver location (S) - - - + printer driver location (S) + + + - Here are the possible scenarios for supporting migration: + +Here are the possible scenarios for supporting migration: + - - If you do not desire the new Windows NT - print driver support, nothing needs to be done. - All existing parameters work the same. - - If you want to take advantage of NT printer - driver support but do not want to migrate the - 9x drivers to the new setup, the leave the existing - printers.def file. When smbd attempts to locate a - 9x driver for the printer in the TDB and fails it - will drop down to using the printers.def (and all - associated parameters). The make_printerdef - tool will also remain for backwards compatibility but will - be moved to the "this tool is the old way of doing it" - pile. - - If you install a Windows 9x driver for a printer - on your Samba host (in the printing TDB), this information will - take precedence and the three old printing parameters - will be ignored (including print driver location). - - If you want to migrate an existing printers.def - file into the new setup, the current only - solution is to use the Windows NT APW to install the NT drivers - and the 9x drivers. This can be scripted using smbclient - and rpcclient. See the - Imprints installation client at http://imprints.sourceforge.net/ - for an example. - - + + If you do not desire the new Windows NT + print driver support, nothing needs to be done. + All existing parameters work the same. + + If you want to take advantage of NT printer + driver support but do not want to migrate the + 9x drivers to the new setup, the leave the existing + printers.def file. When smbd attempts to locate a + 9x driver for the printer in the TDB and fails it + will drop down to using the printers.def (and all + associated parameters). The make_printerdef + tool will also remain for backwards compatibility but will + be moved to the "this tool is the old way of doing it" + pile. + + If you install a Windows 9x driver for a printer + on your Samba host (in the printing TDB), this information will + take precedence and the three old printing parameters + will be ignored (including print driver location). + + If you want to migrate an existing printers.def + file into the new setup, the current only solution is to use the Windows + NT APW to install the NT drivers and the 9x drivers. This can be scripted + using smbclient and rpcclient. See the + Imprints installation client at http://imprints.sourceforge.net/ + for an example. + + + + + diff --git a/docs/docbook/projdoc/samba-doc.sgml b/docs/docbook/projdoc/samba-doc.sgml index b055477db7..fa58399bf1 100644 --- a/docs/docbook/projdoc/samba-doc.sgml +++ b/docs/docbook/projdoc/samba-doc.sgml @@ -8,6 +8,7 @@ + ]> @@ -26,10 +27,10 @@ Abstract -This book is a collection of HOWTOs added to Samba documentation over the year. +This book is a collection of HOWTOs added to Samba documentation over the years. I try to ensure that all are current, but sometimes the is a larger job -than one person can maintain. You can always find the later version of this -PDF file at http://www.samba.org/ +than one person can maintain. The most recent version of this document +can be found at http://www.samba.org/ on the "Documentation" page. Please send updates to jerry@samba.org. @@ -49,5 +50,6 @@ Cheers, jerry &WINBIND; &NT-Security; &OS2-Client; +&CVS-Access; -- cgit