>>> - Execute a
+
+
+
+ Page 4 (printed 1/7/103)
+
+
+
+
+
+
+ RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ GetPrinterDriverDirectory() RPC to retreive the SMB share
+ name and subdirectory for storing printer driver files for
+ a given architecture. Possible values for _a_r_c_h are
+ "Windows 4.0" (for Windows 95/98), "Windows NT x86",
+ "Windows NT PowerPC", "Windows Alpha_AXP", and "Windows NT
+ R4000".
+
+ o+ ggggeeeettttpppprrrriiiinnnntttteeeerrrr <<<>>> - Retrieve the current printer
+ information. This command corresponds to the GetPrinter()
+ MS Platform SDK function.
+
+ o+ ooooppppeeeennnnpppprrrriiiinnnntttteeeerrrr <<<
>>> - Execute an OpenPrinterEx() and
+ ClosePrinter() RPC against a given printer.
+
+ o+ sssseeeettttddddrrrriiiivvvveeeerrrr <<<
>>> <<<>>> - Execute a
+ SetPrinter() command to update the printer driver
+ associated with an installed printer. The printer driver
+ must already be correctly installed on the print server.
+
+ See also the eeeennnnuuuummmmpppprrrriiiinnnntttteeeerrrrssss and eeeennnnuuuummmmddddrrrriiiivvvveeeerrrrssss commands for
+ obtaining a list of of installed printers and drivers.
+
+ GGGGEEEENNNNEEEERRRRAAAALLLL OOOOPPPPTTTTIIIIOOOONNNNSSSS
+
+ o+ ddddeeeebbbbuuuugggglllleeeevvvveeeellll - Set the current debug level used to log
+ information.
+
+ o+ hhhheeeellllpppp ((((????)))) - Print a listing of all known commands or
+ extended help on a particular command.
+
+ o+ qqqquuuuiiiitttt ((((eeeexxxxiiiitttt)))) - Exit rrrrppppcccccccclllliiiieeeennnntttt .
+
+ BBBBUUUUGGGGSSSS
+ rrrrppppcccccccclllliiiieeeennnntttt is designed as a developer testing tool and may
+ not be robust in certain areas (such as command line
+ parsing). It has been known to generate a core dump upon
+ failures when invalid parameters where passed to the
+ interpreter.
+
+ From Luke Leighton's original rpcclient man page:
+
+ """"WWWWAAAARRRRNNNNIIIINNNNGGGG!!!! The MSRPC over SMB code has been developed from
+ examining Network traces. No documentation is available from
+ the original creators (Microsoft) on how MSRPC over SMB
+ works, or how the individual MSRPC services work.
+ Microsoft's implementation of these services has been
+ demonstrated (and reported) to be... a bit flaky in places.
+
+ The development of Samba's implementation is also a bit
+ rough, and as more of the services are understood, it can
+ even result in versions of ssssmmmmbbbbdddd((((8888)))) and rrrrppppcccccccclllliiiieeeennnntttt((((1111)))) that are
+ incompatible for some commands or services. Additionally,
+
+
+
+ Page 5 (printed 1/7/103)
+
+
+
+
+
+
+ RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ the developers are sending reports to Microsoft, and
+ problems found or reported to Microsoft are fixed in Service
+ Packs, which may result in incompatibilities."
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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 rpcclient man page was written by Matthew
+ Geddes, Luke Kenneth Casson Leighton, and rewritten by
+ Gerald Carter. The conversion to DocBook for Samba 2.2 was
+ done by Gerald Carter.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 6 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/smbcacls.1 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/smbcacls.1
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/smbcacls.1 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/smbcacls.1 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,264 @@
+
+
+
+ SSSSMMMMBBBBCCCCAAAACCCCLLLLSSSS((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCAAAACCCCLLLLSSSS((((1111))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ smbcacls - Set or get ACLs on an NT file or directory names
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ ssssmmmmbbbbccccaaaaccccllllssss ////////sssseeeerrrrvvvveeeerrrr////sssshhhhaaaarrrreeee ffffiiiilllleeeennnnaaaammmmeeee [ ----UUUU uuuusssseeeerrrrnnnnaaaammmmeeee ] [ ----AAAA aaaaccccllllssss
+ ] [ ----MMMM aaaaccccllllssss ] [ ----DDDD aaaaccccllllssss ] [ ----SSSS aaaaccccllllssss ] [ ----CCCC nnnnaaaammmmeeee ] [ ----GGGG
+ nnnnaaaammmmeeee ] [ ----nnnn ] [ ----hhhh ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This tool is part of the Samba suite.
+
+ The ssssmmmmbbbbccccaaaaccccllllssss program manipulates NT Access Control Lists
+ (ACLs) on SMB file shares.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ The following options are available to the ssssmmmmbbbbccccaaaaccccllllssss program.
+ The format of ACLs is described in the section ACL FORMAT
+
+ ----AAAA aaaaccccllllssss
+ Add the ACLs specified to the ACL list. Existing access
+ control entries are unchanged.
+
+ ----MMMM aaaaccccllllssss
+ Modify the mask value (permissions) for the ACLs
+ specified on the command line. An error will be printed
+ for each ACL specified that was not already present in
+ the ACL list
+
+ ----DDDD aaaaccccllllssss
+ Delete any ACLs specified on the command line. An error
+ will be printed for each ACL specified that was not
+ already present in the ACL list.
+
+ ----SSSS aaaaccccllllssss
+ This command sets the ACLs on the file with only the
+ ones specified on the command line. All other ACLs are
+ erased. Note that the ACL specified must contain at
+ least a revision, type, owner and group for the call to
+ succeed.
+
+ ----UUUU uuuusssseeeerrrrnnnnaaaammmmeeee
+ Specifies a username used to connect to the specified
+ service. The username may be of the form "username" in
+ which case the user is prompted to enter in a password
+ and the workgroup specified in the _s_m_b._c_o_n_f file is
+ used, or "username%password" or
+ "DOMAIN\username%password" and the password and
+ workgroup names are used as provided.
+
+ ----CCCC nnnnaaaammmmeeee
+ The owner of a file or directory can be changed to the
+ name given using the -_C option. The name can be a sid
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCAAAACCCCLLLLSSSS((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCAAAACCCCLLLLSSSS((((1111))))
+
+
+
+ in the form S-1-x-y-z or a name resolved against the
+ server specified in the first argument.
+
+ This command is a shortcut for -M OWNER:name.
+
+ ----GGGG nnnnaaaammmmeeee
+ The group owner of a file or directory can be changed
+ to the name given using the -_G option. The name can be
+ a sid in the form S-1-x-y-z or a name resolved against
+ the server specified n the first argument.
+
+ This command is a shortcut for -M GROUP:name.
+
+ ----nnnn This option displays all ACL information in numeric
+ format. The default is to convert SIDs to names and ACE
+ types and masks to a readable string format.
+
+ ----hhhh Print usage information on the ssssmmmmbbbbccccaaaaccccllllssss program.
+
+ AAAACCCCLLLL FFFFOOOORRRRMMMMAAAATTTT
+ The format of an ACL is one or more ACL entries separated by
+ either commas or newlines. An ACL entry is one of the
+ following:
+
+
+ REVISION:
+ OWNER:
+ GROUP:
+ ACL:://
+
+
+
+ The revision of the ACL specifies the internal Windows NT
+ ACL revision for the security descriptor. If not specified
+ it defaults to 1. Using values other than 1 may cause
+ strange behaviour.
+
+ The owner and group specify the owner and group sids for the
+ object. If a SID in the format CWS-1-x-y-z is specified this
+ is used, otherwise the name specified is resolved using the
+ server on which the file or directory resides.
+
+ ACLs specify permissions granted to the SID. This SID again
+ can be specified in CWS-1-x-y-z format or as a name in which
+ case it is resolved against the server on which the file or
+ directory resides. The type, flags and mask values determine
+ the type of access granted to the SID.
+
+ The type can be either 0 or 1 corresponding to ALLOWED or
+ DENIED access to the SID. The flags values are generally
+ zero for file ACLs and either 9 or 2 for directory ACLs.
+ Some common flags are:
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCAAAACCCCLLLLSSSS((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCAAAACCCCLLLLSSSS((((1111))))
+
+
+
+ o+ #define SEC_ACE_FLAG_OBJECT_INHERIT 0x1
+
+ o+ #define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2
+
+ o+ #define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4
+
+ o+ #define SEC_ACE_FLAG_INHERIT_ONLY 0x8
+
+ At present flags can only be specified as decimal or
+ hexadecimal values.
+
+ The mask is a value which expresses the access right granted
+ to the SID. It can be given as a decimal or hexadecimal
+ value, or by using one of the following text strings which
+ map to the NT file permissions of the same name.
+
+ o+ RRRR - Allow read access
+
+ o+ WWWW - Allow write access
+
+ o+ XXXX - Execute permission on the object
+
+ o+ DDDD - Delete the object
+
+ o+ PPPP - Change permissions
+
+ o+ OOOO - Take ownership
+
+ The following combined permissions can be specified:
+
+ o+ RRRREEEEAAAADDDD - Equivalent to 'RX' permissions
+
+ o+ CCCCHHHHAAAANNNNGGGGEEEE - Equivalent to 'RXWD' permissions
+
+ o+ FFFFUUUULLLLLLLL - Equivalent to 'RWXDPO' permissions
+
+ EEEEXXXXIIIITTTT SSSSTTTTAAAATTTTUUUUSSSS
+ The ssssmmmmbbbbccccaaaaccccllllssss program sets the exit status depending on the
+ success or otherwise of the operations performed. The exit
+ status may be one of the following values.
+
+ If the operation succeeded, smbcacls returns and exit status
+ of 0. If ssssmmmmbbbbccccaaaaccccllllssss couldn't connect to the specified server,
+ or there was an error getting or setting the ACLs, an exit
+ status of 1 is returned. If there was an error parsing any
+ command line arguments, an exit status of 2 is returned.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ The original Samba software and related utilities were
+
+
+
+ Page 3 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCAAAACCCCLLLLSSSS((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCAAAACCCCLLLLSSSS((((1111))))
+
+
+
+ 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.
+
+ ssssmmmmbbbbccccaaaaccccllllssss was written by Andrew Tridgell and Tim Potter.
+
+ The conversion to DocBook for Samba 2.2 was done by Gerald
+ Carter
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 4 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/smbclient.1 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/smbclient.1
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/smbclient.1 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/smbclient.1 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,1056 @@
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ smbclient - ftp-like client to access SMB/CIFS resources on
+ servers
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ ssssmmmmbbbbcccclllliiiieeeennnntttt sssseeeerrrrvvvviiiicccceeeennnnaaaammmmeeee [ ppppaaaasssssssswwwwoooorrrrdddd ] [ ----bbbb <<<>>> ] [
+ ----dddd ddddeeeebbbbuuuugggglllleeeevvvveeeellll ] [ ----DDDD DDDDiiiirrrreeeeccccttttoooorrrryyyy ] [ ----UUUU uuuusssseeeerrrrnnnnaaaammmmeeee ] [ ----WWWW
+ wwwwoooorrrrkkkkggggrrrroooouuuupppp ] [ ----MMMM <<<>>> ] [ ----mmmm mmmmaaaaxxxxpppprrrroooottttooooccccoooollll ] [ ----AAAA
+ aaaauuuutttthhhhffffiiiilllleeee ] [ ----NNNN ] [ ----llll llllooooggggffffiiiilllleeee ] [ ----LLLL <<<>>> ] [
+ ----IIII ddddeeeessssttttiiiinnnnaaaattttiiiioooonnnnIIIIPPPP ] [ ----EEEE <<<>>> ] [ ----cccc <<<>>> ] [ ----iiii ssssccccooooppppeeee ] [ ----OOOO <<<>>> ] [ ----pppp ppppoooorrrrtttt
+ ] [ ----RRRR <<<>>> ] [ ----ssss <<<>>> ] [
+ ----TTTT<<<>>>IIIIXXXXFFFFqqqqggggbbbbNNNNaaaannnn ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This tool is part of the Samba suite.
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt is a client that can 'talk' to an SMB/CIFS server.
+ It offers an interface similar to that of the ftp program
+ (see ffffttttpppp((((1111))))). Operations include things like getting files
+ from the server to the local machine, putting files from the
+ local machine to the server, retrieving directory
+ information from the server and so on.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ sssseeeerrrrvvvviiiicccceeeennnnaaaammmmeeee
+ servicename is the name of the service you want to use
+ on the server. A service name takes the form
+ //_s_e_r_v_e_r/_s_e_r_v_i_c_e where _s_e_r_v_e_r is the NetBIOS name of
+ the SMB/CIFS server offering the desired service and
+ _s_e_r_v_i_c_e is the name of the service offered. Thus to
+ connect to the service "printer" on the SMB/CIFS server
+ "smbserver", you would use the servicename
+ //_s_m_b_s_e_r_v_e_r/_p_r_i_n_t_e_r
+
+ Note that the server name required is NOT necessarily
+ the IP (DNS) host name of the server ! The name
+ required is a NetBIOS server name, which may or may not
+ be the same as the IP hostname of the machine running
+ the server.
+
+ The server name is looked up according to either the -_R
+ parameter to ssssmmmmbbbbcccclllliiiieeeennnntttt or using the name resolve order
+ parameter in the _s_m_b._c_o_n_f file, allowing an
+ administrator to change the order and methods by which
+ server names are looked up.
+
+ ppppaaaasssssssswwwwoooorrrrdddd
+ The password required to access the specified service
+ on the specified server. If this parameter is supplied,
+ the -_N option (suppress password prompt) is assumed.
+
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ There is no default password. If no password is
+ supplied on the command line (either by using this
+ parameter or adding a password to the -_U option (see
+ below)) and the -_N option is not specified, the client
+ will prompt for a password, even if the desired service
+ does not require one. (If no password is required,
+ simply press ENTER to provide a null password.)
+
+ Note: Some servers (including OS/2 and Windows for
+ Workgroups) insist on an uppercase password. Lowercase
+ or mixed case passwords may be rejected by these
+ servers.
+
+ Be cautious about including passwords in scripts.
+
+ ----ssss ssssmmmmbbbb....ccccoooonnnnffff
+ Specifies the location of the all important _s_m_b._c_o_n_f
+ file.
+
+ ----OOOO ssssoooocccckkkkeeeetttt ooooppppttttiiiioooonnnnssss
+ TCP socket options to set on the client socket. See the
+ socket options parameter in the _s_m_b._c_o_n_f (_5) manpage
+ for the list of valid options.
+
+ ----RRRR <<<>>>
+ This option is used by the programs in the Samba suite
+ to determine what naming services and in what order to
+ resolve host names to IP addresses. The option takes a
+ space-separated string of different name resolution
+ options.
+
+ The options are :"lmhosts", "host", "wins" and "bcast".
+ They cause names to be resolved as follows :
+
+ o+ lmhosts : Lookup an IP address in the Samba lmhosts
+ file. If the line in lmhosts has no name type
+ attached to the NetBIOS name (see the lmhosts(5) for
+ details) then any name type matches for lookup.
+
+ o+ host : Do a standard host name to IP address
+ resolution, using the system /_e_t_c/_h_o_s_t_s , NIS, or DNS
+ lookups. This method of name resolution is operating
+ system dependent, for instance on IRIX or Solaris
+ this may be controlled by the /_e_t_c/_n_s_s_w_i_t_c_h._c_o_n_f
+ file). Note that this method is only used if the
+ NetBIOS name type being queried is the 0x20 (server)
+ name type, otherwise it is ignored.
+
+ o+ wins : Query a name with the IP address listed in the
+ _w_i_n_s _s_e_r_v_e_r parameter. If no WINS server has been
+ specified this method will be ignored.
+
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ o+ bcast : Do a broadcast on each of the known local
+ interfaces listed in the _i_n_t_e_r_f_a_c_e_s parameter. This
+ is the least reliable of the name resolution methods
+ as it depends on the target host being on a locally
+ connected subnet.
+
+ If this parameter is not set then the name resolve order
+ defined in the _s_m_b._c_o_n_f file parameter (name resolve order)
+ will be used.
+
+ The default order is lmhosts, host, wins, bcast and without
+ this parameter or any entry in the _n_a_m_e _r_e_s_o_l_v_e _o_r_d_e_r
+ parameter of the _s_m_b._c_o_n_f file the name resolution methods
+ will be attempted in this order.
+
+ ----MMMM NNNNeeeettttBBBBIIIIOOOOSSSS nnnnaaaammmmeeee
+ This options allows you to send messages, using the
+ "WinPopup" protocol, to another computer. Once a
+ connection is established you then type your message,
+ pressing ^D (control-D) to end.
+
+ If the receiving computer is running WinPopup the user
+ will receive the message and probably a beep. If they
+ are not running WinPopup the message will be lost, and
+ no error message will occur.
+
+ The message is also automatically truncated if the
+ message is over 1600 bytes, as this is the limit of the
+ protocol.
+
+ One useful trick is to cat the message through
+ ssssmmmmbbbbcccclllliiiieeeennnntttt. For example: ccccaaaatttt mmmmyyyymmmmeeeessssssssaaaaggggeeee....ttttxxxxtttt |||| ssssmmmmbbbbcccclllliiiieeeennnntttt
+ ----MMMM FFFFRRRREEEEDDDD will send the message in the file
+ _m_y_m_e_s_s_a_g_e._t_x_t to the machine FRED.
+
+ You may also find the -_U and -_I options useful, as they
+ allow you to control the FROM and TO parts of the
+ message.
+
+ See the message command parameter in the _s_m_b._c_o_n_f(_5)
+ for a description of how to handle incoming WinPopup
+ messages in Samba.
+
+ NNNNooootttteeee: Copy WinPopup into the startup group on your WfWg
+ PCs if you want them to always be able to receive
+ messages.
+
+ ----iiii ssssccccooooppppeeee
+ This specifies a NetBIOS scope that smbclient will use
+ to communicate with when generating NetBIOS names. For
+ details on the use of NetBIOS scopes, see _r_f_c_1_0_0_1._t_x_t
+ and _r_f_c_1_0_0_2._t_x_t. NetBIOS scopes are vvvveeeerrrryyyy rarely used,
+
+
+
+ Page 3 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ only set this parameter if you are the system
+ administrator in charge of all the NetBIOS systems you
+ communicate with.
+
+ ----NNNN If specified, this parameter suppresses the normal
+ password prompt from the client to the user. This is
+ useful when accessing a service that does not require a
+ password.
+
+ Unless a password is specified on the command line or
+ this parameter is specified, the client will request a
+ password.
+
+ ----nnnn NNNNeeeettttBBBBIIIIOOOOSSSS nnnnaaaammmmeeee
+ By default, the client will use the local machine's
+ hostname (in uppercase) as its NetBIOS name. This
+ parameter allows you to override the host name and use
+ whatever NetBIOS name you wish.
+
+ ----dddd ddddeeeebbbbuuuugggglllleeeevvvveeeellll
+ _d_e_b_u_g_l_e_v_e_l is an integer from 0 to 10, or the letter
+ 'A'.
+
+ The default value if this parameter is not specified is
+ zero.
+
+ The higher this value, the more detail will be logged
+ to the log files about the activities of the client. At
+ level 0, only critical errors and serious warnings will
+ be logged. Level 1 is a reasonable level for day to day
+ running - it generates a small amount of information
+ about operations carried out.
+
+ Levels above 1 will generate considerable amounts of
+ log data, and should only be used when investigating a
+ problem. Levels above 3 are designed for use only by
+ developers and generate HUGE amounts of log data, most
+ of which is extremely cryptic. If _d_e_b_u_g_l_e_v_e_l is set to
+ the letter 'A', then aaaallllllll debug messages will be
+ printed. This setting is for developers only (and
+ people who rrrreeeeaaaallllllllyyyy want to know how the code works
+ internally).
+
+ Note that specifying this parameter here will override
+ the log level parameter in the _s_m_b._c_o_n_f (_5) file.
+
+ ----pppp ppppoooorrrrtttt
+ This number is the TCP port number that will be used
+ when making connections to the server. The standard
+ (well-known) TCP port number for an SMB/CIFS server is
+ 139, which is the default.
+
+
+
+
+ Page 4 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ ----llll llllooooggggffffiiiilllleeeennnnaaaammmmeeee
+ If specified, _l_o_g_f_i_l_e_n_a_m_e specifies a base filename
+ into which operational data from the running client
+ will be logged.
+
+ The default base name is specified at compile time.
+
+ The base name is used to generate actual log file
+ names. For example, if the name specified was "log",
+ the debug file would be _l_o_g._c_l_i_e_n_t.
+
+ The log file generated is never removed by the client.
+
+ ----hhhh Print the usage message for the client.
+
+ ----IIII IIIIPPPP----aaaaddddddddrrrreeeessssssss
+ _I_P _a_d_d_r_e_s_s is the address of the server to connect to.
+ It should be specified in standard "a.b.c.d" notation.
+
+ Normally the client would attempt to locate a named
+ SMB/CIFS server by looking it up via the NetBIOS name
+ resolution mechanism described above in the _n_a_m_e
+ _r_e_s_o_l_v_e _o_r_d_e_r parameter above. Using this parameter
+ will force the client to assume that the server is on
+ the machine with the specified IP address and the
+ NetBIOS name component of the resource being connected
+ to will be ignored.
+
+ There is no default for this parameter. If not
+ supplied, it will be determined automatically by the
+ client as described above.
+
+ ----EEEE This parameter causes the client to write messages to
+ the standard error stream (stderr) rather than to the
+ standard output stream.
+
+ By default, the client writes messages to standard
+ output - typically the user's tty.
+
+ ----UUUU uuuusssseeeerrrrnnnnaaaammmmeeee[[[[%%%%ppppaaaassssssss]]]]
+ Sets the SMB username or username and password. If
+ %pass is not specified, The user will be prompted. The
+ client will first check the UUUUSSSSEEEERRRR environment variable,
+ then the LLLLOOOOGGGGNNNNAAAAMMMMEEEE variable and if either exists, the
+ string is uppercased. Anything in these variables
+ following a '%' sign will be treated as the password.
+ If these environment variables are not found, the
+ username GUEST is used.
+
+ If the password is not included in these environment
+ variables (using the %pass syntax), ssssmmmmbbbbcccclllliiiieeeennnntttt will look
+ for a PPPPAAAASSSSSSSSWWWWDDDD environment variable from which to read
+
+
+
+ Page 5 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ the password.
+
+ A third option is to use a credentials file which
+ contains the plaintext of the domain name, username and
+ password. This option is mainly provided for scripts
+ where the admin doesn't wish to pass the credentials on
+ the command line or via environment variables. If this
+ method is used, make certain that the permissions on
+ the file restrict access from unwanted users. See the
+ -_A for more details.
+
+ Be cautious about including passwords in scripts or in
+ the PPPPAAAASSSSSSSSWWWWDDDD environment variable. Also, on many systems
+ the command line of a running process may be seen via
+ the ppppssss command to be safe always allow ssssmmmmbbbbcccclllliiiieeeennnntttt to
+ prompt for a password and type it in directly.
+
+ ----AAAA ffffiiiilllleeeennnnaaaammmmeeee
+ This option allows you to specify a file from which to
+ read the username, domain name, and password used in
+ the connection. The format of the file is
+
+
+ username =
+ password =
+ domain =
+
+
+
+ If the domain parameter is missing the current
+ workgroup name is used instead. Make certain that the
+ permissions on the file restrict access from unwanted
+ users.
+
+ ----LLLL This option allows you to look at what services are
+ available on a server. You use it as ssssmmmmbbbbcccclllliiiieeeennnntttt ----LLLL hhhhoooosssstttt
+ and a list should appear. The -_I option may be useful
+ if your NetBIOS names don't match your TCP/IP DNS host
+ names or if you are trying to reach a host on another
+ network.
+
+ ----tttt tttteeeerrrrmmmmiiiinnnnaaaallll ccccooooddddeeee
+ This option tells ssssmmmmbbbbcccclllliiiieeeennnntttt how to interpret filenames
+ coming from the remote server. Usually Asian language
+ multibyte UNIX implementations use different character
+ sets than SMB/CIFS servers (EEEEUUUUCCCC instead of SSSSJJJJIIIISSSS for
+ example). Setting this parameter will let ssssmmmmbbbbcccclllliiiieeeennnntttt
+ convert between the UNIX filenames and the SMB
+ filenames correctly. This option has not been seriously
+ tested and may have some problems.
+
+ The terminal codes include CWsjis, CWeuc, CWjis7,
+
+
+
+ Page 6 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ CWjis8, CWjunet, CWhex, CWcap. This is not a complete
+ list, check the Samba source code for the complete
+ list.
+
+ ----bbbb bbbbuuuuffffffffeeeerrrrssssiiiizzzzeeee
+ This option changes the transmit/send buffer size when
+ getting or putting a file from/to the server. The
+ default is 65520 bytes. Setting this value smaller (to
+ 1200 bytes) has been observed to speed up file
+ transfers to and from a Win9x server.
+
+ ----WWWW WWWWOOOORRRRKKKKGGGGRRRROOOOUUUUPPPP
+ Override the default workgroup (domain) specified in
+ the workgroup parameter of the _s_m_b._c_o_n_f file for this
+ connection. This may be needed to connect to some
+ servers.
+
+ ----TTTT ttttaaaarrrr ooooppppttttiiiioooonnnnssss
+ smbclient may be used to create ttttaaaarrrr((((1111)))) compatible
+ backups of all the files on an SMB/CIFS share. The
+ secondary tar flags that can be given to this option
+ are :
+
+ o+ _c - Create a tar file on UNIX. Must be followed by
+ the name of a tar file, tape device or "-" for
+ standard output. If using standard output you must
+ turn the log level to its lowest value -d0 to avoid
+ corrupting your tar file. This flag is mutually
+ exclusive with the _x flag.
+
+ o+ _x - Extract (restore) a local tar file back to a
+ share. Unless the -D option is given, the tar files
+ will be restored from the top level of the share.
+ Must be followed by the name of the tar file, device
+ or "-" for standard input. Mutually exclusive with
+ the _c flag. Restored files have their creation times
+ (mtime) set to the date saved in the tar file.
+ Directories currently do not get their creation dates
+ restored properly.
+
+ o+ _I - Include files and directories. Is the default
+ behavior when filenames are specified above. Causes
+ tar files to be included in an extract or create (and
+ therefore everything else to be excluded). See
+ example below. Filename globbing works in one of two
+ ways. See r below.
+
+ o+ _X - Exclude files and directories. Causes tar files
+ to be excluded from an extract or create. See example
+ below. Filename globbing works in one of two ways
+ now. See _r below.
+
+
+
+
+ Page 7 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ o+ _b - Blocksize. Must be followed by a valid (greater
+ than zero) blocksize. Causes tar file to be written
+ out in blocksize*TBLOCK (usually 512 byte) blocks.
+
+ o+ _g - Incremental. Only back up files that have the
+ archive bit set. Useful only with the _c flag.
+
+ o+ _q - Quiet. Keeps tar from printing diagnostics as it
+ works. This is the same as tarmode quiet.
+
+ o+ _r - Regular expression include or exclude. Uses
+ regular expression matching for excluding or
+ excluding files if compiled with HAVE_REGEX_H.
+ However this mode can be very slow. If not compiled
+ with HAVE_REGEX_H, does a limited wildcard match on
+ '*' and '?'.
+
+ o+ _N - Newer than. Must be followed by the name of a
+ file whose date is compared against files found on
+ the share during a create. Only files newer than the
+ file specified are backed up to the tar file. Useful
+ only with the _c flag.
+
+ o+ _a - Set archive bit. Causes the archive bit to be
+ reset when a file is backed up. Useful with the _g and
+ _c flags.
+
+ TTTTaaaarrrr LLLLoooonnnngggg FFFFiiiilllleeee NNNNaaaammmmeeeessss
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt's tar option now supports long file names both on
+ backup and restore. However, the full path name of the file
+ must be less than 1024 bytes. Also, when a tar archive is
+ created, ssssmmmmbbbbcccclllliiiieeeennnntttt's tar option places all files in the
+ archive with relative names, not absolute names.
+
+ TTTTaaaarrrr FFFFiiiilllleeeennnnaaaammmmeeeessss
+
+ All file names can be given as DOS path names (with '\' as
+ the component separator) or as UNIX path names (with '/' as
+ the component separator).
+
+ EEEExxxxaaaammmmpppplllleeeessss
+
+ Restore from tar file _b_a_c_k_u_p._t_a_r into myshare on mypc (no
+ password on share).
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt ////////mmmmyyyyppppcccc////yyyysssshhhhaaaarrrreeee """""""" ----NNNN ----TTTTxxxx bbbbaaaacccckkkkuuuupppp....ttttaaaarrrr
+
+ Restore everything except _u_s_e_r_s/_d_o_c_s
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt ////////mmmmyyyyppppcccc////mmmmyyyysssshhhhaaaarrrreeee """""""" ----NNNN ----TTTTXXXXxxxx bbbbaaaacccckkkkuuuupppp....ttttaaaarrrr uuuusssseeeerrrrssss////ddddooooccccssss
+
+
+
+
+ Page 8 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ Create a tar file of the files beneath _u_s_e_r_s/_d_o_c_s.
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt ////////mmmmyyyyppppcccc////mmmmyyyysssshhhhaaaarrrreeee """""""" ----NNNN ----TTTTcccc bbbbaaaacccckkkkuuuupppp....ttttaaaarrrr uuuusssseeeerrrrssss////ddddooooccccssss
+
+ Create the same tar file as above, but now use a DOS path
+ name.
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt ////////mmmmyyyyppppcccc////mmmmyyyysssshhhhaaaarrrreeee """""""" ----NNNN ----ttttcccc bbbbaaaacccckkkkuuuupppp....ttttaaaarrrr uuuusssseeeerrrrssss\\\\eeeeddddooooccccssss
+
+ Create a tar file of all the files and directories in the
+ share.
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt ////////mmmmyyyyppppcccc////mmmmyyyysssshhhhaaaarrrreeee """""""" ----NNNN ----TTTTcccc bbbbaaaacccckkkkuuuupppp....ttttaaaarrrr ****
+
+ ----DDDD iiiinnnniiiittttiiiiaaaallll ddddiiiirrrreeeeccccttttoooorrrryyyy
+ Change to initial directory before starting. Probably
+ only of any use with the tar -T option.
+
+ ----cccc ccccoooommmmmmmmaaaannnndddd ssssttttrrrriiiinnnngggg
+ command string is a semicolon-separated list of
+ commands to be executed instead of prompting from
+ stdin. -_N is implied by -_c.
+
+ This is particularly useful in scripts and for printing
+ stdin to the server, e.g. ----cccc ''''pppprrrriiiinnnntttt ----''''.
+
+ OOOOPPPPEEEERRRRAAAATTTTIIIIOOOONNNNSSSS
+ Once the client is running, the user is presented with a
+ prompt :
+
+ smb:\>
+
+ The backslash ("\") indicates the current working directory
+ on the server, and will change if the current working
+ directory is changed.
+
+ The prompt indicates that the client is ready and waiting to
+ carry out a user command. Each command is a single word,
+ optionally followed by parameters specific to that command.
+ Command and parameters are space-delimited unless these
+ notes specifically state otherwise. All commands are case-
+ insensitive. Parameters to commands may or may not be case
+ sensitive, depending on the command.
+
+ You can specify file names which have spaces in them by
+ quoting the name with double quotes, for example "a long
+ file name".
+
+ Parameters shown in square brackets (e.g., "[parameter]")
+ are optional. If not given, the command will use suitable
+ defaults. Parameters shown in angle brackets (e.g.,
+ "") are required.
+
+
+
+ Page 9 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ Note that all commands operating on the server are actually
+ performed by issuing a request to the server. Thus the
+ behavior may vary from server to server, depending on how
+ the server was implemented.
+
+ The commands available are given here in alphabetical order.
+
+ ???? [[[[ccccoooommmmmmmmaaaannnndddd]]]]
+ If _c_o_m_m_a_n_d is specified, the ? command will display a
+ brief informative message about the specified command.
+ If no command is specified, a list of available
+ commands will be displayed.
+
+ !!!! [[[[sssshhhheeeellllllll ccccoooommmmmmmmaaaannnndddd]]]]
+ If _s_h_e_l_l _c_o_m_m_a_n_d is specified, the ! command will
+ execute a shell locally and run the specified shell
+ command. If no command is specified, a local shell will
+ be run.
+
+ aaaallllttttnnnnaaaammmmeeee ffffiiiilllleeee
+ The client will request that the server return the
+ "alternate" name (the 8.3 name) for a file or
+ directory.
+
+ ccccaaaannnncccceeeellll jjjjoooobbbbiiiidddd0000 [[[[jjjjoooobbbbiiiidddd1111]]]] ............ [[[[jjjjoooobbbbiiiiddddNNNN]]]]
+ The client will request that the server cancel the
+ printjobs identified by the given numeric print job
+ ids.
+
+ cccchhhhmmmmoooodddd ffffiiiilllleeee mmmmooooddddeeee iiiinnnn ooooccccttttaaaallll
+ This command depends on the server supporting the CIFS
+ UNIX extensions and will fail if the server does not.
+ The client requests that the server change the UNIX
+ permissions to the given octal mode, in standard UNIX
+ format.
+
+ cccchhhhoooowwwwnnnn ffffiiiilllleeee uuuuiiiidddd ggggiiiidddd
+ This command depends on the server supporting the CIFS
+ UNIX extensions and will fail if the server does not.
+ The client requests that the server change the UNIX
+ user and group ownership to the given decimal values.
+ Note there is currently no way to remotely look up the
+ UNIX uid and gid values for a given name. This may be
+ addressed in future versions of the CIFS UNIX
+ extensions.
+
+ ccccdddd [[[[ddddiiiirrrreeeeccccttttoooorrrryyyy nnnnaaaammmmeeee]]]]
+ If "directory name" is specified, the current working
+ directory on the server will be changed to the
+ directory specified. This operation will fail if for
+ any reason the specified directory is inaccessible.
+
+
+
+
+ Page 10 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ If no directory name is specified, the current working
+ directory on the server will be reported.
+
+ ddddeeeellll <<<>>>
+ The client will request that the server attempt to
+ delete all files matching _m_a_s_k from the current working
+ directory on the server.
+
+ ddddiiiirrrr <<<>>>
+ A list of the files matching _m_a_s_k in the current
+ working directory on the server will be retrieved from
+ the server and displayed.
+
+ eeeexxxxiiiitttt Terminate the connection with the server and exit from
+ the program.
+
+ ggggeeeetttt <<<>>> [[[[llllooooccccaaaallll ffffiiiilllleeee nnnnaaaammmmeeee]]]]
+ Copy the file called _r_e_m_o_t_e _f_i_l_e _n_a_m_e from the server
+ to the machine running the client. If specified, name
+ the local copy _l_o_c_a_l _f_i_l_e _n_a_m_e. Note that all transfers
+ in ssssmmmmbbbbcccclllliiiieeeennnntttt are binary. See also the lowercase
+ command.
+
+ hhhheeeellllpppp [[[[ccccoooommmmmmmmaaaannnndddd]]]]
+ See the ? command above.
+
+ llllccccdddd [[[[ddddiiiirrrreeeeccccttttoooorrrryyyy nnnnaaaammmmeeee]]]]
+ If _d_i_r_e_c_t_o_r_y _n_a_m_e is specified, the current working
+ directory on the local machine will be changed to the
+ directory specified. This operation will fail if for
+ any reason the specified directory is inaccessible.
+
+ If no directory name is specified, the name of the
+ current working directory on the local machine will be
+ reported.
+
+ lllliiiinnnnkkkk ssssoooouuuurrrrcccceeee ddddeeeessssttttiiiinnnnaaaattttiiiioooonnnn
+ This command depends on the server supporting the CIFS
+ UNIX extensions and will fail if the server does not.
+ The client requests that the server create a hard link
+ between the source and destination files. The source
+ file must not exist.
+
+ lllloooowwwweeeerrrrccccaaaasssseeee
+ Toggle lowercasing of filenames for the get and mget
+ commands.
+
+ When lowercasing is toggled ON, local filenames are
+ converted to lowercase when using the get and mget
+ commands. This is often useful when copying (say) MSDOS
+ files from a server, because lowercase filenames are
+ the norm on UNIX systems.
+
+
+
+ Page 11 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ llllssss <<<>>>
+ See the dir command above.
+
+ mmmmaaaasssskkkk <<<>>>
+ This command allows the user to set up a mask which
+ will be used during recursive operation of the mget and
+ mput commands.
+
+ The masks specified to the mget and mput commands act
+ as filters for directories rather than files when
+ recursion is toggled ON.
+
+ The mask specified with the mask command is necessary
+ to filter files within those directories. For example,
+ if the mask specified in an mget command is "source*"
+ and the mask specified with the mask command is "*.c"
+ and recursion is toggled ON, the mget command will
+ retrieve all files matching "*.c" in all directories
+ below and including all directories matching "source*"
+ in the current working directory.
+
+ Note that the value for mask defaults to blank
+ (equivalent to "*") and remains so until the mask
+ command is used to change it. It retains the most
+ recently specified value indefinitely. To avoid
+ unexpected results it would be wise to change the value
+ of mask back to "*" after using the mget or mput
+ commands.
+
+ mmmmdddd <<<>>>
+ See the mkdir command.
+
+ mmmmggggeeeetttt <<<>>>
+ Copy all files matching _m_a_s_k from the server to the
+ machine running the client.
+
+ Note that _m_a_s_k is interpreted differently during
+ recursive operation and non-recursive operation - refer
+ to the recurse and mask commands for more information.
+ Note that all transfers in ssssmmmmbbbbcccclllliiiieeeennnntttt are binary. See
+ also the lowercase command.
+
+ mmmmkkkkddddiiiirrrr <<<>>>
+ Create a new directory on the server (user access
+ privileges permitting) with the specified name.
+
+ mmmmppppuuuutttt <<<>>>
+ Copy all files matching _m_a_s_k in the current working
+ directory on the local machine to the current working
+ directory on the server.
+
+ Note that _m_a_s_k is interpreted differently during
+
+
+
+ Page 12 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ recursive operation and non-recursive operation - refer
+ to the recurse and mask commands for more information.
+ Note that all transfers in ssssmmmmbbbbcccclllliiiieeeennnntttt are binary.
+
+ pppprrrriiiinnnntttt <<<>>>
+ Print the specified file from the local machine through
+ a printable service on the server.
+
+ See also the printmode command.
+
+ pppprrrriiiinnnnttttmmmmooooddddeeee <<<>>>
+ Set the print mode to suit either binary data (such as
+ graphical information) or text. Subsequent print
+ commands will use the currently set print mode.
+
+ pppprrrroooommmmpppptttt
+ Toggle prompting for filenames during operation of the
+ mget and mput commands.
+
+ When toggled ON, the user will be prompted to confirm
+ the transfer of each file during these commands. When
+ toggled OFF, all specified files will be transferred
+ without prompting.
+
+ ppppuuuutttt <<<>>> [[[[rrrreeeemmmmooootttteeee ffffiiiilllleeee nnnnaaaammmmeeee]]]]
+ Copy the file called _l_o_c_a_l _f_i_l_e _n_a_m_e from the machine
+ running the client to the server. If specified, name
+ the remote copy _r_e_m_o_t_e _f_i_l_e _n_a_m_e. Note that all
+ transfers in ssssmmmmbbbbcccclllliiiieeeennnntttt are binary. See also the
+ lowercase command.
+
+ qqqquuuueeeeuuuueeee
+ Displays the print queue, showing the job id, name,
+ size and current status.
+
+ qqqquuuuiiiitttt See the exit command.
+
+ rrrrdddd <<<>>>
+ See the rmdir command.
+
+ rrrreeeeccccuuuurrrrsssseeee
+ Toggle directory recursion for the commands mget and
+ mput.
+
+ When toggled ON, these commands will process all
+ directories in the source directory (i.e., the
+ directory they are copying from ) and will recurse into
+ any that match the mask specified to the command. Only
+ files that match the mask specified using the mask
+ command will be retrieved. See also the mask command.
+
+ When recursion is toggled OFF, only files from the
+
+
+
+ Page 13 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ current working directory on the source machine that
+ match the mask specified to the mget or mput commands
+ will be copied, and any mask specified using the mask
+ command will be ignored.
+
+ rrrrmmmm <<<>>>
+ Remove all files matching _m_a_s_k from the current working
+ directory on the server.
+
+ rrrrmmmmddddiiiirrrr <<<>>>
+ Remove the specified directory (user access privileges
+ permitting) from the server.
+
+ sssseeeettttmmmmooooddddeeee <<<>>> <<<>>>
+ A version of the DOS attrib command to set file
+ permissions. For example:
+
+ sssseeeettttmmmmooooddddeeee mmmmyyyyffffiiiilllleeee ++++rrrr
+
+ would make myfile read only.
+
+ ssssyyyymmmmlllliiiinnnnkkkk ssssoooouuuurrrrcccceeee ddddeeeessssttttiiiinnnnaaaattttiiiioooonnnn
+ This command depends on the server supporting the CIFS
+ UNIX extensions and will fail if the server does not.
+ The client requests that the server create a symbolic
+ hard link between the source and destination files. The
+ source file must not exist. Note that the server will
+ not create a link to any path that lies outside the
+ currently connected share. This is enforced by the
+ Samba server.
+
+ ttttaaaarrrr <<<>>>[[[[IIIIXXXXbbbbggggNNNNaaaa]]]]
+ Performs a tar operation - see the -_T command line
+ option above. Behavior may be affected by the tarmode
+ command (see below). Using g (incremental) and N
+ (newer) will affect tarmode settings. Note that using
+ the "-" option with tar x may not work - use the
+ command line option instead.
+
+ bbbblllloooocccckkkkssssiiiizzzzeeee <<<>>>
+ Blocksize. Must be followed by a valid (greater than
+ zero) blocksize. Causes tar file to be written out in
+ _b_l_o_c_k_s_i_z_e*TBLOCK (usually 512 byte) blocks.
+
+ ttttaaaarrrrmmmmooooddddeeee <<<>>>
+ Changes tar's behavior with regard to archive bits. In
+ full mode, tar will back up everything regardless of
+ the archive bit setting (this is the default mode). In
+ incremental mode, tar will only back up files with the
+ archive bit set. In reset mode, tar will reset the
+ archive bit on all files it backs up (implies
+ read/write share).
+
+
+
+ Page 14 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ NNNNOOOOTTTTEEEESSSS
+ Some servers are fussy about the case of supplied usernames,
+ passwords, share names (AKA service names) and machine
+ names. If you fail to connect try giving all parameters in
+ uppercase.
+
+ It is often necessary to use the -n option when connecting
+ to some types of servers. For example OS/2 LanManager
+ insists on a valid NetBIOS name being used, so you need to
+ supply a valid name that would be known to the server.
+
+ smbclient supports long file names where the server supports
+ the LANMAN2 protocol or above.
+
+ EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT VVVVAAAARRRRIIIIAAAABBBBLLLLEEEESSSS
+ The variable UUUUSSSSEEEERRRR may contain the username of the person
+ using the client. This information is used only if the
+ protocol level is high enough to support session-level
+ passwords.
+
+ The variable PPPPAAAASSSSSSSSWWWWDDDD may contain the password of the person
+ using the client. This information is used only if the
+ protocol level is high enough to support session-level
+ passwords.
+
+ The variable LLLLIIIIBBBBSSSSMMMMBBBB____PPPPRRRROOOOGGGG may contain the path, executed with
+ system(), which the client should connect to instead of
+ connecting to a server. This functionality is primarily
+ intended as a development aid, and works best when using a
+ LMHOSTS file
+
+ IIIINNNNSSSSTTTTAAAALLLLLLLLAAAATTTTIIIIOOOONNNN
+ The location of the client program is a matter for
+ individual system administrators. The following are thus
+ suggestions only.
+
+ It is recommended that the smbclient software be installed
+ in the /_u_s_r/_l_o_c_a_l/_s_a_m_b_a/_b_i_n/ or /_u_s_r/_s_a_m_b_a/_b_i_n/ directory,
+ this directory readable by all, writeable only by root. The
+ client program itself should be executable by all. The
+ client should NNNNOOOOTTTT be setuid or setgid!
+
+ The client log files should be put in a directory readable
+ and writeable only by the user.
+
+ To test the client, you will need to know the name of a
+ running SMB/CIFS server. It is possible to run ssssmmmmbbbbdddd((((8888)))) as an
+ ordinary user - running that server as a daemon on a user-
+ accessible port (typically any port number over 1024) would
+ provide a suitable test server.
+
+ DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
+
+
+
+ PPPPaaaaggggeeee 11115555 ((((pppprrrriiiinnnntttteeeedddd 1111////7777////111100003333))))
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ Most diagnostics issued by the client are logged in a
+ specified log file. The log file name is specified at
+ compile time, but may be overridden on the command line.
+
+ The number and nature of diagnostics available depends on
+ the debug level used by the client. If you have problems,
+ set the debug level to 3 and peruse the log files.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 16 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/smbcontrol.1 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/smbcontrol.1
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/smbcontrol.1 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/smbcontrol.1 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,198 @@
+
+
+
+ SSSSMMMMBBBBCCCCOOOONNNNTTTTRRRROOOOLLLL((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCOOOONNNNTTTTRRRROOOOLLLL((((1111))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ smbcontrol - send messages to smbd, nmbd or winbindd
+ processes
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ ssssmmmmbbbbccccoooonnnnttttrrrroooollll [ ----dddd <<<>>> ] [ ----ssss <<<>>> ]
+ ----iiii
+
+ ssssmmmmbbbbccccoooonnnnttttrrrroooollll [ ----dddd <<<>>> ] [ ----ssss <<<>>> ]
+ ddddeeeessssttttiiiinnnnaaaattttiiiioooonnnn mmmmeeeessssssssaaaaggggeeee----ttttyyyyppppeeee [ ppppaaaarrrraaaammmmeeeetttteeeerrrr ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This tool is part of the Samba suite.
+
+ ssssmmmmbbbbccccoooonnnnttttrrrroooollll is a very small program, which sends messages to
+ an smbd(8) an nmbd(8) or a winbindd(8) daemon running on the
+ system.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ ----dddd <<<>>>
+ debuglevel is an integer from 0 to 10.
+
+ ----ssss <<<>>>
+ This parameter specifies the pathname to the Samba
+ configuration file, smb.conf(5) This file controls all
+ aspects of the Samba setup on the machine.
+
+ ----iiii Run interactively. Individual commands of the form
+ destination message-type parameters can be entered on
+ STDIN. An empty command line or a "q" will quit the
+ program.
+
+ ddddeeeessssttttiiiinnnnaaaattttiiiioooonnnn
+ One of _n_m_b_d _s_m_b_d or a process ID.
+
+ The _s_m_b_d destination causes the message to "broadcast"
+ to all smbd daemons.
+
+ The _n_m_b_d destination causes the message to be sent to
+ the nmbd daemon specified in the _n_m_b_d._p_i_d file.
+
+ If a single process ID is given, the message is sent to
+ only that process.
+
+ mmmmeeeessssssssaaaaggggeeee----ttttyyyyppppeeee
+ One of: close-share, debug, force-election, ping ,
+ profile, debuglevel, profilelevel, or printer-notify.
+
+ The close-share message-type sends a message to smbd
+ which will then close the client connections to the
+ named share. Note that this doesn't affect client
+ connections to any other shares. This message-type
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCOOOONNNNTTTTRRRROOOOLLLL((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCOOOONNNNTTTTRRRROOOOLLLL((((1111))))
+
+
+
+ takes an argument of the share name for which client
+ connections will be closed, or the "*" character which
+ will close all currently open shares. This may be
+ useful if you made changes to the access controls on
+ the share. This message can only be sent to smbd.
+
+ The debug message-type allows the debug level to be set
+ to the value specified by the parameter. This can be
+ sent to any of the destinations.
+
+ The force-election message-type can only be sent to the
+ nmbd destination. This message causes the nnnnmmmmbbbbdddd daemon
+ to force a new browse master election.
+
+ The ping message-type sends the number of "ping"
+ messages specified by the parameter and waits for the
+ same number of reply "pong" messages. This can be sent
+ to any of the destinations.
+
+ The profile message-type sends a message to an smbd to
+ change the profile settings based on the parameter. The
+ parameter can be "on" to turn on profile stats
+ collection, "off" to turn off profile stats collection,
+ "count" to enable only collection of count stats (time
+ stats are disabled), and "flush" to zero the current
+ profile stats. This can be sent to any smbd or nmbd
+ destinations.
+
+ The debuglevel message-type sends a "request debug
+ level" message. The current debug level setting is
+ returned by a "debuglevel" message. This can be sent to
+ any of the destinations.
+
+ The profilelevel message-type sends a "request profile
+ level" message. The current profile level setting is
+ returned by a "profilelevel" message. This can be sent
+ to any smbd or nmbd destinations.
+
+ The printer-notify message-type sends a message to smbd
+ which in turn sends a printer notify message to any
+ Windows NT clients connected to a printer. This
+ message-type takes an argument of the printer name to
+ send notify messages to. This message can only be sent
+ to smbd.
+
+ ppppaaaarrrraaaammmmeeeetttteeeerrrrssss
+ any parameters required for the message-type
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+
+
+
+ PPPPaaaaggggeeee 2222 ((((pppprrrriiiinnnntttteeeedddd 1111////7777////111100003333))))
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCOOOONNNNTTTTRRRROOOOLLLL((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCOOOONNNNTTTTRRRROOOOLLLL((((1111))))
+
+
+
+ nnnnmmmmbbbbdddd((((8888)))) and ssssmmmmbbbbdddd((((8888))))
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 3 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/smbsh.1 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/smbsh.1
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/smbsh.1 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/smbsh.1 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,198 @@
+
+
+
+ SSSSMMMMBBBBSSSSHHHH((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBSSSSHHHH((((1111))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ smbsh - Allows access to Windows NT filesystem using UNIX
+ commands
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ ssssmmmmbbbbsssshhhh [ ----WWWW wwwwoooorrrrkkkkggggrrrroooouuuupppp ] [ ----UUUU uuuusssseeeerrrrnnnnaaaammmmeeee ] [ ----PPPP pppprrrreeeeffffiiiixxxx ] [ ----RRRR
+ <<<>>> ] [ ----dddd <<<>>> ] [ ----llll llllooooggggffffiiiilllleeee ]
+ [ ----LLLL lllliiiibbbbddddiiiirrrr ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This tool is part of the Samba suite.
+
+ ssssmmmmbbbbsssshhhh allows you to access an NT filesystem using UNIX
+ commands such as llllssss, eeeeggggrrrreeeepppp, and rrrrccccpppp. You must use a shell
+ that is dynamically linked in order for ssssmmmmbbbbsssshhhh to work
+ correctly.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ ----WWWW WWWWOOOORRRRKKKKGGGGRRRROOOOUUUUPPPP
+ Override the default workgroup specified in the
+ workgroup parameter of the _s_m_b._c_o_n_f file for this
+ session. This may be needed to connect to some servers.
+
+ ----UUUU uuuusssseeeerrrrnnnnaaaammmmeeee[[[[%%%%ppppaaaassssssss]]]]
+ Sets the SMB username or username and password. If
+ this option is not specified, the user will be prompted
+ for both the username and the password. If %pass is not
+ specified, the user will be prompted for the password.
+
+ ----PPPP pppprrrreeeeffffiiiixxxx
+ This option allows the user to set the directory prefix
+ for SMB access. The default value if this option is not
+ specified is ssssmmmmbbbb.
+
+ ----RRRR <<<>>>
+ This option is used to determine what naming services
+ and in what order to resolve host names to IP
+ addresses. The option takes a space-separated string of
+ different name resolution options.
+
+ The options are :"lmhosts", "host", "wins" and "bcast".
+ They cause names to be resolved as follows :
+
+ o+ lmhosts : Lookup an IP address in the Samba lmhosts
+ file. If the line in lmhosts has no name type
+ attached to the NetBIOS name (see the lmhosts(5) for
+ details) then any name type matches for lookup.
+
+ o+ host : Do a standard host name to IP address
+ resolution, using the system /_e_t_c/_h_o_s_t_s, NIS, or DNS
+ lookups. This method of name resolution is operating
+ system dependent, for instance on IRIX or Solaris
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBSSSSHHHH((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBSSSSHHHH((((1111))))
+
+
+
+ this may be controlled by the /_e_t_c/_n_s_s_w_i_t_c_h._c_o_n_f
+ file). Note that this method is only used if the
+ NetBIOS name type being queried is the 0x20 (server)
+ name type, otherwise it is ignored.
+
+ o+ wins : Query a name with the IP address listed in the
+ _w_i_n_s _s_e_r_v_e_r parameter. If no WINS server has been
+ specified this method will be ignored.
+
+ o+ bcast : Do a broadcast on each of the known local
+ interfaces listed in the _i_n_t_e_r_f_a_c_e_s parameter. This
+ is the least reliable of the name resolution methods
+ as it depends on the target host being on a locally
+ connected subnet.
+
+ If this parameter is not set then the name resolve order
+ defined in the _s_m_b._c_o_n_f file parameter (name resolve order)
+ will be used.
+
+ The default order is lmhosts, host, wins, bcast. Without
+ this parameter or any entry in the _n_a_m_e _r_e_s_o_l_v_e _o_r_d_e_r
+ parameter of the _s_m_b._c_o_n_f file, the name resolution methods
+ will be attempted in this order.
+
+ ----dddd <<<>>>
+ debug level is an integer from 0 to 10.
+
+ The default value if this parameter is not specified is
+ zero.
+
+ The higher this value, the more detail will be logged
+ about the activities of nnnnmmmmbbbbllllooooooookkkkuuuupppp. At level 0, only
+ critical errors and serious warnings will be logged.
+
+ ----llll llllooooggggffffiiiilllleeeennnnaaaammmmeeee
+ If specified causes all debug messages to be written to
+ the file specified by _l_o_g_f_i_l_e_n_a_m_e . If not specified
+ then all messages will be written to_s_t_d_e_r_r.
+
+ ----LLLL lllliiiibbbbddddiiiirrrr
+ This parameter specifies the location of the shared
+ libraries used by ssssmmmmbbbbsssshhhh. The default value is specified
+ at compile time.
+
+ EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS
+ To use the ssssmmmmbbbbsssshhhh command, execute ssssmmmmbbbbsssshhhh from the prompt and
+ enter the username and password that authenticates you to
+ the machine running the Windows NT operating system.
+
+ system% ssssmmmmbbbbsssshhhh
+ Username: uuuusssseeeerrrr
+ Password: XXXXXXXXXXXXXXXXXXXXXXXXXXXX
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBSSSSHHHH((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBSSSSHHHH((((1111))))
+
+
+
+
+
+
+ Any dynamically linked command you execute from this shell
+ will access the /_s_m_b directory using the smb protocol. For
+ example, the command llllssss ////ssssmmmmbbbb will show a list of workgroups.
+ The command llllssss ////ssssmmmmbbbb////MMMMYYYYGGGGRRRROOOOUUUUPPPP will show all the machines in
+ the workgroup MYGROUP. The command llllssss
+ ////ssssmmmmbbbb////MMMMYYYYGGGGRRRROOOOUUUUPPPP////<<<>>> will show the share names for
+ that machine. You could then, for example, use the ccccdddd
+ command to change directories, vvvviiii to edit files, and rrrrccccpppp to
+ copy files.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ BBBBUUUUGGGGSSSS
+ ssssmmmmbbbbsssshhhh works by intercepting the standard libc calls with the
+ dynamically loaded versions in _s_m_b_w_r_a_p_p_e_r._o. Not all calls
+ have been "wrapped", so some programs may not function
+ correctly under ssssmmmmbbbbsssshhhh .
+
+ Programs which are not dynamically linked cannot make use of
+ ssssmmmmbbbbsssshhhh's functionality. Most versions of UNIX have a ffffiiiilllleeee
+ command that will describe how a program was linked.
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ ssssmmmmbbbbdddd((((8888)))) smb.conf(5)
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 3 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/smbstatus.1 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/smbstatus.1
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/smbstatus.1 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/smbstatus.1 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,132 @@
+
+
+
+ SSSSMMMMBBBBSSSSTTTTAAAATTTTUUUUSSSS((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBSSSSTTTTAAAATTTTUUUUSSSS((((1111))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ smbstatus - report on current Samba connections
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ ssssmmmmbbbbssssttttaaaattttuuuussss [ ----PPPP ] [ ----bbbb ] [ ----dddd ] [ ----LLLL ] [ ----pppp ] [ ----SSSS ] [
+ ----ssss <<<>>> ] [ ----uuuu <<<>>> ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This tool is part of the Samba suite.
+
+ ssssmmmmbbbbssssttttaaaattttuuuussss is a very simple program to list the current Samba
+ connections.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ ----PPPP If samba has been compiled with the profiling option,
+ print only the contents of the profiling shared memory
+ area.
+
+ ----bbbb gives brief output.
+
+ ----dddd gives verbose output.
+
+ ----LLLL causes smbstatus to only list locks.
+
+ ----pppp print a list of ssssmmmmbbbbdddd((((8888)))) processes and exit. Useful for
+ scripting.
+
+ ----SSSS causes smbstatus to only list shares.
+
+ ----ssss <<<>>>
+ The default configuration file name is determined at
+ compile time. The file specified contains the
+ configuration details required by the server. See
+ _s_m_b._c_o_n_f(_5)
+ for more information.
+
+ ----uuuu <<<>>>
+ selects information relevant to _u_s_e_r_n_a_m_e only.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ ssssmmmmbbbbdddd((((8888)))) and smb.conf(5)
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBSSSSTTTTAAAATTTTUUUUSSSS((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBSSSSTTTTAAAATTTTUUUUSSSS((((1111))))
+
+
+
+ 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/smbtar.1 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/smbtar.1
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/smbtar.1 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/smbtar.1 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,132 @@
+
+
+
+ SSSSMMMMBBBBTTTTAAAARRRR((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBTTTTAAAARRRR((((1111))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ smbtar - shell script for backing up SMB/CIFS shares
+ directly to UNIX tape drives
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ ssssmmmmbbbbttttaaaarrrr ----ssss sssseeeerrrrvvvveeeerrrr [ ----pppp ppppaaaasssssssswwwwoooorrrrdddd ] [ ----xxxx sssseeeerrrrvvvviiiicccceeeessss ] [ ----XXXX ] [
+ ----dddd ddddiiiirrrreeeeccccttttoooorrrryyyy ] [ ----uuuu uuuusssseeeerrrr ] [ ----tttt ttttaaaappppeeee ] [ ----tttt ttttaaaappppeeee ] [ ----bbbb
+ bbbblllloooocccckkkkssssiiiizzzzeeee ] [ ----NNNN ffffiiiilllleeeennnnaaaammmmeeee ] [ ----iiii ] [ ----rrrr ] [ ----llll lllloooogggglllleeeevvvveeeellll
+ ] [ ----vvvv ] ffffiiiilllleeeennnnaaaammmmeeeessss
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This tool is part of the Samba suite.
+
+ ssssmmmmbbbbttttaaaarrrr is a very small shell script on top of ssssmmmmbbbbcccclllliiiieeeennnntttt((((1111))))
+ which dumps SMB shares directly to tape.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ ----ssss sssseeeerrrrvvvveeeerrrr
+ The SMB/CIFS server that the share resides upon.
+
+ ----xxxx sssseeeerrrrvvvviiiicccceeee
+ The share name on the server to connect to. The default
+ is "backup".
+
+ ----XXXX Exclude mode. Exclude filenames... from tar create or
+ restore.
+
+ ----dddd ddddiiiirrrreeeeccccttttoooorrrryyyy
+ Change to initial _d_i_r_e_c_t_o_r_y before restoring / backing
+ up files.
+
+ ----vvvv Verbose mode.
+
+ ----pppp ppppaaaasssssssswwwwoooorrrrdddd
+ The password to use to access a share. Default: none
+
+ ----uuuu uuuusssseeeerrrr
+ The user id to connect as. Default: UNIX login name.
+
+ ----tttt ttttaaaappppeeee
+ Tape device. May be regular file or tape device.
+ Default: $_T_A_P_E environmental variable; if not set, a
+ file called _t_a_r._o_u_t .
+
+ ----bbbb bbbblllloooocccckkkkssssiiiizzzzeeee
+ Blocking factor. Defaults to 20. See ttttaaaarrrr((((1111)))) for a
+ fuller explanation.
+
+ ----NNNN ffffiiiilllleeeennnnaaaammmmeeee
+ Backup only files newer than filename. Could be used
+ (for example) on a log file to implement incremental
+ backups.
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBTTTTAAAARRRR((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBTTTTAAAARRRR((((1111))))
+
+
+
+ ----iiii Incremental mode; tar files are only backed up if they
+ have the archive bit set. The archive bit is reset
+ after each file is read.
+
+ ----rrrr Restore. Files are restored to the share from the tar
+ file.
+
+ ----llll lllloooogggg lllleeeevvvveeeellll
+ Log (debug) level. Corresponds to the -_d flag of
+ ssssmmmmbbbbcccclllliiiieeeennnntttt((((1111)))) .
+
+ EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT VVVVAAAARRRRIIIIAAAABBBBLLLLEEEESSSS
+ The $_T_A_P_E variable specifies the default tape device to
+ write to. May be overridden with the -t option.
+
+ BBBBUUUUGGGGSSSS
+ The ssssmmmmbbbbttttaaaarrrr script has different options from ordinary tar
+ and tar called from smbclient.
+
+ CCCCAAAAVVVVEEEEAAAATTTTSSSS
+ Sites that are more careful about security may not like the
+ way the script handles PC passwords. Backup and restore work
+ on entire shares, should work on file lists. smbtar works
+ best with GNU tar and may not work well with other versions.
+
+ DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
+ See the DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS section for the ssssmmmmbbbbcccclllliiiieeeennnntttt((((1111))))
+ command.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ ssssmmmmbbbbdddd((((8888)))) ssssmmmmbbbbcccclllliiiieeeennnntttt((((1111)))) smb.conf(5)
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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.
+
+ Ricky Poulten wrote the
+ tar extension and this man page. The ssssmmmmbbbbttttaaaarrrr script was
+ heavily rewritten and improved by Martin Kraemer
+ . Many thanks to
+ everyone who suggested extensions, improvements, bug fixes,
+ etc. 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.
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/testparm.1 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/testparm.1
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/testparm.1 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/testparm.1 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,132 @@
+
+
+
+ TTTTEEEESSSSTTTTPPPPAAAARRRRMMMM((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) TTTTEEEESSSSTTTTPPPPAAAARRRRMMMM((((1111))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ testparm - check an smb.conf configuration file for
+ internal correctness
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ tttteeeessssttttppppaaaarrrrmmmm [ ----ssss ] [ ----hhhh ] [ ----xxxx ] [ ----LLLL <<<>>> ] ccccoooonnnnffffiiiigggg
+ ffffiiiilllleeeennnnaaaammmmeeee [ hhhhoooossssttttnnnnaaaammmmeeee hhhhoooossssttttIIIIPPPP ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This tool is part of the Samba suite.
+
+ tttteeeessssttttppppaaaarrrrmmmm is a very simple test program to check an ssssmmmmbbbbdddd
+ configuration file for internal correctness. If this program
+ reports no problems, you can use the configuration file with
+ confidence that ssssmmmmbbbbdddd will successfully load the
+ configuration file.
+
+ Note that this is NNNNOOOOTTTT a guarantee that the services
+ specified in the configuration file will be available or
+ will operate as expected.
+
+ If the optional host name and host IP address are specified
+ on the command line, this test program will run through the
+ service entries reporting whether the specified host has
+ access to each service.
+
+ If tttteeeessssttttppppaaaarrrrmmmm finds an error in the _s_m_b._c_o_n_f file it returns
+ an exit code of 1 to the calling program, else it returns an
+ exit code of 0. This allows shell scripts to test the output
+ from tttteeeessssttttppppaaaarrrrmmmm.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ ----ssss Without this option, tttteeeessssttttppppaaaarrrrmmmm will prompt for a
+ carriage return after printing the service names and
+ before dumping the service definitions.
+
+ ----hhhh Print usage message
+
+ ----xxxx Print only parameters that have non-default values
+
+ ----LLLL sssseeeerrrrvvvveeeerrrrnnnnaaaammmmeeee
+ Sets the value of the %L macro to _s_e_r_v_e_r_n_a_m_e. This is
+ useful for testing include files specified with the %L
+ macro.
+
+ ccccoooonnnnffffiiiiggggffffiiiilllleeeennnnaaaammmmeeee
+ This is the name of the configuration file to check. If
+ this parameter is not present then the default _s_m_b._c_o_n_f
+ file will be checked.
+
+ hhhhoooossssttttnnnnaaaammmmeeee
+ If this parameter and the following are specified, then
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ TTTTEEEESSSSTTTTPPPPAAAARRRRMMMM((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) TTTTEEEESSSSTTTTPPPPAAAARRRRMMMM((((1111))))
+
+
+
+ tttteeeessssttttppppaaaarrrrmmmm will examine the _h_o_s_t_s _a_l_l_o_w and _h_o_s_t_s _d_e_n_y
+ parameters in the _s_m_b._c_o_n_f file to determine if the
+ hostname with this IP address would be allowed access
+ to the ssssmmmmbbbbdddd server. If this parameter is supplied, the
+ hostIP parameter must also be supplied.
+
+ hhhhoooossssttttIIIIPPPP
+ This is the IP address of the host specified in the
+ previous parameter. This address must be supplied if
+ the hostname parameter is supplied.
+
+ FFFFIIIILLLLEEEESSSS
+ _s_m_b._c_o_n_f
+ This is usually the name of the configuration file used
+ by ssssmmmmbbbbdddd.
+
+ DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
+ The program will issue a message saying whether the
+ configuration file loaded OK or not. This message may be
+ preceded by errors and warnings if the file did not load. If
+ the file was loaded OK, the program then dumps all known
+ service details to stdout.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ _s_m_b._c_o_n_f(_5) ssssmmmmbbbbdddd((((8888))))
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/testprns.1 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/testprns.1
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/testprns.1 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/testprns.1 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,132 @@
+
+
+
+ TTTTEEEESSSSTTTTPPPPRRRRNNNNSSSS((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) TTTTEEEESSSSTTTTPPPPRRRRNNNNSSSS((((1111))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ testprns - check printer name for validity with smbd
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ tttteeeessssttttpppprrrrnnnnssss pppprrrriiiinnnntttteeeerrrrnnnnaaaammmmeeee [ pppprrrriiiinnnnttttccccaaaappppnnnnaaaammmmeeee ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This tool is part of the Samba suite.
+
+ tttteeeessssttttpppprrrrnnnnssss is a very simple test program to determine whether
+ a given printer name is valid for use in a service to be
+ provided by ssssmmmmbbbbdddd((((8888))))
+
+ "Valid" in this context means "can be found in the printcap
+ specified". This program is very stupid - so stupid in fact
+ that it would be wisest to always specify the printcap file
+ to use.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ pppprrrriiiinnnntttteeeerrrrnnnnaaaammmmeeee
+ The printer name to validate.
+
+ Printer names are taken from the first field in each
+ record in the printcap file, single printer names and
+ sets of aliases separated by vertical bars ("|") are
+ recognized. Note that no validation or checking of the
+ printcap syntax is done beyond that required to extract
+ the printer name. It may be that the print spooling
+ system is more forgiving or less forgiving than
+ tttteeeessssttttpppprrrrnnnnssss. However, if tttteeeessssttttpppprrrrnnnnssss finds the printer then
+ ssssmmmmbbbbdddd should do so as well.
+
+ pppprrrriiiinnnnttttccccaaaappppnnnnaaaammmmeeee
+ This is the name of the printcap file within which to
+ search for the given printer name.
+
+ If no printcap name is specified tttteeeessssttttpppprrrrnnnnssss will attempt
+ to scan the printcap file name specified at compile
+ time.
+
+ FFFFIIIILLLLEEEESSSS
+ /_e_t_c/_p_r_i_n_t_c_a_p
+ This is usually the default printcap file to scan. See
+ _p_r_i_n_t_c_a_p (_5).
+
+ DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
+ If a printer is found to be valid, the message "Printer name
+ is valid" will be displayed.
+
+ If a printer is found to be invalid, the message "Printer
+ name is not valid" will be displayed.
+
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ TTTTEEEESSSSTTTTPPPPRRRRNNNNSSSS((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) TTTTEEEESSSSTTTTPPPPRRRRNNNNSSSS((((1111))))
+
+
+
+ All messages that would normally be logged during operation
+ of the Samba daemons are logged by this program to the file
+ _t_e_s_t._l_o_g in the current directory. The program runs at
+ debuglevel 3, so quite extensive logging information is
+ written. The log should be checked carefully for errors and
+ warnings.
+
+ Other messages are self-explanatory.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ _p_r_i_n_t_c_a_p(_5), ssssmmmmbbbbdddd((((8888)))) ssssmmmmbbbbcccclllliiiieeeennnntttt((((1111))))
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/wbinfo.1 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/wbinfo.1
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.1/wbinfo.1 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.1/wbinfo.1 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,198 @@
+
+
+
+ WWWWBBBBIIIINNNNFFFFOOOO((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) WWWWBBBBIIIINNNNFFFFOOOO((((1111))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ wbinfo - Query information from winbind daemon
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ wwwwbbbbiiiinnnnffffoooo [ ----uuuu ] [ ----gggg ] [ ----hhhh nnnnaaaammmmeeee ] [ ----iiii iiiipppp ] [ ----nnnn nnnnaaaammmmeeee ]
+ [ ----ssss ssssiiiidddd ] [ ----UUUU uuuuiiiidddd ] [ ----GGGG ggggiiiidddd ] [ ----SSSS ssssiiiidddd ] [ ----YYYY ssssiiiidddd ]
+ [ ----tttt ] [ ----mmmm ] [ ----rrrr uuuusssseeeerrrr ] [ ----aaaa uuuusssseeeerrrr%%%%ppppaaaasssssssswwwwoooorrrrdddd ] [ ----AAAA
+ uuuusssseeeerrrr%%%%ppppaaaasssssssswwwwoooorrrrdddd ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This tool is part of the Samba suite.
+
+ The wwwwbbbbiiiinnnnffffoooo program queries and returns information created
+ and used by the wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888)))) daemon.
+
+ The wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888)))) daemon must be configured and running for
+ the wwwwbbbbiiiinnnnffffoooo program to be able to return information.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ ----uuuu This option will list all users available in the
+ Windows NT domain for which the wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888)))) daemon is
+ operating in. Users in all trusted domains will also be
+ listed. Note that this operation does not assign user
+ ids to any users that have not already been seen by
+ wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888)))).
+
+ ----gggg This option will list all groups available in the
+ Windows NT domain for which the wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888)))) daemon is
+ operating in. Groups in all trusted domains will also
+ be listed. Note that this operation does not assign
+ group ids to any groups that have not already been seen
+ by wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888)))).
+
+ ----hhhh nnnnaaaammmmeeee
+ The -_h option queries wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888)))) to query the WINS
+ server for the IP address associated with the NetBIOS
+ name specified by the _n_a_m_e parameter.
+
+ ----iiii iiiipppp
+ The -_i option queries wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888)))) to send a node status
+ request to get the NetBIOS name associated with the IP
+ address specified by the _i_p parameter.
+
+ ----nnnn nnnnaaaammmmeeee
+ The -_n option queries wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888)))) for the SID
+ associated with the name specified. Domain names can be
+ specified before the user name by using the winbind
+ separator character. For example CWDOM1/Administrator
+ refers to the Administrator user in the domain CWDOM1.
+ If no domain is specified then the domain used is the
+ one specified in the _s_m_b._c_o_n_f _w_o_r_k_g_r_o_u_p parameter.
+
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ WWWWBBBBIIIINNNNFFFFOOOO((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) WWWWBBBBIIIINNNNFFFFOOOO((((1111))))
+
+
+
+ ----ssss ssssiiiidddd
+ Use -_s to resolve a SID to a name. This is the inverse
+ of the -_n option above. SIDs must be specified as ASCII
+ strings in the traditional Microsoft format. For
+ example, S-1-5-21-1455342024-3071081365-2475485837-500.
+
+ ----UUUU uuuuiiiidddd
+ Try to convert a UNIX user id to a Windows NT SID. If
+ the uid specified does not refer to one within the
+ winbind uid range then the operation will fail.
+
+ ----GGGG ggggiiiidddd
+ Try to convert a UNIX group id to a Windows NT SID. If
+ the gid specified does not refer to one within the
+ winbind gid range then the operation will fail.
+
+ ----SSSS ssssiiiidddd
+ Convert a SID to a UNIX user id. If the SID does not
+ correspond to a UNIX user mapped by wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888)))) then
+ the operation will fail.
+
+ ----YYYY ssssiiiidddd
+ Convert a SID to a UNIX group id. If the SID does not
+ correspond to a UNIX group mapped by wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888)))) then
+ the operation will fail.
+
+ ----tttt Verify that the workstation trust account created when
+ the Samba server is added to the Windows NT domain is
+ working.
+
+ ----mmmm Produce a list of domains trusted by the Windows NT
+ server wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888)))) contacts when resolving names. This
+ list does not include the Windows NT domain the server
+ is a Primary Domain Controller for.
+
+ ----rrrr uuuusssseeeerrrrnnnnaaaammmmeeee
+ Try to obtain the list of UNIX group ids to which the
+ user belongs. This only works for users defined on a
+ Domain Controller.
+
+ ----aaaa uuuusssseeeerrrrnnnnaaaammmmeeee%%%%ppppaaaasssssssswwwwoooorrrrdddd
+ Attempt to authenticate a user via winbindd. This
+ checks both authenticaion methods and reports its
+ results.
+
+ ----AAAA uuuusssseeeerrrrnnnnaaaammmmeeee%%%%ppppaaaasssssssswwwwoooorrrrdddd
+ Store username and password used by winbindd during
+ session setup to a domain controller. This enables
+ winbindd to operate in a Windows 2000 domain with
+ Restrict Anonymous turned on (a.k.a. Permissions
+ compatiable with Windows 2000 servers only).
+
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
+
+
+
+ WWWWBBBBIIIINNNNFFFFOOOO((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) WWWWBBBBIIIINNNNFFFFOOOO((((1111))))
+
+
+
+ EEEEXXXXIIIITTTT SSSSTTTTAAAATTTTUUUUSSSS
+ The wbinfo program returns 0 if the operation succeeded, or
+ 1 if the operation failed. If the wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888)))) daemon is not
+ working wwwwbbbbiiiinnnnffffoooo will always return failure.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888))))
+
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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.
+
+ wwwwbbbbiiiinnnnffffoooo and wwwwiiiinnnnbbbbiiiinnnndddddddd were written by Tim Potter.
+
+ The conversion to DocBook for Samba 2.2 was done by Gerald
+ Carter
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 3 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.5/lmhosts.5 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.5/lmhosts.5
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.5/lmhosts.5 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.5/lmhosts.5 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,132 @@
+
+
+
+ LLLLMMMMHHHHOOOOSSSSTTTTSSSS((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) LLLLMMMMHHHHOOOOSSSSTTTTSSSS((((5555))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ lmhosts - The Samba NetBIOS hosts file
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ _l_m_h_o_s_t_s is the Samba NetBIOS name to IP address mapping
+ file.
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This file is part of the Samba suite.
+
+ _l_m_h_o_s_t_s is the SSSSaaaammmmbbbbaaaa NetBIOS name to IP address mapping
+ file. It is very similar to the /_e_t_c/_h_o_s_t_s file format,
+ except that the hostname component must correspond to the
+ NetBIOS naming format.
+
+ FFFFIIIILLLLEEEE FFFFOOOORRRRMMMMAAAATTTT
+ It is an ASCII file containing one line for NetBIOS name.
+ The two fields on each line are separated from each other by
+ white space. Any entry beginning with '#' is ignored. Each
+ line in the lmhosts file contains the following information
+ :
+
+ o+ IP Address - in dotted decimal format.
+
+ o+ NetBIOS Name - This name format is a maximum fifteen
+ character host name, with an optional trailing '#'
+ character followed by the NetBIOS name type as two
+ hexadecimal digits.
+
+ If the trailing '#' is omitted then the given IP address
+ will be returned for all names that match the given name,
+ whatever the NetBIOS name type in the lookup.
+
+ An example follows :
+
+ #
+ # Sample Samba lmhosts file.
+ #
+ 192.9.200.1 TESTPC
+ 192.9.200.20 NTSERVER#20
+ 192.9.200.21 SAMBASERVER
+
+
+
+ Contains three IP to NetBIOS name mappings. The first and
+ third will be returned for any queries for the names
+ "TESTPC" and "SAMBASERVER" respectively, whatever the type
+ component of the NetBIOS name requested.
+
+ The second mapping will be returned only when the "0x20"
+ name type for a name "NTSERVER" is queried. Any other name
+ type will not be resolved.
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ LLLLMMMMHHHHOOOOSSSSTTTTSSSS((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) LLLLMMMMHHHHOOOOSSSSTTTTSSSS((((5555))))
+
+
+
+ The default location of the _l_m_h_o_s_t_s file is in the same
+ directory as the smb.conf(5)> file.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ ssssmmmmbbbbcccclllliiiieeeennnntttt((((1111))))
+ and ssssmmmmbbbbppppaaaasssssssswwwwdddd((((8888))))
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.5/smb.conf.5 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.5/smb.conf.5
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.5/smb.conf.5 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.5/smb.conf.5 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,9108 @@
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ smb.conf - The configuration file for the Samba suite
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ The _s_m_b._c_o_n_f file is a configuration file for the Samba
+ suite. _s_m_b._c_o_n_f contains runtime configuration information
+ for the Samba programs. The _s_m_b._c_o_n_f file is designed to be
+ configured and administered by the sssswwwwaaaatttt((((8888))))
+ program. The complete description of the file format and
+ possible parameters held within are here for reference
+ purposes.
+
+ FFFFIIIILLLLEEEE FFFFOOOORRRRMMMMAAAATTTT
+ The file consists of sections and parameters. A section
+ begins with the name of the section in square brackets and
+ continues until the next section begins. Sections contain
+ parameters of the form
+
+ _n_a_m_e = _v_a_l_u_e
+
+ The file is line-based - that is, each newline-terminated
+ line represents either a comment, a section name or a
+ parameter.
+
+ Section and parameter names are not case sensitive.
+
+ Only the first equals sign in a parameter is significant.
+ Whitespace before or after the first equals sign is
+ discarded. Leading, trailing and internal whitespace in
+ section and parameter names is irrelevant. Leading and
+ trailing whitespace in a parameter value is discarded.
+ Internal whitespace within a parameter value is retained
+ verbatim.
+
+ Any line beginning with a semicolon (';') or a hash ('#')
+ character is ignored, as are lines containing only
+ whitespace.
+
+ Any line ending in a '\' is continued on the next line in
+ the customary UNIX fashion.
+
+ The values following the equals sign in parameters are all
+ either a string (no quotes needed) or a boolean, which may
+ be given as yes/no, 0/1 or true/false. Case is not
+ significant in boolean values, but is preserved in string
+ values. Some items such as create modes are numeric.
+
+ SSSSEEEECCCCTTTTIIIIOOOONNNN DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNNSSSS
+ Each section in the configuration file (except for the
+ [global] section) describes a shared resource (known as a
+ "share"). The section name is the name of the shared
+ resource and the parameters within the section define the
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ shares attributes.
+
+ There are three special sections, [global], [homes] and
+ [printers], which are described under ssssppppeeeecccciiiiaaaallll sssseeeeccccttttiiiioooonnnnssss. The
+ following notes apply to ordinary section descriptions.
+
+ A share consists of a directory to which access is being
+ given plus a description of the access rights which are
+ granted to the user of the service. Some housekeeping
+ options are also specifiable.
+
+ Sections are either file share services (used by the client
+ as an extension of their native file systems) or printable
+ services (used by the client to access print services on the
+ host running the server).
+
+ Sections may be designated gggguuuueeeesssstttt services, in which case no
+ password is required to access them. A specified UNIX gggguuuueeeesssstttt
+ aaaaccccccccoooouuuunnnntttt is used to define access privileges in this case.
+
+ Sections other than guest services will require a password
+ to access them. The client provides the username. As older
+ clients only provide passwords and not usernames, you may
+ specify a list of usernames to check against the password
+ using the "user =" option in the share definition. For
+ modern clients such as Windows 95/98/ME/NT/2000, this should
+ not be necessary.
+
+ Note that the access rights granted by the server are masked
+ by the access rights granted to the specified or guest UNIX
+ user by the host system. The server does not grant more
+ access than the host system grants.
+
+ The following sample section defines a file space share. The
+ user has write access to the path /_h_o_m_e/_b_a_r. The share is
+ accessed via the share name "foo":
+
+ [foo]
+ path = /home/bar
+ read only = no
+
+
+
+
+ The following sample section defines a printable share. The
+ share is readonly, but printable. That is, the only write
+ access permitted is via calls to open, write to and close a
+ spool file. The gggguuuueeeesssstttt ooookkkk parameter means access will be
+ permitted as the default guest user (specified elsewhere):
+
+ [aprinter]
+ path = /usr/spool/public
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ read only = yes
+ printable = yes
+ guest ok = yes
+
+
+
+
+ SSSSPPPPEEEECCCCIIIIAAAALLLL SSSSEEEECCCCTTTTIIIIOOOONNNNSSSS
+ TTTTHHHHEEEE GGGGLLLLOOOOBBBBAAAALLLL SSSSEEEECCCCTTTTIIIIOOOONNNN
+ parameters in this section apply to the server as a whole,
+ or are defaults for sections which do not specifically
+ define certain items. See the notes under PARAMETERS for
+ more information.
+
+ TTTTHHHHEEEE HHHHOOOOMMMMEEEESSSS SSSSEEEECCCCTTTTIIIIOOOONNNN
+ If a section called homes is included in the configuration
+ file, services connecting clients to their home directories
+ can be created on the fly by the server.
+
+ When the connection request is made, the existing sections
+ are scanned. If a match is found, it is used. If no match is
+ found, the requested section name is treated as a user name
+ and looked up in the local password file. If the name exists
+ and the correct password has been given, a share is created
+ by cloning the [homes] section.
+
+ Some modifications are then made to the newly created share:
+
+ o+ The share name is changed from homes to the located
+ username.
+
+ o+ If no path was given, the path is set to the user's home
+ directory.
+
+ If you decide to use a ppppaaaatttthhhh ==== line in your [homes] section
+ then you may find it useful to use the %S macro. For example
+ :
+
+ ppppaaaatttthhhh ==== ////ddddaaaattttaaaa////ppppcccchhhhoooommmmeeee////%%%%SSSS
+
+ would be useful if you have different home directories for
+ your PCs than for UNIX access.
+
+ This is a fast and simple way to give a large number of
+ clients access to their home directories with a minimum of
+ fuss.
+
+ A similar process occurs if the requested section name is
+ "homes", except that the share name is not changed to that
+ of the requesting user. This method of using the [homes]
+ section works well if different users share a client PC.
+
+
+
+
+ Page 3 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ The [homes] section can specify all the parameters a normal
+ service section can specify, though some make more sense
+ than others. The following is a typical and suitable [homes]
+ section:
+
+ [homes]
+ read only = no
+
+
+
+
+ An important point is that if guest access is specified in
+ the [homes] section, all home directories will be visible to
+ all clients wwwwiiiitttthhhhoooouuuutttt aaaa ppppaaaasssssssswwwwoooorrrrdddd. In the very unlikely event
+ that this is actually desirable, it would be wise to also
+ specify rrrreeeeaaaadddd oooonnnnllllyyyy aaaacccccccceeeessssssss.
+
+ Note that the bbbbrrrroooowwwwsssseeeeaaaabbbblllleeee flag for auto home directories will
+ be inherited from the global browseable flag, not the
+ [homes] browseable flag. This is useful as it means setting
+ bbbbrrrroooowwwwsssseeeeaaaabbbblllleeee ==== nnnnoooo in the [homes] section will hide the [homes]
+ share but make any auto home directories visible.
+
+ TTTTHHHHEEEE PPPPRRRRIIIINNNNTTTTEEEERRRRSSSS SSSSEEEECCCCTTTTIIIIOOOONNNN
+ This section works like [homes], but for printers.
+
+ If a [printers] section occurs in the configuration file,
+ users are able to connect to any printer specified in the
+ local host's printcap file.
+
+ When a connection request is made, the existing sections are
+ scanned. If a match is found, it is used. If no match is
+ found, but a [homes] section exists, it is used as described
+ above. Otherwise, the requested section name is treated as a
+ printer name and the appropriate printcap file is scanned to
+ see if the requested section name is a valid printer share
+ name. If a match is found, a new printer share is created by
+ cloning the [printers] section.
+
+ A few modifications are then made to the newly created
+ share:
+
+ o+ The share name is set to the located printer name
+
+ o+ If no printer name was given, the printer name is set to
+ the located printer name
+
+ o+ If the share does not permit guest access and no username
+ was given, the username is set to the located printer
+ name.
+
+ Note that the [printers] service MUST be printable - if you
+
+
+
+ Page 4 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ specify otherwise, the server will refuse to load the
+ configuration file.
+
+ Typically the path specified would be that of a world-
+ writeable spool directory with the sticky bit set on it. A
+ typical [printers] entry would look like this:
+
+ [printers]
+ path = /usr/spool/public
+ guest ok = yes
+ printable = yes
+
+
+
+ All aliases given for a printer in the printcap file are
+ legitimate printer names as far as the server is concerned.
+ If your printing subsystem doesn't work like that, you will
+ have to set up a pseudo-printcap. This is a file consisting
+ of one or more lines like this:
+
+ alias|alias|alias|alias...
+
+
+
+
+ Each alias should be an acceptable printer name for your
+ printing subsystem. In the [global] section, specify the new
+ file as your printcap. The server will then only recognize
+ names found in your pseudo-printcap, which of course can
+ contain whatever aliases you like. The same technique could
+ be used simply to limit access to a subset of your local
+ printers.
+
+ An alias, by the way, is defined as any component of the
+ first entry of a printcap record. Records are separated by
+ newlines, components (if there are more than one) are
+ separated by vertical bar symbols ('|').
+
+ NOTE: On SYSV systems which use lpstat to determine what
+ printers are defined on the system you may be able to use
+ "printcap name = lpstat" to automatically obtain a list of
+ printers. See the "printcap name" option for more details.
+
+ PPPPAAAARRRRAAAAMMMMEEEETTTTEEEERRRRSSSS
+ parameters define the specific attributes of sections.
+
+ Some parameters are specific to the [global] section (e.g.,
+ sssseeeeccccuuuurrrriiiittttyyyy). Some parameters are usable in all sections (e.g.,
+ ccccrrrreeeeaaaatttteeee mmmmooooddddeeee). All others are permissible only in normal
+ sections. For the purposes of the following descriptions the
+ [homes] and [printers] sections will be considered normal.
+ The letter GGGG in parentheses indicates that a parameter is
+
+
+
+ Page 5 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ specific to the [global] section. The letter SSSS indicates
+ that a parameter can be specified in a service specific
+ section. Note that all SSSS parameters can also be specified in
+ the [global] section - in which case they will define the
+ default behavior for all services.
+
+ parameters are arranged here in alphabetical order - this
+ may not create best bedfellows, but at least you can find
+ them! Where there are synonyms, the preferred synonym is
+ described, others refer to the preferred synonym.
+
+ VVVVAAAARRRRIIIIAAAABBBBLLLLEEEE SSSSUUUUBBBBSSSSTTTTIIIITTTTUUUUTTTTIIIIOOOONNNNSSSS
+ Many of the strings that are settable in the config file can
+ take substitutions. For example the option "path = /tmp/%u"
+ would be interpreted as "path = /tmp/john" if the user
+ connected with the username john.
+
+ These substitutions are mostly noted in the descriptions
+ below, but there are some general substitutions which apply
+ whenever they might be relevant. These are:
+
+ %%%%SSSS the name of the current service, if any.
+
+ %%%%PPPP the root directory of the current service, if any.
+
+ %%%%uuuu user name of the current service, if any.
+
+ %%%%gggg primary group name of %u.
+
+ %%%%UUUU session user name (the user name that the client
+ wanted, not necessarily the same as the one they got).
+
+ %%%%GGGG primary group name of %U.
+
+ %%%%HHHH the home directory of the user given by %u.
+
+ %%%%vvvv the Samba version.
+
+ %%%%hhhh the Internet hostname that Samba is running on.
+
+ %%%%mmmm the NetBIOS name of the client machine (very useful).
+
+ %%%%LLLL the NetBIOS name of the server. This allows you to
+ change your config based on what the client calls you.
+ Your server can have a "dual personality".
+
+ Note that this paramater is not available when Samba
+ listens on port 445, as clients no longer send this
+ information
+
+ %%%%MMMM the Internet name of the client machine.
+
+
+
+
+ Page 6 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ %%%%NNNN the name of your NIS home directory server. This is
+ obtained from your NIS auto.map entry. If you have not
+ compiled Samba with the --------wwwwiiiitttthhhh----aaaauuuuttttoooommmmoooouuuunnnntttt option then
+ this value will be the same as %L.
+
+ %%%%pppp the path of the service's home directory, obtained from
+ your NIS auto.map entry. The NIS auto.map entry is
+ split up as "%N:%p".
+
+ %%%%RRRR the selected protocol level after protocol negotiation.
+ It can be one of CORE, COREPLUS, LANMAN1, LANMAN2 or
+ NT1.
+
+ %%%%dddd The process id of the current server process.
+
+ %%%%aaaa the architecture of the remote machine. Only some are
+ recognized, and those may not be 100% reliable. It
+ currently recognizes Samba, WfWg, Win95, WinNT and
+ Win2k. Anything else will be known as "UNKNOWN". If it
+ gets it wrong then sending a level 3 log to
+ samba@samba.org
+ should allow it to be
+ fixed.
+
+ %%%%IIII The IP address of the client machine.
+
+ %%%%TTTT the current date and time.
+
+ %%%%$$$$((((_e_n_v_v_a_r))))
+ The value of the environment variable _e_n_v_a_r.
+
+ There are some quite creative things that can be done with
+ these substitutions and other smb.conf options.
+
+ NNNNAAAAMMMMEEEE MMMMAAAANNNNGGGGLLLLIIIINNNNGGGG
+ Samba supports "name mangling" so that DOS and Windows
+ clients can use files that don't conform to the 8.3 format.
+ It can also be set to adjust the case of 8.3 format
+ filenames.
+
+ There are several options that control the way mangling is
+ performed, and they are grouped here rather than listed
+ separately. For the defaults look at the output of the
+ testparm program.
+
+ All of these options can be set separately for each service
+ (or globally, of course).
+
+ The options are:
+
+ mmmmaaaannnngggglllliiiinnnngggg mmmmeeeetttthhhhoooodddd
+ controls the algorithm used for the generating the
+
+
+
+ Page 7 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ mangled names. Can take two different values, "hash"
+ and "hash2". "hash" is the default and is the algorithm
+ that has been used in Samba for many years. "hash2" is
+ a newer and considered a better algorithm (generates
+ less collisions) in the names. However, many Win32
+ applications store the mangled names and so changing to
+ the new algorithm must not be done lightly as these
+ applications may break unless reinstalled. New
+ installations of Samba may set the default to hash2.
+ Default hhhhaaaasssshhhh.
+
+ mmmmaaaannnngggglllleeee ccccaaaasssseeee ==== yyyyeeeessss////nnnnoooo
+ controls if names that have characters that aren't of
+ the "default" case are mangled. For example, if this is
+ yes then a name like "Mail" would be mangled. Default
+ nnnnoooo.
+
+ ccccaaaasssseeee sssseeeennnnssssiiiittttiiiivvvveeee ==== yyyyeeeessss////nnnnoooo
+ controls whether filenames are case sensitive. If they
+ aren't then Samba must do a filename search and match
+ on passed names. Default nnnnoooo.
+
+ ddddeeeeffffaaaauuuulllltttt ccccaaaasssseeee ==== uuuuppppppppeeeerrrr////lllloooowwwweeeerrrr
+ controls what the default case is for new filenames.
+ Default lllloooowwwweeeerrrr.
+
+ pppprrrreeeesssseeeerrrrvvvveeee ccccaaaasssseeee ==== yyyyeeeessss////nnnnoooo
+ controls if new files are created with the case that
+ the client passes, or if they are forced to be the
+ "default" case. Default yyyyeeeessss.
+
+ sssshhhhoooorrrrtttt pppprrrreeeesssseeeerrrrvvvveeee ccccaaaasssseeee ==== yyyyeeeessss////nnnnoooo
+ controls if new files which conform to 8.3 syntax, that
+ is all in upper case and of suitable length, are
+ created upper case, or if they are forced to be the
+ "default" case. This option can be use with "preserve
+ case = yes" to permit long filenames to retain their
+ case, while short names are lowercased. Default yyyyeeeessss.
+
+ By default, Samba 2.2 has the same semantics as a Windows NT
+ server, in that it is case insensitive but case preserving.
+
+ NNNNOOOOTTTTEEEE AAAABBBBOOOOUUUUTTTT UUUUSSSSEEEERRRRNNNNAAAAMMMMEEEE////PPPPAAAASSSSSSSSWWWWOOOORRRRDDDD VVVVAAAALLLLIIIIDDDDAAAATTTTIIIIOOOONNNN
+ There are a number of ways in which a user can connect to a
+ service. The server uses the following steps in determining
+ if it will allow a connection to a specified service. If all
+ the steps fail, then the connection request is rejected.
+ However, if one of the steps succeeds, then the following
+ steps are not checked.
+
+ If the service is marked "guest only = yes" and the server
+ is running with share-level security ("security = share")
+
+
+
+ Page 8 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ then steps 1 to 5 are skipped.
+
+ 1. If the client has passed a username/password pair and
+ that username/password pair is validated by the UNIX
+ system's password programs then the connection is made
+ as that username. Note that this includes the
+ \\server\service%_u_s_e_r_n_a_m_e method of passing a username.
+
+ 2. If the client has previously registered a username with
+ the system and now supplies a correct password for that
+ username then the connection is allowed.
+
+ 3. The client's NetBIOS name and any previously used user
+ names are checked against the supplied password, if
+ they match then the connection is allowed as the
+ corresponding user.
+
+ 4. If the client has previously validated a
+ username/password pair with the server and the client
+ has passed the validation token then that username is
+ used.
+
+ 5. If a "user = " field is given in the _s_m_b._c_o_n_f file for
+ the service and the client has supplied a password, and
+ that password matches (according to the UNIX system's
+ password checking) with one of the usernames from the
+ "user =" field then the connection is made as the
+ username in the "user =" line. If one of the username
+ in the "user =" list begins with a '@' then that name
+ expands to a list of names in the group of the same
+ name.
+
+ 6. If the service is a guest service then a connection is
+ made as the username given in the "guest account =" for
+ the service, irrespective of the supplied password.
+
+ CCCCOOOOMMMMPPPPLLLLEEEETTTTEEEE LLLLIIIISSSSTTTT OOOOFFFF GGGGLLLLOOOOBBBBAAAALLLL PPPPAAAARRRRAAAAMMMMEEEETTTTEEEERRRRSSSS
+ Here is a list of all global parameters. See the section of
+ each parameter for details. Note that some are synonyms.
+
+ o+ _a_d_d _p_r_i_n_t_e_r _c_o_m_m_a_n_d
+
+ o+ _a_d_d _s_h_a_r_e _c_o_m_m_a_n_d
+
+ o+ _a_d_d _u_s_e_r _s_c_r_i_p_t
+
+ o+ _a_l_l_o_w _t_r_u_s_t_e_d _d_o_m_a_i_n_s
+
+ o+ _a_n_n_o_u_n_c_e _a_s
+
+ o+ _a_n_n_o_u_n_c_e _v_e_r_s_i_o_n
+
+
+
+
+ Page 9 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ _a_u_t_o _s_e_r_v_i_c_e_s
+
+ o+ _b_i_n_d _i_n_t_e_r_f_a_c_e_s _o_n_l_y
+
+ o+ _b_r_o_w_s_e _l_i_s_t
+
+ o+ _c_h_a_n_g_e _n_o_t_i_f_y _t_i_m_e_o_u_t
+
+ o+ _c_h_a_n_g_e _s_h_a_r_e _c_o_m_m_a_n_d
+
+ o+ _c_h_a_r_a_c_t_e_r _s_e_t
+
+ o+ _c_l_i_e_n_t _c_o_d_e _p_a_g_e
+
+ o+ _c_o_d_e _p_a_g_e _d_i_r_e_c_t_o_r_y
+
+ o+ _c_o_d_i_n_g _s_y_s_t_e_m
+
+ o+ _c_o_n_f_i_g _f_i_l_e
+
+ o+ _d_e_a_d_t_i_m_e
+
+ o+ _d_e_b_u_g _h_i_r_e_s _t_i_m_e_s_t_a_m_p
+
+ o+ _d_e_b_u_g _p_i_d
+
+ o+ _d_e_b_u_g _t_i_m_e_s_t_a_m_p
+
+ o+ _d_e_b_u_g _u_i_d
+
+ o+ _d_e_b_u_g_l_e_v_e_l
+
+ o+ _d_e_f_a_u_l_t
+
+ o+ _d_e_f_a_u_l_t _s_e_r_v_i_c_e
+
+ o+ _d_e_l_e_t_e _p_r_i_n_t_e_r _c_o_m_m_a_n_d
+
+ o+ _d_e_l_e_t_e _s_h_a_r_e _c_o_m_m_a_n_d
+
+ o+ _d_e_l_e_t_e _u_s_e_r _s_c_r_i_p_t
+
+ o+ _d_f_r_e_e _c_o_m_m_a_n_d
+
+ o+ _d_i_s_a_b_l_e _s_p_o_o_l_s_s
+
+ o+ _d_n_s _p_r_o_x_y
+
+ o+ _d_o_m_a_i_n _a_d_m_i_n _g_r_o_u_p
+
+ o+ _d_o_m_a_i_n _g_u_e_s_t _g_r_o_u_p
+
+
+
+
+ Page 10 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ _d_o_m_a_i_n _l_o_g_o_n_s
+
+ o+ _d_o_m_a_i_n _m_a_s_t_e_r
+
+ o+ _e_n_c_r_y_p_t _p_a_s_s_w_o_r_d_s
+
+ o+ _e_n_h_a_n_c_e_d _b_r_o_w_s_i_n_g
+
+ o+ _e_n_u_m_p_o_r_t_s _c_o_m_m_a_n_d
+
+ o+ _g_e_t_w_d _c_a_c_h_e
+
+ o+ _h_i_d_e _l_o_c_a_l _u_s_e_r_s
+
+ o+ _h_i_d_e _u_n_r_e_a_d_a_b_l_e
+
+ o+ _h_o_m_e_d_i_r _m_a_p
+
+ o+ _h_o_s_t _m_s_d_f_s
+
+ o+ _h_o_s_t_s _e_q_u_i_v
+
+ o+ _i_n_t_e_r_f_a_c_e_s
+
+ o+ _k_e_e_p_a_l_i_v_e
+
+ o+ _k_e_r_n_e_l _o_p_l_o_c_k_s
+
+ o+ _l_a_n_m_a_n _a_u_t_h
+
+ o+ _l_a_r_g_e _r_e_a_d_w_r_i_t_e
+
+ o+ _l_d_a_p _a_d_m_i_n _d_n
+
+ o+ _l_d_a_p _f_i_l_t_e_r
+
+ o+ _l_d_a_p _p_o_r_t
+
+ o+ _l_d_a_p _s_e_r_v_e_r
+
+ o+ _l_d_a_p _s_s_l
+
+ o+ _l_d_a_p _s_u_f_f_i_x
+
+ o+ _l_m _a_n_n_o_u_n_c_e
+
+ o+ _l_m _i_n_t_e_r_v_a_l
+
+ o+ _l_o_a_d _p_r_i_n_t_e_r_s
+
+ o+ _l_o_c_a_l _m_a_s_t_e_r
+
+
+
+
+ Page 11 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ _l_o_c_k _d_i_r
+
+ o+ _l_o_c_k _d_i_r_e_c_t_o_r_y
+
+ o+ _l_o_c_k _s_p_i_n _c_o_u_n_t
+
+ o+ _l_o_c_k _s_p_i_n _t_i_m_e
+
+ o+ _p_i_d _d_i_r_e_c_t_o_r_y
+
+ o+ _l_o_g _f_i_l_e
+
+ o+ _l_o_g _l_e_v_e_l
+
+ o+ _l_o_g_o_n _d_r_i_v_e
+
+ o+ _l_o_g_o_n _h_o_m_e
+
+ o+ _l_o_g_o_n _p_a_t_h
+
+ o+ _l_o_g_o_n _s_c_r_i_p_t
+
+ o+ _l_p_q _c_a_c_h_e _t_i_m_e
+
+ o+ _m_a_c_h_i_n_e _p_a_s_s_w_o_r_d _t_i_m_e_o_u_t
+
+ o+ _m_a_n_g_l_e_d _s_t_a_c_k
+
+ o+ _m_a_n_g_l_i_n_g _m_e_t_h_o_d
+
+ o+ _m_a_p _t_o _g_u_e_s_t
+
+ o+ _m_a_x _d_i_s_k _s_i_z_e
+
+ o+ _m_a_x _l_o_g _s_i_z_e
+
+ o+ _m_a_x _m_u_x
+
+ o+ _m_a_x _o_p_e_n _f_i_l_e_s
+
+ o+ _m_a_x _p_r_o_t_o_c_o_l
+
+ o+ _m_a_x _s_m_b_d _p_r_o_c_e_s_s_e_s
+
+ o+ _m_a_x _t_t_l
+
+ o+ _m_a_x _w_i_n_s _t_t_l
+
+ o+ _m_a_x _x_m_i_t
+
+ o+ _m_e_s_s_a_g_e _c_o_m_m_a_n_d
+
+
+
+
+ Page 12 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ _m_i_n _p_a_s_s_w_d _l_e_n_g_t_h
+
+ o+ _m_i_n _p_a_s_s_w_o_r_d _l_e_n_g_t_h
+
+ o+ _m_i_n _p_r_o_t_o_c_o_l
+
+ o+ _m_i_n _w_i_n_s _t_t_l
+
+ o+ _n_a_m_e _r_e_s_o_l_v_e _o_r_d_e_r
+
+ o+ _n_e_t_b_i_o_s _a_l_i_a_s_e_s
+
+ o+ _n_e_t_b_i_o_s _n_a_m_e
+
+ o+ _n_e_t_b_i_o_s _s_c_o_p_e
+
+ o+ _n_i_s _h_o_m_e_d_i_r
+
+ o+ _n_t _p_i_p_e _s_u_p_p_o_r_t
+
+ o+ _n_t _s_m_b _s_u_p_p_o_r_t
+
+ o+ _n_t _s_t_a_t_u_s _s_u_p_p_o_r_t
+
+ o+ _n_u_l_l _p_a_s_s_w_o_r_d_s
+
+ o+ _o_b_e_y _p_a_m _r_e_s_t_r_i_c_t_i_o_n_s
+
+ o+ _o_p_l_o_c_k _b_r_e_a_k _w_a_i_t _t_i_m_e
+
+ o+ _o_s _l_e_v_e_l
+
+ o+ _o_s_2 _d_r_i_v_e_r _m_a_p
+
+ o+ _p_a_m _p_a_s_s_w_o_r_d _c_h_a_n_g_e
+
+ o+ _p_a_n_i_c _a_c_t_i_o_n
+
+ o+ _p_a_s_s_w_d _c_h_a_t
+
+ o+ _p_a_s_s_w_d _c_h_a_t _d_e_b_u_g
+
+ o+ _p_a_s_s_w_d _p_r_o_g_r_a_m
+
+ o+ _p_a_s_s_w_o_r_d _l_e_v_e_l
+
+ o+ _p_a_s_s_w_o_r_d _s_e_r_v_e_r
+
+ o+ _p_r_e_f_e_r_e_d _m_a_s_t_e_r
+
+ o+ _p_r_e_f_e_r_r_e_d _m_a_s_t_e_r
+
+
+
+
+ Page 13 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ _p_r_e_l_o_a_d
+
+ o+ _p_r_i_n_t_c_a_p
+
+ o+ _p_r_i_n_t_c_a_p _n_a_m_e
+
+ o+ _p_r_i_n_t_e_r _d_r_i_v_e_r _f_i_l_e
+
+ o+ _p_r_o_t_o_c_o_l
+
+ o+ _r_e_a_d _b_m_p_x
+
+ o+ _r_e_a_d _r_a_w
+
+ o+ _r_e_a_d _s_i_z_e
+
+ o+ _r_e_m_o_t_e _a_n_n_o_u_n_c_e
+
+ o+ _r_e_m_o_t_e _b_r_o_w_s_e _s_y_n_c
+
+ o+ _r_e_s_t_r_i_c_t _a_n_o_n_y_m_o_u_s
+
+ o+ _r_o_o_t
+
+ o+ _r_o_o_t _d_i_r
+
+ o+ _r_o_o_t _d_i_r_e_c_t_o_r_y
+
+ o+ _s_e_c_u_r_i_t_y
+
+ o+ _s_e_r_v_e_r _s_t_r_i_n_g
+
+ o+ _s_h_o_w _a_d_d _p_r_i_n_t_e_r _w_i_z_a_r_d
+
+ o+ _s_m_b _p_a_s_s_w_d _f_i_l_e
+
+ o+ _s_o_c_k_e_t _a_d_d_r_e_s_s
+
+ o+ _s_o_c_k_e_t _o_p_t_i_o_n_s
+
+ o+ _s_o_u_r_c_e _e_n_v_i_r_o_n_m_e_n_t
+
+ o+ _s_s_l
+
+ o+ _s_s_l _C_A _c_e_r_t_D_i_r
+
+ o+ _s_s_l _C_A _c_e_r_t_F_i_l_e
+
+ o+ _s_s_l _c_i_p_h_e_r_s
+
+ o+ _s_s_l _c_l_i_e_n_t _c_e_r_t
+
+
+
+
+ Page 14 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ _s_s_l _c_l_i_e_n_t _k_e_y
+
+ o+ _s_s_l _c_o_m_p_a_t_i_b_i_l_i_t_y
+
+ o+ _s_s_l _e_g_d _s_o_c_k_e_t
+
+ o+ _s_s_l _e_n_t_r_o_p_y _b_y_t_e_s
+
+ o+ _s_s_l _e_n_t_r_o_p_y _f_i_l_e
+
+ o+ _s_s_l _h_o_s_t_s
+
+ o+ _s_s_l _h_o_s_t_s _r_e_s_i_g_n
+
+ o+ _s_s_l _r_e_q_u_i_r_e _c_l_i_e_n_t_c_e_r_t
+
+ o+ _s_s_l _r_e_q_u_i_r_e _s_e_r_v_e_r_c_e_r_t
+
+ o+ _s_s_l _s_e_r_v_e_r _c_e_r_t
+
+ o+ _s_s_l _s_e_r_v_e_r _k_e_y
+
+ o+ _s_s_l _v_e_r_s_i_o_n
+
+ o+ _s_t_a_t _c_a_c_h_e
+
+ o+ _s_t_a_t _c_a_c_h_e _s_i_z_e
+
+ o+ _s_t_r_i_p _d_o_t
+
+ o+ _s_y_s_l_o_g
+
+ o+ _s_y_s_l_o_g _o_n_l_y
+
+ o+ _t_e_m_p_l_a_t_e _h_o_m_e_d_i_r
+
+ o+ _t_e_m_p_l_a_t_e _s_h_e_l_l
+
+ o+ _t_i_m_e _o_f_f_s_e_t
+
+ o+ _t_i_m_e _s_e_r_v_e_r
+
+ o+ _t_i_m_e_s_t_a_m_p _l_o_g_s
+
+ o+ _t_o_t_a_l _p_r_i_n_t _j_o_b_s
+
+ o+ _u_n_i_x _e_x_t_e_n_s_i_o_n_s
+
+ o+ _u_n_i_x _p_a_s_s_w_o_r_d _s_y_n_c
+
+ o+ _u_p_d_a_t_e _e_n_c_r_y_p_t_e_d
+
+
+
+
+ Page 15 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ _u_s_e _m_m_a_p
+
+ o+ _u_s_e _r_h_o_s_t_s
+
+ o+ _u_s_e_r_n_a_m_e _l_e_v_e_l
+
+ o+ _u_s_e_r_n_a_m_e _m_a_p
+
+ o+ _u_t_m_p
+
+ o+ _u_t_m_p _d_i_r_e_c_t_o_r_y
+
+ o+ _v_a_l_i_d _c_h_a_r_s
+
+ o+ _w_i_n_b_i_n_d _c_a_c_h_e _t_i_m_e
+
+ o+ _w_i_n_b_i_n_d _e_n_u_m _u_s_e_r_s
+
+ o+ _w_i_n_b_i_n_d _e_n_u_m _g_r_o_u_p_s
+
+ o+ _w_i_n_b_i_n_d _g_i_d
+
+ o+ _w_i_n_b_i_n_d _s_e_p_a_r_a_t_o_r
+
+ o+ _w_i_n_b_i_n_d _u_i_d
+
+ o+ _w_i_n_b_i_n_d _u_s_e _d_e_f_a_u_l_t _d_o_m_a_i_n
+
+ o+ _w_i_n_s _h_o_o_k
+
+ o+ _w_i_n_s _p_r_o_x_y
+
+ o+ _w_i_n_s _s_e_r_v_e_r
+
+ o+ _w_i_n_s _s_u_p_p_o_r_t
+
+ o+ _w_o_r_k_g_r_o_u_p
+
+ o+ _w_r_i_t_e _r_a_w
+
+ CCCCOOOOMMMMPPPPLLLLEEEETTTTEEEE LLLLIIIISSSSTTTT OOOOFFFF SSSSEEEERRRRVVVVIIIICCCCEEEE PPPPAAAARRRRAAAAMMMMEEEETTTTEEEERRRRSSSS
+ Here is a list of all service parameters. See the section on
+ each parameter for details. Note that some are synonyms.
+
+ o+ _a_d_m_i_n _u_s_e_r_s
+
+ o+ _a_l_l_o_w _h_o_s_t_s
+
+ o+ _a_v_a_i_l_a_b_l_e
+
+ o+ _b_l_o_c_k_i_n_g _l_o_c_k_s
+
+
+
+
+ Page 16 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ _b_l_o_c_k _s_i_z_e
+
+ o+ _b_r_o_w_s_a_b_l_e
+
+ o+ _b_r_o_w_s_e_a_b_l_e
+
+ o+ _c_a_s_e _s_e_n_s_i_t_i_v_e
+
+ o+ _c_a_s_e_s_i_g_n_a_m_e_s
+
+ o+ _c_o_m_m_e_n_t
+
+ o+ _c_o_p_y
+
+ o+ _c_r_e_a_t_e _m_a_s_k
+
+ o+ _c_r_e_a_t_e _m_o_d_e
+
+ o+ _c_s_c _p_o_l_i_c_y
+
+ o+ _d_e_f_a_u_l_t _c_a_s_e
+
+ o+ _d_e_f_a_u_l_t _d_e_v_m_o_d_e
+
+ o+ _d_e_l_e_t_e _r_e_a_d_o_n_l_y
+
+ o+ _d_e_l_e_t_e _v_e_t_o _f_i_l_e_s
+
+ o+ _d_e_n_y _h_o_s_t_s
+
+ o+ _d_i_r_e_c_t_o_r_y
+
+ o+ _d_i_r_e_c_t_o_r_y _m_a_s_k
+
+ o+ _d_i_r_e_c_t_o_r_y _m_o_d_e
+
+ o+ _d_i_r_e_c_t_o_r_y _s_e_c_u_r_i_t_y _m_a_s_k
+
+ o+ _d_o_n_t _d_e_s_c_e_n_d
+
+ o+ _d_o_s _f_i_l_e_m_o_d_e
+
+ o+ _d_o_s _f_i_l_e_t_i_m_e _r_e_s_o_l_u_t_i_o_n
+
+ o+ _d_o_s _f_i_l_e_t_i_m_e_s
+
+ o+ _e_x_e_c
+
+ o+ _f_a_k_e _d_i_r_e_c_t_o_r_y _c_r_e_a_t_e _t_i_m_e_s
+
+ o+ _f_a_k_e _o_p_l_o_c_k_s
+
+
+
+
+ Page 17 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ _f_o_l_l_o_w _s_y_m_l_i_n_k_s
+
+ o+ _f_o_r_c_e _c_r_e_a_t_e _m_o_d_e
+
+ o+ _f_o_r_c_e _d_i_r_e_c_t_o_r_y _m_o_d_e
+
+ o+ _f_o_r_c_e _d_i_r_e_c_t_o_r_y _s_e_c_u_r_i_t_y _m_o_d_e
+
+ o+ _f_o_r_c_e _g_r_o_u_p
+
+ o+ _f_o_r_c_e _s_e_c_u_r_i_t_y _m_o_d_e
+
+ o+ _f_o_r_c_e _u_n_k_n_o_w_n _a_c_l _u_s_e_r
+
+ o+ _f_o_r_c_e _u_s_e_r
+
+ o+ _f_s_t_y_p_e
+
+ o+ _g_r_o_u_p
+
+ o+ _g_u_e_s_t _a_c_c_o_u_n_t
+
+ o+ _g_u_e_s_t _o_k
+
+ o+ _g_u_e_s_t _o_n_l_y
+
+ o+ _h_i_d_e _d_o_t _f_i_l_e_s
+
+ o+ _h_i_d_e _f_i_l_e_s
+
+ o+ _h_o_s_t_s _a_l_l_o_w
+
+ o+ _h_o_s_t_s _d_e_n_y
+
+ o+ _i_n_c_l_u_d_e
+
+ o+ _i_n_h_e_r_i_t _a_c_l_s
+
+ o+ _i_n_h_e_r_i_t _p_e_r_m_i_s_s_i_o_n_s
+
+ o+ _i_n_v_a_l_i_d _u_s_e_r_s
+
+ o+ _l_e_v_e_l_2 _o_p_l_o_c_k_s
+
+ o+ _l_o_c_k_i_n_g
+
+ o+ _l_p_p_a_u_s_e _c_o_m_m_a_n_d
+
+ o+ _l_p_q _c_o_m_m_a_n_d
+
+ o+ _l_p_r_e_s_u_m_e _c_o_m_m_a_n_d
+
+
+
+
+ Page 18 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ _l_p_r_m _c_o_m_m_a_n_d
+
+ o+ _m_a_g_i_c _o_u_t_p_u_t
+
+ o+ _m_a_g_i_c _s_c_r_i_p_t
+
+ o+ _m_a_n_g_l_e _c_a_s_e
+
+ o+ _m_a_n_g_l_e_d _m_a_p
+
+ o+ _m_a_n_g_l_e_d _n_a_m_e_s
+
+ o+ _m_a_n_g_l_i_n_g _c_h_a_r
+
+ o+ _m_a_p _a_r_c_h_i_v_e
+
+ o+ _m_a_p _h_i_d_d_e_n
+
+ o+ _m_a_p _s_y_s_t_e_m
+
+ o+ _m_a_x _c_o_n_n_e_c_t_i_o_n_s
+
+ o+ _m_a_x _p_r_i_n_t _j_o_b_s
+
+ o+ _m_i_n _p_r_i_n_t _s_p_a_c_e
+
+ o+ _m_s_d_f_s _r_o_o_t
+
+ o+ _n_t _a_c_l _s_u_p_p_o_r_t
+
+ o+ _o_n_l_y _g_u_e_s_t
+
+ o+ _o_n_l_y _u_s_e_r
+
+ o+ _o_p_l_o_c_k _c_o_n_t_e_n_t_i_o_n _l_i_m_i_t
+
+ o+ _o_p_l_o_c_k_s
+
+ o+ _p_a_t_h
+
+ o+ _p_o_s_i_x _l_o_c_k_i_n_g
+
+ o+ _p_o_s_t_e_x_e_c
+
+ o+ _p_o_s_t_s_c_r_i_p_t
+
+ o+ _p_r_e_e_x_e_c
+
+ o+ _p_r_e_e_x_e_c _c_l_o_s_e
+
+ o+ _p_r_e_s_e_r_v_e _c_a_s_e
+
+
+
+
+ Page 19 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ _p_r_i_n_t _c_o_m_m_a_n_d
+
+ o+ _p_r_i_n_t _o_k
+
+ o+ _p_r_i_n_t_a_b_l_e
+
+ o+ _p_r_i_n_t_e_r
+
+ o+ _p_r_i_n_t_e_r _a_d_m_i_n
+
+ o+ _p_r_i_n_t_e_r _d_r_i_v_e_r
+
+ o+ _p_r_i_n_t_e_r _d_r_i_v_e_r _l_o_c_a_t_i_o_n
+
+ o+ _p_r_i_n_t_e_r _n_a_m_e
+
+ o+ _p_r_i_n_t_i_n_g
+
+ o+ _p_r_o_f_i_l_e _a_c_l_s
+
+ o+ _p_u_b_l_i_c
+
+ o+ _q_u_e_u_e_p_a_u_s_e _c_o_m_m_a_n_d
+
+ o+ _q_u_e_u_e_r_e_s_u_m_e _c_o_m_m_a_n_d
+
+ o+ _r_e_a_d _l_i_s_t
+
+ o+ _r_e_a_d _o_n_l_y
+
+ o+ _r_o_o_t _p_o_s_t_e_x_e_c
+
+ o+ _r_o_o_t _p_r_e_e_x_e_c
+
+ o+ _r_o_o_t _p_r_e_e_x_e_c _c_l_o_s_e
+
+ o+ _s_e_c_u_r_i_t_y _m_a_s_k
+
+ o+ _s_e_t _d_i_r_e_c_t_o_r_y
+
+ o+ _s_h_a_r_e _m_o_d_e_s
+
+ o+ _s_h_o_r_t _p_r_e_s_e_r_v_e _c_a_s_e
+
+ o+ _s_t_a_t_u_s
+
+ o+ _s_t_r_i_c_t _a_l_l_o_c_a_t_e
+
+ o+ _s_t_r_i_c_t _l_o_c_k_i_n_g
+
+ o+ _s_t_r_i_c_t _s_y_n_c
+
+
+
+
+ Page 20 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ _s_y_n_c _a_l_w_a_y_s
+
+ o+ _u_s_e _c_l_i_e_n_t _d_r_i_v_e_r
+
+ o+ _u_s_e _s_e_n_d_f_i_l_e
+
+ o+ _u_s_e_r
+
+ o+ _u_s_e_r_n_a_m_e
+
+ o+ _u_s_e_r_s
+
+ o+ _v_a_l_i_d _u_s_e_r_s
+
+ o+ _v_e_t_o _f_i_l_e_s
+
+ o+ _v_e_t_o _o_p_l_o_c_k _f_i_l_e_s
+
+ o+ _v_f_s _o_b_j_e_c_t
+
+ o+ _v_f_s _o_p_t_i_o_n_s
+
+ o+ _v_o_l_u_m_e
+
+ o+ _w_i_d_e _l_i_n_k_s
+
+ o+ _w_r_i_t_a_b_l_e
+
+ o+ _w_r_i_t_e _c_a_c_h_e _s_i_z_e
+
+ o+ _w_r_i_t_e _l_i_s_t
+
+ o+ _w_r_i_t_e _o_k
+
+ o+ _w_r_i_t_e_a_b_l_e
+
+ EEEEXXXXPPPPLLLLAAAANNNNAAAATTTTIIIIOOOONNNN OOOOFFFF EEEEAAAACCCCHHHH PPPPAAAARRRRAAAAMMMMEEEETTTTEEEERRRR
+ aaaadddddddd pppprrrriiiinnnntttteeeerrrr ccccoooommmmmmmmaaaannnndddd ((((GGGG))))
+ 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 the underlying printing system. The
+ _a_d_d _p_r_i_n_t_e_r _c_o_m_m_a_n_d 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 _s_m_b._c_o_n_f file in order that
+ it can be shared by ssssmmmmbbbbdddd((((8888))))
+
+
+
+ Page 21 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ The _a_d_d _p_r_i_n_t_e_r _c_o_m_m_a_n_d is automatically invoked with
+ the following parameter (in order:
+
+ o+ _p_r_i_n_t_e_r _n_a_m_e
+
+ o+ _s_h_a_r_e _n_a_m_e
+
+ o+ _p_o_r_t _n_a_m_e
+
+ o+ _d_r_i_v_e_r _n_a_m_e
+
+ o+ _l_o_c_a_t_i_o_n
+
+ o+ _W_i_n_d_o_w_s _9_x _d_r_i_v_e_r _l_o_c_a_t_i_o_n
+
+ 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 _a_d_d _p_r_i_n_t_e_r _c_o_m_m_a_n_d has been executed, ssssmmmmbbbbdddd will
+ reparse the _s_m_b._c_o_n_f to determine if the share defined by
+ the APW exists. If the sharename is still invalid, then ssssmmmmbbbbdddd
+ will return an ACCESS_DENIED error to the client.
+
+ See also _d_e_l_e_t_e _p_r_i_n_t_e_r _c_o_m_m_a_n_d, _p_r_i_n_t_i_n_g, _s_h_o_w _a_d_d _p_r_i_n_t_e_r
+ _w_i_z_a_r_d
+
+ Default: nnnnoooonnnneeee
+
+ Example: aaaaddddddddpppprrrriiiinnnntttteeeerrrr ccccoooommmmmmmmaaaannnndddd ==== ////uuuussssrrrr////bbbbiiiinnnn////aaaaddddddddpppprrrriiiinnnntttteeeerrrr
+
+ aaaadddddddd sssshhhhaaaarrrreeee ccccoooommmmmmmmaaaannnndddd ((((GGGG))))
+ Samba 2.2.0 introduced the ability to dynamically add
+ and delete shares via the Windows NT 4.0 Server
+ Manager. The _a_d_d _s_h_a_r_e _c_o_m_m_a_n_d is used to define an
+ external program or script which will add a new service
+ definition to _s_m_b._c_o_n_f. In order to successfully
+ execute the _a_d_d _s_h_a_r_e _c_o_m_m_a_n_d, ssssmmmmbbbbdddd requires that the
+ administrator be connected using a root account (i.e.
+ uid == 0).
+
+ When executed, ssssmmmmbbbbdddd will automatically invoke the _a_d_d
+ _s_h_a_r_e _c_o_m_m_a_n_d with four parameters.
+
+ o+ _c_o_n_f_i_g_F_i_l_e - the location of the global _s_m_b._c_o_n_f
+ file.
+
+ o+ _s_h_a_r_e_N_a_m_e - the name of the new share.
+
+
+
+
+ Page 22 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ _p_a_t_h_N_a_m_e - path to an **existing** directory on disk.
+
+ o+ _c_o_m_m_e_n_t - comment string to associate with the new
+ share.
+
+ This parameter is only used for add file shares. To add
+ printer shares, see the _a_d_d _p_r_i_n_t_e_r _c_o_m_m_a_n_d.
+
+ See also _c_h_a_n_g_e _s_h_a_r_e _c_o_m_m_a_n_d, _d_e_l_e_t_e _s_h_a_r_e _c_o_m_m_a_n_d.
+
+ Default: nnnnoooonnnneeee
+
+ Example: aaaadddddddd sssshhhhaaaarrrreeee ccccoooommmmmmmmaaaannnndddd ==== ////uuuussssrrrr////llllooooccccaaaallll////bbbbiiiinnnn////aaaaddddddddsssshhhhaaaarrrreeee
+
+ aaaadddddddd uuuusssseeeerrrr ssssccccrrrriiiipppptttt ((((GGGG))))
+ This is the full pathname to a script that will be run
+ AAAASSSS RRRROOOOOOOOTTTT by smbd(8)
+ under special circumstances described below.
+
+ Normally, a Samba server requires that UNIX users are
+ created for all users accessing files on this server.
+ For sites that use Windows NT account databases as
+ their primary user database creating these users and
+ keeping the user list in sync with the Windows NT PDC
+ is an onerous task. This option allows smbd to create
+ the required UNIX users OOOONNNN DDDDEEEEMMMMAAAANNNNDDDD when a user accesses
+ the Samba server.
+
+ In order to use this option, smbd must NNNNOOOOTTTT be set to
+ _s_e_c_u_r_i_t_y = _s_h_a_r_e and _a_d_d _u_s_e_r _s_c_r_i_p_t must be set to a
+ full pathname for a script that will create a UNIX user
+ given one argument of %_u, which expands into the UNIX
+ user name to create.
+
+ When the Windows user attempts to access the Samba
+ server, at login (session setup in the SMB protocol)
+ time, smbd contacts the _p_a_s_s_w_o_r_d _s_e_r_v_e_r and attempts
+ to authenticate the given user with the given password.
+ If the authentication succeeds then ssssmmmmbbbbdddd attempts to
+ find a UNIX user in the UNIX password database to map
+ the Windows user into. If this lookup fails, and _a_d_d
+ _u_s_e_r _s_c_r_i_p_t is set then ssssmmmmbbbbdddd will call the specified
+ script AAAASSSS RRRROOOOOOOOTTTT, expanding any %_u argument to be the
+ user name to create.
+
+ If this script successfully creates the user then ssssmmmmbbbbdddd
+ will continue on as though the UNIX user already
+ existed. In this way, UNIX users are dynamically
+ created to match existing Windows NT accounts.
+
+ See also _s_e_c_u_r_i_t_y, _p_a_s_s_w_o_r_d _s_e_r_v_e_r, _d_e_l_e_t_e _u_s_e_r
+ _s_c_r_i_p_t.
+
+
+
+ Page 23 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Default: aaaadddddddd uuuusssseeeerrrr ssssccccrrrriiiipppptttt ==== <<<>>>
+
+ Example: aaaadddddddd uuuusssseeeerrrr ssssccccrrrriiiipppptttt ====
+ ////uuuussssrrrr////llllooooccccaaaallll////ssssaaaammmmbbbbaaaa////bbbbiiiinnnn////aaaadddddddd____uuuusssseeeerrrr %%%%uuuu
+
+ aaaaddddmmmmiiiinnnn uuuusssseeeerrrrssss ((((SSSS))))
+ This is a list of users who will be granted
+ administrative privileges on the share. This means that
+ they will do all file operations as the super-user
+ (root).
+
+ You should use this option very carefully, as any user
+ in this list will be able to do anything they like on
+ the share, irrespective of file permissions.
+
+ Default: nnnnoooo aaaaddddmmmmiiiinnnn uuuusssseeeerrrrssss
+
+ Example: aaaaddddmmmmiiiinnnn uuuusssseeeerrrrssss ==== jjjjaaaassssoooonnnn
+
+ aaaalllllllloooowwww hhhhoooossssttttssss ((((SSSS))))
+ Synonym for _h_o_s_t_s _a_l_l_o_w.
+
+ aaaalllllllloooowwww ttttrrrruuuusssstttteeeedddd ddddoooommmmaaaaiiiinnnnssss ((((GGGG))))
+ This option only takes effect when the _s_e_c_u_r_i_t_y option
+ is set to server or domain. If it is set to no, then
+ attempts to connect to a resource from a domain or
+ workgroup other than the one which smbd is running in
+ will fail, even if that domain is trusted by the remote
+ server doing the authentication.
+
+ This is useful if you only want your Samba server to
+ serve resources to users in the domain it is a member
+ of. As an example, suppose that there are two domains
+ DOMA and DOMB. DOMB is trusted by DOMA, which contains
+ the Samba server. Under normal circumstances, a user
+ with an account in DOMB can then access the resources
+ of a UNIX account with the same account name on the
+ Samba server even if they do not have an account in
+ DOMA. This can make implementing a security boundary
+ difficult.
+
+ Default: aaaalllllllloooowwww ttttrrrruuuusssstttteeeedddd ddddoooommmmaaaaiiiinnnnssss ==== yyyyeeeessss
+
+ aaaannnnnnnnoooouuuunnnncccceeee aaaassss ((((GGGG))))
+ This specifies what type of server nnnnmmmmbbbbdddd will announce
+ itself as, to a network neighborhood browse list. By
+ default this is set to Windows NT. The valid options
+ are : "NT Server" (which can also be written as "NT"),
+ "NT Workstation", "Win95" or "WfW" meaning Windows NT
+ Server, Windows NT Workstation, Windows 95 and Windows
+ for Workgroups respectively. Do not change this
+ parameter unless you have a specific need to stop Samba
+
+
+
+ Page 24 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ appearing as an NT server as this may prevent Samba
+ servers from participating as browser servers
+ correctly.
+
+ Default: aaaannnnnnnnoooouuuunnnncccceeee aaaassss ==== NNNNTTTT SSSSeeeerrrrvvvveeeerrrr
+
+ Example: aaaannnnnnnnoooouuuunnnncccceeee aaaassss ==== WWWWiiiinnnn99995555
+
+ aaaannnnnnnnoooouuuunnnncccceeee vvvveeeerrrrssssiiiioooonnnn ((((GGGG))))
+ This specifies the major and minor version numbers that
+ nmbd will use when announcing itself as a server. The
+ default is 4.5. Do not change this parameter unless you
+ have a specific need to set a Samba server to be a
+ downlevel server.
+
+ Default: aaaannnnnnnnoooouuuunnnncccceeee vvvveeeerrrrssssiiiioooonnnn ==== 4444....5555
+
+ Example: aaaannnnnnnnoooouuuunnnncccceeee vvvveeeerrrrssssiiiioooonnnn ==== 2222....0000
+
+ aaaauuuuttttoooo sssseeeerrrrvvvviiiicccceeeessss ((((GGGG))))
+ This is a synonym for the _p_r_e_l_o_a_d.
+
+ aaaavvvvaaaaiiiillllaaaabbbblllleeee ((((SSSS))))
+ This parameter lets you "turn off" a service. If
+ _a_v_a_i_l_a_b_l_e = _n_o, then AAAALLLLLLLL attempts to connect to the
+ service will fail. Such failures are logged.
+
+ Default: aaaavvvvaaaaiiiillllaaaabbbblllleeee ==== yyyyeeeessss
+
+ bbbbiiiinnnndddd iiiinnnntttteeeerrrrffffaaaacccceeeessss oooonnnnllllyyyy ((((GGGG))))
+ This global parameter allows the Samba admin to limit
+ what interfaces on a machine will serve SMB requests.
+ If affects file service smbd(8) and name service
+ nmbd(8) in slightly different ways.
+
+ For name service it causes nnnnmmmmbbbbdddd to bind to ports 137
+ and 138 on the interfaces listed in the interfaces
+ parameter. nnnnmmmmbbbbdddd also binds to the "all addresses"
+ interface (0.0.0.0) on ports 137 and 138 for the
+ purposes of reading broadcast messages. If this option
+ is not set then nnnnmmmmbbbbdddd will service name requests on all
+ of these sockets. If _b_i_n_d _i_n_t_e_r_f_a_c_e_s _o_n_l_y is set then
+ nnnnmmmmbbbbdddd will check the source address of any packets
+ coming in on the broadcast sockets and discard any that
+ don't match the broadcast addresses of the interfaces
+ in the _i_n_t_e_r_f_a_c_e_s parameter list. As unicast packets
+ are received on the other sockets it allows nnnnmmmmbbbbdddd to
+ refuse to serve names to machines that send packets
+ that arrive through any interfaces not listed in the
+ _i_n_t_e_r_f_a_c_e_s list. IP Source address spoofing does defeat
+ this simple check, however so it must not be used
+ seriously as a security feature for nnnnmmmmbbbbdddd.
+
+
+
+ Page 25 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ For file service it causes smbd(8) to bind only to the
+ interface list given in the interfaces parameter. This
+ restricts the networks that ssssmmmmbbbbdddd will serve to packets
+ coming in those interfaces. Note that you should not
+ use this parameter for machines that are serving PPP or
+ other intermittent or non-broadcast network interfaces
+ as it will not cope with non-permanent interfaces.
+
+ If _b_i_n_d _i_n_t_e_r_f_a_c_e_s _o_n_l_y is set then unless the network
+ address 111122227777....0000....0000....1111 is added to the _i_n_t_e_r_f_a_c_e_s parameter
+ list ssssmmmmbbbbppppaaaasssssssswwwwdddd((((8888)))) and sssswwwwaaaatttt((((8888)))) may not work as expected
+ due to the reasons covered below.
+
+ To change a users SMB password, the ssssmmmmbbbbppppaaaasssssssswwwwdddd by
+ default connects to the llllooooccccaaaallllhhhhoooosssstttt ---- 111122227777....0000....0000....1111 address
+ as an SMB client to issue the password change request.
+ If _b_i_n_d _i_n_t_e_r_f_a_c_e_s _o_n_l_y is set then unless the network
+ address 111122227777....0000....0000....1111 is added to the _i_n_t_e_r_f_a_c_e_s parameter
+ list then ssssmmmmbbbbppppaaaasssssssswwwwdddd will fail to connect in it's
+ default mode. ssssmmmmbbbbppppaaaasssssssswwwwdddd can be forced to use the
+ primary IP interface of the local host by using its -_r
+ _r_e_m_o_t_e _m_a_c_h_i_n_e
+ parameter, with _r_e_m_o_t_e _m_a_c_h_i_n_e set to the IP name of
+ the primary interface of the local host.
+
+ The sssswwwwaaaatttt status page tries to connect with ssssmmmmbbbbdddd and
+ nnnnmmmmbbbbdddd at the address 111122227777....0000....0000....1111 to determine if they are
+ running. Not adding 111122227777....0000....0000....1111 will cause ssssmmmmbbbbdddd and nnnnmmmmbbbbdddd
+ to always show "not running" even if they really are.
+ This can prevent sssswwwwaaaatttt from
+ starting/stopping/restarting ssssmmmmbbbbdddd and nnnnmmmmbbbbdddd.
+
+ Default: bbbbiiiinnnndddd iiiinnnntttteeeerrrrffffaaaacccceeeessss oooonnnnllllyyyy ==== nnnnoooo
+
+ bbbblllloooocccckkkk ssssiiiizzzzeeee ((((SSSS))))
+ This parameter controls the behavior of smbd(8) when
+ reporting disk free sizes. By default, this reports a
+ disk block size of 1024 bytes.
+
+ Changing this parameter may have some effect on the
+ efficiency of client writes, this is not yet confirmed.
+ This parameter was added to allow advanced
+ administrators to change it (usually to a higher value)
+ and test the effect it has on client write performance
+ without re-compiling the code. As this is an
+ experimental option it may be removed in a future
+ release.
+
+ Changing this option does not change the disk free
+ reporting size, just the block size unit reported to
+ the client.
+
+
+
+
+ Page 26 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Default: bbbblllloooocccckkkk ssssiiiizzzzeeee ==== 1111000022224444
+
+ Example: bbbblllloooocccckkkk ssssiiiizzzzeeee ==== 66665555555533336666
+
+ bbbblllloooocccckkkkiiiinnnngggg lllloooocccckkkkssss ((((SSSS))))
+ This parameter controls the behavior of smbd(8) when
+ given a request by a client to obtain a byte range lock
+ on a region of an open file, and the request has a time
+ limit associated with it.
+
+ If this parameter is set and the lock range requested
+ cannot be immediately satisfied, Samba 2.2 will
+ internally queue the lock request, and periodically
+ attempt to obtain the lock until the timeout period
+ expires.
+
+ If this parameter is set to no, then Samba 2.2 will
+ behave as previous versions of Samba would and will
+ fail the lock request immediately if the lock range
+ cannot be obtained.
+
+ Default: bbbblllloooocccckkkkiiiinnnngggg lllloooocccckkkkssss ==== yyyyeeeessss
+
+ bbbbrrrroooowwwwssssaaaabbbblllleeee ((((SSSS))))
+ See the _b_r_o_w_s_e_a_b_l_e.
+
+ bbbbrrrroooowwwwsssseeee lllliiiisssstttt ((((GGGG))))
+ This controls whether ssssmmmmbbbbdddd((((8888)))) will serve a browse list
+ to a client doing a NNNNeeeettttSSSSeeeerrrrvvvveeeerrrrEEEEnnnnuuuummmm call. Normally set to
+ yes. You should never need to change this.
+
+ Default: bbbbrrrroooowwwwsssseeee lllliiiisssstttt ==== yyyyeeeessss
+
+ bbbbrrrroooowwwwsssseeeeaaaabbbblllleeee ((((SSSS))))
+ This controls whether this share is seen in the list of
+ available shares in a net view and in the browse list.
+
+ Default: bbbbrrrroooowwwwsssseeeeaaaabbbblllleeee ==== yyyyeeeessss
+
+ ccccaaaasssseeee sssseeeennnnssssiiiittttiiiivvvveeee ((((SSSS))))
+ See the discussion in the section NAME MANGLING.
+
+ Default: ccccaaaasssseeee sssseeeennnnssssiiiittttiiiivvvveeee ==== nnnnoooo
+
+ ccccaaaasssseeeessssiiiiggggnnnnaaaammmmeeeessss ((((SSSS))))
+ Synonym for case sensitive.
+
+ cccchhhhaaaannnnggggeeee nnnnoooottttiiiiffffyyyy ttttiiiimmmmeeeeoooouuuutttt ((((GGGG))))
+ This SMB allows a client to tell a server to "watch" a
+ particular directory for any changes and only reply to
+ the SMB request when a change has occurred. Such
+ constant scanning of a directory is expensive under
+
+
+
+ Page 27 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ UNIX, hence an ssssmmmmbbbbdddd((((8888)))) daemon only performs such a
+ scan on each requested directory once every _c_h_a_n_g_e
+ _n_o_t_i_f_y _t_i_m_e_o_u_t seconds.
+
+ Default: cccchhhhaaaannnnggggeeee nnnnoooottttiiiiffffyyyy ttttiiiimmmmeeeeoooouuuutttt ==== 66660000
+
+ Example: cccchhhhaaaannnnggggeeee nnnnoooottttiiiiffffyyyy ttttiiiimmmmeeeeoooouuuutttt ==== 333300000000
+
+ Would change the scan time to every 5 minutes.
+
+ cccchhhhaaaannnnggggeeee sssshhhhaaaarrrreeee ccccoooommmmmmmmaaaannnndddd ((((GGGG))))
+ Samba 2.2.0 introduced the ability to dynamically add
+ and delete shares via the Windows NT 4.0 Server
+ Manager. The _c_h_a_n_g_e _s_h_a_r_e _c_o_m_m_a_n_d is used to define an
+ external program or script which will modify an
+ existing service definition in _s_m_b._c_o_n_f. In order to
+ successfully execute the _c_h_a_n_g_e _s_h_a_r_e _c_o_m_m_a_n_d, ssssmmmmbbbbdddd
+ requires that the administrator be connected using a
+ root account (i.e. uid == 0).
+
+ When executed, ssssmmmmbbbbdddd will automatically invoke the
+ _c_h_a_n_g_e _s_h_a_r_e _c_o_m_m_a_n_d with four parameters.
+
+ o+ _c_o_n_f_i_g_F_i_l_e - the location of the global _s_m_b._c_o_n_f
+ file.
+
+ o+ _s_h_a_r_e_N_a_m_e - the name of the new share.
+
+ o+ _p_a_t_h_N_a_m_e - path to an **existing** directory on disk.
+
+ o+ _c_o_m_m_e_n_t - 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 _a_d_d _s_h_a_r_e _c_o_m_m_a_n_d, _d_e_l_e_t_e _s_h_a_r_e _c_o_m_m_a_n_d.
+
+ Default: nnnnoooonnnneeee
+
+ Example: cccchhhhaaaannnnggggeeee sssshhhhaaaarrrreeee ccccoooommmmmmmmaaaannnndddd ==== ////uuuussssrrrr////llllooooccccaaaallll////bbbbiiiinnnn////aaaaddddddddsssshhhhaaaarrrreeee
+
+ cccchhhhaaaarrrraaaacccctttteeeerrrr sssseeeetttt ((((GGGG))))
+ This allows smbd to map incoming filenames from a DOS
+ Code page (see the client code page parameter) to
+ several built in UNIX character sets. The built in code
+ page translations are:
+
+ o+ ISO8859-1 : Western European UNIX character set. The
+ parameter _c_l_i_e_n_t _c_o_d_e _p_a_g_e MMMMUUUUSSSSTTTT be set to code page
+ 850 if the _c_h_a_r_a_c_t_e_r _s_e_t parameter is set to
+
+
+
+ Page 28 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ ISO8859-1 in order for the conversion to the UNIX
+ character set to be done correctly.
+
+ o+ ISO8859-2 : Eastern European UNIX character set. The
+ parameter _c_l_i_e_n_t _c_o_d_e _p_a_g_e MMMMUUUUSSSSTTTT be set to code page
+ 852 if the _c_h_a_r_a_c_t_e_r _s_e_t parameter is set to
+ ISO8859-2 in order for the conversion to the UNIX
+ character set to be done correctly.
+
+ o+ ISO8859-5 : Russian Cyrillic UNIX character set. The
+ parameter _c_l_i_e_n_t _c_o_d_e _p_a_g_e MMMMUUUUSSSSTTTT be set to code page
+ 866 if the _c_h_a_r_a_c_t_e_r _s_e_t parameter is set to
+ ISO8859-5 in order for the conversion to the UNIX
+ character set to be done correctly.
+
+ o+ ISO8859-7 : Greek UNIX character set. The parameter
+ _c_l_i_e_n_t _c_o_d_e _p_a_g_e MMMMUUUUSSSSTTTT be set to code page 737 if the
+ _c_h_a_r_a_c_t_e_r _s_e_t parameter is set to ISO8859-7 in order
+ for the conversion to the UNIX character set to be
+ done correctly.
+
+ o+ KOI8-R : Alternate mapping for Russian Cyrillic UNIX
+ character set. The parameter _c_l_i_e_n_t _c_o_d_e _p_a_g_e MMMMUUUUSSSSTTTT be
+ set to code page 866 if the _c_h_a_r_a_c_t_e_r _s_e_t parameter
+ is set to KOI8-R in order for the conversion to the
+ UNIX character set to be done correctly.
+
+ BBBBUUUUGGGG. These MSDOS code page to UNIX character set mappings
+ should be dynamic, like the loading of MS DOS code pages,
+ not static.
+
+ Normally this parameter is not set, meaning no filename
+ translation is done.
+
+ Default: cccchhhhaaaarrrraaaacccctttteeeerrrr sssseeeetttt ==== <<<>>>
+
+ Example: cccchhhhaaaarrrraaaacccctttteeeerrrr sssseeeetttt ==== IIIISSSSOOOO8888888855559999----1111
+
+ cccclllliiiieeeennnntttt ccccooooddddeeee ppppaaaaggggeeee ((((GGGG))))
+ This parameter specifies the DOS code page that the
+ clients accessing Samba are using. To determine what
+ code page a Windows or DOS client is using, open a DOS
+ command prompt and type the command cccchhhhccccpppp. This will
+ output the code page. The default for USA MS-DOS,
+ Windows 95, and Windows NT releases is code page 437.
+ The default for western European releases of the above
+ operating systems is code page 850.
+
+ This parameter tells smbd(8) which of the _c_o_d_e_p_a_g_e._X_X_X
+ files to dynamically load on startup. These files,
+ described more fully in the manual page
+ mmmmaaaakkkkeeee____ssssmmmmbbbbccccooooddddeeeeppppaaaaggggeeee((((1111)))) tell ssssmmmmbbbbdddd how to map lower to
+
+
+
+ Page 29 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ upper case characters to provide the case insensitivity
+ of filenames that Windows clients expect.
+
+ Samba currently ships with the following code page
+ files :
+
+ o+ Code Page 437 - MS-DOS Latin US
+
+ o+ Code Page 737 - Windows '95 Greek
+
+ o+ Code Page 850 - MS-DOS Latin 1
+
+ o+ Code Page 852 - MS-DOS Latin 2
+
+ o+ Code Page 861 - MS-DOS Icelandic
+
+ o+ Code Page 866 - MS-DOS Cyrillic
+
+ o+ Code Page 932 - MS-DOS Japanese SJIS
+
+ o+ Code Page 936 - MS-DOS Simplified Chinese
+
+ o+ Code Page 949 - MS-DOS Korean Hangul
+
+ o+ Code Page 950 - MS-DOS Traditional Chinese
+
+ Thus this parameter may have any of the values 437, 737,
+ 850, 852, 861, 932, 936, 949, or 950. If you don't find the
+ codepage you need, read the comments in one of the other
+ codepage files and the mmmmaaaakkkkeeee____ssssmmmmbbbbccccooooddddeeeeppppaaaaggggeeee((((1111)))) man page and
+ write one. Please remember to donate it back to the Samba
+ user community.
+
+ This parameter co-operates with the _v_a_l_i_d _c_h_a_r_s parameter in
+ determining what characters are valid in filenames and how
+ capitalization is done. If you set both this parameter and
+ the _v_a_l_i_d _c_h_a_r_s parameter the _c_l_i_e_n_t _c_o_d_e _p_a_g_e parameter
+ MMMMUUUUSSSSTTTT be set before the _v_a_l_i_d _c_h_a_r_s parameter in the _s_m_b._c_o_n_f
+ file. The _v_a_l_i_d _c_h_a_r_s string will then augment the character
+ settings in the _c_l_i_e_n_t _c_o_d_e _p_a_g_e parameter.
+
+ If not set, _c_l_i_e_n_t _c_o_d_e _p_a_g_e defaults to 850.
+
+ See also : _v_a_l_i_d _c_h_a_r_s, _c_o_d_e _p_a_g_e _d_i_r_e_c_t_o_r_y
+
+ Default: cccclllliiiieeeennnntttt ccccooooddddeeee ppppaaaaggggeeee ==== 888855550000
+
+ Example: cccclllliiiieeeennnntttt ccccooooddddeeee ppppaaaaggggeeee ==== 999933336666
+
+ ccccooooddddeeee ppppaaaaggggeeee ddddiiiirrrreeeeccccttttoooorrrryyyy ((((GGGG))))
+ Define the location of the various client code page
+ files.
+
+
+
+ Page 30 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ See also _c_l_i_e_n_t _c_o_d_e _p_a_g_e
+
+ Default: ccccooooddddeeee ppppaaaaggggeeee ddddiiiirrrreeeeccccttttoooorrrryyyy ==== $$$${{{{pppprrrreeeeffffiiiixxxx}}}}////lllliiiibbbb////ccccooooddddeeeeppppaaaaggggeeeessss
+
+ Example: ccccooooddddeeee ppppaaaaggggeeee ddddiiiirrrreeeeccccttttoooorrrryyyy ====
+ ////uuuussssrrrr////sssshhhhaaaarrrreeee////ssssaaaammmmbbbbaaaa////ccccooooddddeeeeppppaaaaggggeeeessss
+
+ ccccooooddddiiiinnnngggg ssssyyyysssstttteeeemmmm ((((GGGG))))
+ This parameter is used to determine how incoming
+ Shift-JIS Japanese characters are mapped from the
+ incoming _c_l_i_e_n_t _c_o_d_e _p_a_g_e used by the client, into file
+ names in the UNIX filesystem. Only useful if _c_l_i_e_n_t
+ _c_o_d_e _p_a_g_e is set to 932 (Japanese Shift-JIS). The
+ options are :
+
+ o+ SJIS - Shift-JIS. Does no conversion of the incoming
+ filename.
+
+ o+ JIS8, J8BB, J8BH, J8@B, J8@J, J8@H - Convert from
+ incoming Shift-JIS to eight bit JIS code with
+ different shift-in, shift out codes.
+
+ o+ JIS7, J7BB, J7BH, J7@B, J7@J, J7@H - Convert from
+ incoming Shift-JIS to seven bit JIS code with
+ different shift-in, shift out codes.
+
+ o+ JUNET, JUBB, JUBH, JU@B, JU@J, JU@H - Convert from
+ incoming Shift-JIS to JUNET code with different
+ shift-in, shift out codes.
+
+ o+ EUC - Convert an incoming Shift-JIS character to EUC
+ code.
+
+ o+ HEX - Convert an incoming Shift-JIS character to a 3
+ byte hex representation, i.e. :AB.
+
+ o+ CAP - Convert an incoming Shift-JIS character to the
+ 3 byte hex representation used by the Columbia
+ AppleTalk Program (CAP), i.e. :AB. This is used for
+ compatibility between Samba and CAP.
+
+ Default: ccccooooddddiiiinnnngggg ssssyyyysssstttteeeemmmm ==== <<<>>>
+
+ ccccoooommmmmmmmeeeennnntttt ((((SSSS))))
+ This is a text field that is seen next to a share when
+ a client does a queries the server, either via the
+ network neighborhood or via nnnneeeetttt vvvviiiieeeewwww to list what
+ shares are available.
+
+ If you want to set the string that is displayed next to
+ the machine name then see the _s_e_r_v_e_r _s_t_r_i_n_g parameter.
+
+
+
+
+ Page 31 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Default: NNNNoooo ccccoooommmmmmmmeeeennnntttt ssssttttrrrriiiinnnngggg
+
+ Example: ccccoooommmmmmmmeeeennnntttt ==== FFFFrrrreeeedddd''''ssss FFFFiiiilllleeeessss
+
+ ccccoooonnnnffffiiiigggg ffffiiiilllleeee ((((GGGG))))
+ This allows you to override the config file to use,
+ instead of the default (usually _s_m_b._c_o_n_f). There is a
+ chicken and egg problem here as this option is set in
+ the config file!
+
+ For this reason, if the name of the config file has
+ changed when the parameters are loaded then it will
+ reload them from the new config file.
+
+ This option takes the usual substitutions, which can be
+ very useful.
+
+ If the config file doesn't exist then it won't be
+ loaded (allowing you to special case the config files
+ of just a few clients).
+
+ Example: ccccoooonnnnffffiiiigggg ffffiiiilllleeee ==== ////uuuussssrrrr////llllooooccccaaaallll////ssssaaaammmmbbbbaaaa////lllliiiibbbb////ssssmmmmbbbb....ccccoooonnnnffff....%%%%mmmm
+
+ ccccooooppppyyyy ((((SSSS))))
+ This parameter allows you to "clone" service entries.
+ The specified service is simply duplicated under the
+ current service's name. Any parameters specified in the
+ current section will override those in the section
+ being copied.
+
+ This feature lets you set up a 'template' service and
+ create similar services easily. Note that the service
+ being copied must occur earlier in the configuration
+ file than the service doing the copying.
+
+ Default: nnnnoooo vvvvaaaalllluuuueeee
+
+ Example: ccccooooppppyyyy ==== ooootttthhhheeeerrrrsssseeeerrrrvvvviiiicccceeee
+
+ ccccrrrreeeeaaaatttteeee mmmmaaaasssskkkk ((((SSSS))))
+ A synonym for this parameter is _c_r_e_a_t_e _m_o_d_e .
+
+ When a file is created, the necessary permissions are
+ calculated according to the mapping from DOS modes to
+ UNIX permissions, and the resulting UNIX mode is then
+ bit-wise 'AND'ed with this parameter. This parameter
+ may be thought of as a bit-wise MASK for the UNIX modes
+ of a file. Any bit nnnnooootttt set here will be removed from
+ the modes set on a file when it is created.
+
+ The default value of this parameter removes the 'group'
+ and 'other' write and execute bits from the UNIX modes.
+
+
+
+ Page 32 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Following this Samba will bit-wise 'OR' the UNIX mode
+ created from this parameter with the value of the _f_o_r_c_e
+ _c_r_e_a_t_e _m_o_d_e parameter which is set to 000 by default.
+
+ This parameter does not affect directory modes. See the
+ parameter _d_i_r_e_c_t_o_r_y _m_o_d_e for details.
+
+ See also the _f_o_r_c_e _c_r_e_a_t_e _m_o_d_e parameter for forcing
+ particular mode bits to be set on created files. See
+ also the _d_i_r_e_c_t_o_r_y _m_o_d_e parameter for masking mode
+ bits on created directories. See also the _i_n_h_e_r_i_t
+ _p_e_r_m_i_s_s_i_o_n_s 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 _s_e_c_u_r_i_t_y _m_a_s_k.
+
+ Default: ccccrrrreeeeaaaatttteeee mmmmaaaasssskkkk ==== 0000777744444444
+
+ Example: ccccrrrreeeeaaaatttteeee mmmmaaaasssskkkk ==== 0000777777775555
+
+ ccccrrrreeeeaaaatttteeee mmmmooooddddeeee ((((SSSS))))
+ This is a synonym for _c_r_e_a_t_e _m_a_s_k.
+
+ ccccsssscccc ppppoooolllliiiiccccyyyy ((((SSSS))))
+ This stands for cccclllliiiieeeennnntttt----ssssiiiiddddeeee ccccaaaacccchhhhiiiinnnngggg ppppoooolllliiiiccccyyyy, and
+ specifies how clients capable of offline caching will
+ cache the files in the share. The valid values are:
+ manual, documents, programs, disable.
+
+ These values correspond to those used on Windows
+ servers.
+
+ For example, shares containing roaming profiles can
+ have offline caching disabled using ccccsssscccc ppppoooolllliiiiccccyyyy ====
+ ddddiiiissssaaaabbbblllleeee .
+
+ Default: ccccsssscccc ppppoooolllliiiiccccyyyy ==== mmmmaaaannnnuuuuaaaallll
+
+ Example: ccccsssscccc ppppoooolllliiiiccccyyyy ==== pppprrrrooooggggrrrraaaammmmssss
+
+ ddddeeeeaaaaddddttttiiiimmmmeeee ((((GGGG))))
+ The value of the parameter (a decimal integer)
+ represents the number of minutes of inactivity before a
+ connection is considered dead, and it is disconnected.
+ The deadtime only takes effect if the number of open
+ files is zero.
+
+ This is useful to stop a server's resources being
+ exhausted by a large number of inactive connections.
+
+
+
+
+ Page 33 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Most clients have an auto-reconnect feature when a
+ connection is broken so in most cases this parameter
+ should be transparent to users.
+
+ Using this parameter with a timeout of a few minutes is
+ recommended for most systems.
+
+ A deadtime of zero indicates that no auto-disconnection
+ should be performed.
+
+ Default: ddddeeeeaaaaddddttttiiiimmmmeeee ==== 0000
+
+ Example: ddddeeeeaaaaddddttttiiiimmmmeeee ==== 11115555
+
+ ddddeeeebbbbuuuugggg hhhhiiiirrrreeeessss ttttiiiimmmmeeeessssttttaaaammmmpppp ((((GGGG))))
+ Sometimes the timestamps in the log messages are needed
+ with a resolution of higher that seconds, this boolean
+ parameter adds microsecond resolution to the timestamp
+ message header when turned on.
+
+ Note that the parameter _d_e_b_u_g _t_i_m_e_s_t_a_m_p must be on for
+ this to have an effect.
+
+ Default: ddddeeeebbbbuuuugggg hhhhiiiirrrreeeessss ttttiiiimmmmeeeessssttttaaaammmmpppp ==== nnnnoooo
+
+ ddddeeeebbbbuuuugggg ppppiiiidddd ((((GGGG))))
+ When using only one log file for more then one forked
+ smbdprocess there may be hard to follow which process
+ outputs which message. This boolean parameter is adds
+ the process-id to the timestamp message headers in the
+ logfile when turned on.
+
+ Note that the parameter _d_e_b_u_g _t_i_m_e_s_t_a_m_p must be on for
+ this to have an effect.
+
+ Default: ddddeeeebbbbuuuugggg ppppiiiidddd ==== nnnnoooo
+
+ ddddeeeebbbbuuuugggg ttttiiiimmmmeeeessssttttaaaammmmpppp ((((GGGG))))
+ Samba 2.2 debug log messages are timestamped by
+ default. If you are running at a high _d_e_b_u_g _l_e_v_e_l
+ these timestamps can be distracting. This boolean
+ parameter allows timestamping to be turned off.
+
+ Default: ddddeeeebbbbuuuugggg ttttiiiimmmmeeeessssttttaaaammmmpppp ==== yyyyeeeessss
+
+ ddddeeeebbbbuuuugggg uuuuiiiidddd ((((GGGG))))
+ Samba is sometimes run as root and sometime run as the
+ connected user, this boolean parameter inserts the
+ current euid, egid, uid and gid to the timestamp
+ message headers in the log file if turned on.
+
+ Note that the parameter _d_e_b_u_g _t_i_m_e_s_t_a_m_p must be on for
+
+
+
+ Page 34 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ this to have an effect.
+
+ Default: ddddeeeebbbbuuuugggg uuuuiiiidddd ==== nnnnoooo
+
+ ddddeeeebbbbuuuugggglllleeeevvvveeeellll ((((GGGG))))
+ Synonym for _l_o_g _l_e_v_e_l.
+
+ ddddeeeeffffaaaauuuulllltttt ((((GGGG))))
+ A synonym for _d_e_f_a_u_l_t _s_e_r_v_i_c_e.
+
+ ddddeeeeffffaaaauuuulllltttt ccccaaaasssseeee ((((SSSS))))
+ See the section on NAME MANGLING. Also note the _s_h_o_r_t
+ _p_r_e_s_e_r_v_e _c_a_s_e parameter.
+
+ Default: ddddeeeeffffaaaauuuulllltttt ccccaaaasssseeee ==== lllloooowwwweeeerrrr
+
+ ddddeeeeffffaaaauuuulllltttt ddddeeeevvvvmmmmooooddddeeee ((((SSSS))))
+ This parameter is only applicable to printable
+ services. When smbd is serving Printer Drivers to
+ Windows NT/2k/XP clients, each printer on the Samba
+ server has a Device Mode which defines things such as
+ paper size and orientation and duplex settings. The
+ device mode can only correctly be generated by the
+ printer driver itself (which can only be executed on a
+ Win32 platform). Because smbd is unable to execute the
+ driver code to generate the device mode, the default
+ behavior is to set this field to NULL.
+
+ Most problems with serving printer drivers to Windows
+ NT/2k/XP clients can be traced to a problem with the
+ generated device mode. Certain drivers will do things
+ such as crashing the client's Explorer.exe with a NULL
+ devmode. However, other printer drivers can cause the
+ client's spooler service (spoolsv.exe) to die if the
+ devmode was not created by the driver itself (i.e. smbd
+ generates a default devmode).
+
+ This parameter should be used with care and tested with
+ the printer driver in question. It is better to leave
+ the device mode to NULL and let the Windows client set
+ the correct values. Because drivers do not do this all
+ the time, setting ddddeeeeffffaaaauuuulllltttt ddddeeeevvvvmmmmooooddddeeee ==== yyyyeeeessss will instruct
+ smbd to generate a default one.
+
+ For more information on Windows NT/2k printing and
+ Device Modes, see the MSDN documentation
+ .
+
+ Default: ddddeeeeffffaaaauuuulllltttt ddddeeeevvvvmmmmooooddddeeee ==== nnnnoooo
+
+ ddddeeeeffffaaaauuuulllltttt sssseeeerrrrvvvviiiicccceeee ((((GGGG))))
+ This parameter specifies the name of a service which
+
+
+
+ Page 35 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ will be connected to if the service actually requested
+ cannot be found. Note that the square brackets are NNNNOOOOTTTT
+ given in the parameter value (see example below).
+
+ There is no default value for this parameter. If this
+ parameter is not given, attempting to connect to a
+ nonexistent service results in an error.
+
+ Typically the default service would be a _g_u_e_s_t _o_k,
+ _r_e_a_d-_o_n_l_y service.
+
+ Also note that the apparent service name will be
+ changed to equal that of the requested service, this is
+ very useful as it allows you to use macros like %_S to
+ make a wildcard service.
+
+ Note also that any "_" characters in the name of the
+ service used in the default service will get mapped to
+ a "/". This allows for interesting things.
+
+ Example:
+
+
+ [global]
+ default service = pub
+
+ [pub]
+ path = /%S
+
+
+
+ ddddeeeelllleeeetttteeee pppprrrriiiinnnntttteeeerrrr ccccoooommmmmmmmaaaannnndddd ((((GGGG))))
+ 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
+ _d_e_l_e_t_e_p_r_i_n_t_e_r _c_o_m_m_a_n_d defines a script to be run which
+ will perform the necessary operations for removing the
+ printer from the print system and from _s_m_b._c_o_n_f.
+
+ The _d_e_l_e_t_e _p_r_i_n_t_e_r _c_o_m_m_a_n_d is automatically called with
+ only one parameter: "_p_r_i_n_t_e_r _n_a_m_e".
+
+ Once the _d_e_l_e_t_e _p_r_i_n_t_e_r _c_o_m_m_a_n_d has been executed, ssssmmmmbbbbdddd
+ will reparse the _s_m_b._c_o_n_f to associated printer no
+ longer exists. If the sharename is still valid, then
+ ssssmmmmbbbbdddd will return an ACCESS_DENIED error to the client.
+
+ See also _a_d_d _p_r_i_n_t_e_r _c_o_m_m_a_n_d, _p_r_i_n_t_i_n_g, _s_h_o_w _a_d_d
+
+
+
+ Page 36 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ _p_r_i_n_t_e_r _w_i_z_a_r_d
+
+ Default: nnnnoooonnnneeee
+
+ Example: ddddeeeelllleeeetttteeeepppprrrriiiinnnntttteeeerrrr ccccoooommmmmmmmaaaannnndddd ==== ////uuuussssrrrr////bbbbiiiinnnn////rrrreeeemmmmoooovvvveeeepppprrrriiiinnnntttteeeerrrr
+
+ ddddeeeelllleeeetttteeee rrrreeeeaaaaddddoooonnnnllllyyyy ((((SSSS))))
+ This parameter allows readonly files to be deleted.
+ This is not normal DOS semantics, but is allowed by
+ UNIX.
+
+ This option may be useful for running applications such
+ as rcs, where UNIX file ownership prevents changing
+ file permissions, and DOS semantics prevent deletion of
+ a read only file.
+
+ Default: ddddeeeelllleeeetttteeee rrrreeeeaaaaddddoooonnnnllllyyyy ==== nnnnoooo
+
+ ddddeeeelllleeeetttteeee sssshhhhaaaarrrreeee ccccoooommmmmmmmaaaannnndddd ((((GGGG))))
+ Samba 2.2.0 introduced the ability to dynamically add
+ and delete shares via the Windows NT 4.0 Server
+ Manager. The _d_e_l_e_t_e _s_h_a_r_e _c_o_m_m_a_n_d is used to define an
+ external program or script which will remove an
+ existing service definition from _s_m_b._c_o_n_f. In order to
+ successfully execute the _d_e_l_e_t_e _s_h_a_r_e _c_o_m_m_a_n_d, ssssmmmmbbbbdddd
+ requires that the administrator be connected using a
+ root account (i.e. uid == 0).
+
+ When executed, ssssmmmmbbbbdddd will automatically invoke the
+ _d_e_l_e_t_e _s_h_a_r_e _c_o_m_m_a_n_d with two parameters.
+
+ o+ _c_o_n_f_i_g_F_i_l_e - the location of the global _s_m_b._c_o_n_f
+ file.
+
+ o+ _s_h_a_r_e_N_a_m_e - the name of the existing service.
+
+ This parameter is only used to remove file shares. To delete
+ printer shares, see the _d_e_l_e_t_e _p_r_i_n_t_e_r _c_o_m_m_a_n_d.
+
+ See also _a_d_d _s_h_a_r_e _c_o_m_m_a_n_d, _c_h_a_n_g_e _s_h_a_r_e _c_o_m_m_a_n_d.
+
+ Default: nnnnoooonnnneeee
+
+ Example: ddddeeeelllleeeetttteeee sssshhhhaaaarrrreeee ccccoooommmmmmmmaaaannnndddd ==== ////uuuussssrrrr////llllooooccccaaaallll////bbbbiiiinnnn////ddddeeeellllsssshhhhaaaarrrreeee
+
+ ddddeeeelllleeeetttteeee uuuusssseeeerrrr ssssccccrrrriiiipppptttt ((((GGGG))))
+ This is the full pathname to a script that will be run
+ AAAASSSS RRRROOOOOOOOTTTT by ssssmmmmbbbbdddd((((8888)))) under special circumstances
+ described below.
+
+ Normally, a Samba server requires that UNIX users are
+ created for all users accessing files on this server.
+
+
+
+ Page 37 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ For sites that use Windows NT account databases as
+ their primary user database creating these users and
+ keeping the user list in sync with the Windows NT PDC
+ is an onerous task. This option allows ssssmmmmbbbbdddd to delete
+ the required UNIX users OOOONNNN DDDDEEEEMMMMAAAANNNNDDDD when a user accesses
+ the Samba server and the Windows NT user no longer
+ exists.
+
+ In order to use this option, ssssmmmmbbbbdddd must be set to
+ _s_e_c_u_r_i_t_y = _d_o_m_a_i_n or _s_e_c_u_r_i_t_y = _u_s_e_r and _d_e_l_e_t_e _u_s_e_r
+ _s_c_r_i_p_t must be set to a full pathname for a script that
+ will delete a UNIX user given one argument of %_u, which
+ expands into the UNIX user name to delete.
+
+ When the Windows user attempts to access the Samba
+ server, at llllooooggggiiiinnnn (session setup in the SMB protocol)
+ time, ssssmmmmbbbbdddd contacts the _p_a_s_s_w_o_r_d _s_e_r_v_e_r and attempts
+ to authenticate the given user with the given password.
+ If the authentication fails with the specific Domain
+ error code meaning that the user no longer exists then
+ ssssmmmmbbbbdddd attempts to find a UNIX user in the UNIX password
+ database that matches the Windows user account. If this
+ lookup succeeds, and _d_e_l_e_t_e _u_s_e_r _s_c_r_i_p_t is set then
+ ssssmmmmbbbbdddd will all the specified script AAAASSSS RRRROOOOOOOOTTTT, expanding
+ any %_u argument to be the user name to delete.
+
+ This script should delete the given UNIX username. In
+ this way, UNIX users are dynamically deleted to match
+ existing Windows NT accounts.
+
+ See also security = domain, _p_a_s_s_w_o_r_d _s_e_r_v_e_r , _a_d_d _u_s_e_r
+ _s_c_r_i_p_t .
+
+ Default: ddddeeeelllleeeetttteeee uuuusssseeeerrrr ssssccccrrrriiiipppptttt ==== <<<>>>
+
+ Example: ddddeeeelllleeeetttteeee uuuusssseeeerrrr ssssccccrrrriiiipppptttt ====
+ ////uuuussssrrrr////llllooooccccaaaallll////ssssaaaammmmbbbbaaaa////bbbbiiiinnnn////ddddeeeellll____uuuusssseeeerrrr %%%%uuuu
+
+ ddddeeeelllleeeetttteeee vvvveeeettttoooo ffffiiiilllleeeessss ((((SSSS))))
+ This option is used when Samba is attempting to delete
+ a directory that contains one or more vetoed
+ directories (see the _v_e_t_o _f_i_l_e_s option). If this option
+ is set to no (the default) then if a vetoed directory
+ contains any non-vetoed files or directories then the
+ directory delete will fail. This is usually what you
+ want.
+
+ If this option is set to yes, then Samba will attempt
+ to recursively delete any files and directories within
+ the vetoed directory. This can be useful for
+ integration with file serving systems such as NetAtalk
+ which create meta-files within directories you might
+
+
+
+ Page 38 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ normally veto DOS/Windows users from seeing (e.g.
+ ._A_p_p_l_e_D_o_u_b_l_e)
+
+ Setting ddddeeeelllleeeetttteeee vvvveeeettttoooo ffffiiiilllleeeessss ==== yyyyeeeessss allows these
+ directories to be transparently deleted when the parent
+ directory is deleted (so long as the user has
+ permissions to do so).
+
+ See also the _v_e_t_o _f_i_l_e_s parameter.
+
+ Default: ddddeeeelllleeeetttteeee vvvveeeettttoooo ffffiiiilllleeeessss ==== nnnnoooo
+
+ ddddeeeennnnyyyy hhhhoooossssttttssss ((((SSSS))))
+ Synonym for _h_o_s_t_s _d_e_n_y.
+
+ ddddffffrrrreeeeeeee ccccoooommmmmmmmaaaannnndddd ((((GGGG))))
+ The _d_f_r_e_e _c_o_m_m_a_n_d setting should only be used on
+ systems where a problem occurs with the internal disk
+ space calculations. This has been known to happen with
+ Ultrix, but may occur with other operating systems. The
+ symptom that was seen was an error of "Abort Retry
+ Ignore" at the end of each directory listing.
+
+ This setting allows the replacement of the internal
+ routines to calculate the total disk space and amount
+ available with an external routine. The example below
+ gives a possible script that might fulfill this
+ function.
+
+ The external program will be passed a single parameter
+ indicating a directory in the filesystem being queried.
+ This will typically consist of the string ./. The
+ script should return two integers in ASCII. The first
+ should be the total disk space in blocks, and the
+ second should be the number of available blocks. An
+ optional third return value can give the block size in
+ bytes. The default blocksize is 1024 bytes.
+
+ Note: Your script should NNNNOOOOTTTT be setuid or setgid and
+ should be owned by (and writeable only by) root!
+
+ Default: BBBByyyy ddddeeeeffffaaaauuuulllltttt iiiinnnntttteeeerrrrnnnnaaaallll rrrroooouuuuttttiiiinnnneeeessss ffffoooorrrr ddddeeeetttteeeerrrrmmmmiiiinnnniiiinnnngggg
+ tttthhhheeee ddddiiiisssskkkk ccccaaaappppaaaacccciiiittttyyyy aaaannnndddd rrrreeeemmmmaaaaiiiinnnniiiinnnngggg ssssppppaaaacccceeee wwwwiiiillllllll bbbbeeee uuuusssseeeedddd....
+
+ Example: ddddffffrrrreeeeeeee ccccoooommmmmmmmaaaannnndddd ==== ////uuuussssrrrr////llllooooccccaaaallll////ssssaaaammmmbbbbaaaa////bbbbiiiinnnn////ddddffffrrrreeeeeeee
+
+ Where the script dfree (which must be made executable)
+ could be:
+
+
+
+ #!/bin/sh
+
+
+
+ Page 39 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ df $1 | tail -1 | awk '{print $2" "$4}'
+
+
+
+ or perhaps (on Sys V based systems):
+
+
+
+ #!/bin/sh
+ /usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
+
+
+
+ Note that you may have to replace the command names
+ with full path names on some systems.
+
+ ddddiiiirrrreeeeccccttttoooorrrryyyy ((((SSSS))))
+ Synonym for _p_a_t_h .
+
+ ddddiiiirrrreeeeccccttttoooorrrryyyy mmmmaaaasssskkkk ((((SSSS))))
+ This parameter is the octal modes which are used when
+ converting DOS modes to UNIX modes when creating UNIX
+ directories.
+
+ When a directory is created, the necessary permissions
+ are calculated according to the mapping from DOS modes
+ to UNIX permissions, and the resulting UNIX mode is
+ then bit-wise 'AND'ed with this parameter. This
+ parameter may be thought of as a bit-wise MASK for the
+ UNIX modes of a directory. Any bit nnnnooootttt set here will be
+ removed from the modes set on a directory when it is
+ created.
+
+ The default value of this parameter removes the 'group'
+ and 'other' write bits from the UNIX mode, allowing
+ only the user who owns the directory to modify it.
+
+ Following this Samba will bit-wise 'OR' the UNIX mode
+ created from this parameter with the value of the _f_o_r_c_e
+ _d_i_r_e_c_t_o_r_y _m_o_d_e 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 _d_i_r_e_c_t_o_r_y
+ _s_e_c_u_r_i_t_y _m_a_s_k.
+
+ See the _f_o_r_c_e _d_i_r_e_c_t_o_r_y _m_o_d_e parameter to cause
+ particular mode bits to always be set on created
+ directories.
+
+
+
+
+ Page 40 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ See also the _c_r_e_a_t_e _m_o_d_e parameter for masking mode
+ bits on created files, and the _d_i_r_e_c_t_o_r_y _s_e_c_u_r_i_t_y _m_a_s_k
+ parameter.
+
+ Also refer to the _i_n_h_e_r_i_t _p_e_r_m_i_s_s_i_o_n_s parameter.
+
+ Default: ddddiiiirrrreeeeccccttttoooorrrryyyy mmmmaaaasssskkkk ==== 0000777755555555
+
+ Example: ddddiiiirrrreeeeccccttttoooorrrryyyy mmmmaaaasssskkkk ==== 0000777777775555
+
+ ddddiiiirrrreeeeccccttttoooorrrryyyy mmmmooooddddeeee ((((SSSS))))
+ Synonym for _d_i_r_e_c_t_o_r_y _m_a_s_k
+
+ ddddiiiirrrreeeeccccttttoooorrrryyyy sssseeeeccccuuuurrrriiiittttyyyy mmmmaaaasssskkkk ((((SSSS))))
+ This parameter controls what UNIX permission bits can
+ be modified when a Windows NT client is manipulating
+ the UNIX permission on a directory using the native NT
+ security dialog box.
+
+ This parameter is applied as a mask (AND'ed with) to
+ the changed permission bits, thus preventing any bits
+ not in this mask from being modified. Essentially, zero
+ bits in this 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 0777
+ meaning a user is allowed to modify all the
+ user/group/world permissions on a directory.
+
+ NNNNooootttteeee 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 leave it as the default of 0777.
+
+ See also the _f_o_r_c_e _d_i_r_e_c_t_o_r_y _s_e_c_u_r_i_t_y _m_o_d_e, _s_e_c_u_r_i_t_y
+ _m_a_s_k, _f_o_r_c_e _s_e_c_u_r_i_t_y _m_o_d_e parameters.
+
+ Default: ddddiiiirrrreeeeccccttttoooorrrryyyy sssseeeeccccuuuurrrriiiittttyyyy mmmmaaaasssskkkk ==== 0000777777777777
+
+ Example: ddddiiiirrrreeeeccccttttoooorrrryyyy sssseeeeccccuuuurrrriiiittttyyyy mmmmaaaasssskkkk ==== 0000777700000000
+
+ ddddiiiissssaaaabbbblllleeee ssssppppoooooooollllssssssss ((((GGGG))))
+ Enabling this parameter will disables Samba's support
+ for the SPOOLSS set of MS-RPC's and will yield
+ identical behavior as Samba 2.0.x. Windows NT/2000
+ clients will downgrade to using Lanman style printing
+ commands. Windows 9x/ME will be uneffected by the
+ parameter. However, this will also disable the ability
+ to upload printer drivers to a Samba server via the
+ Windows NT Add Printer Wizard or by using the NT
+ printer properties dialog window. It will also disable
+
+
+
+ Page 41 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ the capability of Windows NT/2000 clients to download
+ print drivers from the Samba host upon demand. BBBBeeee vvvveeeerrrryyyy
+ ccccaaaarrrreeeeffffuuuullll aaaabbbboooouuuutttt eeeennnnaaaabbbblllliiiinnnngggg tttthhhhiiiissss ppppaaaarrrraaaammmmeeeetttteeeerrrr....
+
+ See also use client driver
+
+ Default : ddddiiiissssaaaabbbblllleeee ssssppppoooooooollllssssssss ==== nnnnoooo
+
+ ddddnnnnssss pppprrrrooooxxxxyyyy ((((GGGG))))
+ Specifies that nmbd(8) when acting as a WINS server and
+ finding that a NetBIOS name has not been registered,
+ should treat the NetBIOS name word-for-word as a DNS
+ name and do a lookup with the DNS server for that name
+ on behalf of the name-querying client.
+
+ Note that the maximum length for a NetBIOS name is 15
+ characters, so the DNS name (or DNS alias) can likewise
+ only be 15 characters, maximum.
+
+ nnnnmmmmbbbbdddd spawns a second copy of itself to do the DNS name
+ lookup requests, as doing a name lookup is a blocking
+ action.
+
+ See also the parameter _w_i_n_s _s_u_p_p_o_r_t.
+
+ Default: ddddnnnnssss pppprrrrooooxxxxyyyy ==== yyyyeeeessss
+
+ ddddoooommmmaaaaiiiinnnn aaaaddddmmmmiiiinnnn ggggrrrroooouuuupppp ((((GGGG))))
+ 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 _s_m_b._c_o_n_f notation.
+
+ See also _d_o_m_a_i_n _g_u_e_s_t _g_r_o_u_p, _d_o_m_a_i_n _l_o_g_o_n_s
+
+ Default: nnnnoooo ddddoooommmmaaaaiiiinnnn aaaaddddmmmmiiiinnnniiiissssttttrrrraaaattttoooorrrrssss
+
+ Example: ddddoooommmmaaaaiiiinnnn aaaaddddmmmmiiiinnnn ggggrrrroooouuuupppp ==== rrrrooooooootttt @@@@wwwwhhhheeeeeeeellll
+
+ ddddoooommmmaaaaiiiinnnn gggguuuueeeesssstttt ggggrrrroooouuuupppp ((((GGGG))))
+ 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 _s_m_b._c_o_n_f notation.
+
+
+
+ Page 42 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ See also _d_o_m_a_i_n _a_d_m_i_n _g_r_o_u_p, _d_o_m_a_i_n _l_o_g_o_n_s
+
+ Default: nnnnoooo ddddoooommmmaaaaiiiinnnn gggguuuueeeessssttttssss
+
+ Example: ddddoooommmmaaaaiiiinnnn gggguuuueeeesssstttt ggggrrrroooouuuupppp ==== nnnnoooobbbbooooddddyyyy @@@@gggguuuueeeesssstttt
+
+ ddddoooommmmaaaaiiiinnnn llllooooggggoooonnnnssss ((((GGGG))))
+ If set to yes, the Samba server will serve Windows
+ 95/98 Domain logons for the _w_o_r_k_g_r_o_u_p it is in. Samba
+ 2.2 also has limited capability to act as a domain
+ controller for Windows NT 4 Domains. For more details
+ on setting up this feature see the Samba-PDC-HOWTO
+ included in the _h_t_m_l_d_o_c_s/ directory shipped with the
+ source code.
+
+ Default: ddddoooommmmaaaaiiiinnnn llllooooggggoooonnnnssss ==== nnnnoooo
+
+ ddddoooommmmaaaaiiiinnnn mmmmaaaasssstttteeeerrrr ((((GGGG))))
+ Tell nnnnmmmmbbbbdddd((((8888)))) to enable WAN-wide browse list collation.
+ Setting this option causes nnnnmmmmbbbbdddd to claim a special
+ domain specific NetBIOS name that identifies it as a
+ domain master browser for its given _w_o_r_k_g_r_o_u_p. Local
+ master browsers in the same _w_o_r_k_g_r_o_u_p on broadcast-
+ isolated subnets will give this nnnnmmmmbbbbdddd their local browse
+ lists, and then ask ssssmmmmbbbbdddd((((8888)))) for a complete copy of the
+ browse list for the whole wide area network. Browser
+ clients will then contact their local master browser,
+ and will receive the domain-wide browse list, instead
+ of just the list for their broadcast-isolated subnet.
+
+ Note that Windows NT Primary Domain Controllers expect
+ to be able to claim this _w_o_r_k_g_r_o_u_p specific special
+ NetBIOS name that identifies them as domain master
+ browsers for that _w_o_r_k_g_r_o_u_p by default (i.e. there is
+ no way to prevent a Windows NT PDC from attempting to
+ do this). This means that if this parameter is set and
+ nnnnmmmmbbbbdddd claims the special name for a _w_o_r_k_g_r_o_u_p before a
+ Windows NT PDC is able to do so then cross subnet
+ browsing will behave strangely and may fail.
+
+ If ddddoooommmmaaaaiiiinnnn llllooooggggoooonnnnssss ==== yyyyeeeessss , then the default behavior is
+ to enable the _d_o_m_a_i_n _m_a_s_t_e_r parameter. If _d_o_m_a_i_n _l_o_g_o_n_s
+ is not enabled (the default setting), then neither will
+ _d_o_m_a_i_n _m_a_s_t_e_r be enabled by default.
+
+ Default: ddddoooommmmaaaaiiiinnnn mmmmaaaasssstttteeeerrrr ==== aaaauuuuttttoooo
+
+ ddddoooonnnntttt ddddeeeesssscccceeeennnndddd ((((SSSS))))
+ There are certain directories on some systems (e.g.,
+ the /_p_r_o_c tree under Linux) that are either not of
+ interest to clients or are infinitely deep (recursive).
+ This parameter allows you to specify a comma-delimited
+
+
+
+ Page 43 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ list of directories that the server should always show
+ as empty.
+
+ Note that Samba can be very fussy about the exact
+ format of the "dont descend" entries. For example you
+ may need ./_p_r_o_c instead of just /_p_r_o_c. Experimentation
+ is the best policy :-)
+
+ Default: nnnnoooonnnneeee ((((iiii....eeee....,,,, aaaallllllll ddddiiiirrrreeeeccccttttoooorrrriiiieeeessss aaaarrrreeee OOOOKKKK ttttoooo ddddeeeesssscccceeeennnndddd))))
+
+ Example: ddddoooonnnntttt ddddeeeesssscccceeeennnndddd ==== ////pppprrrroooocccc,,,,////ddddeeeevvvv
+
+ ddddoooossss ffffiiiilllleeeemmmmooooddddeeee ((((SSSS))))
+ The default behavior in Samba is to provide UNIX-like
+ behavior where only the owner of a file/directory is
+ able to change the permissions on it. However, this
+ behavior is often confusing to DOS/Windows users.
+ Enabling this parameter allows a user who has write
+ access to the file (by whatever means) to modify the
+ permissions on it. Note that a user belonging to the
+ group owning the file will not be allowed to change
+ permissions if the group is only granted read access.
+ Ownership of the file/directory is not changed, only
+ the permissions are modified.
+
+ Default: ddddoooossss ffffiiiilllleeeemmmmooooddddeeee ==== nnnnoooo
+
+ ddddoooossss ffffiiiilllleeeettttiiiimmmmeeee rrrreeeessssoooolllluuuuttttiiiioooonnnn ((((SSSS))))
+ Under the DOS and Windows FAT filesystem, the finest
+ granularity on time resolution is two seconds. Setting
+ this parameter for a share causes Samba to round the
+ reported time down to the nearest two second boundary
+ when a query call that requires one second resolution
+ is made to ssssmmmmbbbbdddd((((8888))))
+
+
+ This option is mainly used as a compatibility option
+ for Visual C++ when used against Samba shares. If
+ oplocks are enabled on a share, Visual C++ uses two
+ different time reading calls to check if a file has
+ changed since it was last read. One of these calls uses
+ a one-second granularity, the other uses a two second
+ granularity. As the two second call rounds any odd
+ second down, then if the file has a timestamp of an odd
+ number of seconds then the two timestamps will not
+ match and Visual C++ will keep reporting the file has
+ changed. Setting this option causes the two timestamps
+ to match, and Visual C++ is happy.
+
+ Default: ddddoooossss ffffiiiilllleeeettttiiiimmmmeeee rrrreeeessssoooolllluuuuttttiiiioooonnnn ==== nnnnoooo
+
+ ddddoooossss ffffiiiilllleeeettttiiiimmmmeeeessss ((((SSSS))))
+
+
+
+ Page 44 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Under DOS and Windows, if a user can write to a file
+ they can change the timestamp on it. Under POSIX
+ semantics, only the owner of the file or root may
+ change the timestamp. By default, Samba runs with POSIX
+ semantics and refuses to change the timestamp on a file
+ if the user ssssmmmmbbbbdddd is acting on behalf of is not the file
+ owner. Setting this option to yes allows DOS semantics
+ and smbd will change the file timestamp as DOS
+ requires.
+
+ Default: ddddoooossss ffffiiiilllleeeettttiiiimmmmeeeessss ==== nnnnoooo
+
+ eeeennnnccccrrrryyyypppptttt ppppaaaasssssssswwwwoooorrrrddddssss ((((GGGG))))
+ This boolean controls whether encrypted passwords will
+ be negotiated with the client. Note that Windows NT 4.0
+ SP3 and above and also Windows 98 will by default
+ expect encrypted passwords unless a registry entry is
+ changed. To use encrypted passwords in Samba see the
+ file ENCRYPTION.txt in the Samba documentation
+ directory _d_o_c_s/ shipped with the source code.
+
+ In order for encrypted passwords to work correctly
+ ssssmmmmbbbbdddd((((8888)))) must either have access to a local _s_m_b_p_a_s_s_w_d(_5)
+ program for information on how to set up and maintain
+ this file), or set the security = [server|domain]
+ parameter which causes ssssmmmmbbbbdddd to authenticate against
+ another server.
+
+ Default: eeeennnnccccrrrryyyypppptttt ppppaaaasssssssswwwwoooorrrrddddssss ==== nnnnoooo
+
+ eeeennnnhhhhaaaannnncccceeeedddd bbbbrrrroooowwwwssssiiiinnnngggg ((((GGGG))))
+ This option enables a couple of enhancements to cross-
+ subnet browse propagation that have been added in Samba
+ but which are not standard in Microsoft
+ implementations.
+
+ The first enhancement to browse propagation consists of
+ a regular wildcard query to a Samba WINS server for all
+ Domain Master Browsers, followed by a browse
+ synchronization with each of the returned DMBs. The
+ second enhancement consists of a regular randomised
+ browse synchronization with all currently known DMBs.
+
+ You may wish to disable this option if you have a
+ problem with empty workgroups not disappearing from
+ browse lists. Due to the restrictions of the browse
+ protocols these enhancements can cause a empty
+ workgroup to stay around forever which can be annoying.
+
+ In general you should leave this option enabled as it
+ makes cross-subnet browse propagation much more
+ reliable.
+
+
+
+ Page 45 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Default: eeeennnnhhhhaaaannnncccceeeedddd bbbbrrrroooowwwwssssiiiinnnngggg ==== yyyyeeeessss
+
+ eeeennnnuuuummmmppppoooorrrrttttssss ccccoooommmmmmmmaaaannnndddd ((((GGGG))))
+ The concept of a "port" is fairly foreign to UNIX
+ hosts. Under Windows NT/2000 print servers, a port is
+ associated with a port monitor and generally takes the
+ form of a local port (i.e. LPT1:, COM1:, FILE:) or a
+ remote port (i.e. LPD Port Monitor, etc...). By
+ default, Samba has only one port defined--"Samba
+ Printer Port". Under Windows NT/2000, all printers must
+ have a valid port name. If you wish to have a list of
+ ports displayed (ssssmmmmbbbbdddd does not use a port name for
+ anything) other than the default "Samba Printer Port",
+ you can define _e_n_u_m_p_o_r_t_s _c_o_m_m_a_n_d to point to a program
+ which should generate a list of ports, one per line, to
+ standard output. This listing will then be used in
+ response to the level 1 and 2 EnumPorts() RPC.
+
+ Default: nnnnoooo eeeennnnuuuummmmppppoooorrrrttttssss ccccoooommmmmmmmaaaannnndddd
+
+ Example: eeeennnnuuuummmmppppoooorrrrttttssss ccccoooommmmmmmmaaaannnndddd ==== ////uuuussssrrrr////bbbbiiiinnnn////lllliiiissssttttppppoooorrrrttttssss
+
+ eeeexxxxeeeecccc ((((SSSS))))
+ This is a synonym for _p_r_e_e_x_e_c.
+
+ ffffaaaakkkkeeee ddddiiiirrrreeeeccccttttoooorrrryyyy ccccrrrreeeeaaaatttteeee ttttiiiimmmmeeeessss ((((SSSS))))
+ NTFS and Windows VFAT file systems keep a create time
+ for all files and directories. This is not the same as
+ the ctime - status change time - that Unix keeps, so
+ Samba by default reports the earliest of the various
+ times Unix does keep. Setting this parameter for a
+ share causes Samba to always report midnight 1-1-1980
+ as the create time for directories.
+
+ This option is mainly used as a compatibility option
+ for Visual C++ when used against Samba shares. Visual
+ C++ generated makefiles have the object directory as a
+ dependency for each object file, and a make rule to
+ create the directory. Also, when NMAKE compares
+ timestamps it uses the creation time when examining a
+ directory. Thus the object directory will be created if
+ it does not exist, but once it does exist it will
+ always have an earlier timestamp than the object files
+ it contains.
+
+ However, Unix time semantics mean that the create time
+ reported by Samba will be updated whenever a file is
+ created or or deleted in the directory. NMAKE finds all
+ object files in the object directory. The timestamp of
+ the last one built is then compared to the timestamp of
+ the object directory. If the directory's timestamp if
+ newer, then all object files will be rebuilt. Enabling
+
+
+
+ Page 46 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ this option ensures directories always predate their
+ contents and an NMAKE build will proceed as expected.
+
+ Default: ffffaaaakkkkeeee ddddiiiirrrreeeeccccttttoooorrrryyyy ccccrrrreeeeaaaatttteeee ttttiiiimmmmeeeessss ==== nnnnoooo
+
+ ffffaaaakkkkeeee oooopppplllloooocccckkkkssss ((((SSSS))))
+ Oplocks are the way that SMB clients get permission
+ from a server to locally cache file operations. If a
+ server grants an oplock (opportunistic lock) then the
+ client is free to assume that it is the only one
+ accessing the file and it will aggressively cache file
+ data. With some oplock types the client may even cache
+ file open/close operations. This can give enormous
+ performance benefits.
+
+ When you set ffffaaaakkkkeeee oooopppplllloooocccckkkkssss ==== yyyyeeeessss, ssssmmmmbbbbdddd((((8888)))) will always
+ grant oplock requests no matter how many clients are
+ using the file.
+
+ It is generally much better to use the real _o_p_l_o_c_k_s
+ support rather than this parameter.
+
+ If you enable this option on all read-only shares or
+ shares that you know will only be accessed from one
+ client at a time such as physically read-only media
+ like CDROMs, you will see a big performance improvement
+ on many operations. If you enable this option on shares
+ where multiple clients may be accessing the files
+ read-write at the same time you can get data
+ corruption. Use this option carefully!
+
+ Default: ffffaaaakkkkeeee oooopppplllloooocccckkkkssss ==== nnnnoooo
+
+ ffffoooolllllllloooowwww ssssyyyymmmmlllliiiinnnnkkkkssss ((((SSSS))))
+ This parameter allows the Samba administrator to stop
+ ssssmmmmbbbbdddd((((8888)))) from following symbolic links in a particular
+ share. Setting this parameter to no prevents any file
+ or directory that is a symbolic link from being
+ followed (the user will get an error). This option is
+ very useful to stop users from adding a symbolic link
+ to /_e_t_c/_p_a_s_s_w_d in their home directory for instance.
+ However it will slow filename lookups down slightly.
+
+ This option is enabled (i.e. ssssmmmmbbbbdddd will follow symbolic
+ links) by default.
+
+ Default: ffffoooolllllllloooowwww ssssyyyymmmmlllliiiinnnnkkkkssss ==== yyyyeeeessss
+
+ ffffoooorrrrcccceeee ccccrrrreeeeaaaatttteeee mmmmooooddddeeee ((((SSSS))))
+ This parameter specifies a set of UNIX mode bit
+ permissions that will aaaallllwwwwaaaayyyyssss be set on a file created
+ by Samba. This is done by bitwise 'OR'ing these bits
+
+
+
+ Page 47 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ onto the mode bits of a file that is being created or
+ having its permissions changed. The default for this
+ parameter is (in octal) 000. The modes in this
+ parameter are bitwise 'OR'ed onto the file mode after
+ the mask set in the _c_r_e_a_t_e _m_a_s_k parameter is applied.
+
+ See also the parameter _c_r_e_a_t_e _m_a_s_k for details on
+ masking mode bits on files.
+
+ See also the _i_n_h_e_r_i_t _p_e_r_m_i_s_s_i_o_n_s parameter.
+
+ Default: ffffoooorrrrcccceeee ccccrrrreeeeaaaatttteeee mmmmooooddddeeee ==== 000000000000
+
+ Example: ffffoooorrrrcccceeee ccccrrrreeeeaaaatttteeee mmmmooooddddeeee ==== 0000777755555555
+
+ would force all created files to have read and execute
+ permissions set for 'group' and 'other' as well as the
+ read/write/execute bits set for the 'user'.
+
+ ffffoooorrrrcccceeee ddddiiiirrrreeeeccccttttoooorrrryyyy mmmmooooddddeeee ((((SSSS))))
+ This parameter specifies a set of UNIX mode bit
+ permissions that will aaaallllwwwwaaaayyyyssss be set on a directory
+ created by Samba. This is done by bitwise 'OR'ing these
+ bits onto the mode bits of a directory that is being
+ created. The default for this parameter is (in octal)
+ 0000 which will not add any extra permission bits to a
+ created directory. This operation is done after the
+ mode mask in the parameter _d_i_r_e_c_t_o_r_y _m_a_s_k is applied.
+
+ See also the parameter _d_i_r_e_c_t_o_r_y _m_a_s_k for details on
+ masking mode bits on created directories.
+
+ See also the _i_n_h_e_r_i_t _p_e_r_m_i_s_s_i_o_n_s parameter.
+
+ Default: ffffoooorrrrcccceeee ddddiiiirrrreeeeccccttttoooorrrryyyy mmmmooooddddeeee ==== 000000000000
+
+ Example: ffffoooorrrrcccceeee ddddiiiirrrreeeeccccttttoooorrrryyyy mmmmooooddddeeee ==== 0000777755555555
+
+ would force all created directories to have read and
+ execute permissions set for 'group' and 'other' as well
+ as the read/write/execute bits set for the 'user'.
+
+ ffffoooorrrrcccceeee ddddiiiirrrreeeeccccttttoooorrrryyyy
+ This parameter controls what UNIX permission bits can
+ be modified when a Windows NT client is manipulating
+ the UNIX permission on a directory using the native NT
+ security dialog box.
+
+ This parameter is applied as a mask (OR'ed with) to the
+ changed permission bits, thus forcing any bits in this
+ mask that the user may have modified to be on.
+ Essentially, one bits in this mask may be treated as a
+
+
+
+ Page 48 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ 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 000, which
+ allows a user to modify all the user/group/world
+ permissions on a directory without restrictions.
+
+ NNNNooootttteeee 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 leave it set as 0000.
+
+ See also the _d_i_r_e_c_t_o_r_y _s_e_c_u_r_i_t_y _m_a_s_k, _s_e_c_u_r_i_t_y _m_a_s_k,
+ _f_o_r_c_e _s_e_c_u_r_i_t_y _m_o_d_e parameters.
+
+ Default: ffffoooorrrrcccceeee ddddiiiirrrreeeeccccttttoooorrrryyyy sssseeeeccccuuuurrrriiiittttyyyy mmmmooooddddeeee ==== 0000
+
+ Example: ffffoooorrrrcccceeee ddddiiiirrrreeeeccccttttoooorrrryyyy sssseeeeccccuuuurrrriiiittttyyyy mmmmooooddddeeee ==== 777700000000
+
+ ffffoooorrrrcccceeee ggggrrrroooouuuupppp ((((SSSS))))
+ This specifies a UNIX group name that will be assigned
+ as the default primary group for all users connecting
+ to this service. This is useful for sharing files by
+ ensuring that all access to files on service will use
+ the named group for their permissions checking. Thus,
+ by assigning permissions for this group to the files
+ and directories within this service the Samba
+ administrator can restrict or allow sharing of these
+ files.
+
+ In Samba 2.0.5 and above this parameter has extended
+ functionality in the following way. If the group name
+ listed here has a '+' character prepended to it then
+ the current user accessing the share only has the
+ primary group default assigned to this group if they
+ are already assigned as a member of that group. This
+ allows an administrator to decide that only users who
+ are already in a particular group will create files
+ with group ownership set to that group. This gives a
+ finer granularity of ownership assignment. For example,
+ the setting _f_o_r_c_e _g_r_o_u_p = +_s_y_s means that only users
+ who are already in group sys will have their default
+ primary group assigned to sys when accessing this Samba
+ share. All other users will retain their ordinary
+ primary group.
+
+ If the _f_o_r_c_e _u_s_e_r parameter is also set the group
+ specified in _f_o_r_c_e _g_r_o_u_p will override the primary
+ group set in _f_o_r_c_e _u_s_e_r.
+
+ See also _f_o_r_c_e _u_s_e_r.
+
+
+
+ Page 49 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Default: nnnnoooo ffffoooorrrrcccceeeedddd ggggrrrroooouuuupppp
+
+ Example: ffffoooorrrrcccceeee ggggrrrroooouuuupppp ==== aaaaggggrrrroooouuuupppp
+
+ ffffoooorrrrcccceeee sssseeeeccccuuuurrrriiiittttyyyy mmmmooooddddeeee ((((SSSS))))
+ This parameter controls what UNIX permission bits can
+ be modified when a Windows NT client is manipulating
+ the UNIX permission on a file using the native NT
+ security dialog box.
+
+ This parameter is applied as a mask (OR'ed with) to the
+ changed permission bits, thus forcing any bits in this
+ mask that the user may have modified to be on.
+ Essentially, one bits in this 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 0, and
+ allows a user to modify all the user/group/world
+ permissions on a file, with no restrictions.
+
+ NNNNooootttteeee 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 leave this set to 0000.
+
+ See also the _f_o_r_c_e _d_i_r_e_c_t_o_r_y _s_e_c_u_r_i_t_y _m_o_d_e, _d_i_r_e_c_t_o_r_y
+ _s_e_c_u_r_i_t_y _m_a_s_k, _s_e_c_u_r_i_t_y _m_a_s_k parameters.
+
+ Default: ffffoooorrrrcccceeee sssseeeeccccuuuurrrriiiittttyyyy mmmmooooddddeeee ==== 0000
+
+ Example: ffffoooorrrrcccceeee sssseeeeccccuuuurrrriiiittttyyyy mmmmooooddddeeee ==== 777700000000
+
+ ffffoooorrrrcccceeee uuuunnnnkkkknnnnoooowwwwnnnn aaaaccccllll uuuusssseeeerrrr ((((SSSS))))
+ If this parameter is set, a Windows NT ACL that
+ contains an unknown SID (security descriptor, or
+ representation of a user or group id) as the owner or
+ group owner of the file will be silently mapped into
+ the current UNIX uid or gid of the currently connected
+ user.
+
+ This is designed to allow Windows NT clients to copy
+ files and folders containing ACLs that were created
+ locally on the client machine and contain users local
+ to that machine only (no domain users) to be copied to
+ a Samba server (usually with XCOPY /O) and have the
+ unknown userid and groupid of the file owner map to the
+ current connected user. This can only be fixed
+ correctly when winbindd allows arbitrary mapping from
+ any Windows NT SID to a UNIX uid or gid.
+
+
+
+
+ Page 50 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Try using this parameter when XCOPY /O gives an
+ ACCESS_DENIED error.
+
+ See also _f_o_r_c_e _g_r_o_u_p
+
+ Default: FFFFaaaallllsssseeee
+
+ Example: ffffoooorrrrcccceeee uuuunnnnkkkknnnnoooowwwwnnnn aaaaccccllll uuuusssseeeerrrr ==== yyyyeeeessss
+
+ ffffoooorrrrcccceeee uuuusssseeeerrrr ((((SSSS))))
+ This specifies a UNIX user name that will be assigned
+ as the default user for all users connecting to this
+ service. This is useful for sharing files. You should
+ also use it carefully as using it incorrectly can cause
+ security problems.
+
+ This user name only gets used once a connection is
+ established. Thus clients still need to connect as a
+ valid user and supply a valid password. Once connected,
+ all file operations will be performed as the "forced
+ user", no matter what username the client connected as.
+ This can be very useful.
+
+ In Samba 2.0.5 and above this parameter also causes the
+ primary group of the forced user to be used as the
+ primary group for all file activity. Prior to 2.0.5 the
+ primary group was left as the primary group of the
+ connecting user (this was a bug).
+
+ See also _f_o_r_c_e _g_r_o_u_p
+
+ Default: nnnnoooo ffffoooorrrrcccceeeedddd uuuusssseeeerrrr
+
+ Example: ffffoooorrrrcccceeee uuuusssseeeerrrr ==== aaaauuuusssseeeerrrr
+
+ ffffssssttttyyyyppppeeee ((((SSSS))))
+ This parameter allows the administrator to configure
+ the string that specifies the type of filesystem a
+ share is using that is reported by ssssmmmmbbbbdddd((((8888))))
+ when a client queries the filesystem type for a share.
+ The default type is NTFS for compatibility with Windows
+ NT but this can be changed to other strings such as
+ Samba or FAT if required.
+
+ Default: ffffssssttttyyyyppppeeee ==== NNNNTTTTFFFFSSSS
+
+ Example: ffffssssttttyyyyppppeeee ==== SSSSaaaammmmbbbbaaaa
+
+ ggggeeeettttwwwwdddd ccccaaaacccchhhheeee ((((GGGG))))
+ This is a tuning option. When this is enabled a caching
+ algorithm will be used to reduce the time taken for
+ getwd() calls. This can have a significant impact on
+
+
+
+ Page 51 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ performance, especially when the _w_i_d_e _l_i_n_k_s parameter
+ is set to no.
+
+ Default: ggggeeeettttwwwwdddd ccccaaaacccchhhheeee ==== yyyyeeeessss
+
+ ggggrrrroooouuuupppp ((((SSSS))))
+ Synonym for _f_o_r_c_e _g_r_o_u_p.
+
+ gggguuuueeeesssstttt aaaaccccccccoooouuuunnnntttt ((((SSSS))))
+ This is a username which will be used for access to
+ services which are specified as _g_u_e_s_t _o_k (see below).
+ Whatever privileges this user has will be available to
+ any client connecting to the guest service. Typically
+ this user will exist in the password file, but will not
+ have a valid login. The user account "ftp" is often a
+ good choice for this parameter. If a username is
+ specified in a given service, the specified username
+ overrides this one.
+
+ One some systems the default guest account "nobody" may
+ not be able to print. Use another account in this case.
+ You should test this by trying to log in as your guest
+ user (perhaps by using the ssssuuuu ---- command) and trying to
+ print using the system print command such as llllpppprrrr((((1111)))) or
+ llllpppp((((1111)))).
+
+ Default: ssssppppeeeecccciiiiffffiiiieeeedddd aaaatttt ccccoooommmmppppiiiilllleeee ttttiiiimmmmeeee,,,, uuuussssuuuuaaaallllllllyyyy """"nnnnoooobbbbooooddddyyyy""""
+
+ Example: gggguuuueeeesssstttt aaaaccccccccoooouuuunnnntttt ==== ffffttttpppp
+
+ gggguuuueeeesssstttt ooookkkk ((((SSSS))))
+ If this parameter is yes for a service, then no
+ password is required to connect to the service.
+ Privileges will be those of the _g_u_e_s_t _a_c_c_o_u_n_t.
+
+ See the section below on _s_e_c_u_r_i_t_y for more information
+ about this option.
+
+ Default: gggguuuueeeesssstttt ooookkkk ==== nnnnoooo
+
+ gggguuuueeeesssstttt oooonnnnllllyyyy ((((SSSS))))
+ If this parameter is yes for a service, then only guest
+ connections to the service are permitted. This
+ parameter will have no effect if _g_u_e_s_t _o_k is not set
+ for the service.
+
+ See the section below on _s_e_c_u_r_i_t_y for more information
+ about this option.
+
+ Default: gggguuuueeeesssstttt oooonnnnllllyyyy ==== nnnnoooo
+
+ hhhhiiiiddddeeee ddddooootttt ffffiiiilllleeeessss ((((SSSS))))
+
+
+
+ Page 52 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ This is a boolean parameter that controls whether files
+ starting with a dot appear as hidden files.
+
+ Default: hhhhiiiiddddeeee ddddooootttt ffffiiiilllleeeessss ==== yyyyeeeessss
+
+ hhhhiiiiddddeeee ffffiiiilllleeeessss((((SSSS))))
+ This is a list of files or directories that are not
+ visible but are accessible. The DOS 'hidden' attribute
+ is applied to any files or directories that match.
+
+ Each entry in the list must be separated by a '/',
+ which allows spaces to be included in the entry. '*'
+ and '?' can be used to specify multiple files or
+ directories as in DOS wildcards.
+
+ Each entry must be a Unix path, not a DOS path and must
+ not include the Unix directory separator '/'.
+
+ Note that the case sensitivity option is applicable in
+ hiding files.
+
+ Setting this parameter will affect the performance of
+ Samba, as it will be forced to check all files and
+ directories for a match as they are scanned.
+
+ See also _h_i_d_e _d_o_t _f_i_l_e_s, _v_e_t_o _f_i_l_e_s and _c_a_s_e
+ _s_e_n_s_i_t_i_v_e.
+
+ Default: nnnnoooo ffffiiiilllleeee aaaarrrreeee hhhhiiiiddddddddeeeennnn
+
+ Example: hhhhiiiiddddeeee ffffiiiilllleeeessss ====
+ ////....****////DDDDeeeesssskkkkttttooooppppFFFFoooollllddddeeeerrrrDDDDBBBB////TTTTrrrraaaasssshhhhFFFFoooorrrr%%%%mmmm////rrrreeeessssoooouuuurrrrcccceeee....ffffrrrrkkkk////
+
+ The above example is based on files that the Macintosh
+ SMB client (DAVE) available from Thursby
+ creates for internal use,
+ and also still hides all files beginning with a dot.
+
+ hhhhiiiiddddeeee llllooooccccaaaallll uuuusssseeeerrrrssss((((GGGG))))
+ This parameter toggles the hiding of local UNIX users
+ (root, wheel, floppy, etc) from remote clients.
+
+ Default: hhhhiiiiddddeeee llllooooccccaaaallll uuuusssseeeerrrrssss ==== nnnnoooo
+
+ hhhhiiiiddddeeee uuuunnnnrrrreeeeaaaaddddaaaabbbblllleeee ((((SSSS))))
+ This parameter prevents clients from seeing the
+ existance of files that cannot be read. Defaults to
+ off.
+
+ Default: hhhhiiiiddddeeee uuuunnnnrrrreeeeaaaaddddaaaabbbblllleeee ==== nnnnoooo
+
+ hhhhoooommmmeeeeddddiiiirrrr mmmmaaaapppp ((((GGGG))))
+
+
+
+ Page 53 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ If_n_i_s _h_o_m_e_d_i_r is yes, and ssssmmmmbbbbdddd((((8888)))) is also acting as a
+ Win95/98 _l_o_g_o_n _s_e_r_v_e_r then this parameter specifies the
+ NIS (or YP) map from which the server for the user's
+ home directory should be extracted. At present, only
+ the Sun auto.home map format is understood. The form of
+ the map is:
+
+ uuuusssseeeerrrrnnnnaaaammmmeeee sssseeeerrrrvvvveeeerrrr::::////ssssoooommmmeeee////ffffiiiilllleeee////ssssyyyysssstttteeeemmmm
+
+ and the program will extract the servername from before
+ the first ':'. There should probably be a better
+ parsing system that copes with different map formats
+ and also Amd (another automounter) maps.
+
+ NNNNOOOOTTTTEEEE ::::A working NIS client is required on the system
+ for this option to work.
+
+ See also _n_i_s _h_o_m_e_d_i_r , _d_o_m_a_i_n _l_o_g_o_n_s .
+
+ Default: hhhhoooommmmeeeeddddiiiirrrr mmmmaaaapppp ==== <<<>>>
+
+ Example: hhhhoooommmmeeeeddddiiiirrrr mmmmaaaapppp ==== aaaammmmdddd....hhhhoooommmmeeeeddddiiiirrrr
+
+ hhhhoooosssstttt mmmmssssddddffffssss ((((GGGG))))
+ This boolean parameter is only available if Samba has
+ been configured and compiled with the --------wwwwiiiitttthhhh----mmmmssssddddffffssss
+ option. If set to yes, Samba will act as a Dfs server,
+ and allow Dfs-aware clients to browse Dfs trees hosted
+ on the server.
+
+ See also the _m_s_d_f_s _r_o_o_t share level parameter. For
+ more information on setting up a Dfs tree on Samba,
+ refer to msdfs_setup.html
+
+ Default: hhhhoooosssstttt mmmmssssddddffffssss ==== nnnnoooo
+
+ hhhhoooossssttttssss aaaalllllllloooowwww ((((SSSS))))
+ A synonym for this parameter is _a_l_l_o_w _h_o_s_t_s.
+
+ This parameter is a comma, space, or tab delimited set
+ of hosts which are permitted to access a service.
+
+ If specified in the [global] section then it will apply
+ to all services, regardless of whether the individual
+ service has a different setting.
+
+ You can specify the hosts by name or IP number. For
+ example, you could restrict access to only the hosts on
+ a Class C subnet with something like aaaalllllllloooowwww hhhhoooossssttttssss ====
+ 111155550000....222200003333....5555.... . The full syntax of the list is described
+ in the man page _h_o_s_t_s__a_c_c_e_s_s(_5). Note that this man
+ page may not be present on your system, so a brief
+
+
+
+ Page 54 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ description will be given here also.
+
+ Note that the localhost address 127.0.0.1 will always
+ be allowed access unless specifically denied by a _h_o_s_t_s
+ _d_e_n_y option.
+
+ You can also specify hosts by network/netmask pairs and
+ by netgroup names if your system supports netgroups.
+ The EEEEXXXXCCCCEEEEPPPPTTTT keyword can also be used to limit a wildcard
+ list. The following examples may provide some help:
+
+ Example 1: allow all IPs in 150.203.*.*; except one
+
+ hhhhoooossssttttssss aaaalllllllloooowwww ==== 111155550000....222200003333.... EEEEXXXXCCCCEEEEPPPPTTTT 111155550000....222200003333....6666....66666666
+
+ Example 2: allow hosts that match the given
+ network/netmask
+
+ hhhhoooossssttttssss aaaalllllllloooowwww ==== 111155550000....222200003333....11115555....0000////222255555555....222255555555....222255555555....0000
+
+ Example 3: allow a couple of hosts
+
+ hhhhoooossssttttssss aaaalllllllloooowwww ==== llllaaaappppllllaaaannnndddd,,,, aaaarrrrvvvviiiiddddssssjjjjaaaauuuurrrr
+
+ Example 4: allow only hosts in NIS netgroup "foonet",
+ but deny access from one particular host
+
+ hhhhoooossssttttssss aaaalllllllloooowwww ==== @@@@ffffoooooooonnnneeeetttt
+
+ hhhhoooossssttttssss ddddeeeennnnyyyy ==== ppppiiiirrrraaaatttteeee
+
+ Note that access still requires suitable user-level
+ passwords.
+
+ See tttteeeessssttttppppaaaarrrrmmmm((((1111))))
+ for a way of testing your host access to see if it
+ does what you expect.
+
+ Default: nnnnoooonnnneeee ((((iiii....eeee....,,,, aaaallllllll hhhhoooossssttttssss ppppeeeerrrrmmmmiiiitttttttteeeedddd aaaacccccccceeeessssssss))))
+
+ Example: aaaalllllllloooowwww hhhhoooossssttttssss ==== 111155550000....222200003333....5555.... mmmmyyyyhhhhoooosssstttt....mmmmyyyynnnneeeetttt....eeeedddduuuu....aaaauuuu
+
+ hhhhoooossssttttssss ddddeeeennnnyyyy ((((SSSS))))
+ The opposite of _h_o_s_t_s _a_l_l_o_w - hosts listed here are NNNNOOOOTTTT
+ permitted access to services unless the specific
+ services have their own lists to override this one.
+ Where the lists conflict, the _a_l_l_o_w list takes
+ precedence.
+
+ Default: nnnnoooonnnneeee ((((iiii....eeee....,,,, nnnnoooo hhhhoooossssttttssss ssssppppeeeecccciiiiffffiiiiccccaaaallllllllyyyy eeeexxxxcccclllluuuuddddeeeedddd))))
+
+ Example: hhhhoooossssttttssss ddddeeeennnnyyyy ==== 111155550000....222200003333....4444.... bbbbaaaaddddhhhhoooosssstttt....mmmmyyyynnnneeeetttt....eeeedddduuuu....aaaauuuu
+
+
+
+ Page 55 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ hhhhoooossssttttssss eeeeqqqquuuuiiiivvvv ((((GGGG))))
+ If this global parameter is a non-null string, it
+ specifies the name of a file to read for the names of
+ hosts and users who will be allowed access without
+ specifying a password.
+
+ This is not be confused with _h_o_s_t_s _a_l_l_o_w which is
+ about hosts access to services and is more useful for
+ guest services. _h_o_s_t_s _e_q_u_i_v may be useful for NT
+ clients which will not supply passwords to Samba.
+
+ NNNNOOOOTTTTEEEE :::: The use of _h_o_s_t_s _e_q_u_i_v can be a major security
+ hole. This is because you are trusting the PC to supply
+ the correct username. It is very easy to get a PC to
+ supply a false username. I recommend that the _h_o_s_t_s
+ _e_q_u_i_v option be only used if you really know what you
+ are doing, or perhaps on a home network where you trust
+ your spouse and kids. And only if you rrrreeeeaaaallllllllyyyy trust them
+ :-).
+
+ Default: nnnnoooo hhhhoooosssstttt eeeeqqqquuuuiiiivvvvaaaalllleeeennnncccceeeessss
+
+ Example: hhhhoooossssttttssss eeeeqqqquuuuiiiivvvv ==== ////eeeettttcccc////hhhhoooossssttttssss....eeeeqqqquuuuiiiivvvv
+
+ iiiinnnncccclllluuuuddddeeee ((((GGGG))))
+ This allows you to include one config file inside
+ another. The file is included literally, as though
+ typed in place.
+
+ It takes the standard substitutions, except %_u , %_P and
+ %_S.
+
+ Default: nnnnoooo ffffiiiilllleeee iiiinnnncccclllluuuuddddeeeedddd
+
+ Example: iiiinnnncccclllluuuuddddeeee ==== ////uuuussssrrrr////llllooooccccaaaallll////ssssaaaammmmbbbbaaaa////lllliiiibbbb////aaaaddddmmmmiiiinnnn____ssssmmmmbbbb....ccccoooonnnnffff
+
+ iiiinnnnhhhheeeerrrriiiitttt aaaaccccllllssss ((((SSSS))))
+ This parameter can be used to ensure that if default
+ acls exist on parent directories, they are always
+ honored when creating a subdirectory. The default
+ behavior is to use the mode specified when creating the
+ directory. Enabling this option sets the mode to 0777,
+ thus guaranteeing that default directory acls are
+ propagated.
+
+ Default: iiiinnnnhhhheeeerrrriiiitttt aaaaccccllllssss ==== nnnnoooo
+
+ iiiinnnnhhhheeeerrrriiiitttt ppppeeeerrrrmmmmiiiissssssssiiiioooonnnnssss ((((SSSS))))
+ The permissions on new files and directories are
+ normally governed by _c_r_e_a_t_e _m_a_s_k, _d_i_r_e_c_t_o_r_y _m_a_s_k,
+ _f_o_r_c_e _c_r_e_a_t_e _m_o_d_e and _f_o_r_c_e _d_i_r_e_c_t_o_r_y _m_o_d_e but the
+ boolean inherit permissions parameter overrides this.
+
+
+
+ Page 56 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ New directories inherit the mode of the parent
+ directory, including bits such as setgid.
+
+ New files inherit their read/write bits from the parent
+ directory. Their execute bits continue to be determined
+ by _m_a_p _a_r_c_h_i_v_e , _m_a_p _h_i_d_d_e_n and _m_a_p _s_y_s_t_e_m as usual.
+
+ Note that the setuid bit is nnnneeeevvvveeeerrrr set via inheritance
+ (the code explicitly prohibits this).
+
+ This can be particularly useful on large systems with
+ many users, perhaps several thousand, to allow a single
+ [homes] share to be used flexibly by each user.
+
+ See also _c_r_e_a_t_e _m_a_s_k , _d_i_r_e_c_t_o_r_y _m_a_s_k, _f_o_r_c_e _c_r_e_a_t_e
+ _m_o_d_e and _f_o_r_c_e _d_i_r_e_c_t_o_r_y _m_o_d_e .
+
+ Default: iiiinnnnhhhheeeerrrriiiitttt ppppeeeerrrrmmmmiiiissssssssiiiioooonnnnssss ==== nnnnoooo
+
+ iiiinnnntttteeeerrrrffffaaaacccceeeessss ((((GGGG))))
+ This option allows you to override the default network
+ interfaces list that Samba will use for browsing, name
+ registration and other NBT traffic. By default Samba
+ will query the kernel for the list of all active
+ interfaces and use any interfaces except 127.0.0.1 that
+ are broadcast capable.
+
+ The option takes a list of interface strings. Each
+ string can be in any of the following forms:
+
+ o+ a network interface name (such as eth0). This may
+ include shell-like wildcards so eth* will match any
+ interface starting with the substring "eth"
+
+ o+ an IP address. In this case the netmask is determined
+ from the list of interfaces obtained from the kernel
+
+ o+ an IP/mask pair.
+
+ o+ a broadcast/mask pair.
+
+ The "mask" parameters can either be a bit length (such as 24
+ for a C class network) or a full netmask in dotted decimal
+ form.
+
+ The "IP" parameters above can either be a full dotted
+ decimal IP address or a hostname which will be looked up via
+ the OS's normal hostname resolution mechanisms.
+
+ For example, the following line:
+
+ iiiinnnntttteeeerrrrffffaaaacccceeeessss ==== eeeetttthhhh0000 111199992222....111166668888....2222....11110000////22224444 111199992222....111166668888....3333....11110000////222255555555....222255555555....222255555555....0000
+
+
+
+ Page 57 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ would configure three network interfaces corresponding to
+ the eth0 device and IP addresses 192.168.2.10 and
+ 192.168.3.10. The netmasks of the latter two interfaces
+ would be set to 255.255.255.0.
+
+ See also _b_i_n_d _i_n_t_e_r_f_a_c_e_s _o_n_l_y.
+
+ Default: aaaallllllll aaaaccccttttiiiivvvveeee iiiinnnntttteeeerrrrffffaaaacccceeeessss eeeexxxxcccceeeepppptttt 111122227777....0000....0000....1111 tttthhhhaaaatttt aaaarrrreeee
+ bbbbrrrrooooaaaaddddccccaaaasssstttt ccccaaaappppaaaabbbblllleeee
+
+ iiiinnnnvvvvaaaalllliiiidddd uuuusssseeeerrrrssss ((((SSSS))))
+ This is a list of users that should not be allowed to
+ login to this service. This is really a ppppaaaarrrraaaannnnooooiiiidddd check
+ to absolutely ensure an improper setting does not
+ breach your security.
+
+ A name starting with a '@' is interpreted as an NIS
+ netgroup first (if your system supports NIS), and then
+ as a UNIX group if the name was not found in the NIS
+ netgroup database.
+
+ A name starting with '+' is interpreted only by looking
+ in the UNIX group database. A name starting with '&' is
+ interpreted only by looking in the NIS netgroup
+ database (this requires NIS to be working on your
+ system). The characters '+' and '&' may be used at the
+ start of the name in either order so the value +&_g_r_o_u_p
+ means check the UNIX group database, followed by the
+ NIS netgroup database, and the value &+_g_r_o_u_p means
+ check the NIS netgroup database, followed by the UNIX
+ group database (the same as the '@' prefix).
+
+ The current servicename is substituted for %_S. This is
+ useful in the [homes] section.
+
+ See also _v_a_l_i_d _u_s_e_r_s .
+
+ Default: nnnnoooo iiiinnnnvvvvaaaalllliiiidddd uuuusssseeeerrrrssss
+
+ Example: iiiinnnnvvvvaaaalllliiiidddd uuuusssseeeerrrrssss ==== rrrrooooooootttt ffffrrrreeeedddd aaaaddddmmmmiiiinnnn @@@@wwwwhhhheeeeeeeellll
+
+ kkkkeeeeeeeeppppaaaalllliiiivvvveeee ((((GGGG))))
+ The value of the parameter (an integer) represents the
+ number of seconds between _k_e_e_p_a_l_i_v_e packets. If this
+ parameter is zero, no keepalive packets will be sent.
+ Keepalive packets, if sent, allow the server to tell
+ whether a client is still present and responding.
+
+ Keepalives should, in general, not be needed if the
+ socket being used has the SO_KEEPALIVE attribute set on
+ it (see _s_o_c_k_e_t _o_p_t_i_o_n_s). Basically you should only use
+ this option if you strike difficulties.
+
+
+
+ Page 58 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Default: kkkkeeeeeeeeppppaaaalllliiiivvvveeee ==== 333300000000
+
+ Example: kkkkeeeeeeeeppppaaaalllliiiivvvveeee ==== 666600000000
+
+ kkkkeeeerrrrnnnneeeellll oooopppplllloooocccckkkkssss ((((GGGG))))
+ For UNIXes that support kernel based _o_p_l_o_c_k_s (currently
+ only IRIX and the Linux 2.4 kernel), this parameter
+ allows the use of them to be turned on or off.
+
+ Kernel oplocks support allows Samba _o_p_l_o_c_k_s to be
+ broken whenever a local UNIX process or NFS operation
+ accesses a file that ssssmmmmbbbbdddd((((8888))))
+ has oplocked. This allows complete data consistency
+ between SMB/CIFS, NFS and local file access (and is a
+ vvvveeeerrrryyyy cool feature :-).
+
+ This parameter defaults to on, but is translated to a
+ no-op on systems that no not have the necessary kernel
+ support. You should never need to touch this
+ parameter.
+
+ See also the _o_p_l_o_c_k_s and _l_e_v_e_l_2 _o_p_l_o_c_k_s parameters.
+
+ Default: kkkkeeeerrrrnnnneeeellll oooopppplllloooocccckkkkssss ==== yyyyeeeessss
+
+ llllaaaannnnmmmmaaaannnn aaaauuuutttthhhh ((((GGGG))))
+ This parameter determines whether or not smbd will
+ attempt to authenticate users using the LANMAN password
+ hash. If disabled, only clients which support NT
+ password hashes (e.g. Windows NT/2000 clients,
+ smbclient, etc... but not Windows 95/98 or the MS DOS
+ network client) will be able to connect to the Samba
+ host.
+
+ Default : llllaaaannnnmmmmaaaannnn aaaauuuutttthhhh ==== yyyyeeeessss
+
+ llllaaaarrrrggggeeee rrrreeeeaaaaddddwwwwrrrriiiitttteeee ((((GGGG))))
+ This parameter determines whether or not smbd supports
+ the new 64k streaming read and write varient SMB
+ requests introduced with Windows 2000. Note that due to
+ Windows 2000 client redirector bugs this requires Samba
+ to be running on a 64-bit capable operating system such
+ as IRIX, Solaris or a Linux 2.4 kernel. Can improve
+ performance by 10% with Windows 2000 clients. Defaults
+ to on. Windows NT 4.0 only supports read version of
+ this call, and ignores the write version.
+
+ Default : llllaaaarrrrggggeeee rrrreeeeaaaaddddwwwwrrrriiiitttteeee ==== yyyyeeeessss
+
+ llllddddaaaapppp aaaaddddmmmmiiiinnnn ddddnnnn ((((GGGG))))
+ This parameter is only available if Samba has been
+ configure to include the --------wwwwiiiitttthhhh----llllddddaaaappppssssaaaammmm option at
+
+
+
+ Page 59 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ compile time. This option should be considered
+ experimental and under active development.
+
+ The _l_d_a_p _a_d_m_i_n _d_n defines the Distinguished Name (DN)
+ name used by Samba to contact the ldap server when
+ retreiving user account information. The _l_d_a_p _a_d_m_i_n _d_n
+ is used in conjunction with the admin dn password
+ stored in the _p_r_i_v_a_t_e/_s_e_c_r_e_t_s._t_d_b file. See the
+ ssssmmmmbbbbppppaaaasssssssswwwwdddd((((8888)))) man page for more information on how to
+ accmplish this.
+
+ Default : nnnnoooonnnneeee
+
+ llllddddaaaapppp ffffiiiilllltttteeeerrrr ((((GGGG))))
+ This parameter is only available if Samba has been
+ configure to include the --------wwwwiiiitttthhhh----llllddddaaaappppssssaaaammmm option at
+ compile time. This option should be considered
+ experimental and under active development.
+
+ This parameter specifies the RFC 2254 compliant LDAP
+ search filter. The default is to match the login name
+ with the uid attribute for all entries matching the
+ sambaAccount objectclass. Note that this filter should
+ only return one entry.
+
+ Default : llllddddaaaapppp ffffiiiilllltttteeeerrrr ====
+ ((((&&&&((((uuuuiiiidddd====%%%%uuuu))))((((oooobbbbjjjjeeeeccccttttccccllllaaaassssssss====ssssaaaammmmbbbbaaaaAAAAccccccccoooouuuunnnntttt))))))))
+
+ llllddddaaaapppp ppppoooorrrrtttt ((((GGGG))))
+ This parameter is only available if Samba has been
+ configure to include the --------wwwwiiiitttthhhh----llllddddaaaappppssssaaaammmm option at
+ compile time. This option should be considered
+ experimental and under active development.
+
+ This option is used to control the tcp port number used
+ to contact the _l_d_a_p _s_e_r_v_e_r. The default is to use the
+ stand LDAPS port 636.
+
+ See Also: ldap ssl
+
+ Default : llllddddaaaapppp ppppoooorrrrtttt ==== 666633336666 ;;;; iiiiffff llllddddaaaapppp ssssssssllll ==== oooonnnn
+
+ Default : llllddddaaaapppp ppppoooorrrrtttt ==== 333388889999 ;;;; iiiiffff llllddddaaaapppp ssssssssllll ==== ooooffffffff
+
+ llllddddaaaapppp sssseeeerrrrvvvveeeerrrr ((((GGGG))))
+ This parameter is only available if Samba has been
+ configure to include the --------wwwwiiiitttthhhh----llllddddaaaappppssssaaaammmm option at
+ compile time. This option should be considered
+ experimental and under active development.
+
+ This parameter should contains the FQDN of the ldap
+ directory server which should be queried to locate user
+
+
+
+ Page 60 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ account information.
+
+ Default : llllddddaaaapppp sssseeeerrrrvvvveeeerrrr ==== llllooooccccaaaallllhhhhoooosssstttt
+
+ llllddddaaaapppp ssssssssllll ((((GGGG))))
+ This parameter is only available if Samba has been
+ configure to include the --------wwwwiiiitttthhhh----llllddddaaaappppssssaaaammmm option at
+ compile time. This option should be considered
+ experimental and under active development.
+
+ This option is used to define whether or not Samba
+ should use SSL when connecting to the _l_d_a_p _s_e_r_v_e_r. This
+ is NNNNOOOOTTTT related to Samba SSL support which is enabled by
+ specifying the --------wwwwiiiitttthhhh----ssssssssllll option to the _c_o_n_f_i_g_u_r_e
+ script (see _s_s_l).
+
+ The _l_d_a_p _s_s_l can be set to one of three values: (a) on
+ - Always use SSL when contacting the _l_d_a_p _s_e_r_v_e_r, (b)
+ off - Never use SSL when querying the directory, or (c)
+ start_tls - Use the LDAPv3 StartTLS extended operation
+ (RFC2830) for communicating with the directory server.
+
+ Default : llllddddaaaapppp ssssssssllll ==== oooonnnn
+
+ llllddddaaaapppp ssssuuuuffffffffiiiixxxx ((((GGGG))))
+ This parameter is only available if Samba has been
+ configure to include the --------wwwwiiiitttthhhh----llllddddaaaappppssssaaaammmm option at
+ compile time. This option should be considered
+ experimental and under active development.
+
+ Default : nnnnoooonnnneeee
+
+ lllleeeevvvveeeellll2222 oooopppplllloooocccckkkkssss ((((SSSS))))
+ This parameter controls whether Samba supports level2
+ (read-only) oplocks on a share.
+
+ Level2, or read-only oplocks allow Windows NT clients
+ that have an oplock on a file to downgrade from a
+ read-write oplock to a read-only oplock once a second
+ client opens the file (instead of releasing all oplocks
+ on a second open, as in traditional, exclusive
+ oplocks). This allows all openers of the file that
+ support level2 oplocks to cache the file for read-ahead
+ only (ie. they may not cache writes or lock requests)
+ and increases performance for many accesses of files
+ that are not commonly written (such as application .EXE
+ files).
+
+ Once one of the clients which have a read-only oplock
+ writes to the file all clients are notified (no reply
+ is needed or waited for) and told to break their
+ oplocks to "none" and delete any read-ahead caches.
+
+
+
+ Page 61 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ It is recommended that this parameter be turned on to
+ speed access to shared executables.
+
+ For more discussions on level2 oplocks see the CIFS
+ spec.
+
+ Currently, if _k_e_r_n_e_l _o_p_l_o_c_k_s are supported then level2
+ oplocks are not granted (even if this parameter is set
+ to yes). Note also, the _o_p_l_o_c_k_s parameter must be set
+ to yes on this share in order for this parameter to
+ have any effect.
+
+ See also the _o_p_l_o_c_k_s and _k_e_r_n_e_l _o_p_l_o_c_k_s parameters.
+
+ Default: lllleeeevvvveeeellll2222 oooopppplllloooocccckkkkssss ==== yyyyeeeessss
+
+ llllmmmm aaaannnnnnnnoooouuuunnnncccceeee ((((GGGG))))
+ This parameter determines if nnnnmmmmbbbbdddd((((8888)))) will produce
+ Lanman announce broadcasts that are needed by OS/2
+ clients in order for them to see the Samba server in
+ their browse list. This parameter can have three
+ values, yes, no, or auto. The default is auto. If set
+ to no Samba will never produce these broadcasts. If set
+ to yes Samba will produce Lanman announce broadcasts at
+ a frequency set by the parameter _l_m _i_n_t_e_r_v_a_l. If set to
+ auto Samba will not send Lanman announce broadcasts by
+ default but will listen for them. If it hears such a
+ broadcast on the wire it will then start sending them
+ at a frequency set by the parameter _l_m _i_n_t_e_r_v_a_l.
+
+ See also _l_m _i_n_t_e_r_v_a_l .
+
+ Default: llllmmmm aaaannnnnnnnoooouuuunnnncccceeee ==== aaaauuuuttttoooo
+
+ Example: llllmmmm aaaannnnnnnnoooouuuunnnncccceeee ==== yyyyeeeessss
+
+ llllmmmm iiiinnnntttteeeerrrrvvvvaaaallll ((((GGGG))))
+ If Samba is set to produce Lanman announce broadcasts
+ needed by OS/2 clients (see the _l_m _a_n_n_o_u_n_c_e parameter)
+ then this parameter defines the frequency in seconds
+ with which they will be made. If this is set to zero
+ then no Lanman announcements will be made despite the
+ setting of the _l_m _a_n_n_o_u_n_c_e parameter.
+
+ See also _l_m _a_n_n_o_u_n_c_e.
+
+ Default: llllmmmm iiiinnnntttteeeerrrrvvvvaaaallll ==== 66660000
+
+ Example: llllmmmm iiiinnnntttteeeerrrrvvvvaaaallll ==== 111122220000
+
+ llllooooaaaadddd pppprrrriiiinnnntttteeeerrrrssss ((((GGGG))))
+ A boolean variable that controls whether all printers
+
+
+
+ Page 62 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ in the printcap will be loaded for browsing by default.
+ See the printers section for more details.
+
+ Default: llllooooaaaadddd pppprrrriiiinnnntttteeeerrrrssss ==== yyyyeeeessss
+
+ llllooooccccaaaallll mmmmaaaasssstttteeeerrrr ((((GGGG))))
+ This option allows nnnnmmmmbbbbdddd((((8888)))) to try and become a local
+ master browser on a subnet. If set to no then nnnnmmmmbbbbdddd
+ will not attempt to become a local master browser on a
+ subnet and will also lose in all browsing elections. By
+ default this value is set to yes. Setting this value to
+ yes doesn't mean that Samba will bbbbeeeeccccoooommmmeeee the local
+ master browser on a subnet, just that nnnnmmmmbbbbdddd will
+ ppppaaaarrrrttttiiiicccciiiippppaaaatttteeee in elections for local master browser.
+
+ Setting this value to no will cause nnnnmmmmbbbbdddd nnnneeeevvvveeeerrrr to
+ become a local master browser.
+
+ Default: llllooooccccaaaallll mmmmaaaasssstttteeeerrrr ==== yyyyeeeessss
+
+ lllloooocccckkkk ddddiiiirrrr ((((GGGG))))
+ Synonym for _l_o_c_k _d_i_r_e_c_t_o_r_y.
+
+ lllloooocccckkkk ddddiiiirrrreeeeccccttttoooorrrryyyy ((((GGGG))))
+ This option specifies the directory where lock files
+ will be placed. The lock files are used to implement
+ the _m_a_x _c_o_n_n_e_c_t_i_o_n_s option.
+
+ Default: lllloooocccckkkk ddddiiiirrrreeeeccccttttoooorrrryyyy ==== $$$${{{{pppprrrreeeeffffiiiixxxx}}}}////vvvvaaaarrrr////lllloooocccckkkkssss
+
+ Example: lllloooocccckkkk ddddiiiirrrreeeeccccttttoooorrrryyyy ==== ////vvvvaaaarrrr////rrrruuuunnnn////ssssaaaammmmbbbbaaaa////lllloooocccckkkkssss
+
+ lllloooocccckkkk ssssppppiiiinnnn ccccoooouuuunnnntttt ((((GGGG))))
+ This parameter controls the number of times that smbd
+ should attempt to gain a byte range lock on the behalf
+ of a client request. Experiments have shown that
+ Windows 2k servers do not reply with a failure if the
+ lock could not be immediately granted, but try a few
+ more times in case the lock could later be aquired.
+ This behavior is used to support PC database formats
+ such as MS Access and FoxPro.
+
+ Default: lllloooocccckkkk ssssppppiiiinnnn ccccoooouuuunnnntttt ==== 2222
+
+ lllloooocccckkkk ssssppppiiiinnnn ttttiiiimmmmeeee ((((GGGG))))
+ The time in microseconds that smbd should pause before
+ attempting to gain a failed lock. See _l_o_c_k _s_p_i_n _c_o_u_n_t
+ for more details.
+
+ Default: lllloooocccckkkk ssssppppiiiinnnn ttttiiiimmmmeeee ==== 11110000
+
+ lllloooocccckkkkiiiinnnngggg ((((SSSS))))
+
+
+
+ Page 63 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ This controls whether or not locking will be performed
+ by the server in response to lock requests from the
+ client.
+
+ If lllloooocccckkkkiiiinnnngggg ==== nnnnoooo, all lock and unlock requests will
+ appear to succeed and all lock queries will report that
+ the file in question is available for locking.
+
+ If lllloooocccckkkkiiiinnnngggg ==== yyyyeeeessss, real locking will be performed by the
+ server.
+
+ This option mmmmaaaayyyy be useful for read-only filesystems
+ which mmmmaaaayyyy not need locking (such as CDROM drives),
+ although setting this parameter of no is not really
+ recommended even in this case.
+
+ Be careful about disabling locking either globally or
+ in a specific service, as lack of locking may result in
+ data corruption. You should never need to set this
+ parameter.
+
+ Default: lllloooocccckkkkiiiinnnngggg ==== yyyyeeeessss
+
+ lllloooogggg ffffiiiilllleeee ((((GGGG))))
+ This option allows you to override the name of the
+ Samba log file (also known as the debug file).
+
+ This option takes the standard substitutions, allowing
+ you to have separate log files for each user or
+ machine.
+
+ Example: lllloooogggg ffffiiiilllleeee ==== ////uuuussssrrrr////llllooooccccaaaallll////ssssaaaammmmbbbbaaaa////vvvvaaaarrrr////lllloooogggg....%%%%mmmm
+
+ lllloooogggg lllleeeevvvveeeellll ((((GGGG))))
+ The value of the parameter (an integer) allows the
+ debug level (logging level) to be specified in the
+ _s_m_b._c_o_n_f 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: lllloooogggg lllleeeevvvveeeellll ==== 3333
+
+ llllooooggggoooonnnn ddddrrrriiiivvvveeee ((((GGGG))))
+ This parameter specifies the local path to which the
+ home directory will be connected (see _l_o_g_o_n _h_o_m_e) and
+ is only used by NT Workstations.
+
+ Note that this option is only useful if Samba is set up
+ as a logon server.
+
+
+
+
+ Page 64 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Default: llllooooggggoooonnnn ddddrrrriiiivvvveeee ==== zzzz::::
+
+ Example: llllooooggggoooonnnn ddddrrrriiiivvvveeee ==== hhhh::::
+
+ llllooooggggoooonnnn hhhhoooommmmeeee ((((GGGG))))
+ This parameter specifies the home directory location
+ when a Win95/98 or NT Workstation logs into a Samba
+ PDC. It allows you to do
+
+ C:\> NNNNEEEETTTT UUUUSSSSEEEE HHHH:::: ////HHHHOOOOMMMMEEEE
+
+ from a command prompt, for example.
+
+ This option takes the standard substitutions, allowing
+ you to have separate logon scripts for each user or
+ machine.
+
+ This parameter can be used with Win9X workstations to
+ ensure that roaming profiles are stored in a
+ subdirectory of the user's home directory. This is done
+ in the following way:
+
+ llllooooggggoooonnnn hhhhoooommmmeeee ==== \\\\\\\\%%%%NNNN\\\\%%%%UUUU\\\\pppprrrrooooffffiiiilllleeee
+
+ This tells Samba to return the above string, with
+ substitutions made when a client requests the info,
+ generally in a NetUserGetInfo request. Win9X clients
+ truncate the info to \\server\share when a user does
+ nnnneeeetttt uuuusssseeee ////hhhhoooommmmeeee but use the whole string when dealing
+ with profiles.
+
+ Note that in prior versions of Samba, the _l_o_g_o_n _p_a_t_h
+ was returned rather than _l_o_g_o_n _h_o_m_e. This broke nnnneeeetttt uuuusssseeee
+ ////hhhhoooommmmeeee but allowed profiles outside the home directory.
+ The current implementation is correct, and can be used
+ for profiles if you use the above trick.
+
+ This option is only useful if Samba is set up as a
+ logon server.
+
+ Default: llllooooggggoooonnnn hhhhoooommmmeeee ==== """"\\\\\\\\%%%%NNNN\\\\%%%%UUUU""""
+
+ Example: llllooooggggoooonnnn hhhhoooommmmeeee ==== """"\\\\\\\\rrrreeeemmmmooootttteeee____ssssmmmmbbbb____sssseeeerrrrvvvveeeerrrr\\\\%%%%UUUU""""
+
+ llllooooggggoooonnnn ppppaaaatttthhhh ((((GGGG))))
+ This parameter specifies the home directory where
+ roaming profiles (NTuser.dat etc files for Windows NT)
+ are stored. Contrary to previous versions of these
+ manual pages, it has nothing to do with Win 9X roaming
+ profiles. To find out how to handle roaming profiles
+ for Win 9X system, see the _l_o_g_o_n _h_o_m_e parameter.
+
+
+
+
+ Page 65 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ This option takes the standard substitutions, allowing
+ you to have separate logon scripts for each user or
+ machine. It also specifies the directory from which the
+ "Application Data", (_d_e_s_k_t_o_p, _s_t_a_r_t _m_e_n_u, _n_e_t_w_o_r_k
+ _n_e_i_g_h_b_o_r_h_o_o_d, _p_r_o_g_r_a_m_s and other folders, and their
+ contents, are loaded and displayed on your Windows NT
+ client.
+
+ The share and the path must be readable by the user for
+ the preferences and directories to be loaded onto the
+ Windows NT client. The share must be writeable when the
+ user logs in for the first time, in order that the
+ Windows NT client can create the NTuser.dat and other
+ directories.
+
+ Thereafter, the directories and any of the contents
+ can, if required, be made read-only. It is not
+ advisable that the NTuser.dat file be made read-only -
+ rename it to NTuser.man to achieve the desired effect
+ (a MMMMAAAANNNNdatory profile).
+
+ Windows clients can sometimes maintain a connection to
+ the [homes] share, even though there is no user logged
+ in. Therefore, it is vital that the logon path does not
+ include a reference to the homes share (i.e. setting
+ this parameter to \%N\%U\profile_path will cause
+ problems).
+
+ This option takes the standard substitutions, allowing
+ you to have separate logon scripts for each user or
+ machine.
+
+ Note that this option is only useful if Samba is set up
+ as a logon server.
+
+ Default: llllooooggggoooonnnn ppppaaaatttthhhh ==== \\\\\\\\%%%%NNNN\\\\%%%%UUUU\\\\pppprrrrooooffffiiiilllleeee
+
+ Example: llllooooggggoooonnnn ppppaaaatttthhhh ==== \\\\\\\\PPPPRRRROOOOFFFFIIIILLLLEEEESSSSEEEERRRRVVVVEEEERRRR\\\\PPPPRRRROOOOFFFFIIIILLLLEEEE\\\\%%%%UUUU
+
+ llllooooggggoooonnnn ssssccccrrrriiiipppptttt ((((GGGG))))
+ This parameter specifies the batch file (.bat) or NT
+ command file (.cmd) to be downloaded and run on a
+ machine when a user successfully logs in. The file must
+ contain the DOS style CR/LF line endings. Using a DOS-
+ style editor to create the file is recommended.
+
+ The script must be a relative path to the [netlogon]
+ service. If the [netlogon] service specifies a _p_a_t_h of
+ /_u_s_r/_l_o_c_a_l/_s_a_m_b_a/_n_e_t_l_o_g_o_n , and llllooooggggoooonnnn ssssccccrrrriiiipppptttt ====
+ SSSSTTTTAAAARRRRTTTTUUUUPPPP....BBBBAAAATTTT, then the file that will be downloaded is:
+
+ /_u_s_r/_l_o_c_a_l/_s_a_m_b_a/_n_e_t_l_o_g_o_n/_S_T_A_R_T_U_P._B_A_T
+
+
+
+ Page 66 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ The contents of the batch file are entirely your
+ choice. A suggested command would be to add NNNNEEEETTTT TTTTIIIIMMMMEEEE
+ \\\\\\\\SSSSEEEERRRRVVVVEEEERRRR ////SSSSEEEETTTT ////YYYYEEEESSSS, to force every machine to
+ synchronize clocks with the same time server. Another
+ use would be to add NNNNEEEETTTT UUUUSSSSEEEE UUUU:::: \\\\\\\\SSSSEEEERRRRVVVVEEEERRRR\\\\UUUUTTTTIIIILLLLSSSS for
+ commonly used utilities, or NNNNEEEETTTT UUUUSSSSEEEE QQQQ::::
+ \\\\\\\\SSSSEEEERRRRVVVVEEEERRRR\\\\IIIISSSSOOOO9999000000001111____QQQQAAAA for example.
+
+ Note that it is particularly important not to allow
+ write access to the [netlogon] share, or to grant users
+ write permission on the batch files in a secure
+ environment, as this would allow the batch files to be
+ arbitrarily modified and security to be breached.
+
+ This option takes the standard substitutions, allowing
+ you to have separate logon scripts for each user or
+ machine.
+
+ This option is only useful if Samba is set up as a
+ logon server.
+
+ Default: nnnnoooo llllooooggggoooonnnn ssssccccrrrriiiipppptttt ddddeeeeffffiiiinnnneeeedddd
+
+ Example: llllooooggggoooonnnn ssssccccrrrriiiipppptttt ==== ssssccccrrrriiiippppttttssss\\\\%%%%UUUU....bbbbaaaatttt
+
+ llllppppppppaaaauuuusssseeee ccccoooommmmmmmmaaaannnndddd ((((SSSS))))
+ This parameter specifies the command to be executed on
+ the server host in order to stop printing or spooling a
+ specific print job.
+
+ This command should be a program or script which takes
+ a printer name and job number to pause the print job.
+ One way of implementing this is by using job
+ priorities, where jobs having a too low priority won't
+ be sent to the printer.
+
+ If a %_p is given then the printer name is put in its
+ place. A %_j is replaced with the job number (an
+ integer). On HPUX (see _p_r_i_n_t_i_n_g=_h_p_u_x ), if the -_p%_p
+ option is added to the lpq command, the job will show
+ up with the correct status, i.e. if the job priority is
+ lower than the set fence priority it will have the
+ PAUSED status, whereas if the priority is equal or
+ higher it will have the SPOOLED or PRINTING status.
+
+ Note that it is good practice to include the absolute
+ path in the lppause command as the PATH may not be
+ available to the server.
+
+ See also the _p_r_i_n_t_i_n_g parameter.
+
+ Default: Currently no default value is given to this
+
+
+
+ Page 67 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ string, unless the value of the _p_r_i_n_t_i_n_g parameter is
+ SYSV, in which case the default is :
+
+ llllpppp ----iiii %%%%pppp----%%%%jjjj ----HHHH hhhhoooolllldddd
+
+ or if the value of the _p_r_i_n_t_i_n_g parameter is SOFTQ,
+ then the default is:
+
+ qqqqssssttttaaaatttt ----ssss ----jjjj%%%%jjjj ----hhhh
+
+ Example for HPUX: llllppppppppaaaauuuusssseeee ccccoooommmmmmmmaaaannnndddd ==== ////uuuussssrrrr////bbbbiiiinnnn////llllppppaaaalllltttt %%%%pppp----
+ %%%%jjjj ----pppp0000
+
+ llllppppqqqq ccccaaaacccchhhheeee ttttiiiimmmmeeee ((((GGGG))))
+ This controls how long lpq info will be cached for to
+ prevent the llllppppqqqq command being called too often. A
+ separate cache is kept for each variation of the llllppppqqqq
+ command used by the system, so if you use different llllppppqqqq
+ commands for different users then they won't share
+ cache information.
+
+ The cache files are stored in /_t_m_p/_l_p_q._x_x_x_x where xxxx
+ is a hash of the llllppppqqqq command in use.
+
+ The default is 10 seconds, meaning that the cached
+ results of a previous identical llllppppqqqq command will be
+ used if the cached data is less than 10 seconds old. A
+ large value may be advisable if your llllppppqqqq command is
+ very slow.
+
+ A value of 0 will disable caching completely.
+
+ See also the _p_r_i_n_t_i_n_g parameter.
+
+ Default: llllppppqqqq ccccaaaacccchhhheeee ttttiiiimmmmeeee ==== 11110000
+
+ Example: llllppppqqqq ccccaaaacccchhhheeee ttttiiiimmmmeeee ==== 33330000
+
+ llllppppqqqq ccccoooommmmmmmmaaaannnndddd ((((SSSS))))
+ This parameter specifies the command to be executed on
+ the server host in order to obtain llllppppqqqq -style printer
+ status information.
+
+ This command should be a program or script which takes
+ a printer name as its only parameter and outputs
+ printer status information.
+
+ Currently nine styles of printer status information are
+ supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS,
+ and SOFTQ. This covers most UNIX systems. You control
+ which type is expected using the _p_r_i_n_t_i_n_g = option.
+
+
+
+
+ Page 68 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Some clients (notably Windows for Workgroups) may not
+ correctly send the connection number for the printer
+ they are requesting status information about. To get
+ around this, the server reports on the first printer
+ service connected to by the client. This only happens
+ if the connection number sent is invalid.
+
+ If a %_p is given then the printer name is put in its
+ place. Otherwise it is placed at the end of the
+ command.
+
+ Note that it is good practice to include the absolute
+ path in the _l_p_q _c_o_m_m_a_n_d as the $$$$PPPPAAAATTTTHHHH may not be
+ available to the server. When compiled with the CUPS
+ libraries, no _l_p_q _c_o_m_m_a_n_d is needed because smbd will
+ make a library call to obtain the print queue listing.
+
+ See also the _p_r_i_n_t_i_n_g parameter.
+
+ Default: ddddeeeeppppeeeennnnddddssss oooonnnn tttthhhheeee sssseeeettttttttiiiinnnngggg ooooffff _p_r_i_n_t_i_n_g
+
+ Example: llllppppqqqq ccccoooommmmmmmmaaaannnndddd ==== ////uuuussssrrrr////bbbbiiiinnnn////llllppppqqqq ----PPPP%%%%pppp
+
+ llllpppprrrreeeessssuuuummmmeeee ccccoooommmmmmmmaaaannnndddd ((((SSSS))))
+ This parameter specifies the command to be executed on
+ the server host in order to restart or continue
+ printing or spooling a specific print job.
+
+ This command should be a program or script which takes
+ a printer name and job number to resume the print job.
+ See also the _l_p_p_a_u_s_e _c_o_m_m_a_n_d parameter.
+
+ If a %_p is given then the printer name is put in its
+ place. A %_j is replaced with the job number (an
+ integer).
+
+ Note that it is good practice to include the absolute
+ path in the _l_p_r_e_s_u_m_e _c_o_m_m_a_n_d as the PATH may not be
+ available to the server.
+
+ See also the _p_r_i_n_t_i_n_g parameter.
+
+ Default: Currently no default value is given to this
+ string, unless the value of the _p_r_i_n_t_i_n_g parameter is
+ SYSV, in which case the default is :
+
+ llllpppp ----iiii %%%%pppp----%%%%jjjj ----HHHH rrrreeeessssuuuummmmeeee
+
+ or if the value of the _p_r_i_n_t_i_n_g parameter is SOFTQ,
+ then the default is:
+
+ qqqqssssttttaaaatttt ----ssss ----jjjj%%%%jjjj ----rrrr
+
+
+
+ Page 69 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Example for HPUX: llllpppprrrreeeessssuuuummmmeeee ccccoooommmmmmmmaaaannnndddd ==== ////uuuussssrrrr////bbbbiiiinnnn////llllppppaaaalllltttt
+ %%%%pppp----%%%%jjjj ----pppp2222
+
+ llllpppprrrrmmmm ccccoooommmmmmmmaaaannnndddd ((((SSSS))))
+ This parameter specifies the command to be executed on
+ the server host in order to delete a print job.
+
+ This command should be a program or script which takes
+ a printer name and job number, and deletes the print
+ job.
+
+ If a %_p is given then the printer name is put in its
+ place. A %_j is replaced with the job number (an
+ integer).
+
+ Note that it is good practice to include the absolute
+ path in the _l_p_r_m _c_o_m_m_a_n_d as the PATH may not be
+ available to the server.
+
+ See also the _p_r_i_n_t_i_n_g parameter.
+
+ Default: ddddeeeeppppeeeennnnddddssss oooonnnn tttthhhheeee sssseeeettttttttiiiinnnngggg ooooffff _p_r_i_n_t_i_n_g
+
+ Example 1: llllpppprrrrmmmm ccccoooommmmmmmmaaaannnndddd ==== ////uuuussssrrrr////bbbbiiiinnnn////llllpppprrrrmmmm ----PPPP%%%%pppp %%%%jjjj
+
+ Example 2: llllpppprrrrmmmm ccccoooommmmmmmmaaaannnndddd ==== ////uuuussssrrrr////bbbbiiiinnnn////ccccaaaannnncccceeeellll %%%%pppp----%%%%jjjj
+
+ mmmmaaaacccchhhhiiiinnnneeee ppppaaaasssssssswwwwoooorrrrdddd ttttiiiimmmmeeeeoooouuuutttt ((((GGGG))))
+ If a Samba server is a member of a Windows NT Domain
+ (see the security = domain) parameter) then
+ periodically a running smbd(8) process will try and
+ change the MACHINE ACCOUNT PASSWORD stored in the TDB
+ called _p_r_i_v_a_t_e/_s_e_c_r_e_t_s._t_d_b . This parameter specifies
+ how often this password will be changed, in seconds.
+ The default is one week (expressed in seconds), the
+ same as a Windows NT Domain member server.
+
+ See also ssssmmmmbbbbppppaaaasssssssswwwwdddd((((8888))))
+ and the security = domain) parameter.
+
+ Default: mmmmaaaacccchhhhiiiinnnneeee ppppaaaasssssssswwwwoooorrrrdddd ttttiiiimmmmeeeeoooouuuutttt ==== 666600004444888800000000
+
+ mmmmaaaaggggiiiicccc oooouuuuttttppppuuuutttt ((((SSSS))))
+ This parameter specifies the name of a file which will
+ contain output created by a magic script (see the _m_a_g_i_c
+ _s_c_r_i_p_t parameter below).
+
+ Warning: If two clients use the same _m_a_g_i_c _s_c_r_i_p_t in
+ the same directory the output file content is
+ undefined.
+
+ Default: mmmmaaaaggggiiiicccc oooouuuuttttppppuuuutttt ==== <<<>>>....oooouuuutttt
+
+
+
+ Page 70 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Example: mmmmaaaaggggiiiicccc oooouuuuttttppppuuuutttt ==== mmmmyyyyffffiiiilllleeee....ttttxxxxtttt
+
+ mmmmaaaaggggiiiicccc ssssccccrrrriiiipppptttt ((((SSSS))))
+ This parameter specifies the name of a file which, if
+ opened, will be executed by the server when the file is
+ closed. This allows a UNIX script to be sent to the
+ Samba host and executed on behalf of the connected
+ user.
+
+ Scripts executed in this way will be deleted upon
+ completion assuming that the user has the appropriate
+ level of privilege and the file permissions allow the
+ deletion.
+
+ If the script generates output, output will be sent to
+ the file specified by the _m_a_g_i_c _o_u_t_p_u_t parameter (see
+ above).
+
+ Note that some shells are unable to interpret scripts
+ containing CR/LF instead of CR as the end-of-line
+ marker. Magic scripts must be executable aaaassss iiiissss on the
+ host, which for some hosts and some shells will require
+ filtering at the DOS end.
+
+ Magic scripts are EEEEXXXXPPPPEEEERRRRIIIIMMMMEEEENNNNTTTTAAAALLLL and should NNNNOOOOTTTT be relied
+ upon.
+
+ Default: NNNNoooonnnneeee.... MMMMaaaaggggiiiicccc ssssccccrrrriiiippppttttssss ddddiiiissssaaaabbbblllleeeedddd....
+
+ Example: mmmmaaaaggggiiiicccc ssssccccrrrriiiipppptttt ==== uuuusssseeeerrrr....ccccsssshhhh
+
+ mmmmaaaannnngggglllleeee ccccaaaasssseeee ((((SSSS))))
+ See the section on NAME MANGLING
+
+ Default: mmmmaaaannnngggglllleeee ccccaaaasssseeee ==== nnnnoooo
+
+ mmmmaaaannnngggglllleeeedddd mmmmaaaapppp ((((SSSS))))
+ This is for those who want to directly map UNIX file
+ names which cannot be represented on Windows/DOS. The
+ mangling of names is not always what is needed. In
+ particular you may have documents with file extensions
+ that differ between DOS and UNIX. For example, under
+ UNIX it is common to use ._h_t_m_l for HTML files, whereas
+ under Windows/DOS ._h_t_m is more commonly used.
+
+ So to map _h_t_m_l to _h_t_m you would use:
+
+ mmmmaaaannnngggglllleeeedddd mmmmaaaapppp ==== ((((****....hhhhttttmmmmllll ****....hhhhttttmmmm))))
+
+ One very useful case is to remove the annoying ;_1 off
+ the ends of filenames on some CDROMs (only visible
+ under some UNIXes). To do this use a map of (*;1 *;).
+
+
+
+ Page 71 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Default: nnnnoooo mmmmaaaannnngggglllleeeedddd mmmmaaaapppp
+
+ Example: mmmmaaaannnngggglllleeeedddd mmmmaaaapppp ==== ((((****;;;;1111 ****;;;;))))
+
+ mmmmaaaannnngggglllleeeedddd nnnnaaaammmmeeeessss ((((SSSS))))
+ This controls whether non-DOS names under UNIX should
+ be mapped to DOS-compatible names ("mangled") and made
+ visible, or whether non-DOS names should simply be
+ ignored.
+
+ See the section on NAME MANGLING for details on how to
+ control the mangling process.
+
+ If mangling algorithm "hash" is used then the mangling
+ algorithm is as follows:
+
+ o+ The first (up to) five alphanumeric characters before
+ the rightmost dot of the filename are preserved,
+ forced to upper case, and appear as the first (up to)
+ five characters of the mangled name.
+
+ o+ A tilde "~" is appended to the first part of the
+ mangled name, followed by a two-character unique
+ sequence, based on the original root name (i.e., the
+ original filename minus its final extension). The
+ final extension is included in the hash calculation
+ only if it contains any upper case characters or is
+ longer than three characters.
+
+ Note that the character to use may be specified using
+ the _m_a_n_g_l_i_n_g _c_h_a_r option, if you don't like '~'.
+
+ o+ The first three alphanumeric characters of the final
+ extension are preserved, forced to upper case and
+ appear as the extension of the mangled name. The
+ final extension is defined as that part of the
+ original filename after the rightmost dot. If there
+ are no dots in the filename, the mangled name will
+ have no extension (except in the case of "hidden
+ files" - see below).
+
+ o+ Files whose UNIX name begins with a dot will be
+ presented as DOS hidden files. The mangled name will
+ be created as for other filenames, but with the
+ leading dot removed and "___" as its extension
+ regardless of actual original extension (that's three
+ underscores).
+
+ The two-digit hash value consists of upper case alphanumeric
+ characters.
+
+ This algorithm can cause name collisions only if files in a
+
+
+
+ Page 72 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ directory share the same first five alphanumeric characters.
+ The probability of such a clash is 1/1300.
+
+ If mangling algorithm "hash2" is used then the mangling
+ algorithm is as follows:
+
+ o+ The first alphanumeric character before the rightmost
+ dot of the filename is preserved, forced to upper
+ case, and appears as the first character of the
+ mangled name.
+
+ o+ A base63 hash of 5 characters is generated and the
+ first 4 characters of that hash are appended to the
+ first character.
+
+ o+ A tilde "~" is appended to the first part of the
+ mangled name, followed by the final character of the
+ base36 hash of the name.
+
+ Note that the character to use may be specified using
+ the _m_a_n_g_l_i_n_g _c_h_a_r option, if you don't like '~'.
+
+ o+ The first three alphanumeric characters of the final
+ extension are preserved, forced to upper case and
+ appear as the extension of the mangled name. The
+ final extension is defined as that part of the
+ original filename after the rightmost dot. If there
+ are no dots in the filename, the mangled name will
+ have no extension (except in the case of "hidden
+ files" - see below).
+
+ o+ Files whose UNIX name begins with a dot will be
+ presented as DOS hidden files. The mangled name will
+ be created as for other filenames, but with the
+ leading dot removed and "___" as its extension
+ regardless of actual original extension (that's three
+ underscores).
+
+ The name mangling (if enabled) allows a file to be copied
+ between UNIX directories from Windows/DOS while retaining
+ the long UNIX filename. UNIX files can be renamed to a new
+ extension from Windows/DOS and will retain the same
+ basename. Mangled names do not change between sessions.
+
+ Default: mmmmaaaannnngggglllleeeedddd nnnnaaaammmmeeeessss ==== yyyyeeeessss
+
+ mmmmaaaannnngggglllleeeedddd ssssttttaaaacccckkkk ((((GGGG))))
+ This parameter controls the number of mangled names
+ that should be cached in the Samba server smbd(8)
+
+ This stack is a list of recently mangled base names
+ (extensions are only maintained if they are longer than
+
+
+
+ Page 73 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ 3 characters or contains upper case characters).
+
+ The larger this value, the more likely it is that
+ mangled names can be successfully converted to correct
+ long UNIX names. However, large stack sizes will slow
+ most directory accesses. Smaller stacks save memory in
+ the server (each stack element costs 256 bytes).
+
+ It is not possible to absolutely guarantee correct long
+ filenames, so be prepared for some surprises!
+
+ Default: mmmmaaaannnngggglllleeeedddd ssssttttaaaacccckkkk ==== 55550000
+
+ Example: mmmmaaaannnngggglllleeeedddd ssssttttaaaacccckkkk ==== 111100000000
+
+ mmmmaaaannnngggglllliiiinnnngggg cccchhhhaaaarrrr ((((SSSS))))
+ This controls what character is used as the mmmmaaaaggggiiiicccc
+ character in name mangling. The default is a '~' but
+ this may interfere with some software. Use this option
+ to set it to whatever you prefer.
+
+ Default: mmmmaaaannnngggglllliiiinnnngggg cccchhhhaaaarrrr ==== ~~~~
+
+ Example: mmmmaaaannnngggglllliiiinnnngggg cccchhhhaaaarrrr ==== ^^^^
+
+ mmmmaaaannnngggglllliiiinnnngggg mmmmaaaatttthhhhoooodddd((((GGGG))))
+ controls the algorithm used for the generating the
+ mangled names. Can take two different values, "hash"
+ and "hash2". "hash" is the default and is the algorithm
+ that has been used in Samba for many years. "hash2" is
+ a newer and considered a better algorithm (generates
+ less collisions) in the names. However, many Win32
+ applications store the mangled names and so changing to
+ the new algorithm must not be done lightly as these
+ applications may break unless reinstalled. New
+ installations of Samba may set the default to hash2.
+
+ Default: mmmmaaaannnngggglllliiiinnnngggg mmmmeeeetttthhhhoooodddd ==== hhhhaaaasssshhhh
+
+ Example: mmmmaaaannnngggglllliiiinnnngggg mmmmeeeetttthhhhoooodddd ==== hhhhaaaasssshhhh2222
+
+ mmmmaaaapppp aaaarrrrcccchhhhiiiivvvveeee ((((SSSS))))
+ This controls whether the DOS archive attribute should
+ be mapped to the UNIX owner execute bit. The DOS
+ archive bit is set when a file has been modified since
+ its last backup. One motivation for this option it to
+ keep Samba/your PC from making any file it touches from
+ becoming executable under UNIX. This can be quite
+ annoying for shared source code, documents, etc...
+
+ Note that this requires the _c_r_e_a_t_e _m_a_s_k parameter to be
+ set such that owner execute bit is not masked out (i.e.
+
+
+
+ Page 74 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ it must include 100). See the parameter _c_r_e_a_t_e _m_a_s_k
+ for details.
+
+ Default: mmmmaaaapppp aaaarrrrcccchhhhiiiivvvveeee ==== yyyyeeeessss
+
+ mmmmaaaapppp hhhhiiiiddddddddeeeennnn ((((SSSS))))
+ This controls whether DOS style hidden files should be
+ mapped to the UNIX world execute bit.
+
+ Note that this requires the _c_r_e_a_t_e _m_a_s_k to be set such
+ that the world execute bit is not masked out (i.e. it
+ must include 001). See the parameter _c_r_e_a_t_e _m_a_s_k for
+ details.
+
+ Default: mmmmaaaapppp hhhhiiiiddddddddeeeennnn ==== nnnnoooo
+
+ mmmmaaaapppp ssssyyyysssstttteeeemmmm ((((SSSS))))
+ This controls whether DOS style system files should be
+ mapped to the UNIX group execute bit.
+
+ Note that this requires the _c_r_e_a_t_e _m_a_s_k to be set such
+ that the group execute bit is not masked out (i.e. it
+ must include 010). See the parameter _c_r_e_a_t_e _m_a_s_k for
+ details.
+
+ Default: mmmmaaaapppp ssssyyyysssstttteeeemmmm ==== nnnnoooo
+
+ mmmmaaaapppp ttttoooo gggguuuueeeesssstttt ((((GGGG))))
+ This parameter is only useful in security modes other
+ than _s_e_c_u_r_i_t_y = _s_h_a_r_e - i.e. user, server, and domain.
+
+ This parameter can take three different values, which
+ tell smbd(8) what to do with user login requests that
+ don't match a valid UNIX user in some way.
+
+ The three settings are :
+
+ o+ Never - Means user login requests with an invalid
+ password are rejected. This is the default.
+
+ o+ Bad User - Means user logins with an invalid password
+ are rejected, unless the username does not exist, in
+ which case it is treated as a guest login and mapped
+ into the _g_u_e_s_t _a_c_c_o_u_n_t.
+
+ o+ Bad Password - Means user logins with an invalid
+ password are treated as a guest login and mapped into
+ the guest account. Note that this can cause problems
+ as it means that any user incorrectly typing their
+ password will be silently logged on as "guest" - and
+ will not know the reason they cannot access files
+ they think they should - there will have been no
+
+
+
+ Page 75 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ message given to them that they got their password
+ wrong. Helpdesk services will hhhhaaaatttteeee you if you set the
+ _m_a_p _t_o _g_u_e_s_t parameter this way :-).
+
+ Note that this parameter is needed to set up "Guest" share
+ services when using _s_e_c_u_r_i_t_y modes other than share. This is
+ because in these modes the name of the resource being
+ requested is nnnnooootttt sent to the server until after the server
+ has successfully authenticated the client so the server
+ cannot make authentication decisions at the correct time
+ (connection to the share) for "Guest" shares.
+
+ For people familiar with the older Samba releases, this
+ parameter maps to the old compile-time setting of the
+ GUEST_SESSSETUP value in local.h.
+
+ Default: mmmmaaaapppp ttttoooo gggguuuueeeesssstttt ==== NNNNeeeevvvveeeerrrr
+
+ Example: mmmmaaaapppp ttttoooo gggguuuueeeesssstttt ==== BBBBaaaadddd UUUUsssseeeerrrr
+
+ mmmmaaaaxxxx ccccoooonnnnnnnneeeeccccttttiiiioooonnnnssss ((((SSSS))))
+ This option allows the number of simultaneous
+ connections to a service to be limited. If _m_a_x
+ _c_o_n_n_e_c_t_i_o_n_s is greater than 0 then connections will be
+ refused if this number of connections to the service
+ are already open. A value of zero mean an unlimited
+ number of connections may be made.
+
+ Record lock files are used to implement this feature.
+ The lock files will be stored in the directory
+ specified by the _l_o_c_k _d_i_r_e_c_t_o_r_y option.
+
+ Default: mmmmaaaaxxxx ccccoooonnnnnnnneeeeccccttttiiiioooonnnnssss ==== 0000
+
+ Example: mmmmaaaaxxxx ccccoooonnnnnnnneeeeccccttttiiiioooonnnnssss ==== 11110000
+
+ mmmmaaaaxxxx ddddiiiisssskkkk ssssiiiizzzzeeee ((((GGGG))))
+ This option allows you to put an upper limit on the
+ apparent size of disks. If you set this option to 100
+ then all shares will appear to be not larger than 100
+ MB in size.
+
+ Note that this option does not limit the amount of data
+ you can put on the disk. In the above case you could
+ still store much more than 100 MB on the disk, but if a
+ client ever asks for the amount of free disk space or
+ the total disk size then the result will be bounded by
+ the amount specified in _m_a_x _d_i_s_k _s_i_z_e.
+
+ This option is primarily useful to work around bugs in
+ some pieces of software that can't handle very large
+ disks, particularly disks over 1GB in size.
+
+
+
+ Page 76 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ A _m_a_x _d_i_s_k _s_i_z_e of 0 means no limit.
+
+ Default: mmmmaaaaxxxx ddddiiiisssskkkk ssssiiiizzzzeeee ==== 0000
+
+ Example: mmmmaaaaxxxx ddddiiiisssskkkk ssssiiiizzzzeeee ==== 1111000000000000
+
+ mmmmaaaaxxxx lllloooogggg ssssiiiizzzzeeee ((((GGGG))))
+ This option (an integer in kilobytes) specifies the max
+ size the log file should grow to. Samba periodically
+ checks the size and if it is exceeded it will rename
+ the file, adding a ._o_l_d extension.
+
+ A size of 0 means no limit.
+
+ Default: mmmmaaaaxxxx lllloooogggg ssssiiiizzzzeeee ==== 5555000000000000
+
+ Example: mmmmaaaaxxxx lllloooogggg ssssiiiizzzzeeee ==== 1111000000000000
+
+ mmmmaaaaxxxx mmmmuuuuxxxx ((((GGGG))))
+ This option controls the maximum number of outstanding
+ simultaneous SMB operations that Samba tells the client
+ it will allow. You should never need to set this
+ parameter.
+
+ Default: mmmmaaaaxxxx mmmmuuuuxxxx ==== 55550000
+
+ mmmmaaaaxxxx ooooppppeeeennnn ffffiiiilllleeeessss ((((GGGG))))
+ This parameter limits the maximum number of open files
+ that one smbd(8) file serving process may have open for
+ a client at any one time. The default for this
+ parameter is set very high (10,000) as Samba uses only
+ one bit per unopened file.
+
+ The limit of the number of open files is usually set by
+ the UNIX per-process file descriptor limit rather than
+ this parameter so you should never need to touch this
+ parameter.
+
+ Default: mmmmaaaaxxxx ooooppppeeeennnn ffffiiiilllleeeessss ==== 11110000000000000000
+
+ mmmmaaaaxxxx pppprrrriiiinnnntttt jjjjoooobbbbssss ((((SSSS))))
+ This parameter limits the maximum number of jobs
+ allowable in a Samba printer queue at any given moment.
+ If this number is exceeded, ssssmmmmbbbbdddd((((8888)))) will remote "Out
+ of Space" to the client. See all _t_o_t_a_l _p_r_i_n_t _j_o_b_s.
+
+ Default: mmmmaaaaxxxx pppprrrriiiinnnntttt jjjjoooobbbbssss ==== 1111000000000000
+
+ Example: mmmmaaaaxxxx pppprrrriiiinnnntttt jjjjoooobbbbssss ==== 5555000000000000
+
+ mmmmaaaaxxxx pppprrrroooottttooooccccoooollll ((((GGGG))))
+ The value of the parameter (a string) is the highest
+
+
+
+ Page 77 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ protocol level that will be supported by the server.
+
+ Possible values are :
+
+ o+ CORE: Earliest version. No concept of user names.
+
+ o+ COREPLUS: Slight improvements on CORE for efficiency.
+
+ o+ LANMAN1: First mmmmooooddddeeeerrrrnnnn version of the protocol. Long
+ filename support.
+
+ o+ LANMAN2: Updates to Lanman1 protocol.
+
+ o+ NT1: Current up to date version of the protocol. Used
+ by Windows NT. Known as CIFS.
+
+ Normally this option should not be set as the automatic
+ negotiation phase in the SMB protocol takes care of choosing
+ the appropriate protocol.
+
+ See also _m_i_n _p_r_o_t_o_c_o_l
+
+ Default: mmmmaaaaxxxx pppprrrroooottttooooccccoooollll ==== NNNNTTTT1111
+
+ Example: mmmmaaaaxxxx pppprrrroooottttooooccccoooollll ==== LLLLAAAANNNNMMMMAAAANNNN1111
+
+ mmmmaaaaxxxx ssssmmmmbbbbdddd pppprrrroooocccceeeesssssssseeeessss ((((GGGG))))
+ This parameter limits the maximum number of ssssmmmmbbbbdddd((((8888))))
+ processes concurrently running on a system and is
+ intended as a stopgap to prevent degrading service to
+ clients in the event that the server has insufficient
+ resources to handle more than this number of
+ connections. Remember that under normal operating
+ conditions, each user will have an smbd associated with
+ him or her to handle connections to all shares from a
+ given host.
+
+ Default: mmmmaaaaxxxx ssssmmmmbbbbdddd pppprrrroooocccceeeesssssssseeeessss ==== 0000 ## no limit
+
+ Example: mmmmaaaaxxxx ssssmmmmbbbbdddd pppprrrroooocccceeeesssssssseeeessss ==== 1111000000000000
+
+ mmmmaaaaxxxx ttttttttllll ((((GGGG))))
+ This option tells nmbd(8) what the default 'time to
+ live' of NetBIOS names should be (in seconds) when nnnnmmmmbbbbdddd
+ is requesting a name using either a broadcast packet or
+ from a WINS server. You should never need to change
+ this parameter. The default is 3 days.
+
+ Default: mmmmaaaaxxxx ttttttttllll ==== 222255559999222200000000
+
+ mmmmaaaaxxxx wwwwiiiinnnnssss ttttttttllll ((((GGGG))))
+ This option tells nmbd(8)
+
+
+
+ Page 78 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ when acting as a WINS server ( _w_i_n_s _s_u_p_p_o_r_t = _y_e_s)
+ what the maximum 'time to live' of NetBIOS names that
+ nnnnmmmmbbbbdddd will grant will be (in seconds). You should never
+ need to change this parameter. The default is 6 days
+ (518400 seconds).
+
+ See also the _m_i_n _w_i_n_s _t_t_l parameter.
+
+ Default: mmmmaaaaxxxx wwwwiiiinnnnssss ttttttttllll ==== 555511118888444400000000
+
+ mmmmaaaaxxxx xxxxmmmmiiiitttt ((((GGGG))))
+ This option controls the maximum packet size that will
+ be negotiated by Samba. The default in Samba 2.2.6 is
+ now 16644 (changed from 65535 in earlier releases)
+ which matches Windows 2000. This allows better
+ performance with Windows NT clients. The maximum is
+ 65535. In some cases you may find you get better
+ performance with a smaller value. A value below 2048 is
+ likely to cause problems.
+
+ Default: mmmmaaaaxxxx xxxxmmmmiiiitttt ==== 11116666666644444444
+
+ Example: mmmmaaaaxxxx xxxxmmmmiiiitttt ==== 8888111199992222
+
+ mmmmeeeessssssssaaaaggggeeee ccccoooommmmmmmmaaaannnndddd ((((GGGG))))
+ This specifies what command to run when the server
+ receives a WinPopup style message.
+
+ This would normally be a command that would deliver the
+ message somehow. How this is to be done is up to your
+ imagination.
+
+ An example is:
+
+ mmmmeeeessssssssaaaaggggeeee ccccoooommmmmmmmaaaannnndddd ==== ccccsssshhhh ----cccc ''''xxxxeeeeddddiiiitttt %%%%ssss;;;;rrrrmmmm %%%%ssss'''' &&&&
+
+ This delivers the message using xxxxeeeeddddiiiitttt, then removes it
+ afterwards. NNNNOOOOTTTTEEEE TTTTHHHHAAAATTTT IIIITTTT IIIISSSS VVVVEEEERRRRYYYY IIIIMMMMPPPPOOOORRRRTTTTAAAANNNNTTTT TTTTHHHHAAAATTTT TTTTHHHHIIIISSSS
+ CCCCOOOOMMMMMMMMAAAANNNNDDDD RRRREEEETTTTUUUURRRRNNNN IIIIMMMMMMMMEEEEDDDDIIIIAAAATTTTEEEELLLLYYYY. That's why I have the '&'
+ on the end. If it doesn't return immediately then your
+ PCs may freeze when sending messages (they should
+ recover after 30 seconds, hopefully).
+
+ All messages are delivered as the global guest user.
+ The command takes the standard substitutions, although
+ %_u won't work (%_U may be better in this case).
+
+ Apart from the standard substitutions, some additional
+ ones apply. In particular:
+
+ o+ %_s = the filename containing the message.
+
+
+
+
+ Page 79 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ %_t = the destination that the message was sent to
+ (probably the server name).
+
+ o+ %_f = who the message is from.
+
+ You could make this command send mail, or whatever else
+ takes your fancy. Please let us know of any really
+ interesting ideas you have.
+
+ Here's a way of sending the messages as mail to root:
+
+ mmmmeeeessssssssaaaaggggeeee ccccoooommmmmmmmaaaannnndddd ==== ////bbbbiiiinnnn////mmmmaaaaiiiillll ----ssss ''''mmmmeeeessssssssaaaaggggeeee ffffrrrroooommmm %%%%ffff oooonnnn %%%%mmmm'''' rrrrooooooootttt
+ <<<< %%%%ssss;;;; rrrrmmmm %%%%ssss
+
+ If you don't have a message command then the message won't
+ be delivered and Samba will tell the sender there was an
+ error. Unfortunately WfWg totally ignores the error code and
+ carries on regardless, saying that the message was
+ delivered.
+
+ If you want to silently delete it then try:
+
+ mmmmeeeessssssssaaaaggggeeee ccccoooommmmmmmmaaaannnndddd ==== rrrrmmmm %%%%ssss
+
+ Default: nnnnoooo mmmmeeeessssssssaaaaggggeeee ccccoooommmmmmmmaaaannnndddd
+
+ Example: mmmmeeeessssssssaaaaggggeeee ccccoooommmmmmmmaaaannnndddd ==== ccccsssshhhh ----cccc ''''xxxxeeeeddddiiiitttt %%%%ssss;;;; rrrrmmmm %%%%ssss'''' &&&&
+
+ mmmmiiiinnnn ppppaaaasssssssswwwwdddd lllleeeennnnggggtttthhhh ((((GGGG))))
+ Synonym for _m_i_n _p_a_s_s_w_o_r_d _l_e_n_g_t_h.
+
+ mmmmiiiinnnn ppppaaaasssssssswwwwoooorrrrdddd lllleeeennnnggggtttthhhh ((((GGGG))))
+ This option sets the minimum length in characters of a
+ plaintext password that ssssmmmmbbbbdddd will accept when
+ performing UNIX password changing.
+
+ See also _u_n_i_x _p_a_s_s_w_o_r_d _s_y_n_c, _p_a_s_s_w_d _p_r_o_g_r_a_m and _p_a_s_s_w_d
+ _c_h_a_t _d_e_b_u_g .
+
+ Default: mmmmiiiinnnn ppppaaaasssssssswwwwoooorrrrdddd lllleeeennnnggggtttthhhh ==== 5555
+
+ mmmmiiiinnnn pppprrrriiiinnnntttt ssssppppaaaacccceeee ((((SSSS))))
+ This sets the minimum amount of free disk space that
+ must be available before a user will be able to spool a
+ print job. It is specified in kilobytes. The default is
+ 0, which means a user can always spool a print job.
+
+ See also the _p_r_i_n_t_i_n_g parameter.
+
+ Default: mmmmiiiinnnn pppprrrriiiinnnntttt ssssppppaaaacccceeee ==== 0000
+
+ Example: mmmmiiiinnnn pppprrrriiiinnnntttt ssssppppaaaacccceeee ==== 2222000000000000
+
+
+
+ Page 80 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ mmmmiiiinnnn pppprrrroooottttooooccccoooollll ((((GGGG))))
+ The value of the parameter (a string) is the lowest SMB
+ protocol dialect than Samba will support. Please refer
+ to the _m_a_x _p_r_o_t_o_c_o_l parameter for a list of valid
+ protocol names and a brief description of each. You may
+ also wish to refer to the C source code in
+ _s_o_u_r_c_e/_s_m_b_d/_n_e_g_p_r_o_t._c for a listing of known protocol
+ dialects supported by clients.
+
+ If you are viewing this parameter as a security
+ measure, you should also refer to the _l_a_n_m_a_n _a_u_t_h
+ parameter. Otherwise, you should never need to change
+ this parameter.
+
+ Default : mmmmiiiinnnn pppprrrroooottttooooccccoooollll ==== CCCCOOOORRRREEEE
+
+ Example : mmmmiiiinnnn pppprrrroooottttooooccccoooollll ==== NNNNTTTT1111 # disable DOS clients
+
+ mmmmiiiinnnn wwwwiiiinnnnssss ttttttttllll ((((GGGG))))
+ This option tells nmbd(8) when acting as a WINS server
+ ( _w_i_n_s _s_u_p_p_o_r_t = _y_e_s) what the minimum 'time to live'
+ of NetBIOS names that nnnnmmmmbbbbdddd will grant will be (in
+ seconds). You should never need to change this
+ parameter. The default is 6 hours (21600 seconds).
+
+ Default: mmmmiiiinnnn wwwwiiiinnnnssss ttttttttllll ==== 22221111666600000000
+
+ mmmmssssddddffffssss rrrrooooooootttt ((((SSSS))))
+ This boolean parameter is only available if Samba is
+ configured and compiled with the --------wwwwiiiitttthhhh----mmmmssssddddffffssss option.
+ If set to yes, Samba treats the share as a Dfs root and
+ allows clients to browse the distributed file system
+ tree rooted at the share directory. Dfs links are
+ specified in the share directory by symbolic links of
+ the form _m_s_d_f_s:_s_e_r_v_e_r_A\_s_h_a_r_e_A,_s_e_r_v_e_r_B\_s_h_a_r_e_B and so on.
+ For more information on setting up a Dfs tree on Samba,
+ refer to msdfs_setup.html
+
+
+ See also _h_o_s_t _m_s_d_f_s
+
+ Default: mmmmssssddddffffssss rrrrooooooootttt ==== nnnnoooo
+
+ nnnnaaaammmmeeee rrrreeeessssoooollllvvvveeee oooorrrrddddeeeerrrr ((((GGGG))))
+ This option is used by the programs in the Samba suite
+ to determine what naming services to use and in what
+ order to resolve host names to IP addresses. The option
+ takes a space separated string of name resolution
+ options.
+
+ The options are :"lmhosts", "host", "wins" and "bcast".
+ They cause names to be resolved as follows :
+
+
+
+ Page 81 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ lmhosts : Lookup an IP address in the Samba lmhosts
+ file. If the line in lmhosts has no name type
+ attached to the NetBIOS name (see the lmhosts(5) for
+ details) then any name type matches for lookup.
+
+ o+ host : Do a standard host name to IP address
+ resolution, using the system /_e_t_c/_h_o_s_t_s , NIS, or DNS
+ lookups. This method of name resolution is operating
+ system depended for instance on IRIX or Solaris this
+ may be controlled by the /_e_t_c/_n_s_s_w_i_t_c_h._c_o_n_f file.
+ Note that this method is only used if the NetBIOS
+ name type being queried is the 0x20 (server) name
+ type, otherwise it is ignored.
+
+ o+ wins : Query a name with the IP address listed in the
+ _w_i_n_s _s_e_r_v_e_r parameter. If no WINS server has been
+ specified this method will be ignored.
+
+ o+ bcast : Do a broadcast on each of the known local
+ interfaces listed in the _i_n_t_e_r_f_a_c_e_s parameter. This
+ is the least reliable of the name resolution methods
+ as it depends on the target host being on a locally
+ connected subnet.
+
+ Default: nnnnaaaammmmeeee rrrreeeessssoooollllvvvveeee oooorrrrddddeeeerrrr ==== llllmmmmhhhhoooossssttttssss hhhhoooosssstttt wwwwiiiinnnnssss bbbbccccaaaasssstttt
+
+ Example: nnnnaaaammmmeeee rrrreeeessssoooollllvvvveeee oooorrrrddddeeeerrrr ==== llllmmmmhhhhoooossssttttssss bbbbccccaaaasssstttt hhhhoooosssstttt
+
+ This will cause the local lmhosts file to be examined first,
+ followed by a broadcast attempt, followed by a normal system
+ hostname lookup.
+
+ nnnneeeettttbbbbiiiioooossss aaaalllliiiiaaaasssseeeessss ((((GGGG))))
+ This is a list of NetBIOS names that nmbd(8) will
+ advertise as additional names by which the Samba server
+ is known. This allows one machine to appear in browse
+ lists under multiple names. If a machine is acting as a
+ browse server or logon server none of these names will
+ be advertised as either browse server or logon servers,
+ only the primary name of the machine will be advertised
+ with these capabilities.
+
+ See also _n_e_t_b_i_o_s _n_a_m_e.
+
+ Default: eeeemmmmppppttttyyyy ssssttttrrrriiiinnnngggg ((((nnnnoooo aaaaddddddddiiiittttiiiioooonnnnaaaallll nnnnaaaammmmeeeessss))))
+
+ Example: nnnneeeettttbbbbiiiioooossss aaaalllliiiiaaaasssseeeessss ==== TTTTEEEESSSSTTTT TTTTEEEESSSSTTTT1111 TTTTEEEESSSSTTTT2222
+
+ nnnneeeettttbbbbiiiioooossss nnnnaaaammmmeeee ((((GGGG))))
+ This sets the NetBIOS name by which a Samba server is
+ known. By default it is the same as the first component
+ of the host's DNS name. If a machine is a browse server
+
+
+
+ Page 82 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ or logon server this name (or the first component of
+ the hosts DNS name) will be the name that these
+ services are advertised under.
+
+ See also _n_e_t_b_i_o_s _a_l_i_a_s_e_s.
+
+ Default: mmmmaaaacccchhhhiiiinnnneeee DDDDNNNNSSSS nnnnaaaammmmeeee
+
+ Example: nnnneeeettttbbbbiiiioooossss nnnnaaaammmmeeee ==== MMMMYYYYNNNNAAAAMMMMEEEE
+
+ nnnneeeettttbbbbiiiioooossss ssssccccooooppppeeee ((((GGGG))))
+ This sets the NetBIOS scope that Samba will operate
+ under. This should not be set unless every machine on
+ your LAN also sets this value.
+
+ nnnniiiissss hhhhoooommmmeeeeddddiiiirrrr ((((GGGG))))
+ Get the home share server from a NIS map. For UNIX
+ systems that use an automounter, the user's home
+ directory will often be mounted on a workstation on
+ demand from a remote server.
+
+ When the Samba logon server is not the actual home
+ directory server, but is mounting the home directories
+ via NFS then two network hops would be required to
+ access the users home directory if the logon server
+ told the client to use itself as the SMB server for
+ home directories (one over SMB and one over NFS). This
+ can be very slow.
+
+ This option allows Samba to return the home share as
+ being on a different server to the logon server and as
+ long as a Samba daemon is running on the home directory
+ server, it will be mounted on the Samba client directly
+ from the directory server. When Samba is returning the
+ home share to the client, it will consult the NIS map
+ specified in _h_o_m_e_d_i_r _m_a_p and return the server listed
+ there.
+
+ Note that for this option to work there must be a
+ working NIS system and the Samba server with this
+ option must also be a logon server.
+
+ Default: nnnniiiissss hhhhoooommmmeeeeddddiiiirrrr ==== nnnnoooo
+
+ nnnntttt aaaaccccllll ssssuuuuppppppppoooorrrrtttt ((((SSSS))))
+ This boolean parameter controls whether smbd(8) will
+ attempt to map UNIX permissions into Windows NT access
+ control lists. This parameter was formally a global
+ parameter in releases prior to 2.2.2.
+
+ Default: nnnntttt aaaaccccllll ssssuuuuppppppppoooorrrrtttt ==== yyyyeeeessss
+
+
+
+
+ Page 83 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ nnnntttt ppppiiiippppeeee ssssuuuuppppppppoooorrrrtttt ((((GGGG))))
+ This boolean parameter controls whether smbd(8) will
+ allow Windows NT clients to connect to the NT SMB
+ specific IPC$ pipes. This is a developer debugging
+ option and can be left alone.
+
+ Default: nnnntttt ppppiiiippppeeee ssssuuuuppppppppoooorrrrtttt ==== yyyyeeeessss
+
+ nnnntttt ssssmmmmbbbb ssssuuuuppppppppoooorrrrtttt ((((GGGG))))
+ This boolean parameter controls whether smbd(8) will
+ negotiate NT specific SMB support with Windows NT/2k/XP
+ clients. Although this is a developer debugging option
+ and should be left alone, benchmarking has discovered
+ that Windows NT clients give faster performance with
+ this option set to no. This is still being
+ investigated. If this option is set to no then Samba
+ offers exactly the same SMB calls that versions prior
+ to Samba 2.0 offered. This information may be of use
+ if any users are having problems with NT SMB support.
+
+ You should not need to ever disable this parameter.
+
+ Default: nnnntttt ssssmmmmbbbb ssssuuuuppppppppoooorrrrtttt ==== yyyyeeeessss
+
+ nnnntttt ssssttttaaaattttuuuussss ssssuuuuppppppppoooorrrrtttt ((((GGGG))))
+ This boolean parameter controls whether smbd(8) will
+ negotiate NT specific status support with Windows
+ NT/2k/XP clients. This is a developer debugging option
+ and should be left alone. If this option is set to no
+ then Samba offers exactly the same DOS error codes that
+ versions prior to Samba 2.2.3 reported.
+
+ You should not need to ever disable this parameter.
+
+ Default: nnnntttt ssssttttaaaattttuuuussss ssssuuuuppppppppoooorrrrtttt ==== yyyyeeeessss
+
+ nnnnuuuullllllll ppppaaaasssssssswwwwoooorrrrddddssss ((((GGGG))))
+ Allow or disallow client access to accounts that have
+ null passwords.
+
+ See also smbpasswd (5)
+
+ Default: nnnnuuuullllllll ppppaaaasssssssswwwwoooorrrrddddssss ==== nnnnoooo
+
+ oooobbbbeeeeyyyy ppppaaaammmm rrrreeeessssttttrrrriiiiccccttttiiiioooonnnnssss ((((GGGG))))
+ When Samba 2.2 is configured 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
+
+
+
+ Page 84 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ _e_n_c_r_y_p_t _p_a_s_s_w_o_r_d_s _= _y_e_s . The reason is that PAM
+ modules cannot support the challenge/response
+ authentication mechanism needed in the presence of SMB
+ password encryption.
+
+ Default: oooobbbbeeeeyyyy ppppaaaammmm rrrreeeessssttttrrrriiiiccccttttiiiioooonnnnssss ==== nnnnoooo
+
+ oooonnnnllllyyyy uuuusssseeeerrrr ((((SSSS))))
+ This is a boolean option that controls whether
+ connections with usernames not in the _u_s_e_r list will be
+ allowed. By default this option is disabled so that a
+ client can supply a username to be used by the server.
+ Enabling this parameter will force the server to only
+ user the login names from the _u_s_e_r list and is only
+ really useful in shave level security.
+
+ Note that this also means Samba won't try to deduce
+ usernames from the service name. This can be annoying
+ for the [homes] section. To get around this you could
+ use uuuusssseeeerrrr ==== %%%%SSSS which means your _u_s_e_r list will be just
+ the service name, which for home directories is the
+ name of the user.
+
+ See also the _u_s_e_r parameter.
+
+ Default: oooonnnnllllyyyy uuuusssseeeerrrr ==== nnnnoooo
+
+ oooonnnnllllyyyy gggguuuueeeesssstttt ((((SSSS))))
+ A synonym for _g_u_e_s_t _o_n_l_y.
+
+ oooopppplllloooocccckkkk bbbbrrrreeeeaaaakkkk wwwwaaaaiiiitttt ttttiiiimmmmeeee ((((GGGG))))
+ This is a tuning parameter added due to bugs in both
+ Windows 9x and WinNT. If Samba responds to a client too
+ quickly when that client issues an SMB that can cause
+ an oplock break request, then the network client can
+ fail and not respond to the break request. This tuning
+ parameter (which is set in milliseconds) is the amount
+ of time Samba will wait before sending an oplock break
+ request to such (broken) clients.
+
+ DDDDOOOO NNNNOOOOTTTT CCCCHHHHAAAANNNNGGGGEEEE TTTTHHHHIIIISSSS PPPPAAAARRRRAAAAMMMMEEEETTTTEEEERRRR UUUUNNNNLLLLEEEESSSSSSSS YYYYOOOOUUUU HHHHAAAAVVVVEEEE RRRREEEEAAAADDDD AAAANNNNDDDD
+ UUUUNNNNDDDDEEEERRRRSSSSTTTTOOOOOOOODDDD TTTTHHHHEEEE SSSSAAAAMMMMBBBBAAAA OOOOPPPPLLLLOOOOCCCCKKKK CCCCOOOODDDDEEEE.
+
+ Default: oooopppplllloooocccckkkk bbbbrrrreeeeaaaakkkk wwwwaaaaiiiitttt ttttiiiimmmmeeee ==== 0000
+
+ oooopppplllloooocccckkkk ccccoooonnnntttteeeennnnttttiiiioooonnnn lllliiiimmmmiiiitttt ((((SSSS))))
+ This is a vvvveeeerrrryyyy advanced smbd(8) tuning option to
+ improve the efficiency of the granting of oplocks under
+ multiple client contention for the same file.
+
+ In brief it specifies a number, which causes smbd not
+ to grant an oplock even when requested if the
+
+
+
+ Page 85 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ approximate number of clients contending for an oplock
+ on the same file goes over this limit. This causes ssssmmmmbbbbdddd
+ to behave in a similar way to Windows NT.
+
+ DDDDOOOO NNNNOOOOTTTT CCCCHHHHAAAANNNNGGGGEEEE TTTTHHHHIIIISSSS PPPPAAAARRRRAAAAMMMMEEEETTTTEEEERRRR UUUUNNNNLLLLEEEESSSSSSSS YYYYOOOOUUUU HHHHAAAAVVVVEEEE RRRREEEEAAAADDDD AAAANNNNDDDD
+ UUUUNNNNDDDDEEEERRRRSSSSTTTTOOOOOOOODDDD TTTTHHHHEEEE SSSSAAAAMMMMBBBBAAAA OOOOPPPPLLLLOOOOCCCCKKKK CCCCOOOODDDDEEEE.
+
+ Default: oooopppplllloooocccckkkk ccccoooonnnntttteeeennnnttttiiiioooonnnn lllliiiimmmmiiiitttt ==== 2222
+
+ oooopppplllloooocccckkkkssss ((((SSSS))))
+ This boolean option tells ssssmmmmbbbbdddd whether to issue oplocks
+ (opportunistic locks) to file open requests on this
+ share. The oplock code can dramatically (approx. 30% or
+ more) improve the speed of access to files on Samba
+ servers. It allows the clients to aggressively cache
+ files locally and you may want to disable this option
+ for unreliable network environments (it is turned on by
+ default in Windows NT Servers). For more information
+ see the file _S_p_e_e_d._t_x_t in the Samba _d_o_c_s/ directory.
+
+ Oplocks may be selectively turned off on certain files
+ with a share. See the _v_e_t_o _o_p_l_o_c_k _f_i_l_e_s parameter. On
+ some systems oplocks are recognized by the underlying
+ operating system. This allows data synchronization
+ between all access to oplocked files, whether it be via
+ Samba or NFS or a local UNIX process. See the _k_e_r_n_e_l
+ _o_p_l_o_c_k_s parameter for details.
+
+ See also the _k_e_r_n_e_l _o_p_l_o_c_k_s and _l_e_v_e_l_2 _o_p_l_o_c_k_s
+ parameters.
+
+ Default: oooopppplllloooocccckkkkssss ==== yyyyeeeessss
+
+ oooossss lllleeeevvvveeeellll ((((GGGG))))
+ This integer value controls what level Samba advertises
+ itself as for browse elections. The value of this
+ parameter determines whether nmbd(8) has a chance of
+ becoming a local master browser for the _W_O_R_K_G_R_O_U_P in
+ the local broadcast area.
+
+ NNNNooootttteeee ::::By default, Samba will win a local master
+ browsing election over all Microsoft operating systems
+ except a Windows NT 4.0/2000 Domain Controller. This
+ means that a misconfigured Samba host can effectively
+ isolate a subnet for browsing purposes. See
+ _B_R_O_W_S_I_N_G._t_x_t in the Samba _d_o_c_s/ directory for details.
+
+ Default: oooossss lllleeeevvvveeeellll ==== 22220000
+
+ Example: oooossss lllleeeevvvveeeellll ==== 66665555
+
+ oooossss2222 ddddrrrriiiivvvveeeerrrr mmmmaaaapppp ((((GGGG))))
+
+
+
+ Page 86 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ The parameter is used to define the absolute path to a
+ file containing a mapping of Windows NT printer driver
+ names to OS/2 printer driver names. The format is:
+
+ = .
+
+ For example, a valid entry using the HP LaserJet 5
+ printer driver would appear as HHHHPPPP LLLLaaaasssseeeerrrrJJJJeeeetttt 5555LLLL ====
+ LLLLAAAASSSSEEEERRRRJJJJEEEETTTT....HHHHPPPP LLLLaaaasssseeeerrrrJJJJeeeetttt 5555LLLL.
+
+ The need for the file is due to the printer driver
+ namespace problem described in the Samba Printing HOWTO
+ For more details on OS/2 clients, please refer to the
+ OS2-Client-HOWTO
+ containing in the Samba documentation.
+
+ Default: oooossss2222 ddddrrrriiiivvvveeeerrrr mmmmaaaapppp ==== <<<>>>
+
+ ppppaaaammmm ppppaaaasssssssswwwwoooorrrrdddd cccchhhhaaaannnnggggeeee ((((GGGG))))
+ 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 instead of the program listed in _p_a_s_s_w_d
+ _p_r_o_g_r_a_m. It should be possible to enable this without
+ changing your _p_a_s_s_w_d _c_h_a_t parameter for most setups.
+
+ Default: ppppaaaammmm ppppaaaasssssssswwwwoooorrrrdddd cccchhhhaaaannnnggggeeee ==== nnnnoooo
+
+ ppppaaaannnniiiicccc aaaaccccttttiiiioooonnnn ((((GGGG))))
+ This is a Samba developer option that allows a system
+ command to be called when either smbd(8) crashes. This
+ is usually used to draw attention to the fact that a
+ problem occurred.
+
+ Default: ppppaaaannnniiiicccc aaaaccccttttiiiioooonnnn ==== <<<>>>
+
+ Example: ppppaaaannnniiiicccc aaaaccccttttiiiioooonnnn ==== """"////bbbbiiiinnnn////sssslllleeeeeeeepppp 99990000000000000000""""
+
+ ppppaaaasssssssswwwwdddd cccchhhhaaaatttt ((((GGGG))))
+ This string controls the """"cccchhhhaaaatttt"""" conversation that takes
+ places between smbd and the local password changing
+ program to change the user's password. The string
+ describes a sequence of response-receive pairs that
+ smbd(8) uses to determine what to send to the _p_a_s_s_w_d
+ _p_r_o_g_r_a_m and what to expect back. If the expected output
+ is not received then the password is not changed.
+
+ This chat sequence is often quite site specific,
+ depending on what local methods are used for password
+ control (such as NIS etc).
+
+
+
+
+ Page 87 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Note that this parameter only is only used if the _u_n_i_x
+ _p_a_s_s_w_o_r_d _s_y_n_c parameter is set to yes. This sequence is
+ then called AAAASSSS RRRROOOOOOOOTTTT when the SMB password in the
+ smbpasswd file is being changed, without access to the
+ old password cleartext. This means that root must be
+ able to reset the user's password without knowing the
+ text of the previous password. In the presence of
+ NIS/YP, this means that the passwd program must be
+ executed on the NIS master.
+
+ The string can contain the macro %_n which is
+ substituted for the new password. The chat sequence can
+ also contain the standard macros \n, \r, \t and \s to
+ give line-feed, carriage-return, tab and space. The
+ chat sequence string can also contain a '*' which
+ matches any sequence of characters. Double quotes can
+ be used to collect strings with spaces in them into a
+ single string.
+
+ If the send string in any part of the chat sequence is
+ a full stop ".", then no string is sent. Similarly, if
+ the expect string is a full stop then no string is
+ expected.
+
+ If the _p_a_m _p_a_s_s_w_o_r_d _c_h_a_n_g_e parameter is set to yes, the
+ chat pairs may be matched in any order, and success is
+ determined by the PAM result, not any particular
+ output. The \n macro is ignored for PAM conversions.
+
+ See also _u_n_i_x _p_a_s_s_w_o_r_d _s_y_n_c, _p_a_s_s_w_d _p_r_o_g_r_a_m , _p_a_s_s_w_d
+ _c_h_a_t _d_e_b_u_g and _p_a_m _p_a_s_s_w_o_r_d _c_h_a_n_g_e.
+
+ Default: ppppaaaasssssssswwwwdddd cccchhhhaaaatttt ==== ****nnnneeeewwww****ppppaaaasssssssswwwwoooorrrrdddd**** %%%%nnnn\\\\nnnn
+ ****nnnneeeewwww****ppppaaaasssssssswwwwoooorrrrdddd**** %%%%nnnn\\\\nnnn ****cccchhhhaaaannnnggggeeeedddd****
+
+ Example: ppppaaaasssssssswwwwdddd cccchhhhaaaatttt ==== """"****EEEEnnnntttteeeerrrr OOOOLLLLDDDD ppppaaaasssssssswwwwoooorrrrdddd****"""" %%%%oooo\\\\nnnn
+ """"****EEEEnnnntttteeeerrrr NNNNEEEEWWWW ppppaaaasssssssswwwwoooorrrrdddd****"""" %%%%nnnn\\\\nnnn """"****RRRReeeeeeeennnntttteeeerrrr NNNNEEEEWWWW ppppaaaasssssssswwwwoooorrrrdddd****""""
+ %%%%nnnn\\\\nnnn """"****PPPPaaaasssssssswwwwoooorrrrdddd cccchhhhaaaannnnggggeeeedddd****""""
+
+ ppppaaaasssssssswwwwdddd cccchhhhaaaatttt ddddeeeebbbbuuuugggg ((((GGGG))))
+ This boolean specifies if the passwd chat script
+ parameter is run in ddddeeeebbbbuuuugggg mode. In this mode the
+ strings passed to and received from the passwd chat are
+ printed in the smbd(8) log with a _d_e_b_u_g _l_e_v_e_l of 100.
+ This is a dangerous option as it will allow plaintext
+ passwords to be seen in the ssssmmmmbbbbdddd log. It is available
+ to help Samba admins debug their _p_a_s_s_w_d _c_h_a_t scripts
+ when calling the _p_a_s_s_w_d _p_r_o_g_r_a_m and should be turned
+ off after this has been done. This option has no effect
+ if the _p_a_m _p_a_s_s_w_o_r_d _c_h_a_n_g_e paramter is set. This
+ parameter is off by default.
+
+
+
+
+ Page 88 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ See also _p_a_s_s_w_d _c_h_a_t , _p_a_m _p_a_s_s_w_o_r_d _c_h_a_n_g_e , _p_a_s_s_w_d
+ _p_r_o_g_r_a_m .
+
+ Default: ppppaaaasssssssswwwwdddd cccchhhhaaaatttt ddddeeeebbbbuuuugggg ==== nnnnoooo
+
+ ppppaaaasssssssswwwwdddd pppprrrrooooggggrrrraaaammmm ((((GGGG))))
+ The name of a program that can be used to set UNIX user
+ passwords. Any occurrences of %_u will be replaced with
+ the user name. The user name is checked for existence
+ before calling the password changing program.
+
+ Also note that many passwd programs insist in
+ rrrreeeeaaaassssoooonnnnaaaabbbblllleeee passwords, such as a minimum length, or the
+ inclusion of mixed case chars and digits. This can pose
+ a problem as some clients (such as Windows for
+ Workgroups) uppercase the password before sending it.
+
+ NNNNooootttteeee that if the _u_n_i_x _p_a_s_s_w_o_r_d _s_y_n_c parameter is set to
+ yes then this program is called AAAASSSS RRRROOOOOOOOTTTT before the SMB
+ password in the smbpasswd(5)
+ file is changed. If this UNIX password change fails,
+ then ssssmmmmbbbbdddd will fail to change the SMB password also
+ (this is by design).
+
+ If the _u_n_i_x _p_a_s_s_w_o_r_d _s_y_n_c parameter is set this
+ parameter MMMMUUUUSSSSTTTT UUUUSSSSEEEE AAAABBBBSSSSOOOOLLLLUUUUTTTTEEEE PPPPAAAATTTTHHHHSSSS for AAAALLLLLLLL programs
+ called, and must be examined for security implications.
+ Note that by default _u_n_i_x _p_a_s_s_w_o_r_d _s_y_n_c is set to no.
+
+ See also _u_n_i_x _p_a_s_s_w_o_r_d _s_y_n_c.
+
+ Default: ppppaaaasssssssswwwwdddd pppprrrrooooggggrrrraaaammmm ==== ////bbbbiiiinnnn////ppppaaaasssssssswwwwdddd
+
+ Example: ppppaaaasssssssswwwwdddd pppprrrrooooggggrrrraaaammmm ==== ////ssssbbbbiiiinnnn////nnnnppppaaaasssssssswwwwdddd %%%%uuuu
+
+ ppppaaaasssssssswwwwoooorrrrdddd lllleeeevvvveeeellll ((((GGGG))))
+ Some client/server combinations have difficulty with
+ mixed-case passwords. One offending client is Windows
+ for Workgroups, which for some reason forces passwords
+ to upper case when using the LANMAN1 protocol, but
+ leaves them alone when using COREPLUS! Another problem
+ child is the Windows 95/98 family of operating systems.
+ These clients upper case clear text passwords even when
+ NT LM 0.12 selected by the protocol negotiation
+ request/response.
+
+ This parameter defines the maximum number of characters
+ that may be upper case in passwords.
+
+ For example, say the password given was "FRED". If
+ _p_a_s_s_w_o_r_d _l_e_v_e_l is set to 1, the following combinations
+ would be tried if "FRED" failed:
+
+
+
+ Page 89 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ "Fred", "fred", "fRed", "frEd","freD"
+
+ If _p_a_s_s_w_o_r_d _l_e_v_e_l was set to 2, the following
+ combinations would also be tried:
+
+ "FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..
+
+ And so on.
+
+ The higher value this parameter is set to the more
+ likely it is that a mixed case password will be matched
+ against a single case password. However, you should be
+ aware that use of this parameter reduces security and
+ increases the time taken to process a new connection.
+
+ A value of zero will cause only two attempts to be made
+ - the password as is and the password in all-lower
+ case.
+
+ Default: ppppaaaasssssssswwwwoooorrrrdddd lllleeeevvvveeeellll ==== 0000
+
+ Example: ppppaaaasssssssswwwwoooorrrrdddd lllleeeevvvveeeellll ==== 4444
+
+ ppppaaaasssssssswwwwoooorrrrdddd sssseeeerrrrvvvveeeerrrr ((((GGGG))))
+ By specifying the name of another SMB server (such as a
+ WinNT box) with this option, and using sssseeeeccccuuuurrrriiiittttyyyy ====
+ ddddoooommmmaaaaiiiinnnn or sssseeeeccccuuuurrrriiiittttyyyy ==== sssseeeerrrrvvvveeeerrrr you can get Samba to do all
+ its username/password validation via a remote server.
+
+ This option sets the name of the password server to
+ use. It must be a NetBIOS name, so if the machine's
+ NetBIOS name is different from its Internet name then
+ you may have to add its NetBIOS name to the lmhosts
+ file which is stored in the same directory as the
+ _s_m_b._c_o_n_f file.
+
+ The name of the password server is looked up using the
+ parameter _n_a_m_e _r_e_s_o_l_v_e _o_r_d_e_r and so may resolved by any
+ method and order described in that parameter.
+
+ The password server much be a machine capable of using
+ the "LM1.2X002" or the "NT LM 0.12" protocol, and it
+ must be in user level security mode.
+
+ NNNNOOOOTTTTEEEE:::: Using a password server means your UNIX box
+ (running Samba) is only as secure as your password
+ server. DDDDOOOO NNNNOOOOTTTT CCCCHHHHOOOOOOOOSSSSEEEE AAAA PPPPAAAASSSSSSSSWWWWOOOORRRRDDDD SSSSEEEERRRRVVVVEEEERRRR TTTTHHHHAAAATTTT YYYYOOOOUUUU DDDDOOOONNNN''''TTTT
+ CCCCOOOOMMMMPPPPLLLLEEEETTTTEEEELLLLYYYY TTTTRRRRUUUUSSSSTTTT.
+
+ Never point a Samba server at itself for password
+ serving. This will cause a loop and could lock up your
+ Samba server!
+
+
+
+ Page 90 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ The name of the password server takes the standard
+ substitutions, but probably the only useful one is %_m ,
+ which means the Samba server will use the incoming
+ client as the password server. If you use this then you
+ better trust your clients, and you had better restrict
+ them with hosts allow!
+
+ If the _s_e_c_u_r_i_t_y parameter is set to domain, then the
+ list of machines in this option must be a list of
+ Primary or Backup Domain controllers for the Domain or
+ the character '*', as the Samba server is effectively
+ in that domain, and will use cryptographically
+ authenticated RPC calls to authenticate the user
+ logging on. The advantage of using sssseeeeccccuuuurrrriiiittttyyyy ==== ddddoooommmmaaaaiiiinnnn
+ is that if you list several hosts in the _p_a_s_s_w_o_r_d
+ _s_e_r_v_e_r option then ssssmmmmbbbbdddd will try each in turn till it
+ finds one that responds. This is useful in case your
+ primary server goes down.
+
+ If the _p_a_s_s_w_o_r_d _s_e_r_v_e_r option is set to the character
+ '*', then Samba will attempt to auto-locate the Primary
+ or Backup Domain controllers to authenticate against by
+ doing a query for the name WORKGROUP<1C> and then
+ contacting each server returned in the list of IP
+ addresses from the name resolution source.
+
+ If the _s_e_c_u_r_i_t_y parameter is set to server, then there
+ are different restrictions that sssseeeeccccuuuurrrriiiittttyyyy ==== ddddoooommmmaaaaiiiinnnn
+ doesn't suffer from:
+
+ o+ You may list several password servers in the _p_a_s_s_w_o_r_d
+ _s_e_r_v_e_r parameter, however if an ssssmmmmbbbbdddd makes a
+ connection to a password server, and then the
+ password server fails, no more users will be able to
+ be authenticated from this ssssmmmmbbbbdddd. This is a
+ restriction of the SMB/CIFS protocol when in sssseeeeccccuuuurrrriiiittttyyyy
+ ==== sssseeeerrrrvvvveeeerrrr mode and cannot be fixed in Samba.
+
+ o+ If you are using a Windows NT server as your password
+ server then you will have to ensure that your users
+ are able to login from the Samba server, as when in
+ sssseeeeccccuuuurrrriiiittttyyyy ==== sssseeeerrrrvvvveeeerrrr mode the network logon will appear
+ to come from there rather than from the users
+ workstation.
+
+ See also the _s_e_c_u_r_i_t_y parameter.
+
+ Default: ppppaaaasssssssswwwwoooorrrrdddd sssseeeerrrrvvvveeeerrrr ==== <<<>>>
+
+ Example: ppppaaaasssssssswwwwoooorrrrdddd sssseeeerrrrvvvveeeerrrr ==== NNNNTTTT----PPPPDDDDCCCC,,,, NNNNTTTT----BBBBDDDDCCCC1111,,,, NNNNTTTT----BBBBDDDDCCCC2222
+
+ Example: ppppaaaasssssssswwwwoooorrrrdddd sssseeeerrrrvvvveeeerrrr ==== ****
+
+
+
+ Page 91 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ ppppaaaatttthhhh ((((SSSS))))
+ This parameter specifies a directory to which the user
+ of the service is to be given access. In the case of
+ printable services, this is where print data will spool
+ prior to being submitted to the host for printing.
+
+ For a printable service offering guest access, the
+ service should be readonly and the path should be
+ world-writeable and have the sticky bit set. This is
+ not mandatory of course, but you probably won't get the
+ results you expect if you do otherwise.
+
+ Any occurrences of %_u in the path will be replaced with
+ the UNIX username that the client is using on this
+ connection. Any occurrences of %_m will be replaced by
+ the NetBIOS name of the machine they are connecting
+ from. These replacements are very useful for setting up
+ pseudo home directories for users.
+
+ Note that this path will be based on _r_o_o_t _d_i_r if one
+ was specified.
+
+ Default: nnnnoooonnnneeee
+
+ Example: ppppaaaatttthhhh ==== ////hhhhoooommmmeeee////ffffrrrreeeedddd
+
+ ppppiiiidddd ddddiiiirrrreeeeccccttttoooorrrryyyy ((((GGGG))))
+ This option specifies the directory where pid files
+ will be placed.
+
+ Default: ppppiiiidddd ddddiiiirrrreeeeccccttttoooorrrryyyy ==== $$$${{{{pppprrrreeeeffffiiiixxxx}}}}////vvvvaaaarrrr////lllloooocccckkkkssss
+
+ Example: ppppiiiidddd ddddiiiirrrreeeeccccttttoooorrrryyyy ==== ////vvvvaaaarrrr////rrrruuuunnnn////
+
+ ppppoooossssiiiixxxx lllloooocccckkkkiiiinnnngggg ((((SSSS))))
+ The ssssmmmmbbbbdddd((((8888)))) daemon maintains an database of file locks
+ obtained by SMB clients. The default behavior is to
+ map this internal database to POSIX locks. This means
+ that file locks obtained by SMB clients are consistent
+ with those seen by POSIX compliant applications
+ accessing the files via a non-SMB method (e.g. NFS or
+ local file access). You should never need to disable
+ this parameter.
+
+ Default: ppppoooossssiiiixxxx lllloooocccckkkkiiiinnnngggg ==== yyyyeeeessss
+
+ ppppoooosssstttteeeexxxxeeeecccc ((((SSSS))))
+ This option specifies a command to be run whenever the
+ service is disconnected. It takes the usual
+ substitutions. The command may be run as the root on
+ some systems.
+
+
+
+
+ Page 92 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ An interesting example may be to unmount server
+ resources:
+
+ ppppoooosssstttteeeexxxxeeeecccc ==== ////eeeettttcccc////uuuummmmoooouuuunnnntttt ////ccccddddrrrroooommmm
+
+ See also _p_r_e_e_x_e_c .
+
+ Default: nnnnoooonnnneeee ((((nnnnoooo ccccoooommmmmmmmaaaannnndddd eeeexxxxeeeeccccuuuutttteeeedddd))))
+
+ Example: ppppoooosssstttteeeexxxxeeeecccc ==== eeeecccchhhhoooo \\\\""""%%%%uuuu ddddiiiissssccccoooonnnnnnnneeeecccctttteeeedddd ffffrrrroooommmm %%%%SSSS ffffrrrroooommmm
+ %%%%mmmm ((((%%%%IIII))))\\\\"""" >>>>>>>> ////ttttmmmmpppp////lllloooogggg
+
+ ppppoooossssttttssssccccrrrriiiipppptttt ((((SSSS))))
+ This parameter forces a printer to interpret the print
+ files as PostScript. This is done by adding a %! to
+ the start of print output.
+
+ This is most useful when you have lots of PCs that
+ persist in putting a control-D at the start of print
+ jobs, which then confuses your printer.
+
+ Default: ppppoooossssttttssssccccrrrriiiipppptttt ==== nnnnoooo
+
+ pppprrrreeeeeeeexxxxeeeecccc ((((SSSS))))
+ This option specifies a command to be run whenever the
+ service is connected to. It takes the usual
+ substitutions.
+
+ An interesting example is to send the users a welcome
+ message every time they log in. Maybe a message of the
+ day? Here is an example:
+
+ pppprrrreeeeeeeexxxxeeeecccc ==== ccccsssshhhh ----cccc ''''eeeecccchhhhoooo \\\\""""WWWWeeeellllccccoooommmmeeee ttttoooo %%%%SSSS!!!!\\\\"""" ||||
+ ////uuuussssrrrr////llllooooccccaaaallll////ssssaaaammmmbbbbaaaa////bbbbiiiinnnn////ssssmmmmbbbbcccclllliiiieeeennnntttt ----MMMM %%%%mmmm ----IIII %%%%IIII'''' &&&&
+
+ Of course, this could get annoying after a while :-)
+
+ See also _p_r_e_e_x_e_c _c_l_o_s_e and _p_o_s_t_e_x_e_c .
+
+ Default: nnnnoooonnnneeee ((((nnnnoooo ccccoooommmmmmmmaaaannnndddd eeeexxxxeeeeccccuuuutttteeeedddd))))
+
+ Example: pppprrrreeeeeeeexxxxeeeecccc ==== eeeecccchhhhoooo \\\\""""%%%%uuuu ccccoooonnnnnnnneeeecccctttteeeedddd ttttoooo %%%%SSSS ffffrrrroooommmm %%%%mmmm
+ ((((%%%%IIII))))\\\\"""" >>>>>>>> ////ttttmmmmpppp////lllloooogggg
+
+ pppprrrreeeeeeeexxxxeeeecccc cccclllloooosssseeee ((((SSSS))))
+ This boolean option controls whether a non-zero return
+ code from _p_r_e_e_x_e_c should close the service being
+ connected to.
+
+ Default: pppprrrreeeeeeeexxxxeeeecccc cccclllloooosssseeee ==== nnnnoooo
+
+ pppprrrreeeeffffeeeerrrrrrrreeeedddd mmmmaaaasssstttteeeerrrr ((((GGGG))))
+
+
+
+ Page 93 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ This boolean parameter controls if nmbd(8) is a
+ preferred master browser for its workgroup.
+
+ If this is set to yes, on startup, nnnnmmmmbbbbdddd will force an
+ election, and it will have a slight advantage in
+ winning the election. It is recommended that this
+ parameter is used in conjunction with _d_o_m_a_i_n _m_a_s_t_e_r ====
+ yyyyeeeessss, so that nnnnmmmmbbbbdddd can guarantee becoming a domain
+ master.
+
+ Use this option with caution, because if there are
+ several hosts (whether Samba servers, Windows 95 or NT)
+ that are preferred master browsers on the same subnet,
+ they will each periodically and continuously attempt to
+ become the local master browser. This will result in
+ unnecessary broadcast traffic and reduced browsing
+ capabilities.
+
+ See also _o_s _l_e_v_e_l .
+
+ Default: pppprrrreeeeffffeeeerrrrrrrreeeedddd mmmmaaaasssstttteeeerrrr ==== aaaauuuuttttoooo
+
+ pppprrrreeeeffffeeeerrrreeeedddd mmmmaaaasssstttteeeerrrr ((((GGGG))))
+ Synonym for _p_r_e_f_e_r_r_e_d _m_a_s_t_e_r for people who cannot
+ spell :-).
+
+ pppprrrreeeellllooooaaaadddd
+ This is a list of services that you want to be
+ automatically added to the browse lists. This is most
+ useful for homes and printers services that would
+ otherwise not be visible.
+
+ Note that if you just want all printers in your
+ printcap file loaded then the _l_o_a_d _p_r_i_n_t_e_r_s option is
+ easier.
+
+ Default: nnnnoooo pppprrrreeeellllooooaaaaddddeeeedddd sssseeeerrrrvvvviiiicccceeeessss
+
+ Example: pppprrrreeeellllooooaaaadddd ==== ffffrrrreeeedddd llllpppp ccccoooolllloooorrrrllllpppp
+
+ pppprrrreeeesssseeeerrrrvvvveeee ccccaaaasssseeee ((((SSSS))))
+ This controls if new filenames are created with the
+ case that the client passes, or if they are forced to
+ be the _d_e_f_a_u_l_t _c_a_s_e .
+
+ Default: pppprrrreeeesssseeeerrrrvvvveeee ccccaaaasssseeee ==== yyyyeeeessss
+
+ See the section on NAME MANGLING for a fuller
+ discussion.
+
+ pppprrrriiiinnnntttt ccccoooommmmmmmmaaaannnndddd ((((SSSS))))
+ After a print job has finished spooling to a service,
+
+
+
+ Page 94 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ this command will be used via a ssssyyyysssstttteeeemmmm(((()))) call to
+ process the spool file. Typically the command specified
+ will submit the spool file to the host's printing
+ subsystem, but there is no requirement that this be the
+ case. The server will not remove the spool file, so
+ whatever command you specify should remove the spool
+ file when it has been processed, otherwise you will
+ need to manually remove old spool files.
+
+ The print command is simply a text string. It will be
+ used verbatim after macro substitutions have been made:
+
+ s, %p - the path to the spool file name
+
+ %p - the appropriate printer name
+
+ %J - the job name as transmitted by the client.
+
+ %c - The number of printed pages of the spooled job (if
+ known).
+
+ %z - the size of the spooled print job (in bytes)
+
+ The print command MMMMUUUUSSSSTTTT contain at least one occurrence
+ of %_s or %_f - the %_p is optional. At the time a job is
+ submitted, if no printer name is supplied the %_p will
+ be silently removed from the printer command.
+
+ If specified in the [global] section, the print command
+ given will be used for any printable service that does
+ not have its own print command specified.
+
+ If there is neither a specified print command for a
+ printable service nor a global print command, spool
+ files will be created but not processed and (most
+ importantly) not removed.
+
+ Note that printing may fail on some UNIXes from the
+ nobody account. If this happens then create an
+ alternative guest account that can print and set the
+ _g_u_e_s_t _a_c_c_o_u_n_t in the [global] section.
+
+ You can form quite complex print commands by realizing
+ that they are just passed to a shell. For example the
+ following will log a print job, print the file, then
+ remove it. Note that ';' is the usual separator for
+ command in shell scripts.
+
+ pppprrrriiiinnnntttt ccccoooommmmmmmmaaaannnndddd ==== eeeecccchhhhoooo PPPPrrrriiiinnnnttttiiiinnnngggg %%%%ssss >>>>>>>> ////ttttmmmmpppp////pppprrrriiiinnnntttt....lllloooogggg;;;; llllpppprrrr
+ ----PPPP %%%%pppp %%%%ssss;;;; rrrrmmmm %%%%ssss
+
+ You may have to vary this command considerably
+
+
+
+ Page 95 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ depending on how you normally print files on your
+ system. The default for the parameter varies depending
+ on the setting of the _p_r_i_n_t_i_n_g parameter.
+
+ Default: For pppprrrriiiinnnnttttiiiinnnngggg ==== BBBBSSSSDDDD,,,, AAAAIIIIXXXX,,,, QQQQNNNNXXXX,,,, LLLLPPPPRRRRNNNNGGGG oooorrrr PPPPLLLLPPPP ::::
+
+ pppprrrriiiinnnntttt ccccoooommmmmmmmaaaannnndddd ==== llllpppprrrr ----rrrr ----PPPP%%%%pppp %%%%ssss
+
+ For pppprrrriiiinnnnttttiiiinnnngggg ==== SSSSYYYYSSSSVVVV oooorrrr HHHHPPPPUUUUXXXX ::::
+
+ pppprrrriiiinnnntttt ccccoooommmmmmmmaaaannnndddd ==== llllpppp ----cccc ----dddd%%%%pppp %%%%ssss;;;; rrrrmmmm %%%%ssss
+
+ For pppprrrriiiinnnnttttiiiinnnngggg ==== SSSSOOOOFFFFTTTTQQQQ ::::
+
+ pppprrrriiiinnnntttt ccccoooommmmmmmmaaaannnndddd ==== llllpppp ----dddd%%%%pppp ----ssss %%%%ssss;;;; rrrrmmmm %%%%ssss
+
+ For printing = CUPS : If SAMBA is compiled against
+ libcups, then printcap = cups uses the CUPS API to
+ submit jobs, etc. Otherwise it maps to the System V
+ commands with the -oraw option for printing, i.e. it
+ uses llllpppp ----cccc ----dddd%%%%pppp ----oooorrrraaaawwww;;;; rrrrmmmm %%%%ssss. With pppprrrriiiinnnnttttiiiinnnngggg ==== ccccuuuuppppssss, and
+ if SAMBA is compiled against libcups, any manually set
+ print command will be ignored.
+
+ Example: pppprrrriiiinnnntttt ccccoooommmmmmmmaaaannnndddd ====
+ ////uuuussssrrrr////llllooooccccaaaallll////ssssaaaammmmbbbbaaaa////bbbbiiiinnnn////mmmmyyyypppprrrriiiinnnnttttssssccccrrrriiiipppptttt %%%%pppp %%%%ssss
+
+ pppprrrriiiinnnntttt ooookkkk ((((SSSS))))
+ Synonym for _p_r_i_n_t_a_b_l_e.
+
+ pppprrrriiiinnnnttttaaaabbbblllleeee ((((SSSS))))
+ If this parameter is yes, then clients may open, write
+ to and submit spool files on the directory specified
+ for the service.
+
+ Note that a printable service will ALWAYS allow writing
+ to the service path (user privileges permitting) via
+ the spooling of print data. The _r_e_a_d _o_n_l_y parameter
+ controls only non-printing access to the resource.
+
+ Default: pppprrrriiiinnnnttttaaaabbbblllleeee ==== nnnnoooo
+
+ pppprrrriiiinnnnttttccccaaaapppp ((((GGGG))))
+ Synonym for _p_r_i_n_t_c_a_p _n_a_m_e.
+
+ pppprrrriiiinnnnttttccccaaaapppp nnnnaaaammmmeeee ((((GGGG))))
+ This parameter may be used to override the compiled-in
+ default printcap name used by the server (usually
+ /_e_t_c/_p_r_i_n_t_c_a_p). See the discussion of the [printers]
+ section above for reasons why you might want to do
+ this.
+
+
+
+
+ Page 96 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ To use the CUPS printing interface set pppprrrriiiinnnnttttccccaaaapppp nnnnaaaammmmeeee ====
+ ccccuuuuppppssss . This should be supplemented by an addtional
+ setting printing = cups in the [global] section.
+ pppprrrriiiinnnnttttccccaaaapppp nnnnaaaammmmeeee ==== ccccuuuuppppssss will use the "dummy" printcap
+ created by CUPS, as specified in your CUPS
+ configuration file.
+
+ On System V systems that use llllppppssssttttaaaatttt to list available
+ printers you can use pppprrrriiiinnnnttttccccaaaapppp nnnnaaaammmmeeee ==== llllppppssssttttaaaatttt to
+ automatically obtain lists of available printers. This
+ is the default for systems that define SYSV at
+ configure time in Samba (this includes most System V
+ based systems). If _p_r_i_n_t_c_a_p _n_a_m_e is set to llllppppssssttttaaaatttt on
+ these systems then Samba will launch llllppppssssttttaaaatttt ----vvvv and
+ attempt to parse the output to obtain a printer list.
+
+ A minimal printcap file would look something like this:
+
+
+ print1|My Printer 1
+ print2|My Printer 2
+ print3|My Printer 3
+ print4|My Printer 4
+ print5|My Printer 5
+
+
+
+ where the '|' separates aliases of a printer. The fact
+ that the second alias has a space in it gives a hint to
+ Samba that it's a comment.
+
+ NNNNOOOOTTTTEEEE: Under AIX the default printcap name is
+ /_e_t_c/_q_c_o_n_f_i_g. Samba will assume the file is in AIX
+ _q_c_o_n_f_i_g format if the string _q_c_o_n_f_i_g appears in the
+ printcap filename.
+
+ Default: pppprrrriiiinnnnttttccccaaaapppp nnnnaaaammmmeeee ==== ////eeeettttcccc////pppprrrriiiinnnnttttccccaaaapppp
+
+ Example: pppprrrriiiinnnnttttccccaaaapppp nnnnaaaammmmeeee ==== ////eeeettttcccc////mmmmyyyypppprrrriiiinnnnttttccccaaaapppp
+
+ pppprrrriiiinnnntttteeeerrrr aaaaddddmmmmiiiinnnn ((((SSSS))))
+ This is a list of users that can do anything to
+ printers via the remote administration interfaces
+ offered by MS-RPC (usually using a NT workstation).
+ Note that the root user always has admin rights.
+
+ Default: pppprrrriiiinnnntttteeeerrrr aaaaddddmmmmiiiinnnn ==== <<<>>>
+
+ Example: pppprrrriiiinnnntttteeeerrrr aaaaddddmmmmiiiinnnn ==== aaaaddddmmmmiiiinnnn,,,, @@@@ssssttttaaaaffffffff
+
+ pppprrrriiiinnnntttteeeerrrr ddddrrrriiiivvvveeeerrrr ((((SSSS))))
+ NNNNooootttteeee ::::This is a deprecated parameter and will be
+
+
+
+ Page 97 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ removed in the next major release following version
+ 2.2. Please see the instructions in the Samba 2.2.
+ Printing HOWTO for more information on the new method
+ of loading printer drivers onto a Samba server.
+
+ This option allows you to control the string that
+ clients receive when they ask the server for the
+ printer driver associated with a printer. If you are
+ using Windows95 or Windows NT then you can use this to
+ automate the setup of printers on your system.
+
+ You need to set this parameter to the exact string
+ (case sensitive) that describes the appropriate printer
+ driver for your system. If you don't know the exact
+ string to use then you should first try with no
+ _p_r_i_n_t_e_r _d_r_i_v_e_r option set and the client will give you
+ a list of printer drivers. The appropriate strings are
+ shown in a scroll box after you have chosen the printer
+ manufacturer.
+
+ See also _p_r_i_n_t_e_r _d_r_i_v_e_r _f_i_l_e.
+
+ Example: pppprrrriiiinnnntttteeeerrrr ddddrrrriiiivvvveeeerrrr ==== HHHHPPPP LLLLaaaasssseeeerrrrJJJJeeeetttt 4444LLLL
+
+ pppprrrriiiinnnntttteeeerrrr ddddrrrriiiivvvveeeerrrr ffffiiiilllleeee ((((GGGG))))
+ NNNNooootttteeee ::::This is a deprecated parameter and will be
+ removed in the next major release following version
+ 2.2. Please see the instructions in the Samba 2.2.
+ Printing HOWTO for more information on the new method
+ of loading printer drivers onto a Samba server.
+
+ This parameter tells Samba where the printer driver
+ definition file, used when serving drivers to Windows
+ 95 clients, is to be found. If this is not set, the
+ default is :
+
+ _S_A_M_B_A__I_N_S_T_A_L_L__D_I_R_E_C_T_O_R_Y /_l_i_b/_p_r_i_n_t_e_r_s._d_e_f
+
+ This file is created from Windows 95 _m_s_p_r_i_n_t._i_n_f files
+ found on the Windows 95 client system. For more details
+ on setting up serving of printer drivers to Windows 95
+ clients, see the outdated documentation file in the
+ _d_o_c_s/ directory, _P_R_I_N_T_E_R__D_R_I_V_E_R._t_x_t.
+
+ See also _p_r_i_n_t_e_r _d_r_i_v_e_r _l_o_c_a_t_i_o_n.
+
+ Default: NNNNoooonnnneeee ((((sssseeeetttt iiiinnnn ccccoooommmmppppiiiilllleeee))))....
+
+ Example: pppprrrriiiinnnntttteeeerrrr ddddrrrriiiivvvveeeerrrr ffffiiiilllleeee ====
+ ////uuuussssrrrr////llllooooccccaaaallll////ssssaaaammmmbbbbaaaa////pppprrrriiiinnnntttteeeerrrrssss////ddddrrrriiiivvvveeeerrrrssss....ddddeeeeffff
+
+ pppprrrriiiinnnntttteeeerrrr ddddrrrriiiivvvveeeerrrr llllooooccccaaaattttiiiioooonnnn ((((SSSS))))
+
+
+
+ Page 98 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ NNNNooootttteeee ::::This is a deprecated parameter and will be
+ removed in the next major release following version
+ 2.2. Please see the instructions in the Samba 2.2.
+ Printing HOWTO for more information on the new method
+ of loading printer drivers onto a Samba server.
+
+ This parameter tells clients of a particular printer
+ share where to find the printer driver files for the
+ automatic installation of drivers for Windows 95
+ machines. If Samba is set up to serve printer drivers
+ to Windows 95 machines, this should be set to
+
+ \\\\\\\\MMMMAAAACCCCHHHHIIIINNNNEEEE\\\\PPPPRRRRIIIINNNNTTTTEEEERRRR$$$$
+
+ Where MACHINE is the NetBIOS name of your Samba server,
+ and PRINTER$ is a share you set up for serving printer
+ driver files. For more details on setting this up see
+ the outdated documentation file in the _d_o_c_s/ directory,
+ _P_R_I_N_T_E_R__D_R_I_V_E_R._t_x_t.
+
+ See also _p_r_i_n_t_e_r _d_r_i_v_e_r _f_i_l_e.
+
+ Default: nnnnoooonnnneeee
+
+ Example: pppprrrriiiinnnntttteeeerrrr ddddrrrriiiivvvveeeerrrr llllooooccccaaaattttiiiioooonnnn ==== \\\\\\\\MMMMAAAACCCCHHHHIIIINNNNEEEE\\\\PPPPRRRRIIIINNNNTTTTEEEERRRR$$$$
+
+ pppprrrriiiinnnntttteeeerrrr nnnnaaaammmmeeee ((((SSSS))))
+ This parameter specifies the name of the printer to
+ which print jobs spooled through a printable service
+ will be sent.
+
+ If specified in the [global] section, the printer name
+ given will be used for any printable service that does
+ not have its own printer name specified.
+
+ Default: nnnnoooonnnneeee ((((bbbbuuuutttt mmmmaaaayyyy bbbbeeee llllpppp oooonnnn mmmmaaaannnnyyyy ssssyyyysssstttteeeemmmmssss))))
+
+ Example: pppprrrriiiinnnntttteeeerrrr nnnnaaaammmmeeee ==== llllaaaasssseeeerrrrwwwwrrrriiiitttteeeerrrr
+
+ pppprrrriiiinnnntttteeeerrrr ((((SSSS))))
+ Synonym for _p_r_i_n_t_e_r _n_a_m_e.
+
+ pppprrrriiiinnnnttttiiiinnnngggg ((((SSSS))))
+ This parameters controls how printer status information
+ is interpreted on your system. It also affects the
+ default values for the _p_r_i_n_t _c_o_m_m_a_n_d, _l_p_q _c_o_m_m_a_n_d,
+ _l_p_p_a_u_s_e _c_o_m_m_a_n_d , _l_p_r_e_s_u_m_e _c_o_m_m_a_n_d, and _l_p_r_m _c_o_m_m_a_n_d if
+ specified in the [global] section.
+
+ Currently nine printing styles are supported. They are
+ BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, SOFTQ, and CUPS.
+
+
+
+
+ Page 99 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ To see what the defaults are for the other print
+ commands when using the various options use the
+ testparm(1) program.
+
+ This option can be set on a per printer basis
+
+ See also the discussion in the [printers] section.
+
+ pppprrrrooooffffiiiilllleeee aaaaccccllllssss ((((SSSS))))
+ This boolean parameter was added to fix the problems
+ that people have been having with storing user profiles
+ on Samba shares from Windows 2000 or Windows XP
+ clients. New versions of Windows 2000 or Windows XP
+ service packs do security ACL checking on the owner and
+ ability to write of the profile directory stored on a
+ local workstation when copied from a Samba share. When
+ not in domain mode with winbindd then the security info
+ copied onto the local workstation has no meaning to the
+ logged in user (SID) on that workstation so the profile
+ storing fails. Adding this parameter onto a share used
+ for profile storage changes two things about the
+ returned Windows ACL. Firstly it changes the owner and
+ group owner of all reported files and directories to be
+ BUILTIN\Administrators, BUILTIN\Users respectively
+ (SIDs S-1-5-32-544, S-1-5-32-545). Secondly it adds an
+ ACE entry of "Full Control" to the SID BUILTIN\Users to
+ every returned ACL. This will allow any Windows 2000 or
+ XP workstation user to access the profile. Note that if
+ you have multiple users logging on to a workstation
+ then in order to prevent them from being able to access
+ each others profiles you must remove the "Bypass
+ traverse checking" advanced user right. This will
+ prevent access to other users profile directories as
+ the top level profile directory (named after the user)
+ is created by the workstation profile code and has an
+ ACL restricting entry to the directory tree to the
+ owning user.
+
+ If you didn't understand the above text, you probably
+ should not set this parameter :-).
+
+ Default pppprrrrooooffffiiiilllleeee aaaaccccllllssss ==== nnnnoooo
+
+ pppprrrroooottttooooccccoooollll ((((GGGG))))
+ Synonym for _m_a_x _p_r_o_t_o_c_o_l.
+
+ ppppuuuubbbblllliiiicccc ((((SSSS))))
+ Synonym for _g_u_e_s_t _o_k.
+
+ qqqquuuueeeeuuuueeeeppppaaaauuuusssseeee ccccoooommmmmmmmaaaannnndddd ((((SSSS))))
+ This parameter specifies the command to be executed on
+ the server host in order to pause the printer queue.
+
+
+
+ Page 100 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ This command should be a program or script which takes
+ a printer name as its only parameter and stops the
+ printer queue, such that no longer jobs are submitted
+ to the printer.
+
+ This command is not supported by Windows for
+ Workgroups, but can be issued from the Printers window
+ under Windows 95 and NT.
+
+ If a %_p is given then the printer name is put in its
+ place. Otherwise it is placed at the end of the
+ command.
+
+ Note that it is good practice to include the absolute
+ path in the command as the PATH may not be available to
+ the server.
+
+ Default: ddddeeeeppppeeeennnnddddssss oooonnnn tttthhhheeee sssseeeettttttttiiiinnnngggg ooooffff _p_r_i_n_t_i_n_g
+
+ Example: qqqquuuueeeeuuuueeeeppppaaaauuuusssseeee ccccoooommmmmmmmaaaannnndddd ==== ddddiiiissssaaaabbbblllleeee %%%%pppp
+
+ qqqquuuueeeeuuuueeeerrrreeeessssuuuummmmeeee ccccoooommmmmmmmaaaannnndddd ((((SSSS))))
+ This parameter specifies the command to be executed on
+ the server host in order to resume the printer queue.
+ It is the command to undo the behavior that is caused
+ by the previous parameter ( _q_u_e_u_e_p_a_u_s_e _c_o_m_m_a_n_d).
+
+ This command should be a program or script which takes
+ a printer name as its only parameter and resumes the
+ printer queue, such that queued jobs are resubmitted to
+ the printer.
+
+ This command is not supported by Windows for
+ Workgroups, but can be issued from the Printers window
+ under Windows 95 and NT.
+
+ If a %_p is given then the printer name is put in its
+ place. Otherwise it is placed at the end of the
+ command.
+
+ Note that it is good practice to include the absolute
+ path in the command as the PATH may not be available to
+ the server.
+
+ Default: ddddeeeeppppeeeennnnddddssss oooonnnn tttthhhheeee sssseeeettttttttiiiinnnngggg ooooffff _p_r_i_n_t_i_n_g
+
+ Example: qqqquuuueeeeuuuueeeeppppaaaauuuusssseeee ccccoooommmmmmmmaaaannnndddd ==== eeeennnnaaaabbbblllleeee %%%%pppp
+
+ rrrreeeeaaaadddd bbbbmmmmppppxxxx ((((GGGG))))
+ This boolean parameter controls whether smbd(8) will
+ support the "Read Block Multiplex" SMB. This is now
+ rarely used and defaults to no. You should never need
+
+
+
+ Page 101 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ to set this parameter.
+
+ Default: rrrreeeeaaaadddd bbbbmmmmppppxxxx ==== nnnnoooo
+
+ rrrreeeeaaaadddd lllliiiisssstttt ((((SSSS))))
+ This is a list of users that are given read-only access
+ to a service. If the connecting user is in this list
+ then they will not be given write access, no matter
+ what the _r_e_a_d _o_n_l_y option is set to. The list can
+ include group names using the syntax described in the
+ _i_n_v_a_l_i_d _u_s_e_r_s parameter.
+
+ See also the _w_r_i_t_e _l_i_s_t parameter and the _i_n_v_a_l_i_d
+ _u_s_e_r_s parameter.
+
+ Default: rrrreeeeaaaadddd lllliiiisssstttt ==== <<<>>>
+
+ Example: rrrreeeeaaaadddd lllliiiisssstttt ==== mmmmaaaarrrryyyy,,,, @@@@ssssttttuuuuddddeeeennnnttttssss
+
+ rrrreeeeaaaadddd oooonnnnllllyyyy ((((SSSS))))
+ An inverted synonym is _w_r_i_t_e_a_b_l_e.
+
+ If this parameter is yes, then users of a service may
+ not create or modify files in the service's directory.
+
+ Note that a printable service (pppprrrriiiinnnnttttaaaabbbblllleeee ==== yyyyeeeessss) will
+ AAAALLLLWWWWAAAAYYYYSSSS allow writing to the directory (user privileges
+ permitting), but only via spooling operations.
+
+ Default: rrrreeeeaaaadddd oooonnnnllllyyyy ==== yyyyeeeessss
+
+ rrrreeeeaaaadddd rrrraaaawwww ((((GGGG))))
+ This parameter controls whether or not the server will
+ support the raw read SMB requests when transferring
+ data to clients.
+
+ If enabled, raw reads allow reads of 65535 bytes in one
+ packet. This typically provides a major performance
+ benefit.
+
+ However, some clients either negotiate the allowable
+ block size incorrectly or are incapable of supporting
+ larger block sizes, and for these clients you may need
+ to disable raw reads.
+
+ In general this parameter should be viewed as a system
+ tuning tool and left severely alone. See also _w_r_i_t_e
+ _r_a_w.
+
+ Default: rrrreeeeaaaadddd rrrraaaawwww ==== yyyyeeeessss
+
+ rrrreeeeaaaadddd ssssiiiizzzzeeee ((((GGGG))))
+
+
+
+ Page 102 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ The option _r_e_a_d _s_i_z_e affects the overlap of disk
+ reads/writes with network reads/writes. If the amount
+ of data being transferred in several of the SMB
+ commands (currently SMBwrite, SMBwriteX and
+ SMBreadbraw) is larger than this value then the server
+ begins writing the data before it has received the
+ whole packet from the network, or in the case of
+ SMBreadbraw, it begins writing to the network before
+ all the data has been read from disk.
+
+ This overlapping works best when the speeds of disk and
+ network access are similar, having very little effect
+ when the speed of one is much greater than the other.
+
+ The default value is 16384, but very little
+ experimentation has been done yet to determine the
+ optimal value, and it is likely that the best value
+ will vary greatly between systems anyway. A value over
+ 65536 is pointless and will cause you to allocate
+ memory unnecessarily.
+
+ Default: rrrreeeeaaaadddd ssssiiiizzzzeeee ==== 11116666333388884444
+
+ Example: rrrreeeeaaaadddd ssssiiiizzzzeeee ==== 8888111199992222
+
+ rrrreeeemmmmooootttteeee aaaannnnnnnnoooouuuunnnncccceeee ((((GGGG))))
+ This option allows you to setup nmbd(8) to periodically
+ announce itself to arbitrary IP addresses with an
+ arbitrary workgroup name.
+
+ This is useful if you want your Samba server to appear
+ in a remote workgroup for which the normal browse
+ propagation rules don't work. The remote workgroup can
+ be anywhere that you can send IP packets to.
+
+ For example:
+
+ rrrreeeemmmmooootttteeee aaaannnnnnnnoooouuuunnnncccceeee ==== 111199992222....111166668888....2222....222255555555////SSSSEEEERRRRVVVVEEEERRRRSSSS
+ 111199992222....111166668888....4444....222255555555////SSSSTTTTAAAAFFFFFFFF
+
+ the above line would cause nnnnmmmmbbbbdddd to announce itself to
+ the two given IP addresses using the given workgroup
+ names. If you leave out the workgroup name then the one
+ given in the _w_o_r_k_g_r_o_u_p parameter is used instead.
+
+ The IP addresses you choose would normally be the
+ broadcast addresses of the remote networks, but can
+ also be the IP addresses of known browse masters if
+ your network config is that stable.
+
+ See the documentation file _B_R_O_W_S_I_N_G._t_x_t in the _d_o_c_s/
+ directory.
+
+
+
+ Page 103 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Default: rrrreeeemmmmooootttteeee aaaannnnnnnnoooouuuunnnncccceeee ==== <<<>>>
+
+ rrrreeeemmmmooootttteeee bbbbrrrroooowwwwsssseeee ssssyyyynnnncccc ((((GGGG))))
+ This option allows you to setup nmbd(8) to periodically
+ request synchronization of browse lists with the master
+ browser of a Samba server that is on a remote segment.
+ This option will allow you to gain browse lists for
+ multiple workgroups across routed networks. This is
+ done in a manner that does not work with any non-Samba
+ servers.
+
+ This is useful if you want your Samba server and all
+ local clients to appear in a remote workgroup for which
+ the normal browse propagation rules don't work. The
+ remote workgroup can be anywhere that you can send IP
+ packets to.
+
+ For example:
+
+ rrrreeeemmmmooootttteeee bbbbrrrroooowwwwsssseeee ssssyyyynnnncccc ==== 111199992222....111166668888....2222....222255555555 111199992222....111166668888....4444....222255555555
+
+ the above line would cause nnnnmmmmbbbbdddd to request the master
+ browser on the specified subnets or addresses to
+ synchronize their browse lists with the local server.
+
+ The IP addresses you choose would normally be the
+ broadcast addresses of the remote networks, but can
+ also be the IP addresses of known browse masters if
+ your network config is that stable. If a machine IP
+ address is given Samba makes NO attempt to validate
+ that the remote machine is available, is listening, nor
+ that it is in fact the browse master on its segment.
+
+ Default: rrrreeeemmmmooootttteeee bbbbrrrroooowwwwsssseeee ssssyyyynnnncccc ==== <<<>>>
+
+ rrrreeeessssttttrrrriiiicccctttt aaaannnnoooonnnnyyyymmmmoooouuuussss ((((GGGG))))
+ This is a boolean parameter. If it is yes, then
+ anonymous access to the server will be restricted,
+ namely in the case where the server is expecting the
+ client to send a username, but it doesn't. Setting it
+ to yes will force these anonymous connections to be
+ denied, and the client will be required to always
+ supply a username and password when connecting. Use of
+ this parameter is only recommended for homogeneous NT
+ client environments.
+
+ This parameter makes the use of macro expansions that
+ rely on the username (%U, %G, etc) consistent. NT 4.0
+ likes to use anonymous connections when refreshing the
+ share list, and this is a way to work around that.
+
+ When restrict anonymous is yes, all anonymous
+
+
+
+ Page 104 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ connections are denied no matter what they are for.
+ This can effect the ability of a machine to access the
+ Samba Primary Domain Controller to revalidate its
+ machine account after someone else has logged on the
+ client interactively. The NT client will display a
+ message saying that the machine's account in the domain
+ doesn't exist or the password is bad. The best way to
+ deal with this is to reboot NT client machines between
+ interactive logons, using "Shutdown and Restart",
+ rather than "Close all programs and logon as a
+ different user".
+
+ Default: rrrreeeessssttttrrrriiiicccctttt aaaannnnoooonnnnyyyymmmmoooouuuussss ==== nnnnoooo
+
+ rrrrooooooootttt ((((GGGG))))
+ Synonym for _r_o_o_t _d_i_r_e_c_t_o_r_y".
+
+ rrrrooooooootttt ddddiiiirrrr ((((GGGG))))
+ Synonym for _r_o_o_t _d_i_r_e_c_t_o_r_y".
+
+ rrrrooooooootttt ddddiiiirrrreeeeccccttttoooorrrryyyy ((((GGGG))))
+ The server will cccchhhhrrrrooooooootttt(((()))) (i.e. Change its root
+ directory) to this directory on startup. This is not
+ strictly necessary for secure operation. Even without
+ it the server will deny access to files not in one of
+ the service entries. It may also check for, and deny
+ access to, soft links to other parts of the filesystem,
+ or attempts to use ".." in file names to access other
+ directories (depending on the setting of the _w_i_d_e _l_i_n_k_s
+ parameter).
+
+ Adding a _r_o_o_t _d_i_r_e_c_t_o_r_y entry other than "/" adds an
+ extra level of security, but at a price. It absolutely
+ ensures that no access is given to files not in the
+ sub-tree specified in the _r_o_o_t _d_i_r_e_c_t_o_r_y option,
+ iiiinnnncccclllluuuuddddiiiinnnngggg some files needed for complete operation of
+ the server. To maintain full operability of the server
+ you will need to mirror some system files into the _r_o_o_t
+ _d_i_r_e_c_t_o_r_y tree. In particular you will need to mirror
+ /_e_t_c/_p_a_s_s_w_d (or a subset of it), and any binaries or
+ configuration files needed for printing (if required).
+ The set of files that must be mirrored is operating
+ system dependent.
+
+ Default: rrrrooooooootttt ddddiiiirrrreeeeccccttttoooorrrryyyy ==== ////
+
+ Example: rrrrooooooootttt ddddiiiirrrreeeeccccttttoooorrrryyyy ==== ////hhhhoooommmmeeeessss////ssssmmmmbbbb
+
+ rrrrooooooootttt ppppoooosssstttteeeexxxxeeeecccc ((((SSSS))))
+ This is the same as the _p_o_s_t_e_x_e_c parameter except that
+ the command is run as root. This is useful for
+ unmounting filesystems (such as CDROMs) after a
+
+
+
+ Page 105 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ connection is closed.
+
+ See also _p_o_s_t_e_x_e_c.
+
+ Default: rrrrooooooootttt ppppoooosssstttteeeexxxxeeeecccc ==== <<<>>>
+
+ rrrrooooooootttt pppprrrreeeeeeeexxxxeeeecccc ((((SSSS))))
+ This is the same as the _p_r_e_e_x_e_c parameter except that
+ the command is run as root. This is useful for mounting
+ filesystems (such as CDROMs) when a connection is
+ opened.
+
+ See also _p_r_e_e_x_e_c and _p_r_e_e_x_e_c _c_l_o_s_e.
+
+ Default: rrrrooooooootttt pppprrrreeeeeeeexxxxeeeecccc ==== <<<>>>
+
+ rrrrooooooootttt pppprrrreeeeeeeexxxxeeeecccc cccclllloooosssseeee ((((SSSS))))
+ This is the same as the _p_r_e_e_x_e_c _c_l_o_s_e parameter except
+ that the command is run as root.
+
+ See also _p_r_e_e_x_e_c and _p_r_e_e_x_e_c _c_l_o_s_e.
+
+ Default: rrrrooooooootttt pppprrrreeeeeeeexxxxeeeecccc cccclllloooosssseeee ==== nnnnoooo
+
+ sssseeeeccccuuuurrrriiiittttyyyy ((((GGGG))))
+ This option affects how clients respond to Samba and is
+ one of the most important settings in the _s_m_b._c_o_n_f
+ file.
+
+ The option sets the "security mode bit" in replies to
+ protocol negotiations with smbd(8)
+ to turn share level security on or off. Clients decide
+ based on this bit whether (and how) to transfer user
+ and password information to the server.
+
+ The default is sssseeeeccccuuuurrrriiiittttyyyy ==== uuuusssseeeerrrr, as this is the most
+ common setting needed when talking to Windows 98 and
+ Windows NT.
+
+ The alternatives are sssseeeeccccuuuurrrriiiittttyyyy ==== sssshhhhaaaarrrreeee, sssseeeeccccuuuurrrriiiittttyyyy ====
+ sssseeeerrrrvvvveeeerrrr or sssseeeeccccuuuurrrriiiittttyyyy ==== ddddoooommmmaaaaiiiinnnn .
+
+ In versions of Samba prior to 2.0.0, the default was
+ sssseeeeccccuuuurrrriiiittttyyyy ==== sssshhhhaaaarrrreeee mainly because that was the only
+ option at one stage.
+
+ There is a bug in WfWg that has relevance to this
+ setting. When in user or server level security a WfWg
+ client will totally ignore the password you type in the
+ "connect drive" dialog box. This makes it very
+ difficult (if not impossible) to connect to a Samba
+ service as anyone except the user that you are logged
+
+
+
+ Page 106 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ into WfWg as.
+
+ If your PCs use usernames that are the same as their
+ usernames on the UNIX machine then you will want to use
+ sssseeeeccccuuuurrrriiiittttyyyy ==== uuuusssseeeerrrr. If you mostly use usernames that don't
+ exist on the UNIX box then use sssseeeeccccuuuurrrriiiittttyyyy ==== sssshhhhaaaarrrreeee.
+
+ You should also use sssseeeeccccuuuurrrriiiittttyyyy ==== sssshhhhaaaarrrreeee if you want to
+ mainly setup shares without a password (guest shares).
+ This is commonly used for a shared printer server. It
+ is more difficult to setup guest shares with sssseeeeccccuuuurrrriiiittttyyyy ====
+ uuuusssseeeerrrr, see the _m_a_p _t_o _g_u_e_s_t parameter for details.
+
+ It is possible to use ssssmmmmbbbbdddd in a hhhhyyyybbbbrrrriiiidddd mmmmooooddddeeee where it
+ is offers both user and share level security under
+ different _N_e_t_B_I_O_S _a_l_i_a_s_e_s.
+
+ The different settings will now be explained.
+
+ SSSSEEEECCCCUUUURRRRIIIITTTTYYYY ==== SSSSHHHHAAAARRRREEEE
+
+ When clients connect to a share level security server
+ they need not log onto the server with a valid username
+ and password before attempting to connect to a shared
+ resource (although modern clients such as Windows 95/98
+ and Windows NT will send a logon request with a
+ username but no password when talking to a sssseeeeccccuuuurrrriiiittttyyyy ====
+ sssshhhhaaaarrrreeee server). Instead, the clients send authentication
+ information (passwords) on a per-share basis, at the
+ time they attempt to connect to that share.
+
+ Note that ssssmmmmbbbbdddd AAAALLLLWWWWAAAAYYYYSSSS uses a valid UNIX user to act on
+ behalf of the client, even in sssseeeeccccuuuurrrriiiittttyyyy ==== sssshhhhaaaarrrreeee level
+ security.
+
+ As clients are not required to send a username to the
+ server in share level security, ssssmmmmbbbbdddd uses several
+ techniques to determine the correct UNIX user to use on
+ behalf of the client.
+
+ A list of possible UNIX usernames to match with the
+ given client password is constructed using the
+ following methods :
+
+ o+ If the _g_u_e_s_t _o_n_l_y parameter is set, then all the
+ other stages are missed and only the _g_u_e_s_t _a_c_c_o_u_n_t
+ username is checked.
+
+ o+ Is a username is sent with the share connection
+ request, then this username (after mapping - see
+ _u_s_e_r_n_a_m_e _m_a_p), is added as a potential username.
+
+
+
+
+ Page 107 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ If the client did a previous llllooooggggoooonnnn request (the
+ SessionSetup SMB call) then the username sent in this
+ SMB will be added as a potential username.
+
+ o+ The name of the service the client requested is added
+ as a potential username.
+
+ o+ The NetBIOS name of the client is added to the list
+ as a potential username.
+
+ o+ Any users on the _u_s_e_r list are added as potential
+ usernames.
+
+ If the _g_u_e_s_t _o_n_l_y parameter is not set, then this list is
+ then tried with the supplied password. The first user for
+ whom the password matches will be used as the UNIX user.
+
+ If the _g_u_e_s_t _o_n_l_y parameter is set, or no username can be
+ determined then if the share is marked as available to the
+ _g_u_e_s_t _a_c_c_o_u_n_t, then this guest user will be used, otherwise
+ access is denied.
+
+ Note that it can be vvvveeeerrrryyyy confusing in share-level security
+ as to which UNIX username will eventually be used in
+ granting access.
+
+ See also the section NOTE ABOUT USERNAME/PASSWORD
+ VALIDATION.
+
+ SSSSEEEECCCCUUUURRRRIIIITTTTYYYY ==== UUUUSSSSEEEERRRR
+
+ This is the default security setting in Samba 2.2. With
+ user-level security a client must first "log-on" with a
+ valid username and password (which can be mapped using the
+ _u_s_e_r_n_a_m_e _m_a_p parameter). Encrypted passwords (see the
+ _e_n_c_r_y_p_t_e_d _p_a_s_s_w_o_r_d_s parameter) can also be used in this
+ security mode. Parameters such as _u_s_e_r and _g_u_e_s_t _o_n_l_y if
+ set are then applied and may change the UNIX user to use on
+ this connection, but only after the user has been
+ successfully authenticated.
+
+ NNNNooootttteeee that the name of the resource being requested is nnnnooootttt
+ sent to the server until after the server has successfully
+ authenticated the client. This is why guest shares don't
+ work in user level security without allowing the server to
+ automatically map unknown users into the _g_u_e_s_t _a_c_c_o_u_n_t. See
+ the _m_a_p _t_o _g_u_e_s_t parameter for details on doing this.
+
+ See also the section NOTE ABOUT USERNAME/PASSWORD
+ VALIDATION.
+
+ SSSSEEEECCCCUUUURRRRIIIITTTTYYYY ==== SSSSEEEERRRRVVVVEEEERRRR
+
+
+
+ Page 108 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ In this mode Samba will try to validate the
+ username/password by passing it to another SMB server, such
+ as an NT box. If this fails it will revert to sssseeeeccccuuuurrrriiiittttyyyy ====
+ uuuusssseeeerrrr, but note that if encrypted passwords have been
+ negotiated then Samba cannot revert back to checking the
+ UNIX password file, it must have a valid _s_m_b_p_a_s_s_w_d file to
+ check users against. See the documentation file in the _d_o_c_s/
+ directory _E_N_C_R_Y_P_T_I_O_N._t_x_t for details on how to set this up.
+
+ NNNNooootttteeee that from the client's point of view sssseeeeccccuuuurrrriiiittttyyyy ==== sssseeeerrrrvvvveeeerrrr
+ is the same as sssseeeeccccuuuurrrriiiittttyyyy ==== uuuusssseeeerrrr. It only affects how the
+ server deals with the authentication, it does not in any way
+ affect what the client sees.
+
+ NNNNooootttteeee that the name of the resource being requested is nnnnooootttt
+ sent to the server until after the server has successfully
+ authenticated the client. This is why guest shares don't
+ work in user level security without allowing the server to
+ automatically map unknown users into the _g_u_e_s_t _a_c_c_o_u_n_t. See
+ the _m_a_p _t_o _g_u_e_s_t parameter for details on doing this.
+
+ See also the section NOTE ABOUT USERNAME/PASSWORD
+ VALIDATION.
+
+ See also the _p_a_s_s_w_o_r_d _s_e_r_v_e_r parameter and the _e_n_c_r_y_p_t_e_d
+ _p_a_s_s_w_o_r_d_s parameter.
+
+ SSSSEEEECCCCUUUURRRRIIIITTTTYYYY ==== DDDDOOOOMMMMAAAAIIIINNNN
+
+ This mode will only work correctly if smbpasswd(8) has been
+ used to add this machine into a Windows NT Domain. It
+ expects the _e_n_c_r_y_p_t_e_d _p_a_s_s_w_o_r_d_s parameter to be set to yes.
+ In this mode Samba will try to validate the
+ username/password by passing it to a Windows NT Primary or
+ Backup Domain Controller, in exactly the same way that a
+ Windows NT Server would do.
+
+ NNNNooootttteeee that a valid UNIX user must still exist as well as the
+ account on the Domain Controller to allow Samba to have a
+ valid UNIX account to map file access to.
+
+ NNNNooootttteeee that from the client's point of view sssseeeeccccuuuurrrriiiittttyyyy ==== ddddoooommmmaaaaiiiinnnn
+ is the same as sssseeeeccccuuuurrrriiiittttyyyy ==== uuuusssseeeerrrr . It only affects how the
+ server deals with the authentication, it does not in any way
+ affect what the client sees.
+
+ NNNNooootttteeee that the name of the resource being requested is nnnnooootttt
+ sent to the server until after the server has successfully
+ authenticated the client. This is why guest shares don't
+ work in user level security without allowing the server to
+ automatically map unknown users into the _g_u_e_s_t _a_c_c_o_u_n_t. See
+ the _m_a_p _t_o _g_u_e_s_t parameter for details on doing this.
+
+
+
+ Page 109 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ BBBBUUUUGGGG:::: There is currently a bug in the implementation of
+ sssseeeeccccuuuurrrriiiittttyyyy ==== ddddoooommmmaaaaiiiinnnn with respect to multi-byte character set
+ usernames. The communication with a Domain Controller must
+ be done in UNICODE and Samba currently does not widen
+ multi-byte user names to UNICODE correctly, thus a multi-
+ byte username will not be recognized correctly at the Domain
+ Controller. This issue will be addressed in a future
+ release.
+
+ See also the section NOTE ABOUT USERNAME/PASSWORD
+ VALIDATION.
+
+ See also the _p_a_s_s_w_o_r_d _s_e_r_v_e_r parameter and the _e_n_c_r_y_p_t_e_d
+ _p_a_s_s_w_o_r_d_s parameter.
+
+ Default: sssseeeeccccuuuurrrriiiittttyyyy ==== UUUUSSSSEEEERRRR
+
+ Example: sssseeeeccccuuuurrrriiiittttyyyy ==== DDDDOOOOMMMMAAAAIIIINNNN
+
+ sssseeeeccccuuuurrrriiiittttyyyy mmmmaaaasssskkkk ((((SSSS))))
+ This parameter controls what UNIX permission bits can
+ be modified when a Windows NT client is manipulating
+ the UNIX permission on a file using the native NT
+ security dialog box.
+
+ This parameter is applied as a mask (AND'ed with) to
+ the changed permission bits, thus preventing any bits
+ not in this mask from being modified. Essentially, zero
+ bits in this mask may be treated as a set of bits the
+ user is not allowed to change.
+
+ If not set explicitly this parameter is 0777, allowing
+ a user to modify all the user/group/world permissions
+ on a file.
+
+ NNNNooootttteeee 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 leave it set to 0777.
+
+ See also the _f_o_r_c_e _d_i_r_e_c_t_o_r_y _s_e_c_u_r_i_t_y _m_o_d_e, _d_i_r_e_c_t_o_r_y
+ _s_e_c_u_r_i_t_y _m_a_s_k, _f_o_r_c_e _s_e_c_u_r_i_t_y _m_o_d_e parameters.
+
+ Default: sssseeeeccccuuuurrrriiiittttyyyy mmmmaaaasssskkkk ==== 0000777777777777
+
+ Example: sssseeeeccccuuuurrrriiiittttyyyy mmmmaaaasssskkkk ==== 0000777777770000
+
+ sssseeeerrrrvvvveeeerrrr ssssttttrrrriiiinnnngggg ((((GGGG))))
+ This controls what string will show up in the printer
+ comment box in print manager and next to the IPC
+ connection in nnnneeeetttt vvvviiiieeeewwww. It can be any string that you
+
+
+
+ Page 110 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ wish to show to your users.
+
+ It also sets what will appear in browse lists next to
+ the machine name.
+
+ A %_v will be replaced with the Samba version number.
+
+ A %_h will be replaced with the hostname.
+
+ Default: sssseeeerrrrvvvveeeerrrr ssssttttrrrriiiinnnngggg ==== SSSSaaaammmmbbbbaaaa %%%%vvvv
+
+ Example: sssseeeerrrrvvvveeeerrrr ssssttttrrrriiiinnnngggg ==== UUUUnnnniiiivvvveeeerrrrssssiiiittttyyyy ooooffff GGGGNNNNUUUUssss SSSSaaaammmmbbbbaaaa
+ SSSSeeeerrrrvvvveeeerrrr
+
+ sssseeeetttt ddddiiiirrrreeeeccccttttoooorrrryyyy ((((SSSS))))
+ If sssseeeetttt ddddiiiirrrreeeeccccttttoooorrrryyyy ==== nnnnoooo, then users of the service may
+ not use the setdir command to change directory.
+
+ The sssseeeettttddddiiiirrrr command is only implemented in the Digital
+ Pathworks client. See the Pathworks documentation for
+ details.
+
+ Default: sssseeeetttt ddddiiiirrrreeeeccccttttoooorrrryyyy ==== nnnnoooo
+
+ sssshhhhaaaarrrreeee mmmmooooddddeeeessss ((((SSSS))))
+ This enables or disables the honoring of the _s_h_a_r_e
+ _m_o_d_e_s during a file open. These modes are used by
+ clients to gain exclusive read or write access to a
+ file.
+
+ These open modes are not directly supported by UNIX, so
+ they are simulated using shared memory, or lock files
+ if your UNIX doesn't support shared memory (almost all
+ do).
+
+ The share modes that are enabled by this option are
+ DENY_DOS, DENY_ALL, DENY_READ, DENY_WRITE, DENY_NONE
+ and DENY_FCB.
+
+ This option gives full share compatibility and enabled
+ by default.
+
+ You should NNNNEEEEVVVVEEEERRRR turn this parameter off as many
+ Windows applications will break if you do so.
+
+ Default: sssshhhhaaaarrrreeee mmmmooooddddeeeessss ==== yyyyeeeessss
+
+ sssshhhhoooorrrrtttt pppprrrreeeesssseeeerrrrvvvveeee ccccaaaasssseeee ((((SSSS))))
+ This boolean parameter controls if new files which
+ conform to 8.3 syntax, that is all in upper case and of
+ suitable length, are created upper case, or if they are
+ forced to be the _d_e_f_a_u_l_t _c_a_s_e . This option can be use
+
+
+
+ Page 111 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ with pppprrrreeeesssseeeerrrrvvvveeee ccccaaaasssseeee ==== yyyyeeeessss to permit long filenames to
+ retain their case, while short names are lowered.
+
+ See the section on NAME MANGLING.
+
+ Default: sssshhhhoooorrrrtttt pppprrrreeeesssseeeerrrrvvvveeee ccccaaaasssseeee ==== yyyyeeeessss
+
+ sssshhhhoooowwww aaaadddddddd pppprrrriiiinnnntttteeeerrrr wwwwiiiizzzzaaaarrrrdddd ((((GGGG))))
+ With the introduction of MS-RPC based printing support
+ for Windows NT/2000 client in Samba 2.2, a
+ "Printers..." folder will appear on Samba hosts in the
+ share listing. Normally this folder will contain an
+ icon for the MS Add Printer Wizard (APW). However, it
+ is possible to disable this feature regardless of the
+ level of privilege of the connected user.
+
+ Under normal circumstances, the Windows NT/2000 client
+ will open a handle on the printer server with
+ OpenPrinterEx() asking for Administrator privileges. If
+ the user does not have administrative access on the
+ print server (i.e is not root or a member of the
+ _p_r_i_n_t_e_r _a_d_m_i_n group), the OpenPrinterEx() call fails
+ and the client makes another open call with a request
+ for a lower privilege level. This should succeed,
+ however the APW icon will not be displayed.
+
+ Disabling the _s_h_o_w _a_d_d _p_r_i_n_t_e_r _w_i_z_a_r_d parameter will
+ always cause the OpenPrinterEx() on the server to fail.
+ Thus the APW icon will never be displayed. NNNNooootttteeee ::::This
+ does not prevent the same user from having
+ administrative privilege on an individual printer.
+
+ See also _a_d_d_p_r_i_n_t_e_r _c_o_m_m_a_n_d, _d_e_l_e_t_e_p_r_i_n_t_e_r _c_o_m_m_a_n_d,
+ _p_r_i_n_t_e_r _a_d_m_i_n
+
+ Default :sssshhhhoooowwww aaaadddddddd pppprrrriiiinnnntttteeeerrrr wwwwiiiizzzzaaaarrrrdddd ==== yyyyeeeessss
+
+ ssssmmmmbbbb ppppaaaasssssssswwwwdddd ffffiiiilllleeee ((((GGGG))))
+ This option sets the path to the encrypted smbpasswd
+ file. By default the path to the smbpasswd file is
+ compiled into Samba.
+
+ Default: ssssmmmmbbbb ppppaaaasssssssswwwwdddd ffffiiiilllleeee ==== $$$${{{{pppprrrreeeeffffiiiixxxx}}}}////pppprrrriiiivvvvaaaatttteeee////ssssmmmmbbbbppppaaaasssssssswwwwdddd
+
+ Example: ssssmmmmbbbb ppppaaaasssssssswwwwdddd ffffiiiilllleeee ==== ////eeeettttcccc////ssssaaaammmmbbbbaaaa////ssssmmmmbbbbppppaaaasssssssswwwwdddd
+
+ ssssoooocccckkkkeeeetttt aaaaddddddddrrrreeeessssssss ((((GGGG))))
+ This option allows you to control what address Samba
+ will listen for connections on. This is used to support
+ multiple virtual interfaces on the one server, each
+ with a different configuration.
+
+
+
+
+ Page 112 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ By default Samba will accept connections on any
+ address.
+
+ Example: ssssoooocccckkkkeeeetttt aaaaddddddddrrrreeeessssssss ==== 111199992222....111166668888....2222....22220000
+
+ ssssoooocccckkkkeeeetttt ooooppppttttiiiioooonnnnssss ((((GGGG))))
+ This option allows you to set socket options to be used
+ when talking with the client.
+
+ Socket options are controls on the networking layer of
+ the operating systems which allow the connection to be
+ tuned.
+
+ This option will typically be used to tune your Samba
+ server for optimal performance for your local network.
+ There is no way that Samba can know what the optimal
+ parameters are for your net, so you must experiment and
+ choose them yourself. We strongly suggest you read the
+ appropriate documentation for your operating system
+ first (perhaps mmmmaaaannnn sssseeeettttssssoooocccckkkkoooopppptttt will help).
+
+ You may find that on some systems Samba will say
+ "Unknown socket option" when you supply an option. This
+ means you either incorrectly typed it or you need to
+ add an include file to includes.h for your OS. If the
+ latter is the case please send the patch to
+ samba@samba.org .
+
+ Any of the supported socket options may be combined in
+ any way you like, as long as your OS allows it.
+
+ This is the list of socket options currently settable
+ using this option:
+
+ o+ SO_KEEPALIVE
+
+ o+ SO_REUSEADDR
+
+ o+ SO_BROADCAST
+
+ o+ TCP_NODELAY
+
+ o+ IPTOS_LOWDELAY
+
+ o+ IPTOS_THROUGHPUT
+
+ o+ SO_SNDBUF *
+
+ o+ SO_RCVBUF *
+
+ o+ SO_SNDLOWAT *
+
+
+
+
+ Page 113 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ SO_RCVLOWAT *
+
+ Those marked with a ''''****'''' take an integer argument. The others
+ can optionally take a 1 or 0 argument to enable or disable
+ the option, by default they will be enabled if you don't
+ specify 1 or 0.
+
+ To specify an argument use the syntax SOME_OPTION = VALUE
+ for example SSSSOOOO____SSSSNNNNDDDDBBBBUUUUFFFF ==== 8888111199992222. Note that you must not have
+ any spaces before or after the = sign.
+
+ If you are on a local network then a sensible option might
+ be
+
+ ssssoooocccckkkkeeeetttt ooooppppttttiiiioooonnnnssss ==== IIIIPPPPTTTTOOOOSSSS____LLLLOOOOWWWWDDDDEEEELLLLAAAAYYYY
+
+ If you have a local network then you could try:
+
+ ssssoooocccckkkkeeeetttt ooooppppttttiiiioooonnnnssss ==== IIIIPPPPTTTTOOOOSSSS____LLLLOOOOWWWWDDDDEEEELLLLAAAAYYYY TTTTCCCCPPPP____NNNNOOOODDDDEEEELLLLAAAAYYYY
+
+ If you are on a wide area network then perhaps try setting
+ IPTOS_THROUGHPUT.
+
+ Note that several of the options may cause your Samba server
+ to fail completely. Use these options with caution!
+
+ Default: ssssoooocccckkkkeeeetttt ooooppppttttiiiioooonnnnssss ==== TTTTCCCCPPPP____NNNNOOOODDDDEEEELLLLAAAAYYYY
+
+ Example: ssssoooocccckkkkeeeetttt ooooppppttttiiiioooonnnnssss ==== IIIIPPPPTTTTOOOOSSSS____LLLLOOOOWWWWDDDDEEEELLLLAAAAYYYY
+
+ ssssoooouuuurrrrcccceeee eeeennnnvvvviiiirrrroooonnnnmmmmeeeennnntttt ((((GGGG))))
+ This parameter causes Samba to set environment
+ variables as per the content of the file named.
+
+ If the value of this parameter starts with a "|"
+ character then Samba will treat that value as a pipe
+ command to open and will set the environment variables
+ from the output of the pipe.
+
+ The contents of the file or the output of the pipe
+ should be formatted as the output of the standard Unix
+ eeeennnnvvvv((((1111)))) command. This is of the form :
+
+ Example environment entry:
+
+ SSSSAAAAMMMMBBBBAAAA____NNNNEEEETTTTBBBBIIIIOOOOSSSS____NNNNAAAAMMMMEEEE ==== mmmmyyyyhhhhoooossssttttnnnnaaaammmmeeee
+
+ Default: NNNNoooo ddddeeeeffffaaaauuuulllltttt vvvvaaaalllluuuueeee
+
+ Examples: ssssoooouuuurrrrcccceeee eeeennnnvvvviiiirrrroooonnnnmmmmeeeennnntttt ==== ||||////eeeettttcccc////ssssmmmmbbbb....ccccoooonnnnffff....sssshhhh
+
+ Example: ssssoooouuuurrrrcccceeee eeeennnnvvvviiiirrrroooonnnnmmmmeeeennnntttt ==== ////uuuussssrrrr////llllooooccccaaaallll////ssssmmmmbbbb____eeeennnnvvvv____vvvvaaaarrrrssss
+
+
+
+ Page 114 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ ssssssssllll ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ This variable enables or disables the entire SSL mode.
+ If it is set to no, the SSL-enabled Samba behaves
+ exactly like the non-SSL Samba. If set to yes, it
+ depends on the variables _s_s_l _h_o_s_t_s and _s_s_l _h_o_s_t_s
+ _r_e_s_i_g_n whether an SSL connection will be required.
+
+ Default: ssssssssllll ==== nnnnoooo
+
+ ssssssssllll CCCCAAAA cccceeeerrrrttttDDDDiiiirrrr ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ This variable defines where to look up the
+ Certification Authorities. The given directory should
+ contain one file for each CA that Samba will trust. The
+ file name must be the hash value over the
+ "Distinguished Name" of the CA. How this directory is
+ set up is explained later in this document. All files
+ within the directory that don't fit into this naming
+ scheme are ignored. You don't need this variable if you
+ don't verify client certificates.
+
+ Default: ssssssssllll CCCCAAAA cccceeeerrrrttttDDDDiiiirrrr ==== ////uuuussssrrrr////llllooooccccaaaallll////ssssssssllll////cccceeeerrrrttttssss
+
+ ssssssssllll CCCCAAAA cccceeeerrrrttttFFFFiiiilllleeee ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ This variable is a second way to define the trusted
+ CAs. The certificates of the trusted CAs are collected
+ in one big file and this variable points to the file.
+ You will probably only use one of the two ways to
+ define your CAs. The first choice is preferable if you
+ have many CAs or want to be flexible, the second is
+ preferable if you only have one CA and want to keep
+ things simple (you won't need to create the hashed file
+ names). You don't need this variable if you don't
+ verify client certificates.
+
+ Default: ssssssssllll CCCCAAAA cccceeeerrrrttttFFFFiiiilllleeee ====
+ ////uuuussssrrrr////llllooooccccaaaallll////ssssssssllll////cccceeeerrrrttttssss////ttttrrrruuuusssstttteeeeddddCCCCAAAAssss....ppppeeeemmmm
+
+
+
+
+ Page 115 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ ssssssssllll cccciiiipppphhhheeeerrrrssss ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ This variable defines the ciphers that should be
+ offered during SSL negotiation. You should not set this
+ variable unless you know what you are doing.
+
+ ssssssssllll cccclllliiiieeeennnntttt cccceeeerrrrtttt ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ The certificate in this file is used by ssssmmmmbbbbcccclllliiiieeeennnntttt((((1111))))
+ if it exists. It's needed if the server requires a
+ client certificate.
+
+ Default: ssssssssllll cccclllliiiieeeennnntttt cccceeeerrrrtttt ====
+ ////uuuussssrrrr////llllooooccccaaaallll////ssssssssllll////cccceeeerrrrttttssss////ssssmmmmbbbbcccclllliiiieeeennnntttt....ppppeeeemmmm
+
+ ssssssssllll cccclllliiiieeeennnntttt kkkkeeeeyyyy ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ This is the private key for ssssmmmmbbbbcccclllliiiieeeennnntttt((((1111)))) It's only
+ needed if the client should have a certificate.
+
+ Default: ssssssssllll cccclllliiiieeeennnntttt kkkkeeeeyyyy ====
+ ////uuuussssrrrr////llllooooccccaaaallll////ssssssssllll////pppprrrriiiivvvvaaaatttteeee////ssssmmmmbbbbcccclllliiiieeeennnntttt....ppppeeeemmmm
+
+ ssssssssllll ccccoooommmmppppaaaattttiiiibbbbiiiilllliiiittttyyyy ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ This variable defines whether OpenSSL should be
+ configured for bug compatibility with other SSL
+ implementations. This is probably not desirable because
+ currently no clients with SSL implementations other
+ than OpenSSL exist.
+
+ Default: ssssssssllll ccccoooommmmppppaaaattttiiiibbbbiiiilllliiiittttyyyy ==== nnnnoooo
+
+ ssssssssllll eeeeggggdddd ssssoooocccckkkkeeeetttt ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+
+
+
+ Page 116 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ This option is used to define the location of the
+ communiation socket of an EGD or PRNGD daemon, from
+ which entropy can be retrieved. This option can be used
+ instead of or together with the _s_s_l _e_n_t_r_o_p_y _f_i_l_e
+ directive. 255 bytes of entropy will be retrieved from
+ the daemon.
+
+ Default: nnnnoooonnnneeee
+
+ ssssssssllll eeeennnnttttrrrrooooppppyyyy bbbbyyyytttteeeessss ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ This parameter is used to define the number of bytes
+ which should be read from the _s_s_l _e_n_t_r_o_p_y _f_i_l_e If a -1
+ is specified, the entire file will be read.
+
+ Default: ssssssssllll eeeennnnttttrrrrooooppppyyyy bbbbyyyytttteeeessss ==== 222255555555
+
+ ssssssssllll eeeennnnttttrrrrooooppppyyyy ffffiiiilllleeee ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ This parameter is used to specify a file from which
+ processes will read "random bytes" on startup. In order
+ to seed the internal pseudo random number generator,
+ entropy must be provided. On system with a /_d_e_v/_u_r_a_n_d_o_m
+ device file, the processes will retrieve its entropy
+ from the kernel. On systems without kernel entropy
+ support, a file can be supplied that will be read on
+ startup and that will be used to seed the PRNG.
+
+ Default: nnnnoooonnnneeee
+
+ ssssssssllll hhhhoooossssttttssss ((((GGGG))))
+ See _s_s_l _h_o_s_t_s _r_e_s_i_g_n.
+
+ ssssssssllll hhhhoooossssttttssss rrrreeeessssiiiiggggnnnn ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ These two variables define whether Samba will go into
+ SSL mode or not. If none of them is defined, Samba will
+
+
+
+ Page 117 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ allow only SSL connections. If the _s_s_l _h_o_s_t_s variable
+ lists hosts (by IP-address, IP-address range, net group
+ or name), only these hosts will be forced into SSL
+ mode. If the _s_s_l _h_o_s_t_s _r_e_s_i_g_n variable lists hosts,
+ only these hosts will NNNNOOOOTTTT be forced into SSL mode. The
+ syntax for these two variables is the same as for the
+ _h_o_s_t_s _a_l_l_o_w and _h_o_s_t_s _d_e_n_y pair of variables, only
+ that the subject of the decision is different: It's not
+ the access right but whether SSL is used or not.
+
+ The example below requires SSL connections from all
+ hosts outside the local net (which is 192.168.*.*).
+
+ Default: ssssssssllll hhhhoooossssttttssss ==== <<<>>>
+
+ ssssssssllll hhhhoooossssttttssss rrrreeeessssiiiiggggnnnn ==== <<<>>>
+
+ Example: ssssssssllll hhhhoooossssttttssss rrrreeeessssiiiiggggnnnn ==== 111199992222....111166668888....
+
+ ssssssssllll rrrreeeeqqqquuuuiiiirrrreeee cccclllliiiieeeennnnttttcccceeeerrrrtttt ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ If this variable is set to yes, the server will not
+ tolerate connections from clients that don't have a
+ valid certificate. The directory/file given in _s_s_l _C_A
+ _c_e_r_t_D_i_r and _s_s_l _C_A _c_e_r_t_F_i_l_e will be used to look up the
+ CAs that issued the client's certificate. If the
+ certificate can't be verified positively, the
+ connection will be terminated. If this variable is set
+ to no, clients don't need certificates. Contrary to web
+ applications you really sssshhhhoooouuuulllldddd require client
+ certificates. In the web environment the client's data
+ is sensitive (credit card numbers) and the server must
+ prove to be trustworthy. In a file server environment
+ the server's data will be sensitive and the clients
+ must prove to be trustworthy.
+
+ Default: ssssssssllll rrrreeeeqqqquuuuiiiirrrreeee cccclllliiiieeeennnnttttcccceeeerrrrtttt ==== nnnnoooo
+
+ ssssssssllll rrrreeeeqqqquuuuiiiirrrreeee sssseeeerrrrvvvveeeerrrrcccceeeerrrrtttt ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ If this variable is set to yes, the ssssmmmmbbbbcccclllliiiieeeennnntttt((((1111))))
+ will request a certificate from the server. Same as
+ _s_s_l _r_e_q_u_i_r_e _c_l_i_e_n_t_c_e_r_t for the server.
+
+
+
+
+ Page 118 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Default: ssssssssllll rrrreeeeqqqquuuuiiiirrrreeee sssseeeerrrrvvvveeeerrrrcccceeeerrrrtttt ==== nnnnoooo
+
+ ssssssssllll sssseeeerrrrvvvveeeerrrr cccceeeerrrrtttt ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ This is the file containing the server's certificate.
+ The server mmmmuuuusssstttt have a certificate. The file may also
+ contain the server's private key. See later for how
+ certificates and private keys are created.
+
+ Default: ssssssssllll sssseeeerrrrvvvveeeerrrr cccceeeerrrrtttt ==== <<<>>>
+
+ ssssssssllll sssseeeerrrrvvvveeeerrrr kkkkeeeeyyyy ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ This file contains the private key of the server. If
+ this variable is not defined, the key is looked up in
+ the certificate file (it may be appended to the
+ certificate). The server mmmmuuuusssstttt have a private key and
+ the certificate mmmmuuuusssstttt match this private key.
+
+ Default: ssssssssllll sssseeeerrrrvvvveeeerrrr kkkkeeeeyyyy ==== <<<>>>
+
+ ssssssssllll vvvveeeerrrrssssiiiioooonnnn ((((GGGG))))
+ This variable is part of SSL-enabled Samba. This is
+ only available if the SSL libraries have been compiled
+ on your system and the configure option --------wwwwiiiitttthhhh----ssssssssllll was
+ given at configure time.
+
+ This enumeration variable defines the versions of the
+ SSL protocol that will be used. ssl2or3 allows dynamic
+ negotiation of SSL v2 or v3, ssl2 results in SSL v2,
+ ssl3 results in SSL v3 and tls1 results in TLS v1. TLS
+ (Transport Layer Security) is the new standard for SSL.
+
+ Default: ssssssssllll vvvveeeerrrrssssiiiioooonnnn ==== """"ssssssssllll2222oooorrrr3333""""
+
+ ssssttttaaaatttt ccccaaaacccchhhheeee ((((GGGG))))
+ This parameter determines if smbd(8) will use a cache
+ in order to speed up case insensitive name mappings.
+ You should never need to change this parameter.
+
+ Default: ssssttttaaaatttt ccccaaaacccchhhheeee ==== yyyyeeeessss
+
+ ssssttttaaaatttt ccccaaaacccchhhheeee ssssiiiizzzzeeee ((((GGGG))))
+ This parameter determines the number of entries in the
+
+
+
+ Page 119 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ _s_t_a_t _c_a_c_h_e. You should never need to change this
+ parameter.
+
+ Default: ssssttttaaaatttt ccccaaaacccchhhheeee ssssiiiizzzzeeee ==== 55550000
+
+ ssssttttaaaattttuuuussss ((((GGGG))))
+ This enables or disables logging of connections to a
+ status file that smbstatus(1) can read.
+
+ With this disabled ssssmmmmbbbbssssttttaaaattttuuuussss won't be able to tell you
+ what connections are active. You should never need to
+ change this parameter.
+
+ Default: ssssttttaaaattttuuuussss ==== yyyyeeeessss
+
+ ssssttttrrrriiiicccctttt aaaallllllllooooccccaaaatttteeee ((((SSSS))))
+ This is a boolean that controls the handling of disk
+ space allocation in the server. When this is set to yes
+ the server will change from UNIX behaviour of not
+ committing real disk storage blocks when a file is
+ extended to the Windows behaviour of actually forcing
+ the disk system to allocate real storage blocks when a
+ file is created or extended to be a given size. In UNIX
+ terminology this means that Samba will stop creating
+ sparse files. This can be slow on some systems.
+
+ When strict allocate is no the server does sparse disk
+ block allocation when a file is extended.
+
+ Setting this to yes can help Samba return out of quota
+ messages on systems that are restricting the disk quota
+ of users.
+
+ Default: ssssttttrrrriiiicccctttt aaaallllllllooooccccaaaatttteeee ==== nnnnoooo
+
+ ssssttttrrrriiiicccctttt lllloooocccckkkkiiiinnnngggg ((((SSSS))))
+ This is a boolean that controls the handling of file
+ locking in the server. When this is set to yes the
+ server will check every read and write access for file
+ locks, and deny access if locks exist. This can be slow
+ on some systems.
+
+ When strict locking is no the server does file lock
+ checks only when the client explicitly asks for them.
+
+ Well-behaved clients always ask for lock checks when it
+ is important, so in the vast majority of cases ssssttttrrrriiiicccctttt
+ lllloooocccckkkkiiiinnnngggg ==== nnnnoooo is preferable.
+
+ Default: ssssttttrrrriiiicccctttt lllloooocccckkkkiiiinnnngggg ==== nnnnoooo
+
+ ssssttttrrrriiiicccctttt ssssyyyynnnncccc ((((SSSS))))
+
+
+
+ Page 120 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Many Windows applications (including the Windows 98
+ explorer shell) seem to confuse flushing buffer
+ contents to disk with doing a sync to disk. Under UNIX,
+ a sync call forces the process to be suspended until
+ the kernel has ensured that all outstanding data in
+ kernel disk buffers has been safely stored onto stable
+ storage. This is very slow and should only be done
+ rarely. Setting this parameter to no (the default)
+ means that smbd ignores the Windows applications
+ requests for a sync call. There is only a possibility
+ of losing data if the operating system itself that
+ Samba is running on crashes, so there is little danger
+ in this default setting. In addition, this fixes many
+ performance problems that people have reported with the
+ new Windows98 explorer shell file copies.
+
+ See also the _s_y_n_c _a_l_w_a_y_s> parameter.
+
+ Default: ssssttttrrrriiiicccctttt ssssyyyynnnncccc ==== nnnnoooo
+
+ ssssttttrrrriiiipppp ddddooootttt ((((GGGG))))
+ This parameter is now unused in Samba (2.2.5 and
+ above). It used strip trailing dots off UNIX filenames
+ but was not correctly implmented. In Samba 2.2.5 and
+ above UNIX filenames ending in a dot are invalid
+ Windows long filenames (as they are in Windows NT and
+ above) and are mangled to 8.3 before being returned to
+ a client.
+
+ Default: ssssttttrrrriiiipppp ddddooootttt ==== nnnnoooo
+
+ ssssyyyynnnncccc aaaallllwwwwaaaayyyyssss ((((SSSS))))
+ This is a boolean parameter that controls whether
+ writes will always be written to stable storage before
+ the write call returns. If this is no then the server
+ will be guided by the client's request in each write
+ call (clients can set a bit indicating that a
+ particular write should be synchronous). If this is yes
+ then every write will be followed by a ffffssssyyyynnnncccc(((()))) call to
+ ensure the data is written to disk. Note that the
+ _s_t_r_i_c_t _s_y_n_c parameter must be set to yes in order for
+ this parameter to have any affect.
+
+ See also the _s_t_r_i_c_t _s_y_n_c parameter.
+
+ Default: ssssyyyynnnncccc aaaallllwwwwaaaayyyyssss ==== nnnnoooo
+
+ ssssyyyysssslllloooogggg ((((GGGG))))
+ This parameter maps how Samba debug messages are logged
+ onto the system syslog logging levels. Samba debug
+ level zero maps onto syslog LOG_ERR, debug level one
+ maps onto LOG_WARNING, debug level two maps onto
+
+
+
+ Page 121 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ LOG_NOTICE, debug level three maps onto LOG_INFO. All
+ higher levels are mapped to LOG_DEBUG.
+
+ This parameter sets the threshold for sending messages
+ to syslog. Only messages with debug level less than
+ this value will be sent to syslog.
+
+ Default: ssssyyyysssslllloooogggg ==== 1111
+
+ ssssyyyysssslllloooogggg oooonnnnllllyyyy ((((GGGG))))
+ If this parameter is set then Samba debug messages are
+ logged into the system syslog only, and not to the
+ debug log files.
+
+ Default: ssssyyyysssslllloooogggg oooonnnnllllyyyy ==== nnnnoooo
+
+ tttteeeemmmmppppllllaaaatttteeee hhhhoooommmmeeeeddddiiiirrrr ((((GGGG))))
+ When filling out the user information for a Windows NT
+ user, the winbindd(8) daemon uses this parameter to
+ fill in the home directory for that user. If the string
+ %_D is present it is substituted with the user's Windows
+ NT domain name. If the string %_U is present it is
+ substituted with the user's Windows NT user name.
+
+ Default: tttteeeemmmmppppllllaaaatttteeee hhhhoooommmmeeeeddddiiiirrrr ==== ////hhhhoooommmmeeee////%%%%DDDD////%%%%UUUU
+
+ tttteeeemmmmppppllllaaaatttteeee sssshhhheeeellllllll ((((GGGG))))
+ When filling out the user information for a Windows NT
+ user, the winbindd(8) daemon uses this parameter to
+ fill in the login shell for that user.
+
+ Default: tttteeeemmmmppppllllaaaatttteeee sssshhhheeeellllllll ==== ////bbbbiiiinnnn////ffffaaaallllsssseeee
+
+ ttttiiiimmmmeeee ooooffffffffsssseeeetttt ((((GGGG))))
+ This parameter is a setting in minutes to add to the
+ normal GMT to local time conversion. This is useful if
+ you are serving a lot of PCs that have incorrect
+ daylight saving time handling.
+
+ Default: ttttiiiimmmmeeee ooooffffffffsssseeeetttt ==== 0000
+
+ Example: ttttiiiimmmmeeee ooooffffffffsssseeeetttt ==== 66660000
+
+ ttttiiiimmmmeeee sssseeeerrrrvvvveeeerrrr ((((GGGG))))
+ This parameter determines if nmbd(8) advertises itself
+ as a time server to Windows clients.
+
+ Default: ttttiiiimmmmeeee sssseeeerrrrvvvveeeerrrr ==== nnnnoooo
+
+ ttttiiiimmmmeeeessssttttaaaammmmpppp llllooooggggssss ((((GGGG))))
+ Synonym for _d_e_b_u_g _t_i_m_e_s_t_a_m_p.
+
+
+
+
+ Page 122 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ ttttoooottttaaaallll pppprrrriiiinnnntttt jjjjoooobbbbssss ((((GGGG))))
+ This parameter accepts an integer value which defines a
+ limit on the maximum number of print jobs that will be
+ accepted system wide at any given time. If a print job
+ is submitted by a client which will exceed this number,
+ then smbd will return an error indicating that no space
+ is available on the server. The default value of 0
+ means that no such limit exists. This parameter can be
+ used to prevent a server from exceeding its capacity
+ and is designed as a printing throttle. See also _m_a_x
+ _p_r_i_n_t _j_o_b_s.
+
+ Default: ttttoooottttaaaallll pppprrrriiiinnnntttt jjjjoooobbbbssss ==== 0000
+
+ Example: ttttoooottttaaaallll pppprrrriiiinnnntttt jjjjoooobbbbssss ==== 5555000000000000
+
+ uuuunnnniiiixxxx eeeexxxxtttteeeennnnssssiiiioooonnnnssss((((GGGG))))
+ This boolean parameter controls whether Samba implments
+ the CIFS UNIX extensions, as defined by HP. These
+ extensions enable Samba to better serve UNIX CIFS
+ clients by supporting features such as symbolic links,
+ hard links, etc... These extensions require a
+ similarly enabled client, and are of no current use to
+ Windows clients.
+
+ Default: uuuunnnniiiixxxx eeeexxxxtttteeeennnnssssiiiioooonnnnssss ==== nnnnoooo
+
+ uuuunnnniiiixxxx ppppaaaasssssssswwwwoooorrrrdddd ssssyyyynnnncccc ((((GGGG))))
+ This boolean parameter controls whether Samba attempts
+ to synchronize the UNIX password with the SMB password
+ when the encrypted SMB password in the smbpasswd file
+ is changed. If this is set to yes the program specified
+ in the _p_a_s_s_w_d _p_r_o_g_r_a_mparameter is called AAAASSSS RRRROOOOOOOOTTTT - to
+ allow the new UNIX password to be set without access to
+ the old UNIX password (as the SMB password change code
+ has no access to the old password cleartext, only the
+ new).
+
+ See also _p_a_s_s_w_d _p_r_o_g_r_a_m, _p_a_s_s_w_d _c_h_a_t.
+
+ Default: uuuunnnniiiixxxx ppppaaaasssssssswwwwoooorrrrdddd ssssyyyynnnncccc ==== nnnnoooo
+
+ uuuuppppddddaaaatttteeee eeeennnnccccrrrryyyypppptttteeeedddd ((((GGGG))))
+ This boolean parameter allows a user logging on with a
+ plaintext password to have their encrypted (hashed)
+ password in the smbpasswd file to be updated
+ automatically as they log on. This option allows a site
+ to migrate from plaintext password authentication
+ (users authenticate with plaintext password over the
+ wire, and are checked against a UNIX account database)
+ to encrypted password authentication (the SMB
+ challenge/response authentication mechanism) without
+
+
+
+ Page 123 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ forcing all users to re-enter their passwords via
+ smbpasswd at the time the change is made. This is a
+ convenience option to allow the change over to
+ encrypted passwords to be made over a longer period.
+ Once all users have encrypted representations of their
+ passwords in the smbpasswd file this parameter should
+ be set to no.
+
+ In order for this parameter to work correctly the
+ _e_n_c_r_y_p_t _p_a_s_s_w_o_r_d_s parameter must be set to no when this
+ parameter is set to yes.
+
+ Note that even when this parameter is set a user
+ authenticating to ssssmmmmbbbbdddd must still enter a valid
+ password in order to connect correctly, and to update
+ their hashed (smbpasswd) passwords.
+
+ Default: uuuuppppddddaaaatttteeee eeeennnnccccrrrryyyypppptttteeeedddd ==== nnnnoooo
+
+ uuuusssseeee cccclllliiiieeeennnntttt ddddrrrriiiivvvveeeerrrr ((((SSSS))))
+ This parameter applies only to Windows NT/2000 clients.
+ It has no affect on Windows 95/98/ME clients. When
+ serving a printer to Windows NT/2000 clients without
+ first installing a valid printer driver on the Samba
+ host, the client will be required to install a local
+ printer driver. From this point on, the client will
+ treat the print as a local printer and not a network
+ printer connection. This is much the same behavior that
+ will occur when ddddiiiissssaaaabbbblllleeee ssssppppoooooooollllssssssss ==== yyyyeeeessss.
+
+ The differentiating factor is that under normal
+ circumstances, the NT/2000 client will attempt to open
+ the network printer using MS-RPC. The problem is that
+ because the client considers the printer to be local,
+ it will attempt to issue the OpenPrinterEx() call
+ requesting access rights associated with the logged on
+ user. If the user possesses local administator rights
+ but not root privilegde on the Samba host (often the
+ case), the OpenPrinterEx() call will fail. The result
+ is that the client will now display an "Access Denied;
+ Unable to connect" message in the printer queue window
+ (even though jobs may successfully be printed).
+
+ If this parameter is enabled for a printer, then any
+ attempt to open the printer with the
+ PRINTER_ACCESS_ADMINISTER right is mapped to
+ PRINTER_ACCESS_USE instead. Thus allowing the
+ OpenPrinterEx() call to succeed. TTTThhhhiiiissss ppppaaaarrrraaaammmmeeeetttteeeerrrr MMMMUUUUSSSSTTTT
+ nnnnooootttt bbbbeeee aaaabbbblllleeee eeeennnnaaaabbbblllleeeedddd oooonnnn aaaa pppprrrriiiinnnntttt sssshhhhaaaarrrreeee wwwwhhhhiiiicccchhhh hhhhaaaassss vvvvaaaalllliiiidddd
+ pppprrrriiiinnnntttt ddddrrrriiiivvvveeeerrrr iiiinnnnssssttttaaaalllllllleeeedddd oooonnnn tttthhhheeee SSSSaaaammmmbbbbaaaa sssseeeerrrrvvvveeeerrrr....
+
+ See also disable spoolss
+
+
+
+ Page 124 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Default: uuuusssseeee cccclllliiiieeeennnntttt ddddrrrriiiivvvveeeerrrr ==== nnnnoooo
+
+ uuuusssseeee mmmmmmmmaaaapppp ((((GGGG))))
+ This global parameter determines if the tdb internals
+ of Samba can depend on mmap working correctly on the
+ running system. Samba requires a coherent mmap/read-
+ write system memory cache. Currently only HPUX does not
+ have such a coherent cache, and so this parameter is
+ set to no by default on HPUX. On all other systems this
+ parameter should be left alone. This parameter is
+ provided to help the Samba developers track down
+ problems with the tdb internal code.
+
+ Default: uuuusssseeee mmmmmmmmaaaapppp ==== yyyyeeeessss
+
+ uuuusssseeee rrrrhhhhoooossssttttssss ((((GGGG))))
+ If this global parameter is yes, it specifies that the
+ UNIX user's ._r_h_o_s_t_s file in their home directory will
+ be read to find the names of hosts and users who will
+ be allowed access without specifying a password.
+
+ NNNNOOOOTTTTEEEE:::: The use of _u_s_e _r_h_o_s_t_s can be a major security
+ hole. This is because you are trusting the PC to supply
+ the correct username. It is very easy to get a PC to
+ supply a false username. I recommend that the _u_s_e
+ _r_h_o_s_t_s option be only used if you really know what you
+ are doing.
+
+ Default: uuuusssseeee rrrrhhhhoooossssttttssss ==== nnnnoooo
+
+ uuuusssseeeerrrr ((((SSSS))))
+ Synonym for _u_s_e_r_n_a_m_e.
+
+ uuuusssseeeerrrrssss ((((SSSS))))
+ Synonym for _u_s_e_r_n_a_m_e.
+
+ uuuusssseeeerrrrnnnnaaaammmmeeee ((((SSSS))))
+ Multiple users may be specified in a comma-delimited
+ list, in which case the supplied password will be
+ tested against each username in turn (left to right).
+
+ The _u_s_e_r_n_a_m_e line is needed only when the PC is unable
+ to supply its own username. This is the case for the
+ COREPLUS protocol or where your users have different
+ WfWg usernames to UNIX usernames. In both these cases
+ you may also be better using the \\server\share%user
+ syntax instead.
+
+ The _u_s_e_r_n_a_m_e line is not a great solution in many cases
+ as it means Samba will try to validate the supplied
+ password against each of the usernames in the _u_s_e_r_n_a_m_e
+ line in turn. This is slow and a bad idea for lots of
+
+
+
+ Page 125 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ users in case of duplicate passwords. You may get
+ timeouts or security breaches using this parameter
+ unwisely.
+
+ Samba relies on the underlying UNIX security. This
+ parameter does not restrict who can login, it just
+ offers hints to the Samba server as to what usernames
+ might correspond to the supplied password. Users can
+ login as whoever they please and they will be able to
+ do no more damage than if they started a telnet
+ session. The daemon runs as the user that they log in
+ as, so they cannot do anything that user cannot do.
+
+ To restrict a service to a particular set of users you
+ can use the _v_a_l_i_d _u_s_e_r_s parameter.
+
+ If any of the usernames begin with a '@' then the name
+ will be looked up first in the NIS netgroups list (if
+ Samba is compiled with netgroup support), followed by a
+ lookup in the UNIX groups database and will expand to a
+ list of all users in the group of that name.
+
+ If any of the usernames begin with a '+' then the name
+ will be looked up only in the UNIX groups database and
+ will expand to a list of all users in the group of that
+ name.
+
+ If any of the usernames begin with a '&'then the name
+ will be looked up only in the NIS netgroups database
+ (if Samba is compiled with netgroup support) and will
+ expand to a list of all users in the netgroup group of
+ that name.
+
+ Note that searching though a groups database can take
+ quite some time, and some clients may time out during
+ the search.
+
+ See the section NOTE ABOUT USERNAME/PASSWORD VALIDATION
+ for more information on how this parameter determines
+ access to the services.
+
+ Default: TTTThhhheeee gggguuuueeeesssstttt aaaaccccccccoooouuuunnnntttt iiiiffff aaaa gggguuuueeeesssstttt sssseeeerrrrvvvviiiicccceeee,,,, eeeellllsssseeee
+ <<<>>>....
+
+ Examples:uuuusssseeeerrrrnnnnaaaammmmeeee ==== ffffrrrreeeedddd,,,, mmmmaaaarrrryyyy,,,, jjjjaaaacccckkkk,,,, jjjjaaaannnneeee,,,, @@@@uuuusssseeeerrrrssss,,,,
+ @@@@ppppccccggggrrrroooouuuupppp
+
+ uuuusssseeeerrrrnnnnaaaammmmeeee lllleeeevvvveeeellll ((((GGGG))))
+ This option helps Samba to try and 'guess' at the real
+ UNIX username, as many DOS clients send an all-
+ uppercase username. By default Samba tries all
+ lowercase, followed by the username with the first
+
+
+
+ Page 126 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ letter capitalized, and fails if the username is not
+ found on the UNIX machine.
+
+ If this parameter is set to non-zero the behavior
+ changes. This parameter is a number that specifies the
+ number of uppercase combinations to try while trying to
+ determine the UNIX user name. The higher the number the
+ more combinations will be tried, but the slower the
+ discovery of usernames will be. Use this parameter when
+ you have strange usernames on your UNIX machine, such
+ as AstrangeUser .
+
+ Default: uuuusssseeeerrrrnnnnaaaammmmeeee lllleeeevvvveeeellll ==== 0000
+
+ Example: uuuusssseeeerrrrnnnnaaaammmmeeee lllleeeevvvveeeellll ==== 5555
+
+ uuuusssseeeerrrrnnnnaaaammmmeeee mmmmaaaapppp ((((GGGG))))
+ This option allows you to specify a file containing a
+ mapping of usernames from the clients to the server.
+ This can be used for several purposes. The most common
+ is to map usernames that users use on DOS or Windows
+ machines to those that the UNIX box uses. The other is
+ to map multiple users to a single username so that they
+ can more easily share files.
+
+ The map file is parsed line by line. Each line should
+ contain a single UNIX username on the left then a '='
+ followed by a list of usernames on the right. The list
+ of usernames on the right may contain names of the form
+ @group in which case they will match any UNIX username
+ in that group. The special client name '*' is a
+ wildcard and matches any name. Each line of the map
+ file may be up to 1023 characters long.
+
+ The file is processed on each line by taking the
+ supplied username and comparing it with each username
+ on the right hand side of the '=' signs. If the
+ supplied name matches any of the names on the right
+ hand side then it is replaced with the name on the
+ left. Processing then continues with the next line.
+
+ If any line begins with a '#' or a ';' then it is
+ ignored
+
+ If any line begins with an '!' then the processing will
+ stop after that line if a mapping was done by the line.
+ Otherwise mapping continues with every line being
+ processed. Using '!' is most useful when you have a
+ wildcard mapping line later in the file.
+
+ For example to map from the name admin or administrator
+ to the UNIX name root you would use:
+
+
+
+ Page 127 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ rrrrooooooootttt ==== aaaaddddmmmmiiiinnnn aaaaddddmmmmiiiinnnniiiissssttttrrrraaaattttoooorrrr
+
+ Or to map anyone in the UNIX group system to the UNIX
+ name sys you would use:
+
+ ssssyyyyssss ==== @@@@ssssyyyysssstttteeeemmmm
+
+ You can have as many mappings as you like in a username
+ map file.
+
+ If your system supports the NIS NETGROUP option then
+ the netgroup database is checked before the /_e_t_c/_g_r_o_u_p
+ database for matching groups.
+
+ You can map Windows usernames that have spaces in them
+ by using double quotes around the name. For example:
+
+ ttttrrrriiiiddddggggeeee ==== """"AAAAnnnnddddrrrreeeewwww TTTTrrrriiiiddddggggeeeellllllll""""
+
+ would map the windows username "Andrew Tridgell" to the
+ unix username "tridge".
+
+ The following example would map mary and fred to the
+ unix user sys, and map the rest to guest. Note the use
+ of the '!' to tell Samba to stop processing if it gets
+ a match on that line.
+
+
+ !sys = mary fred
+ guest = *
+
+
+
+ Note that the remapping is applied to all occurrences
+ of usernames. Thus if you connect to \\server\fred and
+ fred is remapped to mary then you will actually be
+ connecting to \\server\mary and will need to supply a
+ password suitable for mary not fred. The only exception
+ to this is the username passed to the _p_a_s_s_w_o_r_d _s_e_r_v_e_r
+ (if you have one). The password server will receive
+ whatever username the client supplies without
+ modification.
+
+ Also note that no reverse mapping is done. The main
+ effect this has is with printing. Users who have been
+ mapped may have trouble deleting print jobs as
+ PrintManager under WfWg will think they don't own the
+ print job.
+
+ Default: nnnnoooo uuuusssseeeerrrrnnnnaaaammmmeeee mmmmaaaapppp
+
+ Example: uuuusssseeeerrrrnnnnaaaammmmeeee mmmmaaaapppp ==== ////uuuussssrrrr////llllooooccccaaaallll////ssssaaaammmmbbbbaaaa////lllliiiibbbb////uuuusssseeeerrrrssss....mmmmaaaapppp
+
+
+
+ Page 128 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ uuuusssseeee sssseeeennnnddddffffiiiilllleeee ((((SSSS))))
+ If this parameter is yes, and Samba was built with the
+ --with-sendfile-support option, and the underlying
+ operating system supports sendfile system call, then
+ some SMB read calls (mainly ReadAndX and ReadRaw) will
+ use the more efficient sendfile system call for files
+ that are exclusively oplocked. This may make more
+ efficient use of the system CPU's and cause Samba to be
+ faster. This is off by default as it's effects are
+ unknown as yet.
+
+ Default: uuuusssseeee sssseeeennnnddddffffiiiilllleeee ==== nnnnoooo
+
+ uuuuttttmmmmpppp ((((GGGG))))
+ This boolean parameter is only available if Samba has
+ been configured and compiled with the option --------wwwwiiiitttthhhh----
+ uuuuttttmmmmpppp. If set to yes then Samba will attempt to add utmp
+ or utmpx records (depending on the UNIX system)
+ whenever a connection is made to a Samba server. Sites
+ may use this to record the user connecting to a Samba
+ share.
+
+ See also the _u_t_m_p _d_i_r_e_c_t_o_r_y parameter.
+
+ Default: uuuuttttmmmmpppp ==== nnnnoooo
+
+ uuuuttttmmmmpppp ddddiiiirrrreeeeccccttttoooorrrryyyy((((GGGG))))
+ This parameter is only available if Samba has been
+ configured and compiled with the option --------wwwwiiiitttthhhh----uuuuttttmmmmpppp.
+ It specifies a directory pathname that is used to store
+ the utmp or utmpx files (depending on the UNIX system)
+ that record user connections to a Samba server. See
+ also the _u_t_m_p parameter. By default this is not set,
+ meaning the system will use whatever utmp file the
+ native system is set to use (usually /_v_a_r/_r_u_n/_u_t_m_p on
+ Linux).
+
+ Default: nnnnoooo uuuuttttmmmmpppp ddddiiiirrrreeeeccccttttoooorrrryyyy
+
+ vvvvaaaalllliiiidddd cccchhhhaaaarrrrssss ((((GGGG))))
+ The option allows you to specify additional characters
+ that should be considered valid by the server in
+ filenames. This is particularly useful for national
+ character sets, such as adding u-umlaut or a-ring.
+
+ The option takes a list of characters in either integer
+ or character form with spaces between them. If you give
+ two characters with a colon between them then it will
+ be taken as an lowercase:uppercase pair.
+
+ If you have an editor capable of entering the
+ characters into the config file then it is probably
+
+
+
+ Page 129 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ easiest to use this method. Otherwise you can specify
+ the characters in octal, decimal or hexadecimal form
+ using the usual C notation.
+
+ For example to add the single character 'Z' to the
+ charset (which is a pointless thing to do as it's
+ already there) you could do one of the following
+
+
+ valid chars = Z
+ valid chars = z:Z
+ valid chars = 0132:0172
+
+
+
+ The last two examples above actually add two
+ characters, and alter the uppercase and lowercase
+ mappings appropriately.
+
+ Note that you MMMMUUUUSSSSTTTT specify this parameter after the
+ _c_l_i_e_n_t _c_o_d_e _p_a_g_e parameter if you have both set. If
+ _c_l_i_e_n_t _c_o_d_e _p_a_g_e is set after the _v_a_l_i_d _c_h_a_r_s parameter
+ the _v_a_l_i_d _c_h_a_r_s settings will be overwritten.
+
+ See also the _c_l_i_e_n_t _c_o_d_e _p_a_g_e parameter.
+
+ Default: SSSSaaaammmmbbbbaaaa ddddeeeeffffaaaauuuullllttttssss ttttoooo uuuussssiiiinnnngggg aaaa rrrreeeeaaaassssoooonnnnaaaabbbblllleeee sssseeeetttt ooooffff
+ vvvvaaaalllliiiidddd cccchhhhaaaarrrraaaacccctttteeeerrrrssss ffffoooorrrr EEEEnnnngggglllliiiisssshhhh ssssyyyysssstttteeeemmmmssss
+
+ Example: vvvvaaaalllliiiidddd cccchhhhaaaarrrrssss ==== 0000333344445555::::0000333300005555 0000333366666666::::0000333322226666 0000333344444444::::0000333300004444
+
+ The above example allows filenames to have the Swedish
+ characters in them.
+
+ NNNNOOOOTTTTEEEE:::: It is actually quite difficult to correctly
+ produce a _v_a_l_i_d _c_h_a_r_s line for a particular system. To
+ automate the process tino@augsburg.net
+ has written a package
+ called vvvvaaaalllliiiiddddcccchhhhaaaarrrrssss which will automatically produce a
+ complete _v_a_l_i_d _c_h_a_r_s line for a given client system.
+ Look in the _e_x_a_m_p_l_e_s/_v_a_l_i_d_c_h_a_r_s/ subdirectory of your
+ Samba source code distribution for this package.
+
+ vvvvaaaalllliiiidddd uuuusssseeeerrrrssss ((((SSSS))))
+ This is a list of users that should be allowed to login
+ to this service. Names starting with '@', '+' and '&'
+ are interpreted using the same rules as described in
+ the _i_n_v_a_l_i_d _u_s_e_r_s parameter.
+
+ If this is empty (the default) then any user can login.
+ If a username is in both this list and the _i_n_v_a_l_i_d
+ _u_s_e_r_s list then access is denied for that user.
+
+
+
+ Page 130 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ The current servicename is substituted for %_S . This is
+ useful in the [homes] section.
+
+ See also _i_n_v_a_l_i_d _u_s_e_r_s
+
+ Default: NNNNoooo vvvvaaaalllliiiidddd uuuusssseeeerrrrssss lllliiiisssstttt ((((aaaannnnyyyyoooonnnneeee ccccaaaannnn llllooooggggiiiinnnn))))
+
+ Example: vvvvaaaalllliiiidddd uuuusssseeeerrrrssss ==== ggggrrrreeeegggg,,,, @@@@ppppccccuuuusssseeeerrrrssss
+
+ vvvveeeettttoooo ffffiiiilllleeeessss((((SSSS))))
+ This is a list of files and directories that are
+ neither visible nor accessible. Each entry in the list
+ must be separated by a '/', which allows spaces to be
+ included in the entry. '*' and '?' can be used to
+ specify multiple files or directories as in DOS
+ wildcards.
+
+ Each entry must be a unix path, not a DOS path and must
+ nnnnooootttt include the unix directory separator '/'.
+
+ Note that the _c_a_s_e _s_e_n_s_i_t_i_v_e option is applicable in
+ vetoing files.
+
+ One feature of the veto files parameter that it is
+ important to be aware of is Samba's behaviour when
+ trying to delete a directory. If a directory that is to
+ be deleted contains nothing but veto files this
+ deletion will ffffaaaaiiiillll unless you also set the _d_e_l_e_t_e _v_e_t_o
+ _f_i_l_e_s parameter to _y_e_s.
+
+ Setting this parameter will affect the performance of
+ Samba, as it will be forced to check all files and
+ directories for a match as they are scanned.
+
+ See also _h_i_d_e _f_i_l_e_s and _c_a_s_e _s_e_n_s_i_t_i_v_e.
+
+ Default: NNNNoooo ffffiiiilllleeeessss oooorrrr ddddiiiirrrreeeeccccttttoooorrrriiiieeeessss aaaarrrreeee vvvveeeettttooooeeeedddd....
+
+ Examples:
+
+ ; Veto any files containing the word Security,
+ ; any ending in .tmp, and any directory containing the
+ ; word root.
+ veto files = /*Security*/*.tmp/*root*/
+
+ ; Veto the Apple specific files that a NetAtalk server
+ ; creates.
+ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
+
+
+ vvvveeeettttoooo oooopppplllloooocccckkkk ffffiiiilllleeeessss ((((SSSS))))
+ This parameter is only valid when the _o_p_l_o_c_k_s parameter
+
+
+
+ Page 131 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ is turned on for a share. It allows the Samba
+ administrator to selectively turn off the granting of
+ oplocks on selected files that match a wildcarded list,
+ similar to the wildcarded list used in the _v_e_t_o _f_i_l_e_s
+ parameter.
+
+ Default: NNNNoooo ffffiiiilllleeeessss aaaarrrreeee vvvveeeettttooooeeeedddd ffffoooorrrr oooopppplllloooocccckkkk ggggrrrraaaannnnttttssss
+
+ You might want to do this on files that you know will
+ be heavily contended for by clients. A good example of
+ this is in the NetBench SMB benchmark program, which
+ causes heavy client contention for files ending in
+ ._S_E_M. To cause Samba not to grant oplocks on these
+ files you would use the line (either in the [global]
+ section or in the section for the particular NetBench
+ share :
+
+ Example: vvvveeeettttoooo oooopppplllloooocccckkkk ffffiiiilllleeeessss ==== ////****....SSSSEEEEMMMM////
+
+ vvvvffffssss oooobbbbjjjjeeeecccctttt ((((SSSS))))
+ This parameter specifies a shared object file that is
+ used for Samba VFS I/O operations. By default, normal
+ disk I/O operations are used but these can be
+ overloaded with a VFS object. The Samba VFS layer is
+ new to Samba 2.2 and must be enabled at compile time
+ with --with-vfs.
+
+ Default : nnnnoooo vvvvaaaalllluuuueeee
+
+ vvvvffffssss ooooppppttttiiiioooonnnnssss ((((SSSS))))
+ This parameter allows parameters to be passed to the
+ vfs layer at initialization time. The Samba VFS layer
+ is new to Samba 2.2 and must be enabled at compile time
+ with --with-vfs. See also _v_f_s _o_b_j_e_c_t.
+
+ Default : nnnnoooo vvvvaaaalllluuuueeee
+
+ vvvvoooolllluuuummmmeeee ((((SSSS))))
+ This allows you to override the volume label returned
+ for a share. Useful for CDROMs with installation
+ programs that insist on a particular volume label.
+
+ Default: tttthhhheeee nnnnaaaammmmeeee ooooffff tttthhhheeee sssshhhhaaaarrrreeee
+
+ wwwwiiiiddddeeee lllliiiinnnnkkkkssss ((((SSSS))))
+ This parameter controls whether or not links in the
+ UNIX file system may be followed by the server. Links
+ that point to areas within the directory tree exported
+ by the server are always allowed; this parameter
+ controls access only to areas that are outside the
+ directory tree being exported.
+
+
+
+
+ Page 132 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Note that setting this parameter can have a negative
+ effect on your server performance due to the extra
+ system calls that Samba has to do in order to perform
+ the link checks.
+
+ Default: wwwwiiiiddddeeee lllliiiinnnnkkkkssss ==== yyyyeeeessss
+
+ wwwwiiiinnnnbbbbiiiinnnndddd ccccaaaacccchhhheeee ttttiiiimmmmeeee ((((GGGG))))
+ This parameter specifies the number of seconds the
+ winbindd(8) daemon will cache user and group
+ information before querying a Windows NT server again.
+
+ Default: wwwwiiiinnnnbbbbiiiinnnndddd ccccaaaacccchhhheeee ttttyyyyppppeeee ==== 11115555
+
+ wwwwiiiinnnnbbbbiiiinnnndddd eeeennnnuuuummmm uuuusssseeeerrrrssss ((((GGGG))))
+ On large installations using winbindd(8) it may be
+ necessary to suppress the enumeration of users through
+ the sssseeeettttppppwwwweeeennnntttt(((()))), ggggeeeettttppppwwwweeeennnntttt(((()))) and eeeennnnddddppppwwwweeeennnntttt(((()))) group of
+ system calls. If the _w_i_n_b_i_n_d _e_n_u_m _u_s_e_r_s parameter is
+ no, calls to the ggggeeeettttppppwwwweeeennnntttt system call will not return
+ any data.
+
+ WWWWaaaarrrrnnnniiiinnnngggg:::: Turning off user enumeration may cause some
+ programs to behave oddly. For example, the finger
+ program relies on having access to the full user list
+ when searching for matching usernames.
+
+ Default: wwwwiiiinnnnbbbbiiiinnnndddd eeeennnnuuuummmm uuuusssseeeerrrrssss ==== yyyyeeeessss
+
+ wwwwiiiinnnnbbbbiiiinnnndddd eeeennnnuuuummmm ggggrrrroooouuuuppppssss ((((GGGG))))
+ On large installations using winbindd(8) it may be
+ necessary to suppress the enumeration of groups through
+ the sssseeeettttggggrrrreeeennnntttt(((()))), ggggeeeettttggggrrrreeeennnntttt(((()))) and eeeennnnddddggggrrrreeeennnntttt(((()))) group of
+ system calls. If the _w_i_n_b_i_n_d _e_n_u_m _g_r_o_u_p_s parameter is
+ no, calls to the ggggeeeettttggggrrrreeeennnntttt(((()))) system call will not return
+ any data.
+
+ WWWWaaaarrrrnnnniiiinnnngggg:::: Turning off group enumeration may cause some
+ programs to behave oddly.
+
+ Default: wwwwiiiinnnnbbbbiiiinnnndddd eeeennnnuuuummmm ggggrrrroooouuuuppppssss ==== yyyyeeeessss
+
+ wwwwiiiinnnnbbbbiiiinnnndddd ggggiiiidddd ((((GGGG))))
+ The winbind gid parameter specifies the range of group
+ ids that are allocated by the winbindd(8) daemon. This
+ range of group ids should have no existing local or NIS
+ groups within it as strange conflicts can occur
+ otherwise.
+
+ Default: wwwwiiiinnnnbbbbiiiinnnndddd ggggiiiidddd ==== <<<>>>
+
+ Example: wwwwiiiinnnnbbbbiiiinnnndddd ggggiiiidddd ==== 11110000000000000000----22220000000000000000
+
+
+
+ Page 133 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ wwwwiiiinnnnbbbbiiiinnnndddd sssseeeeppppaaaarrrraaaattttoooorrrr ((((GGGG))))
+ This parameter allows an admin to define the character
+ used when listing a username of the form of _D_O_M_A_I_N
+ \_u_s_e_r. This parameter is only applicable when using the
+ _p_a_m__w_i_n_b_i_n_d._s_o and _n_s_s__w_i_n_b_i_n_d._s_o modules for UNIX
+ services.
+
+ Please note that setting this parameter to + causes
+ problems with group membership at least on glibc
+ systems, as the character + is used as a special
+ character for NIS in /etc/group.
+
+ Default: wwwwiiiinnnnbbbbiiiinnnndddd sssseeeeppppaaaarrrraaaattttoooorrrr ==== ''''\\\\''''
+
+ Example: wwwwiiiinnnnbbbbiiiinnnndddd sssseeeeppppaaaarrrraaaattttoooorrrr ==== ++++
+
+ wwwwiiiinnnnbbbbiiiinnnndddd uuuuiiiidddd ((((GGGG))))
+ The winbind gid parameter specifies the range of group
+ ids that are allocated by the winbindd(8) daemon. This
+ range of ids should have no existing local or NIS users
+ within it as strange conflicts can occur otherwise.
+
+ Default: wwwwiiiinnnnbbbbiiiinnnndddd uuuuiiiidddd ==== <<<>>>
+
+ Example: wwwwiiiinnnnbbbbiiiinnnndddd uuuuiiiidddd ==== 11110000000000000000----22220000000000000000
+
+ wwwwiiiinnnnbbbbiiiinnnndddd uuuusssseeee ddddeeeeffffaaaauuuulllltttt ddddoooommmmaaaaiiiinnnn
+
+ wwwwiiiinnnnbbbbiiiinnnndddd uuuusssseeee ddddeeeeffffaaaauuuulllltttt ddddoooommmmaaaaiiiinnnn
+ This parameter specifies whether the winbindd(8)
+ daemon should operate on users without domain component
+ in their username. Users without a domain component are
+ treated as is part of the winbindd server's own domain.
+ While this does not benifit Windows users, it makes
+ SSH, FTP and e-mail function in a way much closer to
+ the way they would in a native unix system.
+
+ Default: wwwwiiiinnnnbbbbiiiinnnndddd uuuusssseeee ddddeeeeffffaaaauuuulllltttt ddddoooommmmaaaaiiiinnnn ==== <<<>>>
+
+ Example: wwwwiiiinnnnbbbbiiiinnnndddd uuuusssseeee ddddeeeeffffaaaauuuulllltttt ddddoooommmmaaaaiiiinnnn ==== yyyyeeeessss
+
+ wwwwiiiinnnnssss hhhhooooooookkkk ((((GGGG))))
+ When Samba is running as a WINS server this allows you
+ to call an external program for all changes to the WINS
+ database. The primary use for this option is to allow
+ the dynamic update of external name resolution
+ databases such as dynamic DNS.
+
+ The wins hook parameter specifies the name of a script
+ or executable that will be called as follows:
+
+ wwwwiiiinnnnssss____hhhhooooooookkkk ooooppppeeeerrrraaaattttiiiioooonnnn nnnnaaaammmmeeee nnnnaaaammmmeeeettttyyyyppppeeee ttttttttllll IIIIPPPP____lllliiiisssstttt
+
+
+
+ Page 134 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ o+ The first argument is the operation and is one of
+ "add", "delete", or "refresh". In most cases the
+ operation can be ignored as the rest of the
+ parameters provide sufficient information. Note that
+ "refresh" may sometimes be called when the name has
+ not previously been added, in that case it should be
+ treated as an add.
+
+ o+ The second argument is the NetBIOS name. If the name
+ is not a legal name then the wins hook is not called.
+ Legal names contain only letters, digits, hyphens,
+ underscores and periods.
+
+ o+ The third argument is the NetBIOS name type as a 2
+ digit hexadecimal number.
+
+ o+ The fourth argument is the TTL (time to live) for the
+ name in seconds.
+
+ o+ The fifth and subsequent arguments are the IP
+ addresses currently registered for that name. If this
+ list is empty then the name should be deleted.
+
+ An example script that calls the BIND dynamic DNS update
+ program nnnnssssuuuuppppddddaaaatttteeee is provided in the examples directory of
+ the Samba source code.
+
+ wwwwiiiinnnnssss pppprrrrooooxxxxyyyy ((((GGGG))))
+ This is a boolean that controls if nmbd(8) will respond
+ to broadcast name queries on behalf of other hosts. You
+ may need to set this to yes for some older clients.
+
+ Default: wwwwiiiinnnnssss pppprrrrooooxxxxyyyy ==== nnnnoooo
+
+ wwwwiiiinnnnssss sssseeeerrrrvvvveeeerrrr ((((GGGG))))
+ This specifies the IP address (or DNS name: IP address
+ for preference) of the WINS server that nmbd(8) should
+ register with. If you have a WINS server on your
+ network then you should set this to the WINS server's
+ IP.
+
+ You should point this at your WINS server if you have a
+ multi-subnetted network.
+
+ NNNNOOOOTTTTEEEE. You need to set up Samba to point to a WINS
+ server if you have multiple subnets and wish cross-
+ subnet browsing to work correctly.
+
+ See the documentation file _B_R_O_W_S_I_N_G._t_x_t in the docs/
+ directory of your Samba source distribution.
+
+ Default: nnnnooootttt eeeennnnaaaabbbblllleeeedddd
+
+
+
+ Page 135 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ Example: wwwwiiiinnnnssss sssseeeerrrrvvvveeeerrrr ==== 111199992222....9999....222200000000....1111
+
+ wwwwiiiinnnnssss ssssuuuuppppppppoooorrrrtttt ((((GGGG))))
+ This boolean controls if the nmbd(8) process in Samba
+ will act as a WINS server. You should not set this to
+ yes unless you have a multi-subnetted network and you
+ wish a particular nnnnmmmmbbbbdddd to be your WINS server. Note
+ that you should NNNNEEEEVVVVEEEERRRR set this to yes on more than one
+ machine in your network.
+
+ Default: wwwwiiiinnnnssss ssssuuuuppppppppoooorrrrtttt ==== nnnnoooo
+
+ wwwwoooorrrrkkkkggggrrrroooouuuupppp ((((GGGG))))
+ This controls what workgroup your server will appear to
+ be in when queried by clients. Note that this parameter
+ also controls the Domain name used with the sssseeeeccccuuuurrrriiiittttyyyy ====
+ ddddoooommmmaaaaiiiinnnn setting.
+
+ Default: sssseeeetttt aaaatttt ccccoooommmmppppiiiilllleeee ttttiiiimmmmeeee ttttoooo WWWWOOOORRRRKKKKGGGGRRRROOOOUUUUPPPP
+
+ Example: wwwwoooorrrrkkkkggggrrrroooouuuupppp ==== MMMMYYYYGGGGRRRROOOOUUUUPPPP
+
+ wwwwrrrriiiittttaaaabbbblllleeee ((((SSSS))))
+ Synonym for _w_r_i_t_e_a_b_l_e for people who can't spell :-).
+
+ wwwwrrrriiiitttteeee ccccaaaacccchhhheeee ssssiiiizzzzeeee ((((SSSS))))
+ If this integer parameter is set to non-zero value,
+ Samba will create an in-memory cache for each oplocked
+ file (it does nnnnooootttt do this for non-oplocked files). All
+ writes that the client does not request to be flushed
+ directly to disk will be stored in this cache if
+ possible. The cache is flushed onto disk when a write
+ comes in whose offset would not fit into the cache or
+ when the file is closed by the client. Reads for the
+ file are also served from this cache if the data is
+ stored within it.
+
+ This cache allows Samba to batch client writes into a
+ more efficient write size for RAID disks (i.e. writes
+ may be tuned to be the RAID stripe size) and can
+ improve performance on systems where the disk subsystem
+ is a bottleneck but there is free memory for userspace
+ programs.
+
+ The integer parameter specifies the size of this cache
+ (per oplocked file) in bytes.
+
+ Default: wwwwrrrriiiitttteeee ccccaaaacccchhhheeee ssssiiiizzzzeeee ==== 0000
+
+ Example: wwwwrrrriiiitttteeee ccccaaaacccchhhheeee ssssiiiizzzzeeee ==== 222266662222111144444444
+
+ for a 256k cache size per file.
+
+
+
+ Page 136 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ wwwwrrrriiiitttteeee lllliiiisssstttt ((((SSSS))))
+ This is a list of users that are given read-write
+ access to a service. If the connecting user is in this
+ list then they will be given write access, no matter
+ what the _r_e_a_d _o_n_l_y option is set to. The list can
+ include group names using the @group syntax.
+
+ Note that if a user is in both the read list and the
+ write list then they will be given write access.
+
+ See also the _r_e_a_d _l_i_s_t option.
+
+ Default: wwwwrrrriiiitttteeee lllliiiisssstttt ==== <<<>>>
+
+ Example: wwwwrrrriiiitttteeee lllliiiisssstttt ==== aaaaddddmmmmiiiinnnn,,,, rrrrooooooootttt,,,, @@@@ssssttttaaaaffffffff
+
+ wwwwrrrriiiitttteeee ooookkkk ((((SSSS))))
+ Inverted synonym for _r_e_a_d _o_n_l_y.
+
+ wwwwrrrriiiitttteeee rrrraaaawwww ((((GGGG))))
+ This parameter controls whether or not the server will
+ support raw write SMB's when transferring data from
+ clients. You should never need to change this
+ parameter.
+
+ Default: wwwwrrrriiiitttteeee rrrraaaawwww ==== yyyyeeeessss
+
+ wwwwrrrriiiitttteeeeaaaabbbblllleeee ((((SSSS))))
+ Inverted synonym for _r_e_a_d _o_n_l_y.
+
+ WWWWAAAARRRRNNNNIIIINNNNGGGGSSSS
+ Although the configuration file permits service names to
+ contain spaces, your client software may not. Spaces will be
+ ignored in comparisons anyway, so it shouldn't be a problem
+ - but be aware of the possibility.
+
+ On a similar note, many clients - especially DOS clients -
+ limit service names to eight characters. smbd(8)
+ has no such limitation, but attempts to connect from such
+ clients will fail if they truncate the service names. For
+ this reason you should probably keep your service names down
+ to eight characters in length.
+
+ Use of the [homes] and [printers] special sections make life
+ for an administrator easy, but the various combinations of
+ default attributes can be tricky. Take extreme care when
+ designing these sections. In particular, ensure that the
+ permissions on spool directories are correct.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+
+
+
+ Page 137 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((11115555 OOOOccccttttoooobbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBB....CCCCOOOONNNNFFFF((((5555))))
+
+
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ samba(7) ssssmmmmbbbbppppaaaasssssssswwwwdddd((((8888)))) sssswwwwaaaatttt((((8888)))) ssssmmmmbbbbdddd((((8888)))) nnnnmmmmbbbbdddd((((8888)))) ssssmmmmbbbbcccclllliiiieeeennnntttt((((1111))))
+ nnnnmmmmbbbbllllooooooookkkkuuuupppp((((1111)))) tttteeeessssttttppppaaaarrrrmmmm((((1111)))) tttteeeessssttttpppprrrrnnnnssss((((1111))))
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 138 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.5/smbpasswd.5 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.5/smbpasswd.5
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.5/smbpasswd.5 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.5/smbpasswd.5 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,198 @@
+
+
+
+ SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((5555))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ smbpasswd - The Samba encrypted password file
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ _s_m_b_p_a_s_s_w_d
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This tool is part of the Samba suite.
+
+ smbpasswd is the Samba encrypted password file. It contains
+ the username, Unix user id and the SMB hashed passwords of
+ the user, as well as account flag information and the time
+ the password was last changed. This file format has been
+ evolving with Samba and has had several different formats in
+ the past.
+
+ FFFFIIIILLLLEEEE FFFFOOOORRRRMMMMAAAATTTT
+ The format of the smbpasswd file used by Samba 2.2 is very
+ similar to the familiar Unix _p_a_s_s_w_d(_5) file. It is an ASCII
+ file containing one line for each user. Each field within
+ each line is separated from the next by a colon. Any entry
+ beginning with '#' is ignored. The smbpasswd file contains
+ the following information for each user:
+
+ nnnnaaaammmmeeee This is the user name. It must be a name that already
+ exists in the standard UNIX passwd file.
+
+ uuuuiiiidddd This is the UNIX uid. It must match the uid field for
+ the same user entry in the standard UNIX passwd file.
+ If this does not match then Samba will refuse to
+ recognize this smbpasswd file entry as being valid for
+ a user.
+
+ LLLLaaaannnnmmmmaaaannnn PPPPaaaasssssssswwwwoooorrrrdddd HHHHaaaasssshhhh
+ This is the LANMAN hash of the user's password, encoded
+ as 32 hex digits. The LANMAN hash is created by DES
+ encrypting a well known string with the user's password
+ as the DES key. This is the same password used by
+ Windows 95/98 machines. Note that this password hash is
+ regarded as weak as it is vulnerable to dictionary
+ attacks and if two users choose the same password this
+ entry will be identical (i.e. the password is not
+ "salted" as the UNIX password is). If the user has a
+ null password this field will contain the characters
+ "NO PASSWORD" as the start of the hex string. If the
+ hex string is equal to 32 'X' characters then the
+ user's account is marked as disabled and the user will
+ not be able to log onto the Samba server.
+
+ WWWWAAAARRRRNNNNIIIINNNNGGGG !!!!!!!! Note that, due to the challenge-response
+ nature of the SMB/CIFS authentication protocol, anyone
+ with a knowledge of this password hash will be able to
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((5555))))
+
+
+
+ impersonate the user on the network. For this reason
+ these hashes are known as ppppllllaaaaiiiinnnn tttteeeexxxxtttt eeeeqqqquuuuiiiivvvvaaaalllleeeennnnttttssss and
+ must NNNNOOOOTTTT be made available to anyone but the root user.
+ To protect these passwords the smbpasswd file is placed
+ in a directory with read and traverse access only to
+ the root user and the smbpasswd file itself must be set
+ to be read/write only by root, with no other access.
+
+ NNNNTTTT PPPPaaaasssssssswwwwoooorrrrdddd HHHHaaaasssshhhh
+ This is the Windows NT hash of the user's password,
+ encoded as 32 hex digits. The Windows NT hash is
+ created by taking the user's password as represented in
+ 16-bit, little-endian UNICODE and then applying the MD4
+ (internet rfc1321) hashing algorithm to it.
+
+ This password hash is considered more secure than the
+ LANMAN Password Hash as it preserves the case of the
+ password and uses a much higher quality hashing
+ algorithm. However, it is still the case that if two
+ users choose the same password this entry will be
+ identical (i.e. the password is not "salted" as the
+ UNIX password is).
+
+ WWWWAAAARRRRNNNNIIIINNNNGGGG !!!!!!!!. Note that, due to the challenge-response
+ nature of the SMB/CIFS authentication protocol, anyone
+ with a knowledge of this password hash will be able to
+ impersonate the user on the network. For this reason
+ these hashes are known as ppppllllaaaaiiiinnnn tttteeeexxxxtttt eeeeqqqquuuuiiiivvvvaaaalllleeeennnnttttssss and
+ must NNNNOOOOTTTT be made available to anyone but the root user.
+ To protect these passwords the smbpasswd file is placed
+ in a directory with read and traverse access only to
+ the root user and the smbpasswd file itself must be set
+ to be read/write only by root, with no other access.
+
+ AAAAccccccccoooouuuunnnntttt FFFFllllaaaaggggssss
+ This section contains flags that describe the
+ attributes of the users account. In the Samba 2.2
+ release this field is bracketed by '[' and ']'
+ characters and is always 13 characters in length
+ (including the '[' and ']' characters). The contents
+ of this field may be any of the characters.
+
+ o+ UUUU - This means this is a "User" account, i.e. an
+ ordinary user. Only User and Workstation Trust
+ accounts are currently supported in the smbpasswd
+ file.
+
+ o+ NNNN - This means the account has no password (the
+ passwords in the fields LANMAN Password Hash and NT
+ Password Hash are ignored). Note that this will only
+ allow users to log on with no password if the _n_u_l_l
+ _p_a_s_s_w_o_r_d_s parameter is set in the _s_m_b._c_o_n_f(_5)
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((5555)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((5555))))
+
+
+
+ config file.
+
+ o+ DDDD - This means the account is disabled and no
+ SMB/CIFS logins will be allowed for this user.
+
+ o+ WWWW - This means this account is a "Workstation Trust"
+ account. This kind of account is used in the Samba
+ PDC code stream to allow Windows NT Workstations and
+ Servers to join a Domain hosted by a Samba PDC.
+
+ Other flags may be added as the code is extended in future.
+ The rest of this field space is filled in with spaces.
+
+ LLLLaaaasssstttt CCCChhhhaaaannnnggggeeee TTTTiiiimmmmeeee
+ This field consists of the time the account was last
+ modified. It consists of the characters 'LCT-'
+ (standing for "Last Change Time") followed by a numeric
+ encoding of the UNIX time in seconds since the epoch
+ (1970) that the last change was made.
+
+ All other colon separated fields are ignored at this time.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ ssssmmmmbbbbppppaaaasssssssswwwwdddd((((8888)))) samba(7) and the Internet RFC1321 for details
+ on the MD4 algorithm.
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 3 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.7/samba.7 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.7/samba.7
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.7/samba.7 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.7/samba.7 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,198 @@
+
+
+
+ SSSSAAAAMMMMBBBBAAAA((((7777)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSAAAAMMMMBBBBAAAA((((7777))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ SAMBA - A Windows SMB/CIFS fileserver for UNIX
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ SSSSaaaammmmbbbbaaaa
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ The Samba software suite is a collection of programs that
+ implements the Server Message Block (commonly abbreviated as
+ SMB) protocol for UNIX systems. This protocol is sometimes
+ also referred to as the Common Internet File System (CIFS),
+ LanManager or NetBIOS protocol.
+
+ ssssmmmmbbbbdddd The ssssmmmmbbbbdddd daemon provides the file and print services to
+ SMB clients, such as Windows 95/98, Windows NT, Windows
+ for Workgroups or LanManager. The configuration file
+ for this daemon is described in _s_m_b._c_o_n_f
+
+ nnnnmmmmbbbbdddd The nnnnmmmmbbbbdddd daemon provides NetBIOS nameserving and
+ browsing support. The configuration file for this
+ daemon is described in _s_m_b._c_o_n_f
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt
+ The ssssmmmmbbbbcccclllliiiieeeennnntttt program implements a simple ftp-like
+ client. This is useful for accessing SMB shares on
+ other compatible servers (such as Windows NT), and can
+ also be used to allow a UNIX box to print to a printer
+ attached to any SMB server (such as a PC running
+ Windows NT).
+
+ tttteeeessssttttppppaaaarrrrmmmm
+ The tttteeeessssttttppppaaaarrrrmmmm utility is a simple syntax checker for
+ Samba's _s_m_b._c_o_n_fconfiguration file.
+
+ tttteeeessssttttpppprrrrnnnnssss
+ The tttteeeessssttttpppprrrrnnnnssss utility supports testing printer names
+ defined in your _p_r_i_n_t_c_a_p> file used by Samba.
+
+ ssssmmmmbbbbssssttttaaaattttuuuussss
+ The ssssmmmmbbbbssssttttaaaattttuuuussss tool provides access to information about
+ the current connections to ssssmmmmbbbbdddd.
+
+ nnnnmmmmbbbbllllooooooookkkkuuuupppp
+ The nnnnmmmmbbbbllllooooooookkkkuuuupppp tools allows NetBIOS name queries to be
+ made from a UNIX host.
+
+ mmmmaaaakkkkeeee____ssssmmmmbbbbccccooooddddeeeeppppaaaaggggeeee
+ The mmmmaaaakkkkeeee____ssssmmmmbbbbccccooooddddeeeeppppaaaaggggeeee utility provides a means of
+ creating SMB code page definition files for your ssssmmmmbbbbdddd
+ server.
+
+ ssssmmmmbbbbppppaaaasssssssswwwwdddd
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSAAAAMMMMBBBBAAAA((((7777)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSAAAAMMMMBBBBAAAA((((7777))))
+
+
+
+ The ssssmmmmbbbbppppaaaasssssssswwwwdddd command is a tool for changing LanMan and
+ Windows NT password hashes on Samba and Windows NT
+ servers.
+
+ CCCCOOOOMMMMPPPPOOOONNNNEEEENNNNTTTTSSSS
+ The Samba suite is made up of several components. Each
+ component is described in a separate manual page. It is
+ strongly recommended that you read the documentation that
+ comes with Samba and the manual pages of those components
+ that you use. If the manual pages aren't clear enough then
+ please send a patch or bug report to samba@samba.org
+
+
+ AAAAVVVVAAAAIIIILLLLAAAABBBBIIIILLLLIIIITTTTYYYY
+ The Samba software suite is licensed under the GNU Public
+ License(GPL). A copy of that license should have come with
+ the package in the file COPYING. You are encouraged to
+ distribute copies of the Samba suite, but please obey the
+ terms of this license.
+
+ The latest version of the Samba suite can be obtained via
+ anonymous ftp from samba.org in the directory pub/samba/. It
+ is also available on several mirror sites worldwide.
+
+ You may also find useful information about Samba on the
+ newsgroup comp.protocol.smb
+ and the Samba mailing list. Details on how to join the
+ mailing list are given in the README file that comes with
+ Samba.
+
+ If you have access to a WWW viewer (such as Netscape or
+ Mosaic) then you will also find lots of useful information,
+ including back issues of the Samba mailing list, at
+ http://lists.samba.org .
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ CCCCOOOONNNNTTTTRRRRIIIIBBBBUUUUTTTTIIIIOOOONNNNSSSS
+ If you wish to contribute to the Samba project, then I
+ suggest you join the Samba mailing list at
+ http://lists.samba.org .
+
+ If you have patches to submit or bugs to report then you may
+ mail them directly to samba-patches@samba.org. Note,
+ however, that due to the enormous popularity of this package
+ the Samba Team may take some time to respond to mail. We
+ prefer patches in ddddiiiiffffffff ----uuuu format.
+
+ CCCCOOOONNNNTTTTRRRRIIIIBBBBUUUUTTTTOOOORRRRSSSS
+ Contributors to the project are now too numerous to mention
+ here but all deserve the thanks of all Samba users. To see a
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSAAAAMMMMBBBBAAAA((((7777)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSAAAAMMMMBBBBAAAA((((7777))))
+
+
+
+ full list, look at ftp://samba.org/pub/samba/alpha/change-
+ log for the
+ pre-CVS changes and at
+ ftp://samba.org/pub/samba/alpha/cvs.log
+ for the
+ contributors to Samba post-CVS. CVS is the Open Source
+ source code control system used by the Samba Team to develop
+ Samba. The project would have been unmanageable without it.
+
+ In addition, several commercial organizations now help fund
+ the Samba Team with money and equipment. For details see the
+ Samba Web pages at http://samba.org/samba/samba-thanks.html
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 3 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.8/nmbd.8 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.8/nmbd.8
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.8/nmbd.8 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.8/nmbd.8 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,330 @@
+
+
+
+ NNNNMMMMBBBBDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) NNNNMMMMBBBBDDDD((((8888))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ nmbd - NetBIOS name server to provide NetBIOS over IP
+ naming services to clients
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ nnnnmmmmbbbbdddd [ ----DDDD ] [ ----aaaa ] [ ----iiii ] [ ----oooo ] [ ----PPPP ] [ ----hhhh ] [ ----VVVV ]
+ [ ----dddd <<<>>> ] [ ----HHHH <<<>>> ] [ ----llll <<<>>> ] [ ----nnnn <<<>>> ] [ ----pppp <<<
>>> ] [ ----ssss <<<>>> ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This program is part of the Samba suite.
+
+ nnnnmmmmbbbbdddd is a server that understands and can reply to NetBIOS
+ over IP name service requests, like 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.
+
+ SMB/CIFS clients, when they start up, may wish to locate an
+ SMB/CIFS server. That is, they wish to know what IP number a
+ specified host is using.
+
+ Amongst other services, nnnnmmmmbbbbdddd will listen for such requests,
+ and if its own NetBIOS name is specified it will respond
+ with the IP number of the host it is running on. Its "own
+ NetBIOS name" is by default the primary DNS name of the host
+ it is running on, but this can be overridden with the ----nnnn
+ option (see OPTIONS below). Thus nnnnmmmmbbbbdddd will reply to
+ broadcast queries for its own name(s). Additional names for
+ nnnnmmmmbbbbdddd to respond on can be set via parameters in the
+ _s_m_b._c_o_n_f(_5) configuration file.
+
+ nnnnmmmmbbbbdddd can also be used as a WINS (Windows Internet Name
+ Server) server. What this basically means is that it will
+ act as a WINS database server, creating a database from name
+ registration requests that it receives and replying to
+ queries from clients for these names.
+
+ In addition, nnnnmmmmbbbbdddd can act as a WINS proxy, relaying
+ broadcast queries from clients that do not understand how to
+ talk the WINS protocol to a WIN server.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ ----DDDD If specified, this parameter causes nnnnmmmmbbbbdddd to operate as
+ a daemon. That is, it detaches itself and runs in the
+ background, fielding requests on the appropriate port.
+ By default, nnnnmmmmbbbbdddd will operate as a daemon if launched
+ from a command shell. nmbd can also be operated from
+ the iiiinnnneeeettttdddd meta-daemon, although this is not
+ recommended.
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ NNNNMMMMBBBBDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) NNNNMMMMBBBBDDDD((((8888))))
+
+
+
+ ----aaaa If this parameter is specified, each new connection
+ will append log messages to the log file. This is the
+ default.
+
+ ----iiii If this parameter is specified it causes the server to
+ run "interactively", not as a daemon, even if the
+ server is executed on the command line of a shell.
+ Setting this parameter negates the implicit deamon mode
+ when run from the command line.
+
+ ----oooo If this parameter is specified, the log files will be
+ overwritten when opened. By default, ssssmmmmbbbbdddd will append
+ entries to the log files.
+
+ ----hhhh Prints the help information (usage) for nnnnmmmmbbbbdddd.
+
+ ----HHHH <<<>>>
+ NetBIOS lmhosts file. The lmhosts file is a list of
+ NetBIOS names to IP addresses that is loaded by the
+ nmbd server and used via the name resolution mechanism
+ name resolve order described in _s_m_b._c_o_n_f(_5) to resolve
+ any NetBIOS name queries needed by the server. Note
+ that the contents of this file are NNNNOOOOTTTT used by nnnnmmmmbbbbdddd to
+ answer any name queries. Adding a line to this file
+ affects name NetBIOS resolution from this host OOOONNNNLLLLYYYY.
+
+ The default path to this file is compiled into Samba as
+ part of the build process. Common defaults are
+ /_u_s_r/_l_o_c_a_l/_s_a_m_b_a/_l_i_b/_l_m_h_o_s_t_s, /_u_s_r/_s_a_m_b_a/_l_i_b/_l_m_h_o_s_t_s or
+ /_e_t_c/_l_m_h_o_s_t_s. See the _l_m_h_o_s_t_s(_5) man page for details
+ on the contents of this file.
+
+ ----VVVV Prints the version number for nnnnmmmmbbbbdddd.
+
+ ----dddd <<<>>>
+ debuglevel is an integer from 0 to 10. The default
+ value if this parameter is not specified is zero.
+
+ The higher this value, the more detail will be logged
+ to the log files about the activities of the server. At
+ level 0, only critical errors and serious warnings will
+ be logged. Level 1 is a reasonable level for day to day
+ running - it generates a small amount of information
+ about operations carried out.
+
+ Levels above 1 will generate considerable amounts of
+ log data, and should only be used when investigating a
+ problem. Levels above 3 are designed for use only by
+ developers and generate HUGE amounts of log data, most
+ of which is extremely cryptic.
+
+ Note that specifying this parameter here will override
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
+
+
+
+ NNNNMMMMBBBBDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) NNNNMMMMBBBBDDDD((((8888))))
+
+
+
+ the log level parameter in the _s_m_b._c_o_n_f file.
+
+ ----llll <<<>>>
+ The -l parameter specifies a directory into which the
+ "log.nmbd" log file will be created for operational
+ data from the running nnnnmmmmbbbbdddd server. The default log
+ directory is compiled into Samba as part of the build
+ process. Common defaults are
+ /_u_s_r/_l_o_c_a_l/_s_a_m_b_a/_v_a_r/_l_o_g._n_m_b, /_u_s_r/_s_a_m_b_a/_v_a_r/_l_o_g._n_m_b
+ or /_v_a_r/_l_o_g/_l_o_g._n_m_b. BBBBeeeewwwwaaaarrrreeee:::: If the directory specified
+ does not exist, nnnnmmmmbbbbdddd will log to the default debug log
+ location defined at compile time.
+
+ ----nnnn <<<>>>
+ This option allows you to override the NetBIOS name
+ that Samba uses for itself. This is identical to
+ setting the NetBIOS name parameter in the _s_m_b._c_o_n_f
+ file. However, a command line setting will take
+ precedence over settings in _s_m_b._c_o_n_f.
+
+ ----pppp <<<>>>
+ UDP port number is a positive integer value. This
+ option changes the default UDP port number (normally
+ 137) that nnnnmmmmbbbbdddd responds to name queries on. Don't use
+ this option unless you are an expert, in which case you
+ won't need help!
+
+ ----ssss <<<>>>
+ The default configuration file name is set at build
+ time, typically as /_u_s_r/_l_o_c_a_l/_s_a_m_b_a/_l_i_b/_s_m_b._c_o_n_f, but
+ this may be changed when Samba is autoconfigured.
+
+ The file specified contains the configuration details
+ required by the server. See _s_m_b._c_o_n_f(_5) for more
+ information.
+
+ FFFFIIIILLLLEEEESSSS
+ /_e_t_c/_i_n_e_t_d._c_o_n_f
+ If the server is to be run by the iiiinnnneeeettttdddd meta-daemon,
+ this file must contain suitable startup information for
+ the meta-daemon. See the UNIX_INSTALL.html document for
+ details.
+
+ /_e_t_c/_r_c
+ or whatever initialization script your system uses).
+
+ If running the server as a daemon at startup, this file
+ will need to contain an appropriate startup sequence
+ for the server. See the UNIX_INSTALL.html document for
+ details.
+
+ /_e_t_c/_s_e_r_v_i_c_e_s
+
+
+
+ Page 3 (printed 1/7/103)
+
+
+
+
+
+
+ NNNNMMMMBBBBDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) NNNNMMMMBBBBDDDD((((8888))))
+
+
+
+ If running the server via the meta-daemon iiiinnnneeeettttdddd, this
+ file must contain a mapping of service name (e.g.,
+ netbios-ssn) to service port (e.g., 139) and protocol
+ type (e.g., tcp). See the UNIX_INSTALL.html document
+ for details.
+
+ /_u_s_r/_l_o_c_a_l/_s_a_m_b_a/_l_i_b/_s_m_b._c_o_n_f
+ This is the default location of the _s_m_b._c_o_n_f server
+ configuration file. Other common places that systems
+ install this file are /_u_s_r/_s_a_m_b_a/_l_i_b/_s_m_b._c_o_n_f and
+ /_e_t_c/_s_m_b._c_o_n_f.
+
+ When run as a WINS server (see the wins support
+ parameter in the _s_m_b._c_o_n_f(_5) man page), nnnnmmmmbbbbdddd will store
+ the WINS database in the file _w_i_n_s._d_a_t in the _v_a_r/_l_o_c_k_s
+ directory configured under wherever Samba was
+ configured to install itself.
+
+ If nnnnmmmmbbbbdddd is acting as a bbbbrrrroooowwwwsssseeee mmmmaaaasssstttteeeerrrr (see the local
+ master parameter in the _s_m_b._c_o_n_f(_5) man page, nnnnmmmmbbbbdddd will
+ store the browsing database in the file _b_r_o_w_s_e._d_a_t in
+ the _v_a_r/_l_o_c_k_s directory configured under wherever Samba
+ was configured to install itself.
+
+ SSSSIIIIGGGGNNNNAAAALLLLSSSS
+ To shut down an nnnnmmmmbbbbdddd process it is recommended that SIGKILL
+ (-9) NNNNOOOOTTTT be used, except as a last resort, as this may leave
+ the name database in an inconsistent state. The correct way
+ to terminate nnnnmmmmbbbbdddd is to send it a SIGTERM (-15) signal and
+ wait for it to die on its own.
+
+ nnnnmmmmbbbbdddd will accept SIGHUP, which will cause it to dump out its
+ namelists into the file _n_a_m_e_l_i_s_t._d_e_b_u_g in the
+ /_u_s_r/_l_o_c_a_l/_s_a_m_b_a/_v_a_r/_l_o_c_k_s directory (or the _v_a_r/_l_o_c_k_s
+ directory configured under wherever Samba was configured to
+ install itself). This will also cause nnnnmmmmbbbbdddd to dump out its
+ server database in the _l_o_g._n_m_b file.
+
+ The debug log level of nmbd may be raised or lowered using
+ ssssmmmmbbbbccccoooonnnnttttrrrroooollll((((1111))))
+ (SIGUSR[1|2] signals are no longer used in Samba 2.2). This
+ is to allow transient problems to be diagnosed, whilst still
+ running at a normally low log level.
+
+ TTTTRRRROOOOUUUUBBBBLLLLEEEESSSSHHHHOOOOOOOOTTTTIIIINNNNGGGG
+ One of the common causes of difficulty when installing Samba
+ and SWAT is the existsnece of some type of firewall or port
+ filtering software on the Samba server. Make sure that the
+ appropriate ports outlined in this man page are available on
+ the server and are not currently being blocked by some type
+ of security software such as iptables or "port sentry". For
+ more troubleshooting information, refer to the additional
+
+
+
+ Page 4 (printed 1/7/103)
+
+
+
+
+
+
+ NNNNMMMMBBBBDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) NNNNMMMMBBBBDDDD((((8888))))
+
+
+
+ documentation included in the Samba distribution.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ iiiinnnneeeettttdddd((((8888)))), ssssmmmmbbbbdddd((((8888)))) _s_m_b._c_o_n_f(_5)
+ ssssmmmmbbbbcccclllliiiieeeennnntttt((((1111))))
+ and the Internet RFC's _r_f_c_1_0_0_1._t_x_t, _r_f_c_1_0_0_2._t_x_t. In
+ addition the CIFS (formerly SMB) specification is available
+ as a link from the Web page http://samba.org/cifs/
+ .
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 5 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.8/smbd.8 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.8/smbd.8
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.8/smbd.8 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.8/smbd.8 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,396 @@
+
+
+
+ SSSSMMMMBBBBDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBDDDD((((8888))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ smbd - server to provide SMB/CIFS services to clients
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ ssssmmmmbbbbdddd [ ----DDDD ] [ ----aaaa ] [ ----iiii ] [ ----oooo ] [ ----PPPP ] [ ----hhhh ] [ ----VVVV ]
+ [ ----dddd <<<>>> ] [ ----llll <<<>>> ] [ ----pppp <<<>>> ] [ ----OOOO <<<>>> ] [ ----ssss <<<>>>
+ ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This program is part of the Samba suite.
+
+ ssssmmmmbbbbdddd is the server daemon that provides filesharing and
+ printing services to Windows clients. The server provides
+ filespace and printer services to clients using the SMB (or
+ CIFS) protocol. This is compatible with the LanManager
+ protocol, and can service LanManager clients. These include
+ MSCLIENT 3.0 for DOS, Windows for Workgroups, Windows
+ 95/98/ME, Windows NT, Windows 2000, OS/2, DAVE for
+ Macintosh, and smbfs for Linux.
+
+ An extensive description of the services that the server can
+ provide is given in the man page for the configuration file
+ controlling the attributes of those services (see
+ _s_m_b._c_o_n_f(_5)
+ This man page will not describe the services, but will
+ concentrate on the administrative aspects of running the
+ server.
+
+ Please note that there are significant security implications
+ to running this server, and the _s_m_b._c_o_n_f(_5) manpage should
+ be regarded as mandatory reading before proceeding with
+ installation.
+
+ A session is created whenever a client requests one. Each
+ client gets a copy of the server for each session. This copy
+ then services all connections made by the client during that
+ session. When all connections from its client are closed,
+ the copy of the server for that client terminates.
+
+ The configuration file, and any files that it includes, are
+ automatically reloaded every minute, if they change. You can
+ force a reload by sending a SIGHUP to the server. Reloading
+ the configuration file will not affect connections to any
+ service that is already established. Either the user will
+ have to disconnect from the service, or ssssmmmmbbbbdddd killed and
+ restarted.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ ----DDDD If specified, this parameter causes the server to
+ operate as a daemon. That is, it detaches itself and
+ runs in the background, fielding requests on the
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBDDDD((((8888))))
+
+
+
+ appropriate port. Operating the server as a daemon is
+ the recommended way of running ssssmmmmbbbbdddd for servers that
+ provide more than casual use file and print services.
+ This switch is assumed if ssssmmmmbbbbdddd is executed on the
+ command line of a shell.
+
+ ----aaaa If this parameter is specified, each new connection
+ will append log messages to the log file. This is the
+ default.
+
+ ----iiii If this parameter is specified it causes the server to
+ run "interactively", not as a daemon, even if the
+ server is executed on the command line of a shell.
+ Setting this parameter negates the implicit deamon mode
+ when run from the command line.
+
+ ----oooo If this parameter is specified, the log files will be
+ overwritten when opened. By default, ssssmmmmbbbbdddd will append
+ entries to the log files.
+
+ ----PPPP Passive option. Causes ssssmmmmbbbbdddd not to send any network
+ traffic out. Used for debugging by the developers only.
+
+ ----hhhh Prints the help information (usage) for ssssmmmmbbbbdddd.
+
+ ----vvvv Prints the version number for ssssmmmmbbbbdddd.
+
+ ----dddd <<<>>>
+ _d_e_b_u_g_l_e_v_e_l is an integer from 0 to 10. The default
+ value if this parameter is not specified is zero.
+
+ The higher this value, the more detail will be logged
+ to the log files about the activities of the server. At
+ level 0, only critical errors and serious warnings will
+ be logged. Level 1 is a reasonable level for day to day
+ running - it generates a small amount of information
+ about operations carried out.
+
+ Levels above 1 will generate considerable amounts of
+ log data, and should only be used when investigating a
+ problem. Levels above 3 are designed for use only by
+ developers and generate HUGE amounts of log data, most
+ of which is extremely cryptic.
+
+ Note that specifying this parameter here will override
+ the log level file.
+
+ ----llll <<<>>>
+ If specified, _l_o_g _d_i_r_e_c_t_o_r_y specifies a log directory
+ into which the "log.smbd" log file will be created for
+ informational and debug messages from the running
+ server. The log file generated is never removed by the
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBDDDD((((8888))))
+
+
+
+ server although its size may be controlled by the max
+ log size option in the _s_m_b._c_o_n_f(_5) file. BBBBeeeewwwwaaaarrrreeee:::: If
+ the directory specified does not exist, ssssmmmmbbbbdddd will log
+ to the default debug log location defined at compile
+ time.
+
+ The default log directory is specified at compile time.
+
+ ----OOOO <<<>>>
+ See the socket options parameter in the _s_m_b._c_o_n_f(_5)
+ file for details.
+
+ ----pppp <<<>>>
+ _p_o_r_t _n_u_m_b_e_r is a positive integer value. The default
+ value if this parameter is not specified is 139.
+
+ This number is the port number that will be used when
+ making connections to the server from client software.
+ The standard (well-known) port number for the SMB over
+ TCP is 139, hence the default. If you wish to run the
+ server as an ordinary user rather than as root, most
+ systems will require you to use a port number greater
+ than 1024 - ask your system administrator for help if
+ you are in this situation.
+
+ In order for the server to be useful by most clients,
+ should you configure it on a port other than 139, you
+ will require port redirection services on port 139,
+ details of which are outlined in rfc1002.txt section
+ 4.3.5.
+
+ This parameter is not normally specified except in the
+ above situation.
+
+ ----ssss <<<>>>
+ The file specified contains the configuration details
+ required by the server. The information in this file
+ includes server-specific information such as what
+ printcap file to use, as well as descriptions of all
+ the services that the server is to provide. See
+ _s_m_b._c_o_n_f(_5) for more information. The default
+ configuration file name is determined at compile time.
+
+ FFFFIIIILLLLEEEESSSS
+ /_e_t_c/_i_n_e_t_d._c_o_n_f
+ If the server is to be run by the iiiinnnneeeettttdddd meta-daemon,
+ this file must contain suitable startup information for
+ the meta-daemon. See the UNIX_INSTALL.html document for
+ details.
+
+ /_e_t_c/_r_c
+ or whatever initialization script your system uses).
+
+
+
+ Page 3 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBDDDD((((8888))))
+
+
+
+ If running the server as a daemon at startup, this file
+ will need to contain an appropriate startup sequence
+ for the server. See the UNIX_INSTALL.html document for
+ details.
+
+ /_e_t_c/_s_e_r_v_i_c_e_s
+ If running the server via the meta-daemon iiiinnnneeeettttdddd, this
+ file must contain a mapping of service name (e.g.,
+ netbios-ssn) to service port (e.g., 139) and protocol
+ type (e.g., tcp). See the UNIX_INSTALL.html document
+ for details.
+
+ /_u_s_r/_l_o_c_a_l/_s_a_m_b_a/_l_i_b/_s_m_b._c_o_n_f
+ This is the default location of the _s_m_b._c_o_n_f server
+ configuration file. Other common places that systems
+ install this file are /_u_s_r/_s_a_m_b_a/_l_i_b/_s_m_b._c_o_n_f and
+ /_e_t_c/_s_m_b._c_o_n_f.
+
+ This file describes all the services the server is to
+ make available to clients. See _s_m_b._c_o_n_f(_5) for more
+ information.
+
+ LLLLIIIIMMMMIIIITTTTAAAATTTTIIIIOOOONNNNSSSS
+ On some systems ssssmmmmbbbbdddd cannot change uid back to root after a
+ setuid() call. Such systems are called trapdoor uid systems.
+ If you have such a system, you will be unable to connect
+ from a client (such as a PC) as two different users at once.
+ Attempts to connect the second user will result in access
+ denied or similar.
+
+ EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT VVVVAAAARRRRIIIIAAAABBBBLLLLEEEESSSS
+ PPPPRRRRIIIINNNNTTTTEEEERRRR
+ If no printer name is specified to printable services,
+ most systems will use the value of this variable (or lp
+ if this variable is not defined) as the name of the
+ printer to use. This is not specific to the server,
+ however.
+
+ PPPPAAAAMMMM IIIINNNNTTTTEEEERRRRAAAACCCCTTTTIIIIOOOONNNN
+ Samba uses PAM for authentication (when presented with a
+ plaintext password), for account checking (is this account
+ disabled?) and for session management. The degree too which
+ samba supports PAM is restricted by the limitations of the
+ SMB protocol and the obey pam restricions smb.conf
+ paramater. When this is set, the following restrictions
+ apply:
+
+ o+ AAAAccccccccoooouuuunnnntttt VVVVaaaalllliiiiddddaaaattttiiiioooonnnn: All acccesses to a samba server are
+ checked against PAM to see if the account is vaild, not
+ disabled and is permitted to login at this time. This also
+ applies to encrypted logins.
+
+
+
+
+ Page 4 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBDDDD((((8888))))
+
+
+
+ o+ SSSSeeeessssssssiiiioooonnnn MMMMaaaannnnaaaaggggeeeemmmmeeeennnntttt: When not using share level secuirty,
+ users must pass PAM's session checks before access is
+ granted. Note however, that this is bypassed in share
+ level secuirty. Note also that some older pam
+ configuration files may need a line added for session
+ support.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ TTTTRRRROOOOUUUUBBBBLLLLEEEESSSSHHHHOOOOOOOOTTTTIIIINNNNGGGG
+ One of the common causes of difficulty when installing Samba
+ and SWAT is the existsnece of some type of firewall or port
+ filtering software on the Samba server. Make sure that the
+ appropriate ports outlined in this man page are available on
+ the server and are not currently being blocked by some type
+ of security software such as iptables or "port sentry". For
+ more troubleshooting information, refer to the additional
+ documentation included in the Samba distribution.
+
+ Most diagnostics issued by the server are logged in a
+ specified log file. The log file name is specified at
+ compile time, but may be overridden on the command line.
+
+ The number and nature of diagnostics available depends on
+ the debug level used by the server. If you have problems,
+ set the debug level to 3 and peruse the log files.
+
+ Most messages are reasonably self-explanatory.
+ Unfortunately, at the time this man page was created, there
+ are too many diagnostics available in the source code to
+ warrant describing each and every diagnostic. At this stage
+ your best bet is still to grep the source code and inspect
+ the conditions that gave rise to the diagnostics you are
+ seeing.
+
+ SSSSIIIIGGGGNNNNAAAALLLLSSSS
+ Sending the ssssmmmmbbbbdddd a SIGHUP will cause it to reload its
+ _s_m_b._c_o_n_f configuration file within a short period of time.
+
+ To shut down a user's ssssmmmmbbbbdddd process it is recommended that
+ SSSSIIIIGGGGKKKKIIIILLLLLLLL ((((----9999)))) NNNNOOOOTTTT be used, except as a last resort, as this
+ may leave the shared memory area in an inconsistent state.
+ The safe way to terminate an ssssmmmmbbbbdddd is to send it a SIGTERM
+ (-15) signal and wait for it to die on its own.
+
+ The debug log level of ssssmmmmbbbbdddd may be raised or lowered using
+ ssssmmmmbbbbccccoooonnnnttttrrrroooollll((((1111))))
+ program (SIGUSR[1|2] signals are no longer used in Samba
+ 2.2). This is to allow transient problems to be diagnosed,
+ whilst still running at a normally low log level.
+
+
+
+
+ Page 5 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBDDDD((((8888))))
+
+
+
+ Note that as the signal handlers send a debug write, they
+ are not re-entrant in ssssmmmmbbbbdddd. This you should wait until ssssmmmmbbbbdddd
+ is in a state of waiting for an incoming SMB before issuing
+ them. It is possible to make the signal handlers safe by
+ un-blocking the signals before the select call and re-
+ blocking them after, however this would affect performance.
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ hosts_access(5), iiiinnnneeeettttdddd((((8888)))), nnnnmmmmbbbbdddd((((8888)))) _s_m_b._c_o_n_f(_5)
+ ssssmmmmbbbbcccclllliiiieeeennnntttt((((1111))))
+ and the Internet RFC's _r_f_c_1_0_0_1._t_x_t, _r_f_c_1_0_0_2._t_x_t. In
+ addition the CIFS (formerly SMB) specification is available
+ as a link from the Web page http://samba.org/cifs/
+ .
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 6 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.8/smbmnt.8 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.8/smbmnt.8
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.8/smbmnt.8 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.8/smbmnt.8 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,132 @@
+
+
+
+ SSSSMMMMBBBBMMMMNNNNTTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBMMMMNNNNTTTT((((8888))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ smbmnt - helper utility for mounting SMB filesystems
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ ssssmmmmbbbbmmmmnnnntttt mmmmoooouuuunnnntttt----ppppooooiiiinnnntttt [ ----ssss <<<>>> ] [ ----rrrr ] [ ----uuuu <<<>>> ] [
+ ----gggg <<<>>> ] [ ----ffff <<<>>> ] [ ----dddd <<<>>> ] [ ----oooo <<<>>> ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ ssssmmmmbbbbmmmmnnnntttt is a helper application used by the smbmount program
+ to do the actual mounting of SMB shares. ssssmmmmbbbbmmmmnnnntttt can be
+ installed setuid root if you want normal users to be able to
+ mount their SMB shares.
+
+ A setuid smbmnt will only allow mounts on directories owned
+ by the user, and that the user has write permission on.
+
+ The ssssmmmmbbbbmmmmnnnntttt program is normally invoked by ssssmmmmbbbbmmmmoooouuuunnnntttt((((8888))))
+ It should not be invoked directly by users.
+
+ smbmount searches the normal PATH for smbmnt. You must
+ ensure that the smbmnt version in your path matches the
+ smbmount used.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ ----rrrr mount the filesystem read-only
+
+ ----uuuu uuuuiiiidddd
+ specify the uid that the files will be owned by
+
+ ----gggg ggggiiiidddd
+ specify the gid that the files will be owned by
+
+ ----ffff mmmmaaaasssskkkk
+ specify the octal file mask applied
+
+ ----dddd mmmmaaaasssskkkk
+ specify the octal directory mask applied
+
+ ----oooo ooooppppttttiiiioooonnnnssss
+ list of options that are passed as-is to smbfs, if this
+ command is run on a 2.4 or higher Linux kernel.
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ Volker Lendecke, Andrew Tridgell, Michael H. Warfield and
+ others.
+
+ The current maintainer of smbfs and the userspace tools
+ ssssmmmmbbbbmmmmoooouuuunnnntttt, ssssmmmmbbbbuuuummmmoooouuuunnnntttt, and ssssmmmmbbbbmmmmnnnntttt is Urban Widmark
+ . The SAMBA Mailing list
+ is the preferred place to ask
+ questions regarding these programs.
+
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBMMMMNNNNTTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBMMMMNNNNTTTT((((8888))))
+
+
+
+ The conversion of this manpage for Samba 2.2 was performed
+ by Gerald Carter
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.8/smbmount.8 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.8/smbmount.8
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.8/smbmount.8 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.8/smbmount.8 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,264 @@
+
+
+
+ SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ smbmount - mount an smbfs filesystem
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ ssssmmmmbbbbmmmmoooouuuunnnntttt sssseeeerrrrvvvviiiicccceeee mmmmoooouuuunnnntttt----ppppooooiiiinnnntttt [ ----oooo ooooppppttttiiiioooonnnnssss ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ ssssmmmmbbbbmmmmoooouuuunnnntttt mounts a Linux SMB filesystem. It is usually
+ invoked as mmmmoooouuuunnnntttt....ssssmmmmbbbbffffssss by the mmmmoooouuuunnnntttt((((8888)))) command when using
+ the "-t smbfs" option. This command only works in Linux, and
+ the kernel must support the smbfs filesystem.
+
+ Options to ssssmmmmbbbbmmmmoooouuuunnnntttt are specified as a comma-separated list
+ of key=value pairs. It is possible to send options other
+ than those listed here, assuming that smbfs supports them.
+ If you get mount failures, check your kernel log for errors
+ on unknown options.
+
+ ssssmmmmbbbbmmmmoooouuuunnnntttt is a daemon. After mounting it keeps running until
+ the mounted smbfs is umounted. It will log things that
+ happen when in daemon mode using the "machine name"
+ smbmount, so typically this output will end up in
+ _l_o_g._s_m_b_m_o_u_n_t. The ssssmmmmbbbbmmmmoooouuuunnnntttt process may also be called
+ mount.smbfs.
+
+ NNNNOOOOTTTTEEEE:::: ssssmmmmbbbbmmmmoooouuuunnnntttt calls ssssmmmmbbbbmmmmnnnntttt((((8888)))) to do the actual mount. You
+ must make sure that ssssmmmmbbbbmmmmnnnntttt is in the path so that it can be
+ found.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ uuuusssseeeerrrrnnnnaaaammmmeeee====<<<>>>
+ specifies the username to connect as. If this is not
+ given, then the environment variable UUUUSSSSEEEERRRR is used.
+ This option can also take the form "user%password" or
+ "user/workgroup" or "user/workgroup%password" to allow
+ the password and workgroup to be specified as part of
+ the username.
+
+ ppppaaaasssssssswwwwoooorrrrdddd====<<<>>>
+ specifies the SMB password. If this option is not given
+ then the environment variable PPPPAAAASSSSSSSSWWWWDDDD is used. If it can
+ find no password ssssmmmmbbbbmmmmoooouuuunnnntttt will prompt for a passeword,
+ unless the guest option is given.
+
+ Note that password which contain the arguement
+ delimiter character (i.e. a comma ',') will failed to
+ be parsed correctly on the command line. However, the
+ same password defined in the PASSWD environment
+ variable or a credentials file (see below) will be read
+ correctly.
+
+ ccccrrrreeeeddddeeeennnnttttiiiiaaaallllssss====<<<>>>
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888))))
+
+
+
+ specifies a file that contains a username and/or
+ password. The format of the file is:
+
+
+ username =
+ password =
+
+
+
+ This is preferred over having passwords in plaintext in
+ a shared file, such as /_e_t_c/_f_s_t_a_b. Be sure to protect
+ any credentials file properly.
+
+ nnnneeeettttbbbbiiiioooossssnnnnaaaammmmeeee====<<<>>>
+ sets the source NetBIOS name. It defaults to the local
+ hostname.
+
+ uuuuiiiidddd====<<<>>>
+ sets the uid that will own all files on the mounted
+ filesystem. It may be specified as either a username
+ or a numeric uid.
+
+ ggggiiiidddd====<<<>>>
+ sets the gid that will own all files on the mounted
+ filesystem. It may be specified as either a groupname
+ or a numeric gid.
+
+ ppppoooorrrrtttt====<<<>>>
+ sets the remote SMB port number. The default is 139.
+
+ ffffmmmmaaaasssskkkk====<<<>>>
+ sets the file mask. This determines the permissions
+ that remote files have in the local filesystem. The
+ default is based on the current umask.
+
+ ddddmmmmaaaasssskkkk====<<<>>>
+ sets the directory mask. This determines the
+ permissions that remote directories have in the local
+ filesystem. The default is based on the current umask.
+
+ ddddeeeebbbbuuuugggg====<<<>>>
+ sets the debug level. This is useful for tracking down
+ SMB connection problems. A suggested value to start
+ with is 4. If set too high there will be a lot of
+ output, possibly hiding the useful output.
+
+ iiiipppp====<<<>>>
+ sets the destination host or IP address.
+
+ wwwwoooorrrrkkkkggggrrrroooouuuupppp====<<<>>>
+ sets the workgroup on the destination
+
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888))))
+
+
+
+ ssssoooocccckkkkoooopppptttt====<<<>>>
+ sets the TCP socket options. See the _s_m_b._c_o_n_f
+ _s_o_c_k_e_t _o_p_t_i_o_n_s option.
+
+ ssssccccooooppppeeee====<<<>>>
+ sets the NetBIOS scope
+
+ gggguuuueeeesssstttt
+ don't prompt for a password
+
+ rrrroooo mount read-only
+
+ rrrrwwww mount read-write
+
+ iiiioooocccchhhhaaaarrrrsssseeeetttt====<<<>>>
+ sets the charset used by the Linux side for codepage to
+ charset translations (NLS). Argument should be the name
+ of a charset, like iso8859-1. (Note: only kernel 2.4.0
+ or later)
+
+ ccccooooddddeeeeppppaaaaggggeeee====<<<>>>
+ sets the codepage the server uses. See the iocharset
+ option. Example value cp850. (Note: only kernel 2.4.0
+ or later)
+
+ ttttttttllll====<<<>>>
+ how long a directory listing is cached in milliseconds
+ (also affects visibility of file size and date
+ changes). A higher value means that changes on the
+ server take longer to be noticed but it can give better
+ performance on large directories, especially over long
+ distances. Default is 1000ms but something like 10000ms
+ (10 seconds) is probably more reasonable in many cases.
+ (Note: only kernel 2.4.2 or later)
+
+ EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT VVVVAAAARRRRIIIIAAAABBBBLLLLEEEESSSS
+ The variable UUUUSSSSEEEERRRR may contain the username of the person
+ using the client. This information is used only if the
+ protocol level is high enough to support session-level
+ passwords. The variable can be used to set both username and
+ password by using the format username%password.
+
+ The variable PPPPAAAASSSSSSSSWWWWDDDD may contain the password of the person
+ using the client. This information is used only if the
+ protocol level is high enough to support session-level
+ passwords.
+
+ The variable PPPPAAAASSSSSSSSWWWWDDDD____FFFFIIIILLLLEEEE may contain the pathname of a file
+ to read the password from. A single line of input is read
+ and used as the password.
+
+ BBBBUUUUGGGGSSSS
+
+
+
+ PPPPaaaaggggeeee 3333 ((((pppprrrriiiinnnntttteeeedddd 1111////7777////111100003333))))
+
+
+
+
+
+
+ SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888))))
+
+
+
+ Passwords and other options containing , can not be handled.
+ For passwords an alternative way of passing them is in a
+ credentials file or in the PASSWD environment.
+
+ The credentials file does not handle usernames or passwords
+ with leading space.
+
+ One smbfs bug is important enough to mention here, even if
+ it is a bit misplaced:
+
+ o+ Mounts sometimes stop working. This is usually caused by
+ smbmount terminating. Since smbfs needs smbmount to
+ reconnect when the server disconnects, the mount will
+ eventually go dead. An umount/mount normally fixes this.
+ At least 2 ways to trigger this bug are known.
+
+ Note that the typical response to a bug report is suggestion
+ to try the latest version first. So please try doing that
+ first, and always include which versions you use of relevant
+ software when reporting bugs (minimum: samba, kernel,
+ distribution)
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ Documentation/filesystems/smbfs.txt in the linux kernel
+ source tree may contain additional options and information.
+
+ FreeBSD also has a smbfs, but it is not related to smbmount
+
+ For Solaris, HP-UX and others you may want to look at
+ ssssmmmmbbbbsssshhhh((((1111)))) or at other solutions, such as sharity or perhaps
+ replacing the SMB server with a NFS server.
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ Volker Lendecke, Andrew Tridgell, Michael H. Warfield and
+ others.
+
+ The current maintainer of smbfs and the userspace tools
+ ssssmmmmbbbbmmmmoooouuuunnnntttt, ssssmmmmbbbbuuuummmmoooouuuunnnntttt, and ssssmmmmbbbbmmmmnnnntttt is Urban Widmark
+ . The SAMBA Mailing list
+ is the preferred place to ask
+ questions regarding these programs.
+
+ The conversion of this manpage for Samba 2.2 was performed
+ by Gerald Carter
+
+
+
+
+
+
+
+
+
+
+
+ Page 4 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.8/smbpasswd.8 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.8/smbpasswd.8
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.8/smbpasswd.8 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.8/smbpasswd.8 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,462 @@
+
+
+
+ SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((8888))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ smbpasswd - change a user's SMB password
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ When run by root:
+
+ ssssmmmmbbbbppppaaaasssssssswwwwdddd [ ooooppppttttiiiioooonnnnssss ] [ uuuusssseeeerrrrnnnnaaaammmmeeee ] [ ppppaaaasssssssswwwwoooorrrrdddd ]
+
+ otherwise:
+
+ ssssmmmmbbbbppppaaaasssssssswwwwdddd [ ooooppppttttiiiioooonnnnssss ] [ ppppaaaasssssssswwwwoooorrrrdddd ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This tool is part of the Samba suite.
+
+ The smbpasswd program has several different functions,
+ depending on whether it is run by the rrrrooooooootttt user or not. When
+ run as a normal user it allows the user to change the
+ password used for their SMB sessions on any machines that
+ store SMB passwords.
+
+ By default (when run with no arguments) it will attempt to
+ change the current user's SMB password on the local machine.
+ This is similar to the way the ppppaaaasssssssswwwwdddd((((1111)))) program works.
+ ssssmmmmbbbbppppaaaasssssssswwwwdddd differs from how the passwd program works however
+ in that it is not sssseeeettttuuuuiiiidddd rrrrooooooootttt but works in a client-server
+ mode and communicates with a locally running ssssmmmmbbbbdddd((((8888)))). As a
+ consequence in order for this to succeed the smbd daemon
+ must be running on the local machine. On a UNIX machine the
+ encrypted SMB passwords are usually stored in the
+ _s_m_b_p_a_s_s_w_d(_5) file.
+
+ When run by an ordinary user with no options. smbpasswd will
+ prompt them for their old SMB password and then ask them for
+ their new password twice, to ensure that the new password
+ was typed correctly. No passwords will be echoed on the
+ screen whilst being typed. If you have a blank SMB password
+ (specified by the string "NO PASSWORD" in the smbpasswd
+ file) then just press the key when asked for your
+ old password.
+
+ smbpasswd can also be used by a normal user to change their
+ SMB password on remote machines, such as Windows NT Primary
+ Domain Controllers. See the (-r) and -U options below.
+
+ When run by root, smbpasswd allows new users to be added and
+ deleted in the smbpasswd file, as well as allows changes to
+ the attributes of the user in this file to be made. When run
+ by root, ssssmmmmbbbbppppaaaasssssssswwwwdddd accesses the local smbpasswd file
+ directly, thus enabling changes to be made even if smbd is
+ not running.
+
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((8888))))
+
+
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ ----LLLL Run the smbpasswd command in local mode. This allows a
+ non-root user to specify the root-only options. This is
+ used mostly in test environments where a non-root user
+ needs to make changes to the local _s_m_b_p_a_s_s_w_d file. The
+ _s_m_b_p_a_s_s_w_d file must have read/write permissions for the
+ user running the command.
+
+ ----hhhh This option prints the help string for ssssmmmmbbbbppppaaaasssssssswwwwdddd.
+
+ ----cccc ssssmmmmbbbb....ccccoooonnnnffff ffffiiiilllleeee
+ This option specifies that the configuration file
+ specified should be used instead of the default value
+ specified at compile time.
+
+ ----DDDD ddddeeeebbbbuuuugggglllleeeevvvveeeellll
+ _d_e_b_u_g_l_e_v_e_l is an integer from 0 to 10. The default
+ value if this parameter is not specified is zero.
+
+ The higher this value, the more detail will be logged
+ to the log files about the activities of smbpasswd. At
+ level 0, only critical errors and serious warnings will
+ be logged.
+
+ Levels above 1 will generate considerable amounts of
+ log data, and should only be used when investigating a
+ problem. Levels above 3 are designed for use only by
+ developers and generate HUGE amounts of log data, most
+ of which is extremely cryptic.
+
+ ----rrrr rrrreeeemmmmooootttteeee mmmmaaaacccchhhhiiiinnnneeee nnnnaaaammmmeeee
+ This option allows a user to specify what machine they
+ wish to change their password on. Without this
+ parameter smbpasswd defaults to the local host. The
+ _r_e_m_o_t_e _m_a_c_h_i_n_e _n_a_m_e is the NetBIOS name of the SMB/CIFS
+ server to contact to attempt the password change. This
+ name is resolved into an IP address using the standard
+ name resolution mechanism in all programs of the Samba
+ suite. See the -_R _n_a_m_e _r_e_s_o_l_v_e _o_r_d_e_r parameter for
+ details on changing this resolving mechanism.
+
+ The username whose password is changed is that of the
+ current UNIX logged on user. See the -_U _u_s_e_r_n_a_m_e
+ parameter for details on changing the password for a
+ different username.
+
+ Note that if changing a Windows NT Domain password the
+ remote machine specified must be the Primary Domain
+ Controller for the domain (Backup Domain Controllers
+ only have a read-only copy of the user account database
+ and will not allow the password change).
+
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((8888))))
+
+
+
+ NNNNooootttteeee that Windows 95/98 do not have a real password
+ database so it is not possible to change passwords
+ specifying a Win95/98 machine as remote machine target.
+
+ ----ssss This option causes smbpasswd to be silent (i.e. not
+ issue prompts) and to read its old and new passwords
+ from standard input, rather than from /_d_e_v/_t_t_y (like
+ the ppppaaaasssssssswwwwdddd((((1111)))) program does). This option is to aid
+ people writing scripts to drive smbpasswd
+
+ ----SSSS This option causes ssssmmmmbbbbppppaaaasssssssswwwwdddd to query a domain
+ controller of the domain specified by the workgroup
+ parameter in _s_m_b._c_o_n_f and store the domain SID in the
+ _s_e_c_r_e_t_s._t_d_b file as its own machine SID. This is only
+ useful when configuring a Samba PDC and Samba BDC, or
+ when migrating from a Windows PDC to a Samba PDC.
+
+ The -_r options can be used as well to indicate a
+ specific domain controller which should be contacted.
+ In this case, the domain SID obtained is the one for
+ the domain to which the remote machine belongs.
+
+ ----tttt This option is used to force smbpasswd to change the
+ current password assigned to the machine trust account
+ when operating in domain security mode. This is really
+ meant to be used on systems that only run wwwwiiiinnnnbbbbiiiinnnndddddddd
+ Under server installations, ssssmmmmbbbbdddd handle the password
+ updates automatically.
+
+ ----UUUU uuuusssseeeerrrrnnnnaaaammmmeeee[[[[%%%%ppppaaaassssssss]]]]
+ This option may only be used in conjunction with the -_r
+ option. When changing a password on a remote machine it
+ allows the user to specify the user name on that
+ machine whose password will be changed. It is present
+ to allow users who have different user names on
+ different systems to change these passwords. The
+ optional %pass may be used to specify to old password.
+
+ In particular, this parameter specifies the username
+ used to create the machine account when invoked with -j
+
+ NNNNOOOOTTTTEEEE::::
+ TTTThhhheeee ffffoooolllllllloooowwwwiiiinnnngggg ooooppppttttiiiioooonnnnssss aaaarrrreeee aaaavvvvaaaaiiiillllaaaabbbblllleeee oooonnnnllllyyyy wwwwhhhheeeennnn tttthhhheeee
+ ssssmmmmbbbbppppaaaasssssssswwwwdddd ccccoooommmmmmmmaaaannnndddd iiiissss rrrruuuunnnn aaaassss rrrrooooooootttt oooorrrr iiiinnnn llllooooccccaaaallll mmmmooooddddeeee....
+
+ ----aaaa This option specifies that the username following
+ should be added to the local smbpasswd file, with the
+ new password typed. This option is ignored if the
+ username specified already exists in the smbpasswd file
+ and it is treated like a regular change password
+ command. Note that the user to be added must already
+ exist in the system password file (usually /_e_t_c/_p_a_s_s_w_d)
+
+
+
+ Page 3 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((8888))))
+
+
+
+ else the request to add the user will fail.
+
+ ----dddd This option specifies that the username following
+ should be disabled in the local smbpasswd file. This is
+ done by writing a 'D' flag into the account control
+ space in the smbpasswd file. Once this is done all
+ attempts to authenticate via SMB using this username
+ will fail.
+
+ If the smbpasswd file is in the 'old' format (pre-Samba
+ 2.0 format) there is no space in the user's password
+ entry to write this information and so the user is
+ disabled by writing 'X' characters into the password
+ space in the smbpasswd file. See ssssmmmmbbbbppppaaaasssssssswwwwdddd((((5555)))) for
+ details on the 'old' and new password file formats.
+
+ ----eeee This option specifies that the username following
+ should be enabled in the local smbpasswd file, if the
+ account was previously disabled. If the account was not
+ disabled this option has no effect. Once the account is
+ enabled then the user will be able to authenticate via
+ SMB once again.
+
+ If the smbpasswd file is in the 'old' format, then
+ ssssmmmmbbbbppppaaaasssssssswwwwdddd will prompt for a new password for this user,
+ otherwise the account will be enabled by removing the
+ 'D' flag from account control space in the _s_m_b_p_a_s_s_w_d
+ file. See ssssmmmmbbbbppppaaaasssssssswwwwdddd ((((5555)))) for details on the 'old' and
+ new password file formats.
+
+ ----mmmm This option tells smbpasswd that the account being
+ changed is a MACHINE account. Currently this is used
+ when Samba is being used as an NT Primary Domain
+ Controller.
+
+ ----nnnn This option specifies that the username following
+ should have their password set to null (i.e. a blank
+ password) in the local smbpasswd file. This is done by
+ writing the string "NO PASSWORD" as the first part of
+ the first password stored in the smbpasswd file.
+
+ Note that to allow users to logon to a Samba server
+ once the password has been set to "NO PASSWORD" in the
+ smbpasswd file the administrator must set the following
+ parameter in the [global] section of the _s_m_b._c_o_n_f file
+ :
+
+ nnnnuuuullllllll ppppaaaasssssssswwwwoooorrrrddddssss ==== yyyyeeeessss
+
+ ----wwww ppppaaaasssssssswwwwoooorrrrdddd
+ This parameter is only available is Samba has been
+ configured to use the experimental --------wwwwiiiitttthhhh----llllddddaaaappppssssaaaammmm
+
+
+
+ Page 4 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((8888))))
+
+
+
+ option. The -_w switch is used to specify the password
+ to be used with the _l_d_a_p _a_d_m_i_n _d_n Note that the
+ password is stored in the _p_r_i_v_a_t_e/_s_e_c_r_e_t_s._t_d_b and is
+ keyed off of the admin's DN. This means that if the
+ value of _l_d_a_p _a_d_m_i_n _d_n ever changes, the password will
+ need to be manually updated as well.
+
+ ----xxxx This option specifies that the username following
+ should be deleted from the local smbpasswd file.
+
+ ----jjjj DDDDOOOOMMMMAAAAIIIINNNN
+ This option is used to add a Samba server into a
+ Windows NT Domain, as a Domain member capable of
+ authenticating user accounts to any Domain Controller
+ in the same way as a Windows NT Server. See the
+ sssseeeeccccuuuurrrriiiittttyyyy ==== ddddoooommmmaaaaiiiinnnn option in the _s_m_b._c_o_n_f(_5) man page.
+
+ This command can work both with and without the -U
+ parameter.
+
+ When invoked with -U, that username (and optional
+ password) are used to contact the PDC (which must be
+ specified with -r) to both create a machine account,
+ and to set a password on it.
+
+ Alternately, if -U is omitted, Samba will contact its
+ PDC and attempt to change the password on a pre-
+ existing account.
+
+ In order to be used in this way, the Administrator for
+ the Windows NT Domain must have used the program
+ "Server Manager for Domains" to add the primary NetBIOS
+ name of the Samba server as a member of the Domain.
+
+ After this has been done, to join the Domain invoke
+ ssssmmmmbbbbppppaaaasssssssswwwwdddd with this parameter. smbpasswd will then look
+ up the Primary Domain Controller for the Domain (found
+ in the _s_m_b._c_o_n_f file in the parameter _p_a_s_s_w_o_r_d _s_e_r_v_e_r
+ and change the machine account password used to create
+ the secure Domain communication.
+
+ Either way, this password is then stored by smbpasswd
+ in a TDB, writeable only by root, called _s_e_c_r_e_t_s._t_d_b
+
+ Once this operation has been performed the _s_m_b._c_o_n_f
+ file may be updated to set the sssseeeeccccuuuurrrriiiittttyyyy ==== ddddoooommmmaaaaiiiinnnn
+ option and all future logins to the Samba server will
+ be authenticated to the Windows NT PDC.
+
+ Note that even though the authentication is being done
+ to the PDC all users accessing the Samba server must
+ still have a valid UNIX account on that machine. The
+
+
+
+ Page 5 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((8888))))
+
+
+
+ wwwwiiiinnnnbbbbiiiinnnndddddddd((((8888)))) daemon can be used to create UNIX accounts
+ for NT users.
+
+ ----RRRR nnnnaaaammmmeeee rrrreeeessssoooollllvvvveeee oooorrrrddddeeeerrrr
+ This option allows the user of smbpasswd to determine
+ what name resolution services to use when looking up
+ the NetBIOS name of the host being connected to.
+
+ The options are :"lmhosts", "host", "wins" and "bcast".
+ They cause names to be resolved as follows :
+
+ o+ lmhosts : Lookup an IP address in the Samba lmhosts
+ file. If the line in lmhosts has no name type
+ attached to the NetBIOS name (see the lmhosts(5) for
+ details) then any name type matches for lookup.
+
+ o+ host : Do a standard host name to IP address
+ resolution, using the system /_e_t_c/_h_o_s_t_s , NIS, or DNS
+ lookups. This method of name resolution is operating
+ system dependent. For instance, on IRIX or Solaris
+ this may be controlled by the /_e_t_c/_n_s_s_w_i_t_c_h._c_o_n_f
+ file). Note that this method is only used if the
+ NetBIOS name type being queried is the 0x20 (server)
+ name type, otherwise it is ignored.
+
+ o+ wins : Query a name with the IP address listed in the
+ _w_i_n_s _s_e_r_v_e_r parameter. If no WINS server has been
+ specified this method will be ignored.
+
+ o+ bcast : Do a broadcast on each of the known local
+ interfaces listed in the _i_n_t_e_r_f_a_c_e_s parameter. This
+ is the least reliable of the name resolution methods
+ as it depends on the target host being on a locally
+ connected subnet.
+
+ The default order is llllmmmmhhhhoooossssttttssss,,,, hhhhoooosssstttt,,,, wwwwiiiinnnnssss,,,, bbbbccccaaaasssstttt and without
+ this parameter or any entry in the _s_m_b._c_o_n_f file the name
+ resolution methods will be attempted in this order.
+
+ uuuusssseeeerrrrnnnnaaaammmmeeee
+ This specifies the username for all of the rrrrooooooootttt oooonnnnllllyyyy
+ options to operate on. Only root can specify this
+ parameter as only root has the permission needed to
+ modify attributes directly in the local smbpasswd file.
+
+ ppppaaaasssssssswwwwoooorrrrdddd
+ This specifies the new password. If this parameter is
+ specified you will not be prompted for the new
+ password.
+
+ NNNNOOOOTTTTEEEESSSS
+ Since ssssmmmmbbbbppppaaaasssssssswwwwdddd works in client-server mode communicating
+
+
+
+ Page 6 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBPPPPAAAASSSSSSSSWWWWDDDD((((8888))))
+
+
+
+ with a local smbd for a non-root user then the smbd daemon
+ must be running for this to work. A common problem is to add
+ a restriction to the hosts that may access the ssssmmmmbbbbdddd running
+ on the local machine by specifying a _a_l_l_o_w _h_o_s_t_s or _d_e_n_y
+ _h_o_s_t_s entry in the _s_m_b._c_o_n_f file and neglecting to allow
+ "localhost" access to the smbd.
+
+ In addition, the smbpasswd command is only useful if Samba
+ has been set up to use encrypted passwords. See the file
+ _E_N_C_R_Y_P_T_I_O_N._t_x_t in the docs directory for details on how to
+ do this.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ _s_m_b_p_a_s_s_w_d(_5) samba(7)
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 7 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.8/smbumount.8 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.8/smbumount.8
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.8/smbumount.8 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.8/smbumount.8 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,66 @@
+
+
+
+ SSSSMMMMBBBBUUUUMMMMOOOOUUUUNNNNTTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBUUUUMMMMOOOOUUUUNNNNTTTT((((8888))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ smbumount - smbfs umount for normal users
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ ssssmmmmbbbbuuuummmmoooouuuunnnntttt mmmmoooouuuunnnntttt----ppppooooiiiinnnntttt
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ With this program, normal users can unmount smb-filesystems,
+ provided that it is suid root. ssssmmmmbbbbuuuummmmoooouuuunnnntttt has been written to
+ give normal Linux users more control over their resources.
+ It is safe to install this program suid root, because only
+ the user who has mounted a filesystem is allowed to unmount
+ it again. For root it is not necessary to use smbumount. The
+ normal umount program works perfectly well, but it would
+ certainly be problematic to make umount setuid root.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ mmmmoooouuuunnnntttt----ppppooooiiiinnnntttt
+ The directory to unmount.
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ ssssmmmmbbbbmmmmoooouuuunnnntttt((((8888))))
+
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ Volker Lendecke, Andrew Tridgell, Michael H. Warfield and
+ others.
+
+ The current maintainer of smbfs and the userspace tools
+ ssssmmmmbbbbmmmmoooouuuunnnntttt, ssssmmmmbbbbuuuummmmoooouuuunnnntttt, and ssssmmmmbbbbmmmmnnnntttt is Urban Widmark
+ . The SAMBA Mailing list
+ is the preferred place to ask
+ questions regarding these programs.
+
+ The conversion of this manpage for Samba 2.2 was performed
+ by Gerald Carter
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.8/swat.8 samba-2.2.8/packaging/Caldera/OpenServer/man/cat.8/swat.8
--- samba-2.2.7a/packaging/Caldera/OpenServer/man/cat.8/swat.8 Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/man/cat.8/swat.8 Fri Mar 14 15:16:04 2003
@@ -0,0 +1,264 @@
+
+
+
+ SSSSWWWWAAAATTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSWWWWAAAATTTT((((8888))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ swat - Samba Web Administration Tool
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ sssswwwwaaaatttt [ ----ssss <<<>>> ] [ ----aaaa ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This tool is part of the Samba suite.
+
+ sssswwwwaaaatttt allows a Samba administrator to configure the complex
+ _s_m_b._c_o_n_f(_5) file via a Web browser. In addition, a sssswwwwaaaatttt
+ configuration page has help links to all the configurable
+ options in the _s_m_b._c_o_n_f file allowing an administrator to
+ easily look up the effects of any change.
+
+ sssswwwwaaaatttt is run from iiiinnnneeeettttdddd
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ ----ssss ssssmmmmbbbb ccccoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn ffffiiiilllleeee
+ The default configuration file path is determined at
+ compile time. The file specified contains the
+ configuration details required by the ssssmmmmbbbbdddd server. This
+ is the file that sssswwwwaaaatttt will modify. The information in
+ this file includes server-specific information such as
+ what printcap file to use, as well as descriptions of
+ all the services that the server is to provide. See
+ _s_m_b._c_o_n_f for more information.
+
+ ----aaaa This option disables authentication and puts sssswwwwaaaatttt in
+ demo mode. In that mode anyone will be able to modify
+ the _s_m_b._c_o_n_f file.
+
+ DDDDoooo NNNNOOOOTTTT eeeennnnaaaabbbblllleeee tttthhhhiiiissss ooooppppttttiiiioooonnnn oooonnnn aaaa pppprrrroooodddduuuuccccttttiiiioooonnnn sssseeeerrrrvvvveeeerrrr....
+
+ IIIINNNNSSSSTTTTAAAALLLLLLLLAAAATTTTIIIIOOOONNNN
+ After you compile SWAT you need to run mmmmaaaakkkkeeee iiiinnnnssssttttaaaallllllll to
+ install the sssswwwwaaaatttt binary and the various help files and
+ images. A default install would put these in:
+
+ o+ /usr/local/samba/bin/swat
+
+ o+ /usr/local/samba/swat/images/*
+
+ o+ /usr/local/samba/swat/help/*
+
+ IIIINNNNEEEETTTTDDDD IIIINNNNSSSSTTTTAAAALLLLLLLLAAAATTTTIIIIOOOONNNN
+ You need to edit your /_e_t_c/_i_n_e_t_d._c_o_n_f and /_e_t_c/_s_e_r_v_i_c_e_s to
+ enable SWAT to be launched via iiiinnnneeeettttdddd.
+
+ In /_e_t_c/_s_e_r_v_i_c_e_s you need to add a line like this:
+
+ sssswwwwaaaatttt 999900001111////ttttccccpppp
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSWWWWAAAATTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSWWWWAAAATTTT((((8888))))
+
+
+
+ Note for NIS/YP users - you may need to rebuild the NIS
+ service maps rather than alter your local /_e_t_c/_s_e_r_v_i_c_e_s
+ file.
+
+ the choice of port number isn't really important except that
+ it should be less than 1024 and not currently used (using a
+ number above 1024 presents an obscure security hole
+ depending on the implementation details of your iiiinnnneeeettttdddd
+ daemon).
+
+ In /_e_t_c/_i_n_e_t_d._c_o_n_f you should add a line like this:
+
+ sssswwwwaaaatttt ssssttttrrrreeeeaaaammmm ttttccccpppp nnnnoooowwwwaaaaiiiitttt....444400000000 rrrrooooooootttt ////uuuussssrrrr////llllooooccccaaaallll////ssssaaaammmmbbbbaaaa////bbbbiiiinnnn////sssswwwwaaaatttt
+ sssswwwwaaaatttt
+
+ One you have edited /_e_t_c/_s_e_r_v_i_c_e_s and /_e_t_c/_i_n_e_t_d._c_o_n_f you
+ need to send a HUP signal to inetd. To do this use kkkkiiiillllllll ----1111
+ PPPPIIIIDDDD where PID is the process ID of the inetd daemon.
+
+ XXXXIIIINNNNEEEETTTTDDDD IIIINNNNSSSSTTTTAAAALLLLLLLLAAAATTTTIIIIOOOONNNN
+ Newer Linux systems ship with a more secure implementation
+ of the inetd meta-daemon. The xxxxiiiinnnneeeettttdddd daemon can read
+ configuration inf9ormation from a single file (i.e.
+ /_e_t_c/_x_i_n_e_t_d._c_o_n_f) or from a collection of service control
+ files in the _x_i_n_e_t_d._d/ directory. These directions assume
+ the latter configuration.
+
+ The following file should be created as /_e_t_c/_x_i_e_n_t_d._d/_s_w_a_t.
+ It is then be neccessary cause the meta-daemon to reload its
+ configuration files. Refer to the xinetd man page for
+ details on how to accomplish this.
+
+ ## /etc/xinetd.d/swat
+ service swat
+ {
+ port = 901
+ socket_type = stream
+ wait = no
+ only_from = localhost
+ user = root
+ server = /usr/local/samba/bin/swat
+ log_on_failure += USERID
+ disable = No
+ }
+
+
+ LLLLAAAAUUUUNNNNCCCCHHHHIIIINNNNGGGG
+ To launch SWAT just run your favorite web browser and point
+ it at "http://localhost:901/".
+
+ Note that you can attach to SWAT from any IP connected
+ machine but connecting from a remote machine leaves your
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSWWWWAAAATTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSWWWWAAAATTTT((((8888))))
+
+
+
+ connection open to password sniffing as passwords will be
+ sent in the clear over the wire.
+
+ TTTTRRRROOOOUUUUBBBBLLLLEEEESSSSHHHHOOOOOOOOTTTTIIIINNNNGGGG
+ One of the common causes of difficulty when installing Samba
+ and SWAT is the existsnece of some type of firewall or port
+ filtering software on the Samba server. Make sure that the
+ appropriate ports outlined in this man page are available on
+ the server and are not currently being blocked by some type
+ of security software such as iptables or "port sentry". For
+ more troubleshooting information, refer to the additional
+ documentation included in the Samba distribution.
+
+ FFFFIIIILLLLEEEESSSS
+ /_e_t_c/_i_n_e_t_d._c_o_n_f
+ This file must contain suitable startup information for
+ the meta-daemon.
+
+ /_e_t_c/_x_i_n_e_t_d._d/_s_w_a_t
+ This file must contain suitable startup information for
+ the xxxxiiiinnnneeeettttdddd meta-daemon.
+
+ /_e_t_c/_s_e_r_v_i_c_e_s
+ This file must contain a mapping of service name (e.g.,
+ swat) to service port (e.g., 901) and protocol type
+ (e.g., tcp).
+
+ /_u_s_r/_l_o_c_a_l/_s_a_m_b_a/_l_i_b/_s_m_b._c_o_n_f
+ This is the default location of the _s_m_b._c_o_n_f(_5) server
+ configuration file that swat edits. Other common places
+ that systems install this file are
+ /_u_s_r/_s_a_m_b_a/_l_i_b/_s_m_b._c_o_n_f and /_e_t_c/_s_m_b._c_o_n_f . This file
+ describes all the services the server is to make
+ available to clients.
+
+ WWWWAAAARRRRNNNNIIIINNNNGGGGSSSS
+ sssswwwwaaaatttt will rewrite your _s_m_b._c_o_n_f file. It will rearrange the
+ entries and delete all comments, _i_n_c_l_u_d_e= and _c_o_p_y="
+ options. If you have a carefully crafted _s_m_b._c_o_n_f then back
+ it up or don't use swat!
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ SSSSEEEEEEEE AAAALLLLSSSSOOOO
+ iiiinnnneeeettttdddd((((5555)))), ssssmmmmbbbbdddd((((8888)))) smb.conf(5) xxxxiiiinnnneeeettttdddd((((8888))))
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ 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.
+
+
+
+ Page 3 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSWWWWAAAATTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSWWWWAAAATTTT((((8888))))
+
+
+
+ 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 4 (printed 1/7/103)
+
+
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/pkg/cdmt.config samba-2.2.8/packaging/Caldera/OpenServer/pkg/cdmt.config
--- samba-2.2.7a/packaging/Caldera/OpenServer/pkg/cdmt.config Fri Jun 7 08:40:36 2002
+++ samba-2.2.8/packaging/Caldera/OpenServer/pkg/cdmt.config Fri Mar 14 15:34:46 2003
@@ -1,7 +1,7 @@
MACROS:
Samba_NAME = Samba File and Print Server
-Samba_VER = 2.2.5a
+Samba_VER = 2.2.8a
DEFAULT_EXEC_MODE = 0755
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/pkg/cntl/packages/SambaDOC/ccs samba-2.2.8/packaging/Caldera/OpenServer/pkg/cntl/packages/SambaDOC/ccs
--- samba-2.2.7a/packaging/Caldera/OpenServer/pkg/cntl/packages/SambaDOC/ccs Mon Jun 3 01:02:34 2002
+++ samba-2.2.8/packaging/Caldera/OpenServer/pkg/cntl/packages/SambaDOC/ccs Fri Mar 14 15:34:46 2003
@@ -15,7 +15,11 @@
if [ -x /usr/bin/doctool ]; then
/usr/bin/doctool --add NetworkDoc/WinConnect/Samba/.directory >&- 2>&-
/usr/bin/doctool --add \
- NetworkDoc/WinConnect/Samba/samba.desktop >&- 2>&-
+ NetworkDoc/WinConnect/Samba/samba_help.desktop >&- 2>&-
+ /usr/bin/doctool --add \
+ NetworkDoc/WinConnect/Samba/samba_using.desktop >&- 2>&-
+ /usr/bin/doctool --add \
+ NetworkDoc/WinConnect/Samba/samba_configure.desktop >&- 2>&-
fi
}
@@ -23,8 +27,13 @@
{
if [ -x /usr/bin/doctool ]; then
/usr/bin/doctool --remove \
- NetworkDoc/WinConnect/Samba/samba.desktop >&- 2>&-
- /usr/bin/doctool --remove NetworkDoc/WinConnect/Samba/.directory >&- 2>&-
+ NetworkDoc/WinConnect/Samba/samba_help.desktop >&- 2>&-
+ /usr/bin/doctool --remove \
+ NetworkDoc/WinConnect/Samba/samba_using.desktop >&- 2>&-
+ /usr/bin/doctool --remove \
+ NetworkDoc/WinConnect/Samba/samba_configure.desktop >&- 2>&-
+ /usr/bin/doctool --remove \
+ NetworkDoc/WinConnect/Samba/.directory >&- 2>&-
fi
}
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/pkg/input/Samba.pkg samba-2.2.8/packaging/Caldera/OpenServer/pkg/input/Samba.pkg
--- samba-2.2.7a/packaging/Caldera/OpenServer/pkg/input/Samba.pkg Fri Jun 7 08:40:36 2002
+++ samba-2.2.8/packaging/Caldera/OpenServer/pkg/input/Samba.pkg Fri Mar 14 15:34:46 2003
@@ -9,61 +9,51 @@
mode = 0755
owner = root
group = sys
-flags =
FILE:Control:SHARED:cntl/ccs:
mode = 0755
owner = root
group = sys
-flags =
FILE:Control:SHARED:cntl/cqs:
mode = 0755
owner = root
group = sys
-flags =
DIR:Control:SHARED:cntl/packages:
mode = 0755
owner = root
group = sys
-flags =
DIR:Control:SHARED:cntl/packages/Samba:
mode = 0755
owner = root
group = sys
-flags =
FILE:Control:SHARED:cntl/packages/Samba/ccs:
mode = 0755
owner = root
group = sys
-flags =
DIR:Control:SHARED:cntl/packages/SambaSWAT:
mode = 0755
owner = root
group = sys
-flags =
FILE:Control:SHARED:cntl/packages/SambaSWAT/ccs:
mode = 0755
owner = root
group = sys
-flags =
DIR:Control:SHARED:cntl/packages/SambaDOC:
mode = 0755
owner = root
group = sys
-flags =
FILE:Control:SHARED:cntl/packages/SambaDOC/ccs:
mode = 0755
owner = root
group = sys
-flags =
PKG:Samba:
description = "Samba"
@@ -75,485 +65,425 @@
mode = 0755
owner = root
group = sys
-flags =
+
+DIR:Samba:SHARED:etc/copyrights:
+mode = 0755
+owner = root
+group = sys
+
+FILE:Samba:SHARED:etc/copyrights/samba:
+mode = 0644
+owner = root
+group = sys
+exportPath = /etc/copyrights/samba
DIR:Samba:SHARED:etc/init.d:
mode = 0755
owner = root
group = sys
-flags =
FILE:Samba:SHARED:etc/init.d/samba:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /etc/init.d/samba
DIR:Samba:SHARED:usr:
mode = 0755
owner = root
group = sys
-flags =
DIR:Samba:SHARED:usr/lib:
mode = 0755
owner = root
group = sys
-flags =
DIR:Samba:SHARED:usr/lib/mkdev:
mode = 0755
owner = root
group = sys
-flags =
FILE:Samba:SHARED:usr/lib/mkdev/samba:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/mkdev/samba
DIR:Samba:SHARED:usr/lib/samba:
mode = 0755
owner = root
group = sys
-flags =
DIR:Samba:SHARED:usr/lib/samba/bin:
mode = 0755
owner = root
group = sys
-flags =
FILE:Samba:SHARED:usr/lib/samba/bin/initconfig:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/initconfig
FILE:Samba:SHARED:usr/lib/samba/bin/nmblookup:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/nmblookup
FILE:Samba:SHARED:usr/lib/samba/bin/smbclient:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/smbclient
FILE:Samba:SHARED:usr/lib/samba/bin/smbpasswd:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/smbpasswd
FILE:Samba:SHARED:usr/lib/samba/bin/smbstatus:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/smbstatus
FILE:Samba:SHARED:usr/lib/samba/bin/testparm:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/testparm
FILE:Samba:SHARED:usr/lib/samba/bin/testprns:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/testprns
FILE:Samba:SHARED:usr/lib/samba/bin/make_smbcodepage:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/make_smbcodepage
FILE:Samba:SHARED:usr/lib/samba/bin/make_unicodemap:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/make_unicodemap
FILE:Samba:SHARED:usr/lib/samba/bin/make_printerdef:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/make_printerdef
FILE:Samba:SHARED:usr/lib/samba/bin/rpcclient:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/rpcclient
FILE:Samba:SHARED:usr/lib/samba/bin/smbspool:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/smbspool
FILE:Samba:SHARED:usr/lib/samba/bin/mksmbpasswd.sh:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/mksmbpasswd.sh
FILE:Samba:SHARED:usr/lib/samba/bin/smbtar:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/smbtar
FILE:Samba:SHARED:usr/lib/samba/bin/smbprint:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/smbprint
FILE:Samba:SHARED:usr/lib/samba/bin/findsmb:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/findsmb
FILE:Samba:SHARED:usr/lib/samba/bin/smbadduser:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/bin/smbadduser
DIR:Samba:SHARED:usr/lib/samba/sbin:
mode = 0755
owner = root
group = sys
-flags =
FILE:Samba:SHARED:usr/lib/samba/sbin/smbd:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/sbin/smbd
FILE:Samba:SHARED:usr/lib/samba/sbin/nmbd:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/sbin/nmbd
FILE:Samba:SHARED:usr/lib/samba/sbin/debug2html:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/sbin/debug2html
FILE:Samba:SHARED:usr/lib/samba/sbin/smbfilter:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/sbin/smbfilter
FILE:Samba:SHARED:etc/samba.d/smb.conf.default:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /etc/samba.d/smb.conf.default
FILE:Samba:SHARED:etc/samba.d/example.block.smb.conf:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /etc/samba.d/example.block.smb.conf
DIR:Samba:SHARED:usr/lib/samba/lib:
mode = 0755
owner = root
group = sys
-flags =
FILE:Samba:SHARED:usr/lib/samba/lib/audit.so:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/audit.so
FILE:Samba:SHARED:usr/lib/samba/lib/block.so:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/block.so
FILE:Samba:SHARED:usr/lib/samba/lib/recycle.so:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/recycle.so
FILE:Samba:SHARED:usr/lib/samba/lib/skel.so:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/skel.so
DIR:Samba:SHARED:usr/lib/samba/lib/codepages:
mode = 0755
owner = root
group = sys
-flags =
DIR:Samba:SHARED:usr/lib/samba/lib/codepages/src:
mode = 0755
owner = root
group = sys
-flags =
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/codepage_def.437:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/codepage_def.437
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/codepage_def.737:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/codepage_def.737
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/codepage_def.775:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/codepage_def.775
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/codepage_def.850:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/codepage_def.850
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/codepage_def.852:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/codepage_def.852
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/codepage_def.861:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/codepage_def.861
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/codepage_def.866:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/codepage_def.866
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/codepage_def.932:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/codepage_def.932
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/codepage_def.936:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/codepage_def.936
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/codepage_def.949:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/codepage_def.949
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/codepage_def.950:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/codepage_def.950
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/codepage_def.1251:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/codepage_def.1251
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CP437.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CP437.TXT
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CP737.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CP737.TXT
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CP850.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CP850.TXT
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CP852.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CP852.TXT
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CP861.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CP861.TXT
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CP866.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CP866.TXT
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CP932.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CP932.TXT
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CP936.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CP936.TXT
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CP949.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CP949.TXT
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CP950.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CP950.TXT
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CPISO8859-1.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CPISO8859-1.TXT
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CPISO8859-2.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CPISO8859-2.TXT
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CPISO8859-5.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CPISO8859-5.TXT
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CPISO8859-7.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CPISO8859-7.TXT
FILE:Samba:SHARED:usr/lib/samba/lib/codepages/src/CPKOI8-R.TXT:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/lib/codepages/src/CPKOI8-R.TXT
FILE:Samba:CLIENT:etc/samba.d/smbusers:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /etc/samba.d/smbusers
FILE:Samba:CLIENT:etc/samba.d/lmhosts:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /etc/samba.d/lmhosts
DIR:Samba:CLIENT:usr/lib/samba/var:
mode = 0755
owner = root
group = sys
-flags =
DIR:Samba:CLIENT:usr/lib/samba/var/log:
mode = 0755
owner = root
group = sys
-flags =
exportPath = /var/log/samba.d
exportPath = /usr/lib/samba/var/log
@@ -561,7 +491,6 @@
mode = 1777
owner = root
group = sys
-flags =
exportPath = /var/locks/samba.d
exportPath = /usr/lib/samba/var/locks
@@ -569,6 +498,5 @@
mode = 0755
owner = root
group = sys
-flags =
exportPath = /var/spool/samba
exportPath = /usr/lib/samba/var/spool
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/pkg/input/SambaDOC.pkg samba-2.2.8/packaging/Caldera/OpenServer/pkg/input/SambaDOC.pkg
--- samba-2.2.7a/packaging/Caldera/OpenServer/pkg/input/SambaDOC.pkg Mon Jun 3 01:02:35 2002
+++ samba-2.2.8/packaging/Caldera/OpenServer/pkg/input/SambaDOC.pkg Fri Mar 14 15:34:46 2003
@@ -9,1386 +9,1362 @@
mode = 0755
owner = root
group = sys
-flags =
FILE:SambaDOC:SHARED:doc/samba.directory:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/meta/doc/NetworkDoc/WinConnect/Samba/.directory
-FILE:SambaDOC:SHARED:doc/samba.desktop:
+FILE:SambaDOC:SHARED:doc/samba_using.desktop:
mode = 0644
owner = root
group = sys
-flags =
-exportPath = /usr/share/meta/doc/NetworkDoc/WinConnect/Samba/samba.desktop
+exportPath = /usr/share/meta/doc/NetworkDoc/WinConnect/Samba/samba_using.desktop
+
+FILE:SambaDOC:SHARED:doc/samba_configure.desktop:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/share/meta/doc/NetworkDoc/WinConnect/Samba/samba_configure.desktop
+
+FILE:SambaDOC:SHARED:doc/samba_help.desktop:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/share/meta/doc/NetworkDoc/WinConnect/Samba/samba_help.desktop
FILE:SambaDOC:SHARED:doc/index.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/help/index.html
FILE:SambaDOC:SHARED:doc/osr5config.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/help/osr5config.html
-FILE:SambaDOC:SHARED:doc/callogo.gif:
+FILE:SambaDOC:SHARED:doc/sco_logo_med.gif:
mode = 0644
owner = root
group = sys
-flags =
-exportPath = /usr/share/doc/samba/help/callogo.gif
+exportPath = /usr/share/doc/samba/help/sco_logo_med.gif
DIR:SambaDOC:SHARED:usr/lib:
mode = 0755
owner = root
group = sys
-flags =
DIR:SambaDOC:SHARED:usr/lib/samba:
mode = 0755
owner = root
group = sys
-flags =
DIR:SambaDOC:SHARED:usr/lib/samba/man:
mode = 0755
owner = root
group = sys
-flags =
DIR:SambaDOC:SHARED:usr/lib/samba/man/man.1:
mode = 0755
owner = root
group = sys
-flags =
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.1/findsmb.1:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.1/findsmb.1
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.1/make_smbcodepage.1:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.1/make_smbcodepage.1
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.1/make_unicodemap.1:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.1/make_unicodemap.1
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.1/nmblookup.1:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.1/nmblookup.1
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.1/rpcclient.1:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.1/rpcclient.1
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.1/smbcacls.1:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.1/smbcacls.1
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.1/smbclient.1:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.1/smbclient.1
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.1/smbcontrol.1:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.1/smbcontrol.1
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.1/smbstatus.1:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.1/smbstatus.1
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.1/smbtar.1:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.1/smbtar.1
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.1/testparm.1:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.1/testparm.1
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.1/testprns.1:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.1/testprns.1
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.1/wbinfo.1:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.1/wbinfo.1
DIR:SambaDOC:SHARED:usr/lib/samba/man/man.5:
mode = 0755
owner = root
group = sys
-flags =
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.5/smb.conf.5:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.5/smb.conf.5
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.5/lmhosts.5:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.5/lmhosts.5
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.5/smbpasswd.5:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.5/smbpasswd.5
DIR:SambaDOC:SHARED:usr/lib/samba/man/man.7:
mode = 0755
owner = root
group = sys
-flags =
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.7/samba.7:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.7/samba.7
DIR:SambaDOC:SHARED:usr/lib/samba/man/man.8:
mode = 0755
owner = root
group = sys
-flags =
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.8/smbd.8:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.8/smbd.8
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.8/nmbd.8:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.8/nmbd.8
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.8/smbpasswd.8:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.8/smbpasswd.8
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.8/swat.8:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.8/swat.8
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.8/smbmount.8:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.8/smbmount.8
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.8/smbmnt.8:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.8/smbmnt.8
FILE:SambaDOC:SHARED:usr/lib/samba/man/man.8/smbumount.8:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/man/man.8/smbumount.8
+DIR:SambaDOC:SHARED:usr/lib/samba/man/cat.1:
+mode = 0755
+owner = root
+group = sys
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.1/findsmb.1:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.1/findsmb.1
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.1/make_smbcodepage.1:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.1/make_smbcodepage.1
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.1/make_unicodemap.1:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.1/make_unicodemap.1
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.1/nmblookup.1:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.1/nmblookup.1
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.1/rpcclient.1:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.1/rpcclient.1
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.1/smbcacls.1:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.1/smbcacls.1
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.1/smbclient.1:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.1/smbclient.1
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.1/smbcontrol.1:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.1/smbcontrol.1
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.1/smbstatus.1:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.1/smbstatus.1
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.1/smbtar.1:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.1/smbtar.1
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.1/testparm.1:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.1/testparm.1
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.1/testprns.1:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.1/testprns.1
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.1/wbinfo.1:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.1/wbinfo.1
+
+DIR:SambaDOC:SHARED:usr/lib/samba/man/cat.5:
+mode = 0755
+owner = root
+group = sys
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.5/smb.conf.5:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.5/smb.conf.5
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.5/lmhosts.5:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.5/lmhosts.5
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.5/smbpasswd.5:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.5/smbpasswd.5
+
+DIR:SambaDOC:SHARED:usr/lib/samba/man/cat.7:
+mode = 0755
+owner = root
+group = sys
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.7/samba.7:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.7/samba.7
+
+DIR:SambaDOC:SHARED:usr/lib/samba/man/cat.8:
+mode = 0755
+owner = root
+group = sys
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.8/smbd.8:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.8/smbd.8
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.8/nmbd.8:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.8/nmbd.8
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.8/smbpasswd.8:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.8/smbpasswd.8
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.8/swat.8:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.8/swat.8
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.8/smbmount.8:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.8/smbmount.8
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.8/smbmnt.8:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.8/smbmnt.8
+
+FILE:SambaDOC:SHARED:usr/lib/samba/man/cat.8/smbumount.8:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/man/cat.8/smbumount.8
+
DIR:SambaDOC:SHARED:usr/lib/samba/swat:
mode = 0755
owner = root
group = sys
-flags =
DIR:SambaDOC:SHARED:usr/lib/samba/swat/using_samba:
mode = 0755
owner = root
group = sys
-flags =
DIR:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/gifs:
mode = 0755
owner = root
group = sys
-flags =
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/gifs/index.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/gifs/index.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/gifs/samba.s.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/gifs/samba.s.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/gifs/txthome.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/gifs/txthome.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/gifs/txtnexta.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/gifs/txtnexta.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/gifs/txtpreva.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/gifs/txtpreva.gif
DIR:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs:
mode = 0755
owner = root
group = sys
-flags =
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0101.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0101.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0102.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0102.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0103.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0103.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0104.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0104.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0105.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0105.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0106.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0106.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0107.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0107.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0108.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0108.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0109.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0109.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0110.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0110.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0111.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0111.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0112.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0112.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0113.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0113.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0114.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0114.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0201.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0201.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0202.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0202.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0203.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0203.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0204.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0204.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0301.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0301.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0302.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0302.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0303.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0303.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0304.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0304.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0305.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0305.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0306.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0306.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0307.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0307.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0308.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0308.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0309.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0309.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0310.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0310.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0311.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0311.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0312.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0312.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0313.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0313.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0314.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0314.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0315.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0315.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0316.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0316.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0317.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0317.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0318.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0318.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0319.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0319.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0320.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0320.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0321.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0321.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0322.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0322.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0323.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0323.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0324.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0324.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0325.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0325.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0326.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0326.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0327.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0327.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0328.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0328.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0401.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0401.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0402.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0402.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0403.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0403.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0404.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0404.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0405.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0405.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0406.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0406.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0407.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0407.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0501.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0501.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0502.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0502.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0503.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0503.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0504.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0504.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0505.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0505.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0506.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0506.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0507.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0507.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0508.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0508.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0601.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0601.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0602.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0602.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0603.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0603.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0604.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0604.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0605.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0605.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0606.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0606.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0701.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0701.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0702.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0702.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0703.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0703.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0704.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0704.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0705.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0705.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0706.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0706.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0707.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0707.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0708.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0708.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0709.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0709.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0801.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0801.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0802.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0802.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0803.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0803.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0804.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0804.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0805.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0805.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0901.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0901.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0902.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0902.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0903.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0903.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0904.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0904.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.0905.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.0905.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.aa01.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.aa01.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.ab01.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.ab01.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/figs/sam.ab02.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/figs/sam.ab02.gif
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/appa_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/appa_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/appa_02.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/appa_02.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/appa_03.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/appa_03.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/appa_04.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/appa_04.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/appa_05.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/appa_05.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/appb_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/appb_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/appb_02.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/appb_02.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/appb_03.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/appb_03.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/appc_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/appc_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/appd_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/appd_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/appe_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/appe_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/appf_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/appf_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch01_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch01_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch01_02.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch01_02.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch01_03.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch01_03.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch01_04.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch01_04.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch01_05.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch01_05.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch01_06.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch01_06.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch01_07.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch01_07.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch01_08.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch01_08.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch02_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch02_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch02_02.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch02_02.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch02_03.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch02_03.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch02_04.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch02_04.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch02_05.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch02_05.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch02_06.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch02_06.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch03_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch03_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch03_02.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch03_02.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch03_03.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch03_03.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch04_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch04_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch04_02.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch04_02.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch04_03.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch04_03.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch04_04.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch04_04.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch04_05.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch04_05.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch04_06.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch04_06.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch04_07.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch04_07.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch04_08.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch04_08.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch05_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch05_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch05_02.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch05_02.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch05_03.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch05_03.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch05_04.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch05_04.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch05_05.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch05_05.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch06_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch06_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch06_02.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch06_02.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch06_03.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch06_03.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch06_04.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch06_04.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch06_05.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch06_05.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch06_06.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch06_06.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch07_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch07_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch07_02.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch07_02.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch07_03.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch07_03.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch08_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch08_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch08_02.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch08_02.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch08_03.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch08_03.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch08_04.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch08_04.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch08_05.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch08_05.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch08_06.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch08_06.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch08_07.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch08_07.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch09_01.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch09_01.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch09_02.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch09_02.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/ch09_03.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/ch09_03.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/index.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/index.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/inx.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/inx.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/licenseinfo.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/licenseinfo.html
FILE:SambaDOC:SHARED:usr/lib/samba/swat/using_samba/this_edition.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/share/doc/samba/using_samba/this_edition.html
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/pkg/input/SambaSWAT.pkg samba-2.2.8/packaging/Caldera/OpenServer/pkg/input/SambaSWAT.pkg
--- samba-2.2.7a/packaging/Caldera/OpenServer/pkg/input/SambaSWAT.pkg Tue Apr 30 08:25:18 2002
+++ samba-2.2.8/packaging/Caldera/OpenServer/pkg/input/SambaSWAT.pkg Fri Mar 14 15:34:46 2003
@@ -9,103 +9,95 @@
mode = 0755
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/sbin/swat
DIR:SambaSWAT:SHARED:usr/lib/samba/swat:
mode = 0755
owner = root
group = sys
-flags =
DIR:SambaSWAT:SHARED:usr/lib/samba/swat/images:
mode = 0755
owner = root
group = sys
-flags =
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/images/globals.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/images/globals.gif
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/images/home.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/images/home.gif
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/images/passwd.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/images/passwd.gif
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/images/printers.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/images/printers.gif
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/images/samba.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/images/samba.gif
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/images/shares.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/images/shares.gif
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/images/status.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/images/status.gif
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/images/viewconfig.gif:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/images/viewconfig.gif
DIR:SambaSWAT:SHARED:usr/lib/samba/swat/help:
mode = 0755
owner = root
group = sys
-flags =
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/help/welcome.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/welcome.html
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/help/DOMAIN_MEMBER.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/DOMAIN_MEMBER.html
exportPath = /usr/share/doc/samba/help/DOMAIN_MEMBER.html
+FILE:SambaSWAT:SHARED:usr/lib/samba/swat/help/Integrating-with-Windows.html:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/lib/samba/swat/help/Integrating-with-Windows.html
+exportPath = /usr/share/doc/samba/help/Integrating-with-Windows.html
+
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/help/NT_Security.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/NT_Security.html
exportPath = /usr/share/doc/samba/help/NT_Security.html
@@ -113,7 +105,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/OS2-Client-HOWTO.html
exportPath = /usr/share/doc/samba/help/OS2-Client-HOWTO.html
@@ -121,7 +112,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/Samba-HOWTO-Collection.html
exportPath = /usr/share/doc/samba/help/Samba-HOWTO-Collection.html
@@ -129,7 +119,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/Samba-LDAP-HOWTO.html
exportPath = /usr/share/doc/samba/help/Samba-LDAP-HOWTO.html
@@ -137,7 +126,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/UNIX_INSTALL.html
exportPath = /usr/share/doc/samba/help/UNIX_INSTALL.html
@@ -145,7 +133,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/findsmb.1.html
exportPath = /usr/share/doc/samba/help/findsmb.1.html
@@ -153,15 +140,20 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/lmhosts.5.html
exportPath = /usr/share/doc/samba/help/lmhosts.5.html
+FILE:SambaSWAT:SHARED:usr/lib/samba/swat/help/make_unicodemap.1.html:
+mode = 0644
+owner = root
+group = sys
+exportPath = /usr/lib/samba/swat/help/make_unicodemap.1.html
+exportPath = /usr/share/doc/samba/help/make_unicodemap.1.html
+
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/help/make_smbcodepage.1.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/make_smbcodepage.1.html
exportPath = /usr/share/doc/samba/help/make_smbcodepage.1.html
@@ -169,7 +161,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/msdfs_setup.html
exportPath = /usr/share/doc/samba/help/msdfs_setup.html
@@ -177,7 +168,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/nmbd.8.html
exportPath = /usr/share/doc/samba/help/nmbd.8.html
@@ -185,7 +175,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/nmblookup.1.html
exportPath = /usr/share/doc/samba/help/nmblookup.1.html
@@ -193,7 +182,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/pdbedit.1.html
exportPath = /usr/share/doc/samba/help/pdbedit.1.html
@@ -201,7 +189,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/printer_driver2.html
exportPath = /usr/share/doc/samba/help/printer_driver2.html
@@ -209,7 +196,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/rpcclient.1.html
exportPath = /usr/share/doc/samba/help/rpcclient.1.html
@@ -217,7 +203,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/samba.7.html
exportPath = /usr/share/doc/samba/help/samba.7.html
@@ -225,7 +210,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/smb.conf.5.html
exportPath = /usr/share/doc/samba/help/smb.conf.5.html
@@ -233,7 +217,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/smbcacls.1.html
exportPath = /usr/share/doc/samba/help/smbcacls.1.html
@@ -241,7 +224,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/smbclient.1.html
exportPath = /usr/share/doc/samba/help/smbclient.1.html
@@ -249,7 +231,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/smbcontrol.1.html
exportPath = /usr/share/doc/samba/help/smbcontrol.1.html
@@ -257,7 +238,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/smbd.8.html
exportPath = /usr/share/doc/samba/help/smbd.8.html
@@ -265,7 +245,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/smbmnt.8.html
exportPath = /usr/share/doc/samba/help/smbmnt.8.html
@@ -273,7 +252,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/smbmount.8.html
exportPath = /usr/share/doc/samba/help/smbmount.8.html
@@ -281,7 +259,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/smbpasswd.5.html
exportPath = /usr/share/doc/samba/help/smbpasswd.5.html
@@ -289,7 +266,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/smbpasswd.8.html
exportPath = /usr/share/doc/samba/help/smbpasswd.8.html
@@ -297,7 +273,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/smbspool.8.html
exportPath = /usr/share/doc/samba/help/smbspool.8.html
@@ -305,7 +280,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/smbstatus.1.html
exportPath = /usr/share/doc/samba/help/smbstatus.1.html
@@ -313,7 +287,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/smbtar.1.html
exportPath = /usr/share/doc/samba/help/smbtar.1.html
@@ -321,7 +294,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/smbumount.8.html
exportPath = /usr/share/doc/samba/help/smbumount.8.html
@@ -329,7 +301,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/swat.8.html
exportPath = /usr/share/doc/samba/help/swat.8.html
@@ -337,7 +308,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/testparm.1.html
exportPath = /usr/share/doc/samba/help/testparm.1.html
@@ -345,7 +315,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/testprns.1.html
exportPath = /usr/share/doc/samba/help/testprns.1.html
@@ -353,7 +322,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/wbinfo.1.html
exportPath = /usr/share/doc/samba/help/wbinfo.1.html
@@ -361,7 +329,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/winbind.html
exportPath = /usr/share/doc/samba/help/winbind.html
@@ -369,7 +336,6 @@
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/help/winbindd.8.html
exportPath = /usr/share/doc/samba/help/winbindd.8.html
@@ -377,25 +343,21 @@
mode = 0755
owner = root
group = sys
-flags =
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/include/footer.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/include/footer.html
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/include/header.html:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/include/header.html
FILE:SambaSWAT:SHARED:usr/lib/samba/swat/README:
mode = 0644
owner = root
group = sys
-flags =
exportPath = /usr/lib/samba/swat/README
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/samba_configure.desktop samba-2.2.8/packaging/Caldera/OpenServer/samba_configure.desktop
--- samba-2.2.7a/packaging/Caldera/OpenServer/samba_configure.desktop Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/samba_configure.desktop Fri Mar 14 15:16:04 2003
@@ -0,0 +1,5 @@
+[Desktop Entry]
+Name=Configuring Samba
+DocPath=/usr/share/doc/samba/help/osr5config.html
+X-COL-Weight=2.0
+X-COL-rewrite=samba_help
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/samba_help.desktop samba-2.2.8/packaging/Caldera/OpenServer/samba_help.desktop
--- samba-2.2.7a/packaging/Caldera/OpenServer/samba_help.desktop Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/samba_help.desktop Fri Mar 14 15:16:04 2003
@@ -0,0 +1,4 @@
+[Desktop Entry]
+Name=About Samba
+DocPath=/usr/share/doc/samba/help/index.html
+X-COL-Weight=1.0
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/samba_using.desktop samba-2.2.8/packaging/Caldera/OpenServer/samba_using.desktop
--- samba-2.2.7a/packaging/Caldera/OpenServer/samba_using.desktop Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Caldera/OpenServer/samba_using.desktop Fri Mar 14 15:16:04 2003
@@ -0,0 +1,5 @@
+[Desktop Entry]
+Name=Using Samba
+DocPath=/usr/share/doc/samba/using_samba/index.html
+X-COL-Rewrite=using_samba
+X-COL-Weight=3.0
Binary files samba-2.2.7a/packaging/Caldera/OpenServer/sco_logo_med.gif and samba-2.2.8/packaging/Caldera/OpenServer/sco_logo_med.gif differ
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Caldera/OpenServer/smb.conf samba-2.2.8/packaging/Caldera/OpenServer/smb.conf
--- samba-2.2.7a/packaging/Caldera/OpenServer/smb.conf Tue Apr 30 08:25:17 2002
+++ samba-2.2.8/packaging/Caldera/OpenServer/smb.conf Fri Mar 14 15:34:46 2003
@@ -114,7 +114,7 @@
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
- domain master = %%DOMAINMASTER%%
+; domain master = %%DOMAINMASTER%%
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
@@ -126,7 +126,7 @@
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
- domain logons = %%DOMAINLOGONS%%
+; domain logons = %%DOMAINLOGONS%%
# if you enable domain logons then you may want a per-machine or
# per user logon script
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Mandrake/makerpms.sh samba-2.2.8/packaging/Mandrake/makerpms.sh
--- samba-2.2.7a/packaging/Mandrake/makerpms.sh Wed Dec 11 09:34:35 2002
+++ samba-2.2.8/packaging/Mandrake/makerpms.sh Fri Mar 14 22:47:05 2003
@@ -20,7 +20,7 @@
USERID=`id -u`
GRPID=`id -g`
-VERSION='2.2.7a'
+VERSION='2.2.8'
RPMVER=`rpm --version | awk '{print $3}'`
echo The RPM Version on this machine is: $RPMVER
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Mandrake/samba-2.2.7a-smbldaptools-paths.patch samba-2.2.8/packaging/Mandrake/samba-2.2.7a-smbldaptools-paths.patch
--- samba-2.2.7a/packaging/Mandrake/samba-2.2.7a-smbldaptools-paths.patch Wed Dec 31 18:00:00 1969
+++ samba-2.2.8/packaging/Mandrake/samba-2.2.7a-smbldaptools-paths.patch Fri Feb 28 08:42:15 2003
@@ -0,0 +1,139 @@
+diff -ur samba-2.2.7a.orig/examples/LDAP/ldapchpasswd samba-2.2.7a/examples/LDAP/ldapchpasswd
+--- samba-2.2.7a.orig/examples/LDAP/ldapchpasswd 2003-02-10 15:17:53.000000000 -0500
++++ samba-2.2.7a/examples/LDAP/ldapchpasswd 2003-02-10 15:38:24.000000000 -0500
+@@ -103,7 +103,7 @@
+ $password = crypt($pass, $modsalt);
+
+ # LanManager and NT clear text passwords
+-$ntpwd = `/usr/local/sbin/mkntpwd '$pass'`;
++$ntpwd = `/usr/sbin/mkntpwd '$pass'`;
+ chomp($lmpassword = substr($ntpwd, 0, index($ntpwd, ':')));
+ chomp($ntpassword = substr($ntpwd, index($ntpwd, ':')+1));
+
+diff -ur samba-2.2.7a.orig/examples/LDAP/smbldap-tools/INSTALL samba-2.2.7a/examples/LDAP/smbldap-tools/INSTALL
+--- samba-2.2.7a.orig/examples/LDAP/smbldap-tools/INSTALL 2003-02-10 15:17:53.000000000 -0500
++++ samba-2.2.7a/examples/LDAP/smbldap-tools/INSTALL 2003-02-10 15:56:06.000000000 -0500
+@@ -4,12 +4,12 @@
+
+ Quick & Dirty:
+ =-=-=-=-=-=-=-
+- . Copy all those scripts in /usr/local/sbin/
++ . Copy all those scripts in /usr/share/samba/scripts
+ . Modify smbldap_conf.pm to match your configuration
+ . If not already done : "smbpasswd -w secret" to set up
+ the ldap admin password in secrets.tdb
+- . Either add /usr/local/sbin in $PERLLIB or run the scripts
+- from this directory, or make a symlink from /usr/local/sbin/*.pm
++ . Either add /usr/share/samba/scripts in $PERLLIB or run the scripts
++ from this directory, or make a symlink from /etc/samba/*.pm
+ to /usr/lib/perl5/.
+ . to allow a domain admin to add user using "add user script" in smb.conf :
+ chmod 753 smbldap_conf.pm
+@@ -21,7 +21,7 @@
+ RedHat RPM:
+ =-=-=-=-=-=
+ Install smbldap-tools-0.7-1.i386.rpm
+-Modify /usr/local/sbin/smbldap_conf.pm to match you configuration
++Modify /etc/samba/smbldap_conf.pm to match you configuration
+ If not already done : "smbpasswd -w secret" to set up
+ the ldap admin password in secrets.tdb
+
+diff -ur samba-2.2.7a.orig/examples/LDAP/smbldap-tools/smbldap_conf.pm samba-2.2.7a/examples/LDAP/smbldap-tools/smbldap_conf.pm
+--- samba-2.2.7a.orig/examples/LDAP/smbldap-tools/smbldap_conf.pm 2003-02-10 15:17:53.000000000 -0500
++++ samba-2.2.7a/examples/LDAP/smbldap-tools/smbldap_conf.pm 2003-02-10 15:39:42.000000000 -0500
+@@ -230,7 +230,7 @@
+ # prefer mkntpwd... most of the time, it's a wise choice :-)
+ $with_smbpasswd = 0;
+ $smbpasswd = "/usr/bin/smbpasswd";
+-$mk_ntpasswd = "/usr/local/sbin/mkntpwd";
++$mk_ntpasswd = "/usr/sbin/mkntpwd";
+
+ $ldap_path = "/usr/bin";
+ $ldap_opts = "-x";
+diff -ur samba-2.2.7a.orig/examples/LDAP/smbldap-tools/smbldap-migrate-accounts.pl samba-2.2.7a/examples/LDAP/smbldap-tools/smbldap-migrate-accounts.pl
+--- samba-2.2.7a.orig/examples/LDAP/smbldap-tools/smbldap-migrate-accounts.pl 2003-02-10 15:17:53.000000000 -0500
++++ samba-2.2.7a/examples/LDAP/smbldap-tools/smbldap-migrate-accounts.pl 2003-02-10 15:50:15.000000000 -0500
+@@ -134,7 +134,7 @@
+ if (!$user_exists) {
+ if (!defined($Options{'C'})) {
+ # uid doesn't exist and we want to create it
+- my $addcmd = "/usr/local/sbin/smbldap-useradd.pl $usertype $login > /dev/null";
++ my $addcmd = "/usr/share/samba/scripts/smbldap-useradd.pl $usertype $login > /dev/null";
+ print STDERR "$addcmd\n";
+ my $r = system "$addcmd";
+ if ($r != 0) {
+diff -ur samba-2.2.7a.orig/examples/LDAP/smbldap-tools/smbldap-migrate-groups.pl samba-2.2.7a/examples/LDAP/smbldap-tools/smbldap-migrate-groups.pl
+--- samba-2.2.7a.orig/examples/LDAP/smbldap-tools/smbldap-migrate-groups.pl 2003-02-10 15:17:53.000000000 -0500
++++ samba-2.2.7a/examples/LDAP/smbldap-tools/smbldap-migrate-groups.pl 2003-02-10 15:52:51.000000000 -0500
+@@ -135,7 +135,7 @@
+ if (!defined($dn_line = get_group_dn($group))) {
+ # group not found, create it ?
+ if (!$nocreate) {
+- system "/usr/local/sbin/smbldap-groupadd.pl \"$group\"; sleep 5";
++ system "/usr/share/samba/scripts/smbldap-groupadd.pl \"$group\"; sleep 5";
+ if (!defined($dn_line = get_group_dn($group))) {
+ return 1;
+ }
+diff -ur samba-2.2.7a.orig/examples/LDAP/smbldap-tools/smbldap-tools.spec samba-2.2.7a/examples/LDAP/smbldap-tools/smbldap-tools.spec
+--- samba-2.2.7a.orig/examples/LDAP/smbldap-tools/smbldap-tools.spec 2003-02-10 15:17:53.000000000 -0500
++++ samba-2.2.7a/examples/LDAP/smbldap-tools/smbldap-tools.spec 2003-02-10 15:47:58.000000000 -0500
+@@ -1,6 +1,6 @@
+ # $Source: /data/cvs/samba/packaging/Mandrake/Attic/samba-2.2.7a-smbldaptools-paths.patch,v $
+ %define version 0.7
+-%define release 1
++%define release 2
+ %define name smbldap-tools
+ %define realname smbldap-tools
+
+@@ -37,7 +37,7 @@
+ Source20: smbldap-migrate-groups.pl
+ Source21: INFRA
+ BuildRoot: /%{_tmppath}/%{name}
+-Prefix: /usr/local
++Prefix: /usr
+ BuildRequires: perl >= 5.6
+ Requires: perl >= 5.6, openldap, openldap-clients, samba
+
+@@ -94,7 +94,7 @@
+ %post
+ ln -sf %{prefix}/sbin/smbldap_tools.pm /usr/lib/perl5/site_perl/smbldap_tools.pm
+ ln -sf %{prefix}/sbin/smbldap_conf.pm /usr/lib/perl5/site_perl/smbldap_conf.pm
+-chgrp 512 %{prefix}/sbin/smbldap-useradd.pl %{prefix}/sbin/smbldap_conf.pm || echo "An error occured while changing groups of smbldap-useradd.pl and smbldap_conf.pm in /usr/local/sbin. For proper operations, please ensure that they have the same posix group as the Samba domain administrator if there's a local Samba PDC."
++chgrp 512 %{prefix}/sbin/smbldap-useradd.pl %{prefix}/sbin/smbldap_conf.pm || echo "An error occured while changing groups of smbldap-useradd.pl and smbldap_conf.pm in /etc/samba. For proper operations, please ensure that they have the same posix group as the Samba domain administrator if there's a local Samba PDC."
+ perl -i -pe 's/_SLAVELDAP_/localhost/' %{prefix}/sbin/smbldap_conf.pm
+ perl -i -pe 's/_MASTERLDAP_/localhost/' %{prefix}/sbin/smbldap_conf.pm
+ perl -i -pe 's/_SUFFIX_/dc=IDEALX,dc=org/' %{prefix}/sbin/smbldap_conf.pm
+@@ -129,6 +129,10 @@
+
+
+ %changelog
++* Mon Feb 10 2003 Jim Collings 0.7-2
++- Changed prefix to /usr instead of
++- /usr/local for Mandrake compatibility.
++
+ * Sat Jun 1 2002 Olivier Lemaire 0.7-1
+ - some bugfixes about smbldap-populate
+ - bugfixed the smbpasswd call in smbldap-useradd
+diff -ur samba-2.2.7a.orig/examples/LDAP/smbldap-tools/smbldap-useradd.pl samba-2.2.7a/examples/LDAP/smbldap-tools/smbldap-useradd.pl
+--- samba-2.2.7a.orig/examples/LDAP/smbldap-tools/smbldap-useradd.pl 2003-02-10 15:17:53.000000000 -0500
++++ samba-2.2.7a/examples/LDAP/smbldap-tools/smbldap-useradd.pl 2003-02-10 15:53:50.000000000 -0500
+@@ -346,7 +346,7 @@
+ }
+
+ if (defined($Options{'P'})) {
+- exec "/usr/local/sbin/smbldap-passwd.pl $userName"
++ exec "/usr/share/samba/scripts/smbldap-passwd.pl $userName"
+ }
+
+ exit 0;
+diff -ur samba-2.2.7a.orig/examples/VFS/block/smb.conf samba-2.2.7a/examples/VFS/block/smb.conf
+--- samba-2.2.7a.orig/examples/VFS/block/smb.conf 2003-02-10 15:17:53.000000000 -0500
++++ samba-2.2.7a/examples/VFS/block/smb.conf 2003-02-11 13:53:53.000000000 -0500
+@@ -1,6 +1,6 @@
+ [homes]
+ comment = Home Directories
+- vfs object = /usr/local/samba/lib/block.so
++ vfs object = /usr/lib/samba/vfs/block.so
+ browseable = yes
+ writable = yes
+
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Mandrake/samba-print-pdf.sh samba-2.2.8/packaging/Mandrake/samba-print-pdf.sh
--- samba-2.2.7a/packaging/Mandrake/samba-print-pdf.sh Tue Dec 10 08:58:00 2002
+++ samba-2.2.8/packaging/Mandrake/samba-print-pdf.sh Fri Feb 28 09:56:06 2003
@@ -10,9 +10,10 @@
# Arguments:
# $1 = file (usually passed with %s from samba)
# $2 = unix prefix to where to place the file (~%u should work)
-# $3 = windows prefix to the same location (\\%L\%u should work)
+# $3 = windows prefix to the same location (//%L/%u should work)
# $4 = user/computer to send a notification to (%u or %m)
# $5 = IP address of client (%I)
+# $6 = Name of destination file without extension (%J)
PS2PDF=ps2pdf13
@@ -22,6 +23,9 @@
PERMS=640
INFILE=$(basename $INPUT)
BASEFILE=pdf-service
+PREFIX="$2"
+NAME="$6"
+WINBASE=$(echo "$3"|sed -e 's,/,\\\\,g')
#make a temp file to use for the output of the PDF
OUTPUT=`mktemp -q $2/$BASEFILE-XXXXXX`
@@ -29,30 +33,34 @@
echo "$0: Can't create temp file $2/$BASEFILE-XXXXXX, exiting..."
exit 1
fi
+if [ "$NAME" != "" ]; then
+ FINALOUTPUT="$PREFIX/$NAME"
+else
+ FINALOUTPUT="$OUTPUT"
+fi
-WIN_OUTPUT="$3\\`basename $OUTPUT`"
+WIN_OUTPUT="$WINBASE\\"`basename "$FINALOUTPUT"`
# create the PDF:
-$PS2PDF $OPTIONS $INPUT $OUTPUT.pdf >/dev/null 2>&1
+$PS2PDF $OPTIONS $INPUT "$OUTPUT".pdf >/dev/null 2>&1
+mv -f "$OUTPUT".pdf "$FINALOUTPUT".pdf
# Generate a message to send to the user, and deal with the original file:
MESSAGE=$(echo "Your PDF file has been created as $WIN_OUTPUT.pdf\n")
if [ $KEEP_PS ];then
- mv $INPUT $OUTPUT.ps
+ mv -f $INPUT "${FINALOUTPUT}".ps
MESSAGE=$(echo "$MESSAGE and your postscript file as $WIN_OUTPUT.ps")
# Fix permissions on the generated files
- chmod $PERMS $OUTPUT.ps
+ chmod $PERMS "${FINALOUTPUT}".ps
else
rm -f $INPUT
- chmod $PERMS $OUTPUT.ps $OUTPUT.pdf
+ chmod $PERMS "${FINALOUTPUT}".ps "${FINALOUTPUT}".pdf
# Fix permissions on the generated files
fi
-chmod $PERMS $OUTPUT.ps $OUTPUT.pdf
-
#Remove empty file from mktemp:
-rm -f $OUTPUT
+[ "x$NAME" -eq "x" ] && rm -f $OUTPUT
# Send notification to user
echo -e $MESSAGE|smbclient -M $4 -I $5 -U "PDF Generator" >/dev/null 2>&1
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Mandrake/samba2.spec samba-2.2.8/packaging/Mandrake/samba2.spec
--- samba-2.2.7a/packaging/Mandrake/samba2.spec Wed Dec 11 09:34:35 2002
+++ samba-2.2.8/packaging/Mandrake/samba2.spec Fri Mar 14 22:47:05 2003
@@ -1,9 +1,9 @@
-%define ver 2.2.5
-%define rel 21mdk
-%define vscanver 0.2.5c
+%define ver 2.2.7a
+%define rel 4mdk
+%define vscanver 0.3.1
# 2.2.4 and 1 replace by samba-team at release
-%define pversion 2.2.7a
+%define pversion 2.2.8
%define prelease 1
# For testing this setup:
#%define pversion1 2.2.5
@@ -33,6 +33,7 @@
# We now do detection of the Mandrake release we are building on:
#%define build_cooker %(if [ `awk '{print $3}' /etc/mandrake-release` = "Cooker" ];then echo 1; else echo 0; fi)
#%define build_cooker %(if [[ `cat /etc/mandrake-release|grep Cooker` ]];then echo 1; else echo 0; fi)
+%define build_mdk91 %(if [ `awk '{print $4}' /etc/mandrake-release` = 9.1 ];then echo 1; else echo 0; fi)
%define build_mdk90 %(if [ `awk '{print $4}' /etc/mandrake-release` = 9.0 ];then echo 1; else echo 0; fi)
%define build_mdk83 %(if [ `awk '{print $4}' /etc/mandrake-release` = 8.3 ];then echo 1; else echo 0; fi)
%define build_mdk82 %(if [ `awk '{print $4}' /etc/mandrake-release` = 8.2 ];then echo 1; else echo 0; fi)
@@ -41,12 +42,18 @@
%define build_mdk72 %(if [ `awk '{print $4}' /etc/mandrake-release` = 7.2 ];then echo 1; else echo 0; fi)
%define build_non_default 0
-%define build_acl 1
-%define build_winbind 1
-%define build_wins 1
-%define build_ldap 0
+# Default options
+%define build_acl 1
+%define build_winbind 1
+%define build_wins 1
+%define build_ldap 0
+%define build_scanners 0
# Set defaults for each version
+%if %build_mdk91
+%define build_ldap 0
+%endif
+
%if %build_mdk90
%define build_ldap 0
%endif
@@ -98,6 +105,8 @@
%{?_with_ldap: %{expand: %%define build_non_default 1}}
%{?_without_ldap: %{expand: %%global build_ldap 0}}
%{?_without_ldap: %{expand: %%define build_non_default 1}}
+%{?_with_scanners: %{expand: %%define build_scanners 1}}
+%{?_with_scanners: %{expand: %%define build_non_default 1}}
# As if that weren't enough, we're going to try building with antivirus
# support as an option also
@@ -108,17 +117,26 @@
%define build_sophos 0
%define build_symantec 0
%define build_trend 0
+%if %build_vscan && %build_scanners
+#These can be enabled here by default
+# (kaspersky requires their library present)
+%define build_fprot 1
+%define build_mks 1
+%define build_openantivirus 1
+%define build_sophos 1
+%define build_trend 1
+%endif
%if %build_vscan
%{?_with_fprot: %{expand: %%global build_fprot 1}}
%{?_with_kaspersky: %{expand: %%global build_kaspersky 1}}
%{?_with_mks: %{expand: %%global build_mks 1}}
%{?_with_openav: %{expand: %%global build_openantivirus 1}}
%{?_with_sophos: %{expand: %%global build_sophos 1}}
-%{?_with_symantec: %{expand: %%global build_symantec 1}}
+#%{?_with_symantec: %{expand: %%global build_symantec 1}}
%{?_with_trend: %{expand: %%global build_trend 1}}
-%define vscandir "samba-vscan-%{vscanver}"
+%global vscandir samba-vscan-%{vscanver}
%endif
-%define vfsdir "examples.bin/VFS"
+%global vfsdir examples.bin/VFS
#Workaround missing macros in 8.x:
%{!?perl_vendorlib: %{expand: %%global perl_vendorlib %{perl_sitearch}/../}}
@@ -147,6 +165,7 @@
Release: %{rel}
%endif
License: GPL
+URL: http://www.samba.org
Group: System/Servers
Source: ftp://samba.org/pub/samba/samba-%{source_ver}.tar.bz2
Source1: samba.log
@@ -161,35 +180,27 @@
%endif
Source10: samba-print-pdf.sh.bz2
Patch1: smbw.patch.bz2
-Patch5: samba-2.2.0-gawk.patch.bz2
-#Patch11: samba-2.0.7-smbspool-guest.patch.bz2
-Patch12: samba-2.2.0-buildroot.patch.bz2
-#Patch16: samba-mkdir.patch.bz2
-Patch17: smbmount-sbin.patch.bz2
-Patch18: samba-2.2.5-gp-reloc-fix.patch.bz2
+Patch2: samba-2.2.0-gawk.patch.bz2
+Patch3: samba-2.2.0-buildroot.patch.bz2
+Patch4: smbmount-sbin.patch.bz2
+Patch5: samba-2.2.5-gp-reloc-fix.patch.bz2
+Patch6: samba-2.2.7a-smbldaptools-paths.patch.bz2
%if !%have_pversion
# Version specific patches: current version
-Patch26: samba-2.2.5-smb.conf.patch.bz2
-Patch28: samba-2.2.5-ldap_start_tls.patch.bz2
-Patch29: samba-2.2.5-parse_sec.patch.bz2
-Patch30: samba-2.2.5-nt-dirlisting.patch.bz2
-Patch31: samba-2.2.5-random_smbd-read.patch.bz2
-Patch32: samba-2.2.5-winbind-init.patch.bz2
-Patch33: samba-2.2.5-pam-password.patch.bz2
-Patch34: samba-2.2.5-win2k_copy_bug.patch.bz2
-Patch35: samba-2.2.5-samba-ldap-include-conf.patch.bz2
-Patch36: samba-2.2.6-smb.conf.patch.bz2
-Patch37: samba-2.2.6-smbumount_lazy.patch.bz2
+Patch101: samba-2.2.7a-smbtar-large-file-fix.patch.bz2
+Patch102: samba-2.2.7a-smbclient-large-file-fix.patch.bz2
+Patch103: samba-2.2.7a-ldap-rebind.patch.bz2
+Patch104: samba-2.2.7a-mandrake-packaging.patch.bz2
+Patch105: samba-2.2.6-smbumount_lazy.patch.bz2
%else
# Version specific patches: upcoming version
%endif
# Limbo patches (applied to prereleases, but not preleases, ie destined for
# samba CVS)
%if %have_pversion && %have_pre
-Patch36: samba-2.2.6-smb.conf.patch.bz2
%endif
Requires: pam >= 0.64, samba-common = %{version}
-BuildRequires: pam-devel autoconf readline-devel
+BuildRequires: pam-devel autoconf readline-devel libldap2-devel popt-devel
%if %build_acl
BuildRequires: libacl-devel
%endif
@@ -198,9 +209,9 @@
%else
BuildRequires: libcups-devel
%endif
-%if %build_ldap
-BuildRequires: libldap-devel
-%endif
+#%if %build_ldap
+#BuildRequires: libldap-devel
+#%endif
BuildRoot: %{_tmppath}/%{name}-root
Prefix: /usr
Prereq: /sbin/chkconfig /bin/mktemp /usr/bin/killall
@@ -411,6 +422,7 @@
Summary: On-access virus scanning for samba using FPROT
Group: System/Servers
Requires: samba = %{version}
+Provides: samba-vscan
Autoreq: 0
%description vscan-fprot
A vfs-module for samba to implement on-access scanning using the
@@ -422,6 +434,7 @@
Summary: On-access virus scanning for samba using Kaspersky
Group: System/Servers
Requires: samba = %{version}
+Provides: samba-vscan
Autoreq: 0
%description vscan-kaspersky
A vfs-module for samba to implement on-access scanning using the
@@ -433,6 +446,7 @@
Summary: On-access virus scanning for samba using MKS
Group: System/Servers
Requires: samba = %{version}
+Provides: samba-vscan
Autoreq: 0
%description vscan-mks
A vfs-module for samba to implement on-access scanning using the
@@ -444,6 +458,7 @@
Summary: On-access virus scanning for samba using OpenAntivirus
Group: System/Servers
Requires: samba = %{version}
+Provides: samba-vscan
Autoreq: 0
%description vscan-openantivirus
A vfs-module for samba to implement on-access scanning using the
@@ -455,6 +470,7 @@
Summary: On-access virus scanning for samba using Sophos
Group: System/Servers
Requires: samba = %{version}
+Provides: samba-vscan
Autoreq: 0
%description vscan-sophos
A vfs-module for samba to implement on-access scanning using the
@@ -466,6 +482,7 @@
Summary: On-access virus scanning for samba using Symantec
Group: System/Servers
Requires: samba = %{version}
+Provides: samba-vscan
Autoreq: 0
%description vscan-symantec
A vfs-module for samba to implement on-access scanning using the
@@ -477,6 +494,7 @@
Summary: On-access virus scanning for samba using Trend
Group: System/Servers
Requires: samba = %{version}
+Provides: samba-vscan
Autoreq: 0
%description vscan-trend
A vfs-module for samba to implement on-access scanning using the
@@ -523,28 +541,26 @@
%else
%setup -q -n %{name}-%{source_ver}
%endif
-#%patch111 -p1
+# Current patches
+echo "Applying patches for version: %{ver}"
%patch1 -p1 -b .smbw
-%patch5 -p1 -b .gawk
-#%patch7 -p1
-#%patch11 -p0 -b .smbspool
-%patch12 -p1 -b .buildroot
-%patch17 -p1
-%patch18 -p1 -b .gp-reloc-fix
+%patch2 -p1 -b .gawk
+%patch3 -p1 -b .buildroot
+%patch4 -p1
+%patch5 -p1 -b .gp-reloc-fix
+%patch6 -p1
# Version specific patches: current version
%if !%have_pversion
echo "Applying patches for current version: %{ver}"
-%patch26 -p1 -b .mdk
-%patch28 -p1
-%patch29 -p1
-%patch30 -p1
-%patch31 -p1
-%patch32 -p1
-%patch33 -p1
-%patch34 -p1
-%patch35 -p1
-%patch36 -p1
-%patch37 -p1
+(cd source/client
+%patch101 -p0 -b .lfs
+)
+( cd source
+%patch102 -p0 -b .lfs
+)
+%patch103 -p1 -b .ldap
+%patch104 -p1 -b .mdk
+%patch105 -p1
%else
# Version specific patches: upcoming version
echo "Applying patches for new versions: %{pversion}"
@@ -553,7 +569,6 @@
# Limbo patches
%if %have_pversion && %have_pre
echo "Appling patches which should only be applied to prereleases"
-%patch36 -p1
%endif
cp %{SOURCE7} .
@@ -563,9 +578,12 @@
%if %build_vscan
# put antivirus files in examples.bin/VFS/
-for av in fprot kaspersky mks openantivirus sophos symantec trend; do
- cp -a %{vscandir}/$av %{vfsdir}
-done
+#for av in fprot kaspersky mks openantivirus sophos trend; do
+# [ -e %{vscandir}/$av ] && cp -a %{vscandir}/$av %{vfsdir}
+#done
+cp -a %{vscandir} %{vfsdir}
+#fix stupid directory names:
+mv %{vfsdir}/%{vscandir}/openantivirus %{vfsdir}/%{vscandir}/oav
%endif
%build
@@ -575,31 +593,34 @@
CPPFLAGS="-I/usr/include/openssl"; export CPPFLAGS
CFLAGS="$RPM_OPT_FLAGS"
%configure --prefix=%{prefix} \
- --with-fhs \
- --libdir=/etc/samba \
- --sysconfdir=/etc/samba \
- --localstatedir=/var \
- --with-configdir=/etc/samba \
- --with-codepagedir=/var/lib/samba/codepages \
- --with-privatedir=/etc/samba \
- --with-swatdir=%{prefix}/share/swat \
- --with-smbmount \
- --with-syslog \
- --with-automount \
- --with-pam \
- --with-pam_smbpass \
- --with-vfs \
- --with-utmp \
- --with-msdfs \
- --with-smbwrapper \
- --with-libsmbclient \
+ --with-fhs \
+ --libdir=/etc/samba \
+ --sysconfdir=/etc/samba \
+ --localstatedir=/var \
+ --with-configdir=/etc/samba \
+ --with-codepagedir=/var/lib/samba/codepages \
+ --with-privatedir=/etc/samba \
+ --with-swatdir=%{prefix}/share/swat \
+ --with-smbmount \
+ --with-syslog \
+ --with-automount \
+ --with-pam \
+ --with-sendfile-support \
+ --with-pam_smbpass \
+ --with-vfs \
+ --with-utmp \
+ --with-msdfs \
+ --with-smbwrapper \
+ --with-libsmbclient \
%if %build_acl
- --with-acl-support \
+ --with-acl-support \
%endif
%if %build_ldap
- --with-ldapsam \
+ --with-ldapsam \
+ --with-winbind-ldap-hack \
%endif
- --with-quotas
+ --with-winbind-auth-challenge \
+ --with-quotas
#make CFLAGS="$RPM_OPT_FLAGS -D_GNU_SOURCE" all
make CFLAGS="$RPM_OPT_FLAGS -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE" \
@@ -609,8 +630,6 @@
%configure --prefix=%{prefix} \
--mandir=%{prefix}/share/man
make
-#make CFLAGS="$RPM_OPT_FLAGS -I../../source -I../../source/include -I../../source/ubiqx \
-# -I../../source/smbwrapper -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE"
)
# Build mkntpasswd in examples/LDAP/ for smbldaptools
@@ -621,31 +640,33 @@
# Build antivirus vfs objects:
%if %build_fprot
+echo -e "\n\nBuild antivirus VFS modules\n\n"
echo "Building fprot"
+(cd %{vfsdir}/%{vscandir}/fprot;make)
%endif
%if %build_kaspersky
echo "Building Kaspersky"
-(cd %{vfsdir}/kaspersky;make)
+(cd %{vfsdir}/%{vscandir}/kaspersky;make)
%endif
%if %build_mks
echo "Building mks"
-(cd %{vfsdir}/mks;make)
+(cd %{vfsdir}/%{vscandir}/mks;make)
%endif
%if %build_openantivirus
echo "Building OpenAntivirus"
-(cd %{vfsdir}/openantivirus;make)
+(cd %{vfsdir}/%{vscandir}/oav;make)
%endif
%if %build_sophos
echo "building sophos"
-(cd %{vfsdir}/sophos;make)
+(cd %{vfsdir}/%{vscandir}/sophos;make)
%endif
%if %build_symantec
echo "Building symantec"
-(cd %{vfsdir}/symantec;make)
+(cd %{vfsdir}/%{vscandir}/symantec;make)
%endif
%if %build_trend
echo "Building Trend"
-(cd %{vfsdir}/trend;make)
+(cd %{vfsdir}/%{vscandir}/trend;make)
%endif
%install
@@ -694,10 +715,12 @@
# Antivirus support:
# mkdir -p $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan
- for av in fprotd kavp mksd oav sophos symantec trend; do
- if [ -d %{vfsdir}/$av -a -e %{vfsdir}/$av/vscan-$av.so ];then
- cp %{vfsdir}/$av/vscan-$av.so \
+ for av in fprot kavp mks oav sophos symantec trend; do
+ if [ -d %{vfsdir}/%{vscandir}/$av -a -e %{vfsdir}/%{vscandir}/$av/vscan-$av*.so ];then
+ cp %{vfsdir}/%{vscandir}/$av/vscan-$av*.so \
$RPM_BUILD_ROOT%{_libdir}/samba/vfs/
+ cp %{vfsdir}/%{vscandir}/$av/vscan-$av*.conf \
+ $RPM_BUILD_ROOT%{_sysconfdir}/%{name}
fi
done
@@ -729,7 +752,7 @@
install -m644 source/codepages/codepage_def.$i $RPM_BUILD_ROOT/var/lib/samba/codepages/src
done
-for i in 437 737 775 850 852 857 861 862 866 932 936 949 950 1125 1251 ISO8859-1 ISO8859-2 ISO8859-5 ISO8859-7 ISO8859-9 ISO8859-13 ISO8859-15 KOI8-R KOI8-U
+for i in 437 737 775 850 852 857 861 862 866 932 936 949 950 1125 1251 ISO8859-1 ISO8859-2 ISO8859-5 ISO8859-7 ISO8859-8 ISO8859-9 ISO8859-13 ISO8859-15 KOI8-R KOI8-U
do
install -m644 source/codepages/CP$i.TXT $RPM_BUILD_ROOT/var/lib/samba/codepages/src
done
@@ -740,7 +763,7 @@
done
# Build unicode load files
-for i in 437 737 775 850 852 857 861 862 866 932 936 949 950 1125 1251 ISO8859-1 ISO8859-2 ISO8859-5 ISO8859-7 ISO8859-9 ISO8859-13 ISO8859-15 KOI8-R KOI8-U; do
+for i in 437 737 775 850 852 857 861 862 866 932 936 949 950 1125 1251 ISO8859-1 ISO8859-2 ISO8859-5 ISO8859-7 ISO8859-8 ISO8859-9 ISO8859-13 ISO8859-15 KOI8-R KOI8-U; do
$RPM_BUILD_ROOT/%{prefix}/bin/make_unicodemap $i $RPM_BUILD_ROOT/var/lib/samba/codepages/src/CP$i.TXT $RPM_BUILD_ROOT/var/lib/samba/codepages/unicode_map.$i
done
rm -rf $RPM_BUILD_ROOT/var/lib/samba/codepages/src
@@ -785,7 +808,6 @@
install -m644 packaging/Mandrake/smb.conf $RPM_BUILD_ROOT/etc/samba/smb.conf
install -m644 packaging/Mandrake/smbusers $RPM_BUILD_ROOT/etc/samba/smbusers
install -m755 packaging/Mandrake/smbprint $RPM_BUILD_ROOT/usr/bin
- #install -m755 packaging/RedHat/smbadduser $RPM_BUILD_ROOT/usr/bin
install -m755 packaging/Mandrake/findsmb $RPM_BUILD_ROOT/usr/bin
install -m755 packaging/Mandrake/smb.init $RPM_BUILD_ROOT/etc/rc.d/init.d/smb
install -m755 packaging/Mandrake/smb.init $RPM_BUILD_ROOT/usr/sbin/samba
@@ -800,6 +822,7 @@
# Install smbldap-tools scripts:
for i in examples/LDAP/smbldap-tools/*.pl; do
install -m 750 $i $RPM_BUILD_ROOT/%{_datadir}/samba/scripts/
+ ln -s %{_datadir}/%{name}/scripts/`basename $i` $RPM_BUILD_ROOT/%{_bindir}/`basename $i|sed -e 's/\.pl//g'`
done
install -m 750 examples/LDAP/smbldap-tools/smbldap_tools.pm $RPM_BUILD_ROOT/%{_datadir}/samba/scripts/
@@ -860,6 +883,71 @@
bzcat %{SOURCE6} > $RPM_BUILD_ROOT%{_miconsdir}/swat.xpm
bzcat %{SOURCE10}> $RPM_BUILD_ROOT%{_datadir}/samba/scripts/print-pdf
+
+# Delete files which will not be included, so that /usr/lib/rpm/check-files
+# doesn't error out when Checking for unpackaged file(s)
+%if ! %build_ldap
+%endif
+
+%if ! %build_acl
+%endif
+
+%if ! %build_winbind
+rm -f $RPM_BUILD_ROOT%{_sbindir}/winbind
+rm -f $RPM_BUILD_ROOT%{_sbindir}/winbindd
+rm -f $RPM_BUILD_ROOT%{_bindir}/wbinfo
+rm -f $RPM_BUILD_ROOT/lib/security/pam_winbind*
+rm -f $RPM_BUILD_ROOT/lib/libnss_winbind*
+rm -f $RPM_BUILD_ROOT/etc/rc.d/init.d/winbind
+rm -f $RPM_BUILD_ROOT/etc/pam.d/system-auth-winbind
+rm -f $RPM_BUILD_ROOT%{_mandir}/man8/winbindd.8*
+rm -f $RPM_BUILD_ROOT%{_mandir}/man1/wbinfo.1*
+%endif
+
+%if ! %build_wins
+rm -f $RPM_BUILD_ROOT/lib/libnss_wins.so*
+%endif
+
+%ifarch alpha
+rm -f $RPM_BUILD_ROOT/sbin/mount.smb
+rm -f $RPM_BUILD_ROOT/sbin/mount.smbfs
+rm -f $RPM_BUILD_ROOT%{_bindir}/smbmount
+rm -f $RPM_BUILD_ROOT%{_bindir}/smbumount
+rm -f $RPM_BUILD_ROOT%{_sbindir}/smbmnt
+rm -f $RPM_BUILD_ROOT%{_mandir}/man8/smbmnt.8*
+rm -f $RPM_BUILD_ROOT%{_mandir}/man8/smbmount.8*
+rm -f $RPM_BUILD_ROOT%{_mandir}/man8/smbumount.8*
+%endif
+
+#Files for antivirus support:
+%if ! %build_fprot
+rm -f $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan-fprotd.so
+%endif
+
+%if ! %build_kaspersky
+rm -f $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan-kavp.so
+%endif
+
+%if ! %build_mks
+rm -f $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan-mksd.so
+%endif
+
+%if ! %build_openantivirus
+rm -f $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan-oav.so
+%endif
+
+%if ! %build_sophos
+rm -f $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan-sophos.so
+%endif
+
+%if ! %build_symantec
+rm -f $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan-symantec.so
+%endif
+
+%if ! %build_trend
+rm -f $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan-trend.so
+%endif
+
%clean
rm -rf $RPM_BUILD_ROOT
@@ -1013,15 +1101,6 @@
if [ $1 = 0 ] ; then
%_preun_service smb
-# /sbin/chkconfig --level 35 smb reset
-# Let's not loose /var/cache/samba
-
-# for i in browse.dat wins.dat brlock.tdb unexpected.tdb connections.tdb \
-#locking.tdb messages.tdb;do
-# if [ -e /var/cache/samba/$i ]; then
-# mv -f /var/cache/samba/$i /var/cache/samba/$i.BAK
-# fi;
-# done
if [ -d /var/log/samba ]; then
rm -rf /var/log/samba/*
fi
@@ -1050,6 +1129,11 @@
%else
%post -n samba-swat
%endif
+# Change only_from entry in /etc/xinetd.d/swat (localhost bug)
+[[ `/bin/grep "localhost" /etc/xinetd.d/swat` ]] && {
+echo "-- Setting swat xinetd only_from entry to 127.0.0.1"
+perl -pi -e 's/localhost/127.0.0.1/' /etc/xinetd.d/swat
+}
if [ -f /var/lock/subsys/xinetd ]; then
service xinetd reload >/dev/null 2>&1 || :
fi
@@ -1100,7 +1184,6 @@
%{_bindir}/smbstatus
%{_bindir}/convert_smbpasswd
%attr(755,root,root) /lib/security/pam_smbpass*
-#/usr/share/swat
%attr(-,root,root) %config(noreplace) /etc/samba/smbusers
%attr(-,root,root) %config /etc/rc.d/init.d/smb
%attr(-,root,root) %config(noreplace) /etc/logrotate.d/samba
@@ -1113,10 +1196,9 @@
%{_mandir}/man8/nmbd.8*
%{_mandir}/man1/smbcontrol.1*
#%{_mandir}/man1/lmhosts.1*
-%{_mandir}/man5/smb.conf.5*
%attr(755,root,root) %dir /var/lib/samba/netlogon
%attr(775,root,users) %dir /var/lib/samba/profiles
-%attr(755,root,root) %dir /var/lib/samba/printers/*
+%attr(775,root,adm) %dir /var/lib/samba/printers/*
%attr(755,root,root) %dir %{_libdir}/samba/vfs
%attr(755,root,root) %{_libdir}/samba/vfs/audit.so
%attr(755,root,root) %{_libdir}/samba/vfs/block.so
@@ -1126,15 +1208,16 @@
%attr(1777,root,root) %dir /var/spool/samba
%dir %{_datadir}/%{name}/scripts
%attr(0755,root,root) %{_datadir}/%{name}/scripts/print-pdf
-%attr(0750,root,root) %{_datadir}/%{name}/scripts/smbldap*.pl
-%attr(0640,root,root) %config(noreplace) %{_sysconfdir}/%{name}/smbldap_conf.pm
+%attr(0750,root,adm) %{_datadir}/%{name}/scripts/smbldap*.pl
+%attr(0750,root,adm) %{_bindir}/smbldap*
+%attr(0640,root,adm) %config(noreplace) %{_sysconfdir}/%{name}/smbldap_conf.pm
%attr(0644,root,root) %{_datadir}/%{name}/scripts/smbldap_tools.pm
%{perl_vendorlib}/*.pm
%attr(0700,root,root) %{_datadir}/%{name}/scripts/*port_smbpasswd.pl
%files doc
-%defattr(-,root,root)
+%defattr(644,root,root,755)
%doc README COPYING Manifest Read-Manifest-Now
%doc WHATSNEW.txt Roadmap
%doc README.%{name}-mandrake-rpm
@@ -1180,11 +1263,12 @@
%{_bindir}/smbtar
%{_bindir}/smbspool
# Link of smbspool to CUPS
-/%{_libdir}/cups/backend/smb
-/%{_mandir}/man1/nmblookup.1*
-/%{_mandir}/man1/findsmb.1*
-/%{_mandir}/man1/smbclient.1*
-/%{_mandir}/man1/smbtar.1*
+%{_libdir}/cups/backend/smb
+%{_mandir}/man1/nmblookup.1*
+%{_mandir}/man1/findsmb.1*
+%{_mandir}/man1/smbclient.1*
+%{_mandir}/man1/smbtar.1*
+%{_mandir}/man8/smbspool.8*
%if %build_ldap
%files common-ldap
@@ -1204,6 +1288,8 @@
%{_bindir}/smbsh
%{_bindir}/smbpasswd
%{_bindir}/smbcacls
+%{_sbindir}/debug2html
+%{_sbindir}/smbfilter
%{_libdir}/smbwrapper.so
%{_libdir}/libsmbclient.so
%attr(-,root,root) %config(noreplace) /etc/samba/smb.conf
@@ -1218,7 +1304,9 @@
%{_mandir}/man5/smb.conf.5*
%{_mandir}/man5/lmhosts.5*
%{_mandir}/man8/smbpasswd.8*
-/%{_mandir}/man1/smbcacls.1*
+%{_mandir}/man1/smbcacls.1*
+%{_mandir}/man1/rpcclient.1*
+%{_mandir}/man8/pdbedit.8*
#%if %build_winbind
#%if %build_ldap
@@ -1232,6 +1320,7 @@
%if %build_winbind
%defattr(-,root,root)
%{_sbindir}/winbindd
+%{_sbindir}/winbind
%{_bindir}/wbinfo
%attr(755,root,root) /lib/security/pam_winbind*
%attr(755,root,root) /lib/libnss_winbind*
@@ -1252,52 +1341,155 @@
%files vscan-fprot
%defattr(-,root,root)
%{_libdir}/samba/vfs/vscan-fprotd.so
-%doc examples.bin/VFS/fprot/INSTALL
+%config(noreplace) %{_sysconfdir}/%{name}/vscan-fprotd.conf
+%doc %{vfsdir}/%{vscandir}/INSTALL
%endif
%if %build_kaspersky
%files vscan-kaspersky
%defattr(-,root,root)
%{_libdir}/samba/vfs/vscan-kavp.so
-%doc examples.bin/VFS/kaspersky/INSTALL
+%config(noreplace) %{_sysconfdir}/%{name}/vscan-kavp.conf
+%doc %{vfsdir}/%{vscandir}/examples.bin/VFS/kaspersky/INSTALL
%endif
%if %build_mks
%files vscan-mks
%defattr(-,root,root)
%{_libdir}/samba/vfs/vscan-mksd.so
-%doc examples.bin/VFS/mks/INSTALL
+%config(noreplace) %{_sysconfdir}/%{name}/vscan-mks*.conf
+%doc %{vfsdir}/%{vscandir}/INSTALL
%endif
%if %build_openantivirus
%files vscan-openantivirus
%defattr(-,root,root)
%{_libdir}/samba/vfs/vscan-oav.so
-%doc examples.bin/VFS/openantivirus/INSTALL
+%config(noreplace) %{_sysconfdir}/%{name}/vscan-oav.conf
+%doc %{vfsdir}/%{vscandir}/INSTALL
%endif
%if %build_sophos
%files vscan-sophos
%defattr(-,root,root)
%{_libdir}/samba/vfs/vscan-sophos.so
-%doc examples.bin/VFS/sophos/INSTALL
+%config(noreplace) %{_sysconfdir}/%{name}/vscan-sophos.conf
+%doc %{vfsdir}/%{vscandir}/INSTALL
%endif
%if %build_symantec
%files vscan-symantec
%defattr(-,root,root)
%{_libdir}/samba/vfs/vscan-symantec.so
-%doc examples.bin/VFS/symantec/INSTALL
+%config(noreplace) %{_sysconfdir}/%{name}/vscan-symantec.conf
+%doc %{vfsdir}/%{vscandir}/INSTALL
%endif
%if %build_trend
%files vscan-trend
%defattr(-,root,root)
%{_libdir}/samba/vfs/vscan-trend.so
-%doc examples.bin/VFS/trend/INSTALL
+%config(noreplace) %{_sysconfdir}/%{name}/vscan-trend.conf
+%doc %{vfsdir}/%{vscandir}/INSTALL
%endif
%changelog
+* Fri Feb 14 2003 Buchan Milne 2.2.7a-4mdk
+- Fix build openantivirus with default scanners
+- buildrequire popt-devel
+- From Jim Collings
+ - Patched smbldap-tools and created links to same in /usr/bin
+
+* Thu Jan 23 2003 Buchan Milne 2.2.7a-3mdk
+- Two patches to fix large file support (smbtar:p101 and smbclient:p102)
+- Patch to enable ldap referral (103)
+- Build all vscan except kav (requires kaspersky lib) with --with-scanners
+- Allow adm group to install printer drivers and use smbldaptools by default
+- Remove smb.conf man page conflict
+
+* Thu Jan 02 2003 Sylvestre Taburet 2.2.7a-2mdk
+- Rebuilt because of new rpm macros and new glibc.
+- Happy new year 2003 to all samba developers, contributors and users!
+
+* Wed Dec 11 2002 Sylvestre Taburet 2.2.7a-1mdk
+- Upgraded to 2.2.7a.
+
+* Sun Dec 08 2002 Buchan Milne 2.2.7-5mdk
+- samba-vscan 0.3.1 (and make it build again)
+- Make all vscan packages provide samba-vscan
+- All scanner packages (besides kaspersky) can be built without the
+ scanner installed, but we don't quite to this yet ...
+- Add vscan-(scanner).conf files
+- Add winbind-auth-challenge to configure, for squid support
+- Use winbind-ldap-hack only when building with ldapsam support
+ since no-one has been able to test this thoroughly, and my only
+ tests indicated performance problems with it (and I need this RPM to
+ work for squid)
+
+* Tue Nov 26 2002 Sylvestre Taburet 2.2.7-4mdk
+- Fix perms on doc.
+- Cleaned up specfile a bit.
+- Added support for upcoming Mandrake Linux 9.1 in auto build process.
+
+* Tue Nov 26 2002 Sylvestre Taburet 2.2.7-3mdk
+- Put (noreplace) back in %files swat.
+- Changed only_from entry in sample swat to "127.0.0.1".
+- Change only_from entry in /etc/xinetd.d/swat to "127.0.0.1" on %post swat.
+
+* Fri Nov 22 2002 Sylvestre Taburet 2.2.7-2mdk
+- Removed noreplace of /etc/xinetd.d/swat on update.
+- Updated samba-vscan (0.3.0).
+
+* Wed Nov 20 2002 Sylvestre Taburet 2.2.7-1mdk
+- Update to 2.2.7.
+- Removed patch 38.
+
+* Sat Nov 16 2002 Alexander Skwar 2.2.6-6mdk
+- Remove installed files which will not be included due to build options,
+ so that /usr/lib/rpm/check-files doesn't error out when
+ Checking for unpackaged file(s)
+- Add debug2html, smbfilter to common package
+- Add /usr/sbin/winbind to winbind package
+- Add rpcclient manpage to common package
+- Add smbspool, pdbedit manpage to client package
+
+* Wed Nov 06 2002 Sylvestre Taburet 2.2.6-5mdk
+- add winbind ldap hack again, with proper build-require (libldap2-devel)
+- enable --with-sendfile-support (default in 3.0. Increases performance).
+
+* Wed Oct 30 2002 Sylvestre Taburet 2.2.6-4mdk
+- Patch to fix fd leak with kernel change notify. (38) (--Jeremy Allison)
+
+* Fri Oct 25 2002 Sylvestre Taburet 2.2.6-3mdk
+- Add URL to http://www.samba.org
+- Add --with-winbind-ldap-hack to remove the need to enable
+ pre-windows2000-compatible access for winbind.
+
+* Tue Oct 22 2002 Sylvestre Taburet 2.2.6-2mdk
+- Really switch back to std versioning.
+- samba-vscan v-0.2.5e
+
+* Fri Oct 18 2002 Sylvestre Taburet 2.2.6-1.3mdk
+- Clean-up patches.
+- Switch back to normal versioning.
+- added ISO8859-8 (Hebrew).
+
+* Fri Oct 18 2002 Sylvestre Taburet 2.2.6-1.2mdk
+- Birthday release ;o)
+- Added smbumount patch back (37).
+
+* Thu Oct 17 2002 Sylvestre Taburet 2.2.6-1.1mdk
+- New version: 2.2.6
+
+* Wed Oct 16 2002 Sylvestre Taburet 2.2.5-23mdk
+- Upgrade to 2.2.6rc4
+- 2.2.6-1.0.rc4.1mdk
+- remove patch 36.
+
+* Mon Oct 14 2002 Sylvestre Taburet 2.2.5-22mdk
+- Upgrade to 2.2.6rc3
+- 2.2.6-1.0.rc3.1mdk
+
* Thu Oct 10 2002 Buchan Milne 2.2.5-21mdk
- Put docs back (aka rpm sucks, builds cleanly when doc fails)
- 2.2.6-1.0.rc2.3mdk
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Mandrake/samba2.spec.tmpl samba-2.2.8/packaging/Mandrake/samba2.spec.tmpl
--- samba-2.2.7a/packaging/Mandrake/samba2.spec.tmpl Tue Dec 10 08:58:00 2002
+++ samba-2.2.8/packaging/Mandrake/samba2.spec.tmpl Fri Feb 28 09:56:06 2003
@@ -1,6 +1,6 @@
-%define ver 2.2.5
-%define rel 21mdk
-%define vscanver 0.2.5c
+%define ver 2.2.7a
+%define rel 4mdk
+%define vscanver 0.3.1
# 2.2.4 and 1 replace by samba-team at release
%define pversion PVERSION
@@ -33,6 +33,7 @@
# We now do detection of the Mandrake release we are building on:
#%define build_cooker %(if [ `awk '{print $3}' /etc/mandrake-release` = "Cooker" ];then echo 1; else echo 0; fi)
#%define build_cooker %(if [[ `cat /etc/mandrake-release|grep Cooker` ]];then echo 1; else echo 0; fi)
+%define build_mdk91 %(if [ `awk '{print $4}' /etc/mandrake-release` = 9.1 ];then echo 1; else echo 0; fi)
%define build_mdk90 %(if [ `awk '{print $4}' /etc/mandrake-release` = 9.0 ];then echo 1; else echo 0; fi)
%define build_mdk83 %(if [ `awk '{print $4}' /etc/mandrake-release` = 8.3 ];then echo 1; else echo 0; fi)
%define build_mdk82 %(if [ `awk '{print $4}' /etc/mandrake-release` = 8.2 ];then echo 1; else echo 0; fi)
@@ -41,12 +42,18 @@
%define build_mdk72 %(if [ `awk '{print $4}' /etc/mandrake-release` = 7.2 ];then echo 1; else echo 0; fi)
%define build_non_default 0
-%define build_acl 1
-%define build_winbind 1
-%define build_wins 1
-%define build_ldap 0
+# Default options
+%define build_acl 1
+%define build_winbind 1
+%define build_wins 1
+%define build_ldap 0
+%define build_scanners 0
# Set defaults for each version
+%if %build_mdk91
+%define build_ldap 0
+%endif
+
%if %build_mdk90
%define build_ldap 0
%endif
@@ -98,6 +105,8 @@
%{?_with_ldap: %{expand: %%define build_non_default 1}}
%{?_without_ldap: %{expand: %%global build_ldap 0}}
%{?_without_ldap: %{expand: %%define build_non_default 1}}
+%{?_with_scanners: %{expand: %%define build_scanners 1}}
+%{?_with_scanners: %{expand: %%define build_non_default 1}}
# As if that weren't enough, we're going to try building with antivirus
# support as an option also
@@ -108,17 +117,26 @@
%define build_sophos 0
%define build_symantec 0
%define build_trend 0
+%if %build_vscan && %build_scanners
+#These can be enabled here by default
+# (kaspersky requires their library present)
+%define build_fprot 1
+%define build_mks 1
+%define build_openantivirus 1
+%define build_sophos 1
+%define build_trend 1
+%endif
%if %build_vscan
%{?_with_fprot: %{expand: %%global build_fprot 1}}
%{?_with_kaspersky: %{expand: %%global build_kaspersky 1}}
%{?_with_mks: %{expand: %%global build_mks 1}}
%{?_with_openav: %{expand: %%global build_openantivirus 1}}
%{?_with_sophos: %{expand: %%global build_sophos 1}}
-%{?_with_symantec: %{expand: %%global build_symantec 1}}
+#%{?_with_symantec: %{expand: %%global build_symantec 1}}
%{?_with_trend: %{expand: %%global build_trend 1}}
-%define vscandir "samba-vscan-%{vscanver}"
+%global vscandir samba-vscan-%{vscanver}
%endif
-%define vfsdir "examples.bin/VFS"
+%global vfsdir examples.bin/VFS
#Workaround missing macros in 8.x:
%{!?perl_vendorlib: %{expand: %%global perl_vendorlib %{perl_sitearch}/../}}
@@ -147,6 +165,7 @@
Release: %{rel}
%endif
License: GPL
+URL: http://www.samba.org
Group: System/Servers
Source: ftp://samba.org/pub/samba/samba-%{source_ver}.tar.bz2
Source1: samba.log
@@ -161,35 +180,27 @@
%endif
Source10: samba-print-pdf.sh.bz2
Patch1: smbw.patch.bz2
-Patch5: samba-2.2.0-gawk.patch.bz2
-#Patch11: samba-2.0.7-smbspool-guest.patch.bz2
-Patch12: samba-2.2.0-buildroot.patch.bz2
-#Patch16: samba-mkdir.patch.bz2
-Patch17: smbmount-sbin.patch.bz2
-Patch18: samba-2.2.5-gp-reloc-fix.patch.bz2
+Patch2: samba-2.2.0-gawk.patch.bz2
+Patch3: samba-2.2.0-buildroot.patch.bz2
+Patch4: smbmount-sbin.patch.bz2
+Patch5: samba-2.2.5-gp-reloc-fix.patch.bz2
+Patch6: samba-2.2.7a-smbldaptools-paths.patch.bz2
%if !%have_pversion
# Version specific patches: current version
-Patch26: samba-2.2.5-smb.conf.patch.bz2
-Patch28: samba-2.2.5-ldap_start_tls.patch.bz2
-Patch29: samba-2.2.5-parse_sec.patch.bz2
-Patch30: samba-2.2.5-nt-dirlisting.patch.bz2
-Patch31: samba-2.2.5-random_smbd-read.patch.bz2
-Patch32: samba-2.2.5-winbind-init.patch.bz2
-Patch33: samba-2.2.5-pam-password.patch.bz2
-Patch34: samba-2.2.5-win2k_copy_bug.patch.bz2
-Patch35: samba-2.2.5-samba-ldap-include-conf.patch.bz2
-Patch36: samba-2.2.6-smb.conf.patch.bz2
-Patch37: samba-2.2.6-smbumount_lazy.patch.bz2
+Patch101: samba-2.2.7a-smbtar-large-file-fix.patch.bz2
+Patch102: samba-2.2.7a-smbclient-large-file-fix.patch.bz2
+Patch103: samba-2.2.7a-ldap-rebind.patch.bz2
+Patch104: samba-2.2.7a-mandrake-packaging.patch.bz2
+Patch105: samba-2.2.6-smbumount_lazy.patch.bz2
%else
# Version specific patches: upcoming version
%endif
# Limbo patches (applied to prereleases, but not preleases, ie destined for
# samba CVS)
%if %have_pversion && %have_pre
-Patch36: samba-2.2.6-smb.conf.patch.bz2
%endif
Requires: pam >= 0.64, samba-common = %{version}
-BuildRequires: pam-devel autoconf readline-devel
+BuildRequires: pam-devel autoconf readline-devel libldap2-devel popt-devel
%if %build_acl
BuildRequires: libacl-devel
%endif
@@ -198,9 +209,9 @@
%else
BuildRequires: libcups-devel
%endif
-%if %build_ldap
-BuildRequires: libldap-devel
-%endif
+#%if %build_ldap
+#BuildRequires: libldap-devel
+#%endif
BuildRoot: %{_tmppath}/%{name}-root
Prefix: /usr
Prereq: /sbin/chkconfig /bin/mktemp /usr/bin/killall
@@ -411,6 +422,7 @@
Summary: On-access virus scanning for samba using FPROT
Group: System/Servers
Requires: samba = %{version}
+Provides: samba-vscan
Autoreq: 0
%description vscan-fprot
A vfs-module for samba to implement on-access scanning using the
@@ -422,6 +434,7 @@
Summary: On-access virus scanning for samba using Kaspersky
Group: System/Servers
Requires: samba = %{version}
+Provides: samba-vscan
Autoreq: 0
%description vscan-kaspersky
A vfs-module for samba to implement on-access scanning using the
@@ -433,6 +446,7 @@
Summary: On-access virus scanning for samba using MKS
Group: System/Servers
Requires: samba = %{version}
+Provides: samba-vscan
Autoreq: 0
%description vscan-mks
A vfs-module for samba to implement on-access scanning using the
@@ -444,6 +458,7 @@
Summary: On-access virus scanning for samba using OpenAntivirus
Group: System/Servers
Requires: samba = %{version}
+Provides: samba-vscan
Autoreq: 0
%description vscan-openantivirus
A vfs-module for samba to implement on-access scanning using the
@@ -455,6 +470,7 @@
Summary: On-access virus scanning for samba using Sophos
Group: System/Servers
Requires: samba = %{version}
+Provides: samba-vscan
Autoreq: 0
%description vscan-sophos
A vfs-module for samba to implement on-access scanning using the
@@ -466,6 +482,7 @@
Summary: On-access virus scanning for samba using Symantec
Group: System/Servers
Requires: samba = %{version}
+Provides: samba-vscan
Autoreq: 0
%description vscan-symantec
A vfs-module for samba to implement on-access scanning using the
@@ -477,6 +494,7 @@
Summary: On-access virus scanning for samba using Trend
Group: System/Servers
Requires: samba = %{version}
+Provides: samba-vscan
Autoreq: 0
%description vscan-trend
A vfs-module for samba to implement on-access scanning using the
@@ -523,28 +541,26 @@
%else
%setup -q -n %{name}-%{source_ver}
%endif
-#%patch111 -p1
+# Current patches
+echo "Applying patches for version: %{ver}"
%patch1 -p1 -b .smbw
-%patch5 -p1 -b .gawk
-#%patch7 -p1
-#%patch11 -p0 -b .smbspool
-%patch12 -p1 -b .buildroot
-%patch17 -p1
-%patch18 -p1 -b .gp-reloc-fix
+%patch2 -p1 -b .gawk
+%patch3 -p1 -b .buildroot
+%patch4 -p1
+%patch5 -p1 -b .gp-reloc-fix
+%patch6 -p1
# Version specific patches: current version
%if !%have_pversion
echo "Applying patches for current version: %{ver}"
-%patch26 -p1 -b .mdk
-%patch28 -p1
-%patch29 -p1
-%patch30 -p1
-%patch31 -p1
-%patch32 -p1
-%patch33 -p1
-%patch34 -p1
-%patch35 -p1
-%patch36 -p1
-%patch37 -p1
+(cd source/client
+%patch101 -p0 -b .lfs
+)
+( cd source
+%patch102 -p0 -b .lfs
+)
+%patch103 -p1 -b .ldap
+%patch104 -p1 -b .mdk
+%patch105 -p1
%else
# Version specific patches: upcoming version
echo "Applying patches for new versions: %{pversion}"
@@ -553,7 +569,6 @@
# Limbo patches
%if %have_pversion && %have_pre
echo "Appling patches which should only be applied to prereleases"
-%patch36 -p1
%endif
cp %{SOURCE7} .
@@ -563,9 +578,12 @@
%if %build_vscan
# put antivirus files in examples.bin/VFS/
-for av in fprot kaspersky mks openantivirus sophos symantec trend; do
- cp -a %{vscandir}/$av %{vfsdir}
-done
+#for av in fprot kaspersky mks openantivirus sophos trend; do
+# [ -e %{vscandir}/$av ] && cp -a %{vscandir}/$av %{vfsdir}
+#done
+cp -a %{vscandir} %{vfsdir}
+#fix stupid directory names:
+mv %{vfsdir}/%{vscandir}/openantivirus %{vfsdir}/%{vscandir}/oav
%endif
%build
@@ -575,31 +593,34 @@
CPPFLAGS="-I/usr/include/openssl"; export CPPFLAGS
CFLAGS="$RPM_OPT_FLAGS"
%configure --prefix=%{prefix} \
- --with-fhs \
- --libdir=/etc/samba \
- --sysconfdir=/etc/samba \
- --localstatedir=/var \
- --with-configdir=/etc/samba \
- --with-codepagedir=/var/lib/samba/codepages \
- --with-privatedir=/etc/samba \
- --with-swatdir=%{prefix}/share/swat \
- --with-smbmount \
- --with-syslog \
- --with-automount \
- --with-pam \
- --with-pam_smbpass \
- --with-vfs \
- --with-utmp \
- --with-msdfs \
- --with-smbwrapper \
- --with-libsmbclient \
+ --with-fhs \
+ --libdir=/etc/samba \
+ --sysconfdir=/etc/samba \
+ --localstatedir=/var \
+ --with-configdir=/etc/samba \
+ --with-codepagedir=/var/lib/samba/codepages \
+ --with-privatedir=/etc/samba \
+ --with-swatdir=%{prefix}/share/swat \
+ --with-smbmount \
+ --with-syslog \
+ --with-automount \
+ --with-pam \
+ --with-sendfile-support \
+ --with-pam_smbpass \
+ --with-vfs \
+ --with-utmp \
+ --with-msdfs \
+ --with-smbwrapper \
+ --with-libsmbclient \
%if %build_acl
- --with-acl-support \
+ --with-acl-support \
%endif
%if %build_ldap
- --with-ldapsam \
+ --with-ldapsam \
+ --with-winbind-ldap-hack \
%endif
- --with-quotas
+ --with-winbind-auth-challenge \
+ --with-quotas
#make CFLAGS="$RPM_OPT_FLAGS -D_GNU_SOURCE" all
make CFLAGS="$RPM_OPT_FLAGS -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE" \
@@ -609,8 +630,6 @@
%configure --prefix=%{prefix} \
--mandir=%{prefix}/share/man
make
-#make CFLAGS="$RPM_OPT_FLAGS -I../../source -I../../source/include -I../../source/ubiqx \
-# -I../../source/smbwrapper -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE"
)
# Build mkntpasswd in examples/LDAP/ for smbldaptools
@@ -621,31 +640,33 @@
# Build antivirus vfs objects:
%if %build_fprot
+echo -e "\n\nBuild antivirus VFS modules\n\n"
echo "Building fprot"
+(cd %{vfsdir}/%{vscandir}/fprot;make)
%endif
%if %build_kaspersky
echo "Building Kaspersky"
-(cd %{vfsdir}/kaspersky;make)
+(cd %{vfsdir}/%{vscandir}/kaspersky;make)
%endif
%if %build_mks
echo "Building mks"
-(cd %{vfsdir}/mks;make)
+(cd %{vfsdir}/%{vscandir}/mks;make)
%endif
%if %build_openantivirus
echo "Building OpenAntivirus"
-(cd %{vfsdir}/openantivirus;make)
+(cd %{vfsdir}/%{vscandir}/oav;make)
%endif
%if %build_sophos
echo "building sophos"
-(cd %{vfsdir}/sophos;make)
+(cd %{vfsdir}/%{vscandir}/sophos;make)
%endif
%if %build_symantec
echo "Building symantec"
-(cd %{vfsdir}/symantec;make)
+(cd %{vfsdir}/%{vscandir}/symantec;make)
%endif
%if %build_trend
echo "Building Trend"
-(cd %{vfsdir}/trend;make)
+(cd %{vfsdir}/%{vscandir}/trend;make)
%endif
%install
@@ -694,10 +715,12 @@
# Antivirus support:
# mkdir -p $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan
- for av in fprotd kavp mksd oav sophos symantec trend; do
- if [ -d %{vfsdir}/$av -a -e %{vfsdir}/$av/vscan-$av.so ];then
- cp %{vfsdir}/$av/vscan-$av.so \
+ for av in fprot kavp mks oav sophos symantec trend; do
+ if [ -d %{vfsdir}/%{vscandir}/$av -a -e %{vfsdir}/%{vscandir}/$av/vscan-$av*.so ];then
+ cp %{vfsdir}/%{vscandir}/$av/vscan-$av*.so \
$RPM_BUILD_ROOT%{_libdir}/samba/vfs/
+ cp %{vfsdir}/%{vscandir}/$av/vscan-$av*.conf \
+ $RPM_BUILD_ROOT%{_sysconfdir}/%{name}
fi
done
@@ -729,7 +752,7 @@
install -m644 source/codepages/codepage_def.$i $RPM_BUILD_ROOT/var/lib/samba/codepages/src
done
-for i in 437 737 775 850 852 857 861 862 866 932 936 949 950 1125 1251 ISO8859-1 ISO8859-2 ISO8859-5 ISO8859-7 ISO8859-9 ISO8859-13 ISO8859-15 KOI8-R KOI8-U
+for i in 437 737 775 850 852 857 861 862 866 932 936 949 950 1125 1251 ISO8859-1 ISO8859-2 ISO8859-5 ISO8859-7 ISO8859-8 ISO8859-9 ISO8859-13 ISO8859-15 KOI8-R KOI8-U
do
install -m644 source/codepages/CP$i.TXT $RPM_BUILD_ROOT/var/lib/samba/codepages/src
done
@@ -740,7 +763,7 @@
done
# Build unicode load files
-for i in 437 737 775 850 852 857 861 862 866 932 936 949 950 1125 1251 ISO8859-1 ISO8859-2 ISO8859-5 ISO8859-7 ISO8859-9 ISO8859-13 ISO8859-15 KOI8-R KOI8-U; do
+for i in 437 737 775 850 852 857 861 862 866 932 936 949 950 1125 1251 ISO8859-1 ISO8859-2 ISO8859-5 ISO8859-7 ISO8859-8 ISO8859-9 ISO8859-13 ISO8859-15 KOI8-R KOI8-U; do
$RPM_BUILD_ROOT/%{prefix}/bin/make_unicodemap $i $RPM_BUILD_ROOT/var/lib/samba/codepages/src/CP$i.TXT $RPM_BUILD_ROOT/var/lib/samba/codepages/unicode_map.$i
done
rm -rf $RPM_BUILD_ROOT/var/lib/samba/codepages/src
@@ -785,7 +808,6 @@
install -m644 packaging/Mandrake/smb.conf $RPM_BUILD_ROOT/etc/samba/smb.conf
install -m644 packaging/Mandrake/smbusers $RPM_BUILD_ROOT/etc/samba/smbusers
install -m755 packaging/Mandrake/smbprint $RPM_BUILD_ROOT/usr/bin
- #install -m755 packaging/RedHat/smbadduser $RPM_BUILD_ROOT/usr/bin
install -m755 packaging/Mandrake/findsmb $RPM_BUILD_ROOT/usr/bin
install -m755 packaging/Mandrake/smb.init $RPM_BUILD_ROOT/etc/rc.d/init.d/smb
install -m755 packaging/Mandrake/smb.init $RPM_BUILD_ROOT/usr/sbin/samba
@@ -800,6 +822,7 @@
# Install smbldap-tools scripts:
for i in examples/LDAP/smbldap-tools/*.pl; do
install -m 750 $i $RPM_BUILD_ROOT/%{_datadir}/samba/scripts/
+ ln -s %{_datadir}/%{name}/scripts/`basename $i` $RPM_BUILD_ROOT/%{_bindir}/`basename $i|sed -e 's/\.pl//g'`
done
install -m 750 examples/LDAP/smbldap-tools/smbldap_tools.pm $RPM_BUILD_ROOT/%{_datadir}/samba/scripts/
@@ -860,6 +883,71 @@
bzcat %{SOURCE6} > $RPM_BUILD_ROOT%{_miconsdir}/swat.xpm
bzcat %{SOURCE10}> $RPM_BUILD_ROOT%{_datadir}/samba/scripts/print-pdf
+
+# Delete files which will not be included, so that /usr/lib/rpm/check-files
+# doesn't error out when Checking for unpackaged file(s)
+%if ! %build_ldap
+%endif
+
+%if ! %build_acl
+%endif
+
+%if ! %build_winbind
+rm -f $RPM_BUILD_ROOT%{_sbindir}/winbind
+rm -f $RPM_BUILD_ROOT%{_sbindir}/winbindd
+rm -f $RPM_BUILD_ROOT%{_bindir}/wbinfo
+rm -f $RPM_BUILD_ROOT/lib/security/pam_winbind*
+rm -f $RPM_BUILD_ROOT/lib/libnss_winbind*
+rm -f $RPM_BUILD_ROOT/etc/rc.d/init.d/winbind
+rm -f $RPM_BUILD_ROOT/etc/pam.d/system-auth-winbind
+rm -f $RPM_BUILD_ROOT%{_mandir}/man8/winbindd.8*
+rm -f $RPM_BUILD_ROOT%{_mandir}/man1/wbinfo.1*
+%endif
+
+%if ! %build_wins
+rm -f $RPM_BUILD_ROOT/lib/libnss_wins.so*
+%endif
+
+%ifarch alpha
+rm -f $RPM_BUILD_ROOT/sbin/mount.smb
+rm -f $RPM_BUILD_ROOT/sbin/mount.smbfs
+rm -f $RPM_BUILD_ROOT%{_bindir}/smbmount
+rm -f $RPM_BUILD_ROOT%{_bindir}/smbumount
+rm -f $RPM_BUILD_ROOT%{_sbindir}/smbmnt
+rm -f $RPM_BUILD_ROOT%{_mandir}/man8/smbmnt.8*
+rm -f $RPM_BUILD_ROOT%{_mandir}/man8/smbmount.8*
+rm -f $RPM_BUILD_ROOT%{_mandir}/man8/smbumount.8*
+%endif
+
+#Files for antivirus support:
+%if ! %build_fprot
+rm -f $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan-fprotd.so
+%endif
+
+%if ! %build_kaspersky
+rm -f $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan-kavp.so
+%endif
+
+%if ! %build_mks
+rm -f $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan-mksd.so
+%endif
+
+%if ! %build_openantivirus
+rm -f $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan-oav.so
+%endif
+
+%if ! %build_sophos
+rm -f $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan-sophos.so
+%endif
+
+%if ! %build_symantec
+rm -f $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan-symantec.so
+%endif
+
+%if ! %build_trend
+rm -f $RPM_BUILD_ROOT%{_libdir}/samba/vfs/vscan-trend.so
+%endif
+
%clean
rm -rf $RPM_BUILD_ROOT
@@ -1013,15 +1101,6 @@
if [ $1 = 0 ] ; then
%_preun_service smb
-# /sbin/chkconfig --level 35 smb reset
-# Let's not loose /var/cache/samba
-
-# for i in browse.dat wins.dat brlock.tdb unexpected.tdb connections.tdb \
-#locking.tdb messages.tdb;do
-# if [ -e /var/cache/samba/$i ]; then
-# mv -f /var/cache/samba/$i /var/cache/samba/$i.BAK
-# fi;
-# done
if [ -d /var/log/samba ]; then
rm -rf /var/log/samba/*
fi
@@ -1050,6 +1129,11 @@
%else
%post -n samba-swat
%endif
+# Change only_from entry in /etc/xinetd.d/swat (localhost bug)
+[[ `/bin/grep "localhost" /etc/xinetd.d/swat` ]] && {
+echo "-- Setting swat xinetd only_from entry to 127.0.0.1"
+perl -pi -e 's/localhost/127.0.0.1/' /etc/xinetd.d/swat
+}
if [ -f /var/lock/subsys/xinetd ]; then
service xinetd reload >/dev/null 2>&1 || :
fi
@@ -1100,7 +1184,6 @@
%{_bindir}/smbstatus
%{_bindir}/convert_smbpasswd
%attr(755,root,root) /lib/security/pam_smbpass*
-#/usr/share/swat
%attr(-,root,root) %config(noreplace) /etc/samba/smbusers
%attr(-,root,root) %config /etc/rc.d/init.d/smb
%attr(-,root,root) %config(noreplace) /etc/logrotate.d/samba
@@ -1113,10 +1196,9 @@
%{_mandir}/man8/nmbd.8*
%{_mandir}/man1/smbcontrol.1*
#%{_mandir}/man1/lmhosts.1*
-%{_mandir}/man5/smb.conf.5*
%attr(755,root,root) %dir /var/lib/samba/netlogon
%attr(775,root,users) %dir /var/lib/samba/profiles
-%attr(755,root,root) %dir /var/lib/samba/printers/*
+%attr(775,root,adm) %dir /var/lib/samba/printers/*
%attr(755,root,root) %dir %{_libdir}/samba/vfs
%attr(755,root,root) %{_libdir}/samba/vfs/audit.so
%attr(755,root,root) %{_libdir}/samba/vfs/block.so
@@ -1126,15 +1208,16 @@
%attr(1777,root,root) %dir /var/spool/samba
%dir %{_datadir}/%{name}/scripts
%attr(0755,root,root) %{_datadir}/%{name}/scripts/print-pdf
-%attr(0750,root,root) %{_datadir}/%{name}/scripts/smbldap*.pl
-%attr(0640,root,root) %config(noreplace) %{_sysconfdir}/%{name}/smbldap_conf.pm
+%attr(0750,root,adm) %{_datadir}/%{name}/scripts/smbldap*.pl
+%attr(0750,root,adm) %{_bindir}/smbldap*
+%attr(0640,root,adm) %config(noreplace) %{_sysconfdir}/%{name}/smbldap_conf.pm
%attr(0644,root,root) %{_datadir}/%{name}/scripts/smbldap_tools.pm
%{perl_vendorlib}/*.pm
%attr(0700,root,root) %{_datadir}/%{name}/scripts/*port_smbpasswd.pl
%files doc
-%defattr(-,root,root)
+%defattr(644,root,root,755)
%doc README COPYING Manifest Read-Manifest-Now
%doc WHATSNEW.txt Roadmap
%doc README.%{name}-mandrake-rpm
@@ -1180,11 +1263,12 @@
%{_bindir}/smbtar
%{_bindir}/smbspool
# Link of smbspool to CUPS
-/%{_libdir}/cups/backend/smb
-/%{_mandir}/man1/nmblookup.1*
-/%{_mandir}/man1/findsmb.1*
-/%{_mandir}/man1/smbclient.1*
-/%{_mandir}/man1/smbtar.1*
+%{_libdir}/cups/backend/smb
+%{_mandir}/man1/nmblookup.1*
+%{_mandir}/man1/findsmb.1*
+%{_mandir}/man1/smbclient.1*
+%{_mandir}/man1/smbtar.1*
+%{_mandir}/man8/smbspool.8*
%if %build_ldap
%files common-ldap
@@ -1204,6 +1288,8 @@
%{_bindir}/smbsh
%{_bindir}/smbpasswd
%{_bindir}/smbcacls
+%{_sbindir}/debug2html
+%{_sbindir}/smbfilter
%{_libdir}/smbwrapper.so
%{_libdir}/libsmbclient.so
%attr(-,root,root) %config(noreplace) /etc/samba/smb.conf
@@ -1218,7 +1304,9 @@
%{_mandir}/man5/smb.conf.5*
%{_mandir}/man5/lmhosts.5*
%{_mandir}/man8/smbpasswd.8*
-/%{_mandir}/man1/smbcacls.1*
+%{_mandir}/man1/smbcacls.1*
+%{_mandir}/man1/rpcclient.1*
+%{_mandir}/man8/pdbedit.8*
#%if %build_winbind
#%if %build_ldap
@@ -1232,6 +1320,7 @@
%if %build_winbind
%defattr(-,root,root)
%{_sbindir}/winbindd
+%{_sbindir}/winbind
%{_bindir}/wbinfo
%attr(755,root,root) /lib/security/pam_winbind*
%attr(755,root,root) /lib/libnss_winbind*
@@ -1252,52 +1341,155 @@
%files vscan-fprot
%defattr(-,root,root)
%{_libdir}/samba/vfs/vscan-fprotd.so
-%doc examples.bin/VFS/fprot/INSTALL
+%config(noreplace) %{_sysconfdir}/%{name}/vscan-fprotd.conf
+%doc %{vfsdir}/%{vscandir}/INSTALL
%endif
%if %build_kaspersky
%files vscan-kaspersky
%defattr(-,root,root)
%{_libdir}/samba/vfs/vscan-kavp.so
-%doc examples.bin/VFS/kaspersky/INSTALL
+%config(noreplace) %{_sysconfdir}/%{name}/vscan-kavp.conf
+%doc %{vfsdir}/%{vscandir}/examples.bin/VFS/kaspersky/INSTALL
%endif
%if %build_mks
%files vscan-mks
%defattr(-,root,root)
%{_libdir}/samba/vfs/vscan-mksd.so
-%doc examples.bin/VFS/mks/INSTALL
+%config(noreplace) %{_sysconfdir}/%{name}/vscan-mks*.conf
+%doc %{vfsdir}/%{vscandir}/INSTALL
%endif
%if %build_openantivirus
%files vscan-openantivirus
%defattr(-,root,root)
%{_libdir}/samba/vfs/vscan-oav.so
-%doc examples.bin/VFS/openantivirus/INSTALL
+%config(noreplace) %{_sysconfdir}/%{name}/vscan-oav.conf
+%doc %{vfsdir}/%{vscandir}/INSTALL
%endif
%if %build_sophos
%files vscan-sophos
%defattr(-,root,root)
%{_libdir}/samba/vfs/vscan-sophos.so
-%doc examples.bin/VFS/sophos/INSTALL
+%config(noreplace) %{_sysconfdir}/%{name}/vscan-sophos.conf
+%doc %{vfsdir}/%{vscandir}/INSTALL
%endif
%if %build_symantec
%files vscan-symantec
%defattr(-,root,root)
%{_libdir}/samba/vfs/vscan-symantec.so
-%doc examples.bin/VFS/symantec/INSTALL
+%config(noreplace) %{_sysconfdir}/%{name}/vscan-symantec.conf
+%doc %{vfsdir}/%{vscandir}/INSTALL
%endif
%if %build_trend
%files vscan-trend
%defattr(-,root,root)
%{_libdir}/samba/vfs/vscan-trend.so
-%doc examples.bin/VFS/trend/INSTALL
+%config(noreplace) %{_sysconfdir}/%{name}/vscan-trend.conf
+%doc %{vfsdir}/%{vscandir}/INSTALL
%endif
%changelog
+* Fri Feb 14 2003 Buchan Milne 2.2.7a-4mdk
+- Fix build openantivirus with default scanners
+- buildrequire popt-devel
+- From Jim Collings
+ - Patched smbldap-tools and created links to same in /usr/bin
+
+* Thu Jan 23 2003 Buchan Milne 2.2.7a-3mdk
+- Two patches to fix large file support (smbtar:p101 and smbclient:p102)
+- Patch to enable ldap referral (103)
+- Build all vscan except kav (requires kaspersky lib) with --with-scanners
+- Allow adm group to install printer drivers and use smbldaptools by default
+- Remove smb.conf man page conflict
+
+* Thu Jan 02 2003 Sylvestre Taburet 2.2.7a-2mdk
+- Rebuilt because of new rpm macros and new glibc.
+- Happy new year 2003 to all samba developers, contributors and users!
+
+* Wed Dec 11 2002 Sylvestre Taburet 2.2.7a-1mdk
+- Upgraded to 2.2.7a.
+
+* Sun Dec 08 2002 Buchan Milne 2.2.7-5mdk
+- samba-vscan 0.3.1 (and make it build again)
+- Make all vscan packages provide samba-vscan
+- All scanner packages (besides kaspersky) can be built without the
+ scanner installed, but we don't quite to this yet ...
+- Add vscan-(scanner).conf files
+- Add winbind-auth-challenge to configure, for squid support
+- Use winbind-ldap-hack only when building with ldapsam support
+ since no-one has been able to test this thoroughly, and my only
+ tests indicated performance problems with it (and I need this RPM to
+ work for squid)
+
+* Tue Nov 26 2002 Sylvestre Taburet 2.2.7-4mdk
+- Fix perms on doc.
+- Cleaned up specfile a bit.
+- Added support for upcoming Mandrake Linux 9.1 in auto build process.
+
+* Tue Nov 26 2002 Sylvestre Taburet 2.2.7-3mdk
+- Put (noreplace) back in %files swat.
+- Changed only_from entry in sample swat to "127.0.0.1".
+- Change only_from entry in /etc/xinetd.d/swat to "127.0.0.1" on %post swat.
+
+* Fri Nov 22 2002 Sylvestre Taburet 2.2.7-2mdk
+- Removed noreplace of /etc/xinetd.d/swat on update.
+- Updated samba-vscan (0.3.0).
+
+* Wed Nov 20 2002 Sylvestre Taburet 2.2.7-1mdk
+- Update to 2.2.7.
+- Removed patch 38.
+
+* Sat Nov 16 2002 Alexander Skwar 2.2.6-6mdk
+- Remove installed files which will not be included due to build options,
+ so that /usr/lib/rpm/check-files doesn't error out when
+ Checking for unpackaged file(s)
+- Add debug2html, smbfilter to common package
+- Add /usr/sbin/winbind to winbind package
+- Add rpcclient manpage to common package
+- Add smbspool, pdbedit manpage to client package
+
+* Wed Nov 06 2002 Sylvestre Taburet 2.2.6-5mdk
+- add winbind ldap hack again, with proper build-require (libldap2-devel)
+- enable --with-sendfile-support (default in 3.0. Increases performance).
+
+* Wed Oct 30 2002 Sylvestre Taburet 2.2.6-4mdk
+- Patch to fix fd leak with kernel change notify. (38) (--Jeremy Allison)
+
+* Fri Oct 25 2002 Sylvestre Taburet 2.2.6-3mdk
+- Add URL to http://www.samba.org
+- Add --with-winbind-ldap-hack to remove the need to enable
+ pre-windows2000-compatible access for winbind.
+
+* Tue Oct 22 2002 Sylvestre Taburet 2.2.6-2mdk
+- Really switch back to std versioning.
+- samba-vscan v-0.2.5e
+
+* Fri Oct 18 2002 Sylvestre Taburet 2.2.6-1.3mdk
+- Clean-up patches.
+- Switch back to normal versioning.
+- added ISO8859-8 (Hebrew).
+
+* Fri Oct 18 2002 Sylvestre Taburet 2.2.6-1.2mdk
+- Birthday release ;o)
+- Added smbumount patch back (37).
+
+* Thu Oct 17 2002 Sylvestre Taburet 2.2.6-1.1mdk
+- New version: 2.2.6
+
+* Wed Oct 16 2002 Sylvestre Taburet 2.2.5-23mdk
+- Upgrade to 2.2.6rc4
+- 2.2.6-1.0.rc4.1mdk
+- remove patch 36.
+
+* Mon Oct 14 2002 Sylvestre Taburet 2.2.5-22mdk
+- Upgrade to 2.2.6rc3
+- 2.2.6-1.0.rc3.1mdk
+
* Thu Oct 10 2002 Buchan Milne 2.2.5-21mdk
- Put docs back (aka rpm sucks, builds cleanly when doc fails)
- 2.2.6-1.0.rc2.3mdk
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/Mandrake/smb.conf samba-2.2.8/packaging/Mandrake/smb.conf
--- samba-2.2.7a/packaging/Mandrake/smb.conf Tue Dec 10 08:58:00 2002
+++ samba-2.2.8/packaging/Mandrake/smb.conf Fri Feb 28 09:56:06 2003
@@ -77,6 +77,8 @@
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
+# Allow users to map to guest:
+ map to guest = bad user
# Security mode. Most people will want user level security. See
# security_level.txt for details.
@@ -227,7 +229,7 @@
# Domain groups:
# domain admin group is a list of unix users or groups who are made members
# of the Domain Admin group
-; domain admin group = root @wheel
+; domain admin group = root @adm
#
# domain guest groups is a list of unix users or groups who are made members
# of the Domain Guests group
@@ -313,6 +315,8 @@
# examples/VFS/recycle/REAME in samba-doc for details
; vfs object = /usr/lib/samba/vfs/recycle.so
; vfs options= /etc/samba/recycle.conf
+# You may want to prevent abuse of your server disk space, and spread of virii
+; veto files = /*.eml/*.nws/*.dll/*.mp3/*.MP3/*.mpg/*.MPG/*.vbs/*.VBS/
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
@@ -338,7 +342,7 @@
# You may want to turn off guest acces if you enable this, as it
# hasn't been thoroughly tested.
; root preexec = PROFILE=/var/lib/samba/profiles/%u; if [ ! -e $PROFILE ]; \
-; then mkdir -pm700 $PROFILE; chown %u $PROFILE;fi
+; then mkdir -pm700 $PROFILE; chown %u.%g $PROFILE;fi
# NOTE: If you have a CUPS print system there is no need to
@@ -388,8 +392,8 @@
guest ok = No
printable = Yes
comment = PDF Generator (only valid users)
- #print command = /usr/share/samba/scripts/print-pdf file path win_path recipient IP &
- print command = /usr/share/samba/scripts/print-pdf %s ~%u \\\\\\\\%L\\\\%u %m %I &
+ #print command = /usr/share/samba/scripts/print-pdf file path win_path recipient IP doc_name &
+ print command = /usr/share/samba/scripts/print-pdf %s ~%u //%L/%u %m %I "%J" &
# This one is useful for people to share files
;[tmp]
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/PHT/TurboLinux/makerpms.sh samba-2.2.8/packaging/PHT/TurboLinux/makerpms.sh
--- samba-2.2.7a/packaging/PHT/TurboLinux/makerpms.sh Wed Dec 11 09:34:35 2002
+++ samba-2.2.8/packaging/PHT/TurboLinux/makerpms.sh Fri Mar 14 22:47:05 2003
@@ -6,8 +6,8 @@
USERID=`id -u`
GRPID=`id -g`
-( cd ../../../.. ; chown -R ${USERID}.${GRPID} ${SRCDIR}/samba-2.2.7a )
-( cd ../../../.. ; tar czvf ${SRCDIR}/samba-2.2.7a.tar.gz samba-2.2.7a )
+( cd ../../../.. ; chown -R ${USERID}.${GRPID} ${SRCDIR}/samba-2.2.8 )
+( cd ../../../.. ; tar czvf ${SRCDIR}/samba-2.2.8.tar.gz samba-2.2.8 )
cp -a *.spec $SPECDIR
cp -a *.patch smb.* samba.log $SRCDIR
cd $SPECDIR
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/PHT/TurboLinux/samba2.spec samba-2.2.8/packaging/PHT/TurboLinux/samba2.spec
--- samba-2.2.7a/packaging/PHT/TurboLinux/samba2.spec Wed Dec 11 09:34:35 2002
+++ samba-2.2.8/packaging/PHT/TurboLinux/samba2.spec Fri Mar 14 22:47:05 2003
@@ -1,10 +1,10 @@
Summary: Samba SMB client and server
Name: samba
-Version: 2.2.7a
+Version: 2.2.8
Release: 1
Copyright: GNU GPL version 2
Group: Networking
-Source: ftp://samba.org/pub/samba/samba-2.2.7a.tar.gz
+Source: ftp://samba.org/pub/samba/samba-2.2.8.tar.gz
Patch: smbw.patch
Requires: pam >= 0.64 kernel >= 2.2.1 glibc >= 2.1.2
Prereq: chkconfig fileutils
@@ -12,7 +12,7 @@
Prefix: /usr
%package -n smbfs
-Version: 2.2.7a
+Version: 2.2.8
Release: 1
Group: Utilities/File
Summary: Programs to mount SMB shares.
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/RedHat/makerpms.sh samba-2.2.8/packaging/RedHat/makerpms.sh
--- samba-2.2.7a/packaging/RedHat/makerpms.sh Wed Dec 11 09:34:35 2002
+++ samba-2.2.8/packaging/RedHat/makerpms.sh Fri Mar 14 22:47:05 2003
@@ -12,9 +12,9 @@
# Note: Under this directory rpm expects to find the same directories that are under the
# /usr/src/redhat directory
#
-if [ -x ~/.rpmmacros ]; then
+if [ -r ~/.rpmmacros ]; then
TOPDIR=`awk '/topdir/ {print $2}' < ~/.rpmmacros`
- if [ z$TOPDIR <> "z" ]; then
+ if [ z$TOPDIR != "z" ]; then
SPECDIR=${TOPDIR}/SPECS
SRCDIR=${TOPDIR}/SOURCES
fi
@@ -27,7 +27,7 @@
USERID=`id -u`
GRPID=`id -g`
-VERSION='2.2.7a'
+VERSION='2.2.8'
RPMVER=`rpm --version | awk '{print $3}'`
RPM="rpm"
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/RedHat/makerpms.sh.tmpl samba-2.2.8/packaging/RedHat/makerpms.sh.tmpl
--- samba-2.2.7a/packaging/RedHat/makerpms.sh.tmpl Tue Dec 10 08:58:00 2002
+++ samba-2.2.8/packaging/RedHat/makerpms.sh.tmpl Wed Feb 5 10:25:21 2003
@@ -12,9 +12,9 @@
# Note: Under this directory rpm expects to find the same directories that are under the
# /usr/src/redhat directory
#
-if [ -x ~/.rpmmacros ]; then
+if [ -r ~/.rpmmacros ]; then
TOPDIR=`awk '/topdir/ {print $2}' < ~/.rpmmacros`
- if [ z$TOPDIR <> "z" ]; then
+ if [ z$TOPDIR != "z" ]; then
SPECDIR=${TOPDIR}/SPECS
SRCDIR=${TOPDIR}/SOURCES
fi
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/RedHat/samba2-devel.spec samba-2.2.8/packaging/RedHat/samba2-devel.spec
--- samba-2.2.7a/packaging/RedHat/samba2-devel.spec Wed Dec 11 09:34:35 2002
+++ samba-2.2.8/packaging/RedHat/samba2-devel.spec Fri Mar 14 22:47:05 2003
@@ -1,6 +1,6 @@
Summary: Samba SMB client and server
Name: samba
-Version: 2.2.7a
+Version: 2.2.8
Release: 1
Copyright: GNU GPL version 2
Group: Networking
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/RedHat/samba2.spec samba-2.2.8/packaging/RedHat/samba2.spec
--- samba-2.2.7a/packaging/RedHat/samba2.spec Wed Dec 11 09:34:35 2002
+++ samba-2.2.8/packaging/RedHat/samba2.spec Fri Mar 14 22:47:05 2003
@@ -1,14 +1,15 @@
Summary: Samba SMB client and server
Name: samba
-Version: 2.2.7a
+Version: 2.2.8
Release: 1
Copyright: GNU GPL version 2
Group: Networking
Source: http://download.samba.org/samba/ftp/samba-%{version}.tar.bz2
-Packager: John H Terpstra [Samba-Team]
+Packager: Gerald Carter [Samba-Team]
Requires: pam >= 0.72 kernel >= 2.2.1 glibc >= 2.1.2
Prereq: chkconfig fileutils
Provides: samba = %{version}
+BuildPreReq: libtool
Obsoletes: samba-common, samba-client, samba-swat
BuildRoot: /var/tmp/samba
Prefix: /usr
@@ -318,6 +319,9 @@
install -m644 packaging/RedHat/samba.xinetd $RPM_BUILD_ROOT/etc/samba/samba.xinetd
echo 127.0.0.1 localhost > $RPM_BUILD_ROOT/etc/samba/lmhosts
+# Remove "*.old" files
+find $RPM_BUILD_ROOT -name "*.old" -exec rm -f {} \;
+
%clean
rm -rf $RPM_BUILD_ROOT
@@ -504,10 +508,10 @@
fi
fi
-%triggerpostun -- samba < samba-2.0.0
-if [ $0 != 0 ]; then
- /sbin/chkconfig --add smb
-fi
+#%triggerpostun -- samba < samba-2.0.0
+#if [ $0 != 0 ]; then
+# /sbin/chkconfig --add smb
+#fi
%files
%defattr(-,root,root)
@@ -523,6 +527,8 @@
%{prefix}/sbin/smbmount
%{prefix}/sbin/smbumount
%{prefix}/sbin/winbindd
+%{prefix}/sbin/debug2html
+%{prefix}/sbin/samba
/sbin/mount.smbfs
/sbin/mount.smb
%{prefix}/bin/mksmbpasswd.sh
@@ -543,6 +549,10 @@
%{prefix}/bin/smbcontrol
%{prefix}/bin/smbcacls
%{prefix}/bin/wbinfo
+%{prefix}/bin/pam_smbpass.so
+%{prefix}/bin/smbmount
+%{prefix}/bin/smbumount
+%{prefix}/bin/tdbbackup
%attr(755,root,root) /lib/libnss_wins.s*
%attr(755,root,root) %{prefix}/lib/samba/vfs/*.so
%{prefix}/include/libsmbclient.h
@@ -553,6 +563,7 @@
%{prefix}/share/swat/include/header.html
%{prefix}/share/swat/include/footer.html
%{prefix}/share/swat/using_samba/*
+%{prefix}/share/swat/README
%config(noreplace) /etc/samba/lmhosts
%config(noreplace) /etc/samba/smb.conf
%config(noreplace) /etc/samba/recycle.conf
@@ -569,6 +580,7 @@
MANDIR_MACRO/man7/*
MANDIR_MACRO/man8/*
%dir /etc/codepages/*
+%dir /etc/codepages/src/*
%attr(755,root,root) %dir /var/cache/samba
%dir /var/log/samba
%dir /var/run/samba
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/RedHat/samba2.spec.tmpl samba-2.2.8/packaging/RedHat/samba2.spec.tmpl
--- samba-2.2.7a/packaging/RedHat/samba2.spec.tmpl Wed Dec 4 11:16:12 2002
+++ samba-2.2.8/packaging/RedHat/samba2.spec.tmpl Fri Mar 14 15:34:47 2003
@@ -5,10 +5,11 @@
Copyright: GNU GPL version 2
Group: Networking
Source: http://download.samba.org/samba/ftp/samba-%{version}.tar.bz2
-Packager: John H Terpstra [Samba-Team]
+Packager: Gerald Carter [Samba-Team]
Requires: pam >= 0.72 kernel >= 2.2.1 glibc >= 2.1.2
Prereq: chkconfig fileutils
Provides: samba = %{version}
+BuildPreReq: libtool
Obsoletes: samba-common, samba-client, samba-swat
BuildRoot: /var/tmp/samba
Prefix: /usr
@@ -318,6 +319,9 @@
install -m644 packaging/RedHat/samba.xinetd $RPM_BUILD_ROOT/etc/samba/samba.xinetd
echo 127.0.0.1 localhost > $RPM_BUILD_ROOT/etc/samba/lmhosts
+# Remove "*.old" files
+find $RPM_BUILD_ROOT -name "*.old" -exec rm -f {} \;
+
%clean
rm -rf $RPM_BUILD_ROOT
@@ -504,10 +508,10 @@
fi
fi
-%triggerpostun -- samba < samba-2.0.0
-if [ $0 != 0 ]; then
- /sbin/chkconfig --add smb
-fi
+#%triggerpostun -- samba < samba-2.0.0
+#if [ $0 != 0 ]; then
+# /sbin/chkconfig --add smb
+#fi
%files
%defattr(-,root,root)
@@ -523,6 +527,8 @@
%{prefix}/sbin/smbmount
%{prefix}/sbin/smbumount
%{prefix}/sbin/winbindd
+%{prefix}/sbin/debug2html
+%{prefix}/sbin/samba
/sbin/mount.smbfs
/sbin/mount.smb
%{prefix}/bin/mksmbpasswd.sh
@@ -543,6 +549,10 @@
%{prefix}/bin/smbcontrol
%{prefix}/bin/smbcacls
%{prefix}/bin/wbinfo
+%{prefix}/bin/pam_smbpass.so
+%{prefix}/bin/smbmount
+%{prefix}/bin/smbumount
+%{prefix}/bin/tdbbackup
%attr(755,root,root) /lib/libnss_wins.s*
%attr(755,root,root) %{prefix}/lib/samba/vfs/*.so
%{prefix}/include/libsmbclient.h
@@ -553,6 +563,7 @@
%{prefix}/share/swat/include/header.html
%{prefix}/share/swat/include/footer.html
%{prefix}/share/swat/using_samba/*
+%{prefix}/share/swat/README
%config(noreplace) /etc/samba/lmhosts
%config(noreplace) /etc/samba/smb.conf
%config(noreplace) /etc/samba/recycle.conf
@@ -569,6 +580,7 @@
MANDIR_MACRO/man7/*
MANDIR_MACRO/man8/*
%dir /etc/codepages/*
+%dir /etc/codepages/src/*
%attr(755,root,root) %dir /var/cache/samba
%dir /var/log/samba
%dir /var/run/samba
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/SGI/idb.pl samba-2.2.8/packaging/SGI/idb.pl
--- samba-2.2.7a/packaging/SGI/idb.pl Fri May 31 17:07:35 2002
+++ samba-2.2.8/packaging/SGI/idb.pl Fri Feb 28 09:56:06 2003
@@ -111,7 +111,7 @@
chdir $curdir;
# add my local files to the list of binaries to install
-@bins = sort byfilename (@sprogs,@progs,@progs1,@progs2,@mprogs,@scripts,@winbind_progs,@winbind_sprogs,("/sambalp","/smbprint"));
+@bins = sort byfilename (@sprogs,@progs,@progs1,@progs2,@mprogs,@scripts,@winbind_progs,@winbind_sprogs,("/sambalp","/smbprint","bin/pdbedit","bin/tdbdump"));
@nsswitch = sort byfilename (@winbind_lprogs,@winbind_pam_progs);
@@ -154,10 +154,10 @@
print IDB "f 0644 root sys usr/lib32/samba/libsmbclient.so $SRCPFX/source/bin/libsmbclient.so $PKG.sw.base\n";
print IDB "d 0755 root sys usr/relnotes/samba_irix $SRCPFX/packaging/SGI $PKG.man.relnotes\n";
- print IDB "f 0644 root sys usr/relnotes/samba_irix/TC build/TC $PKG.man.relnotes\n";
- print IDB "f 0644 root sys usr/relnotes/samba_irix/ch1.z build/ch1.z $PKG.man.relnotes\n";
- print IDB "f 0644 root sys usr/relnotes/samba_irix/ch2.z build/ch2.z $PKG.man.relnotes\n";
- print IDB "f 0644 root sys usr/relnotes/samba_irix/ch3.z build/ch3.z $PKG.man.relnotes\n";
+ print IDB "f 0644 root sys usr/relnotes/samba_irix/TC relnotes/TC $PKG.man.relnotes\n";
+ print IDB "f 0644 root sys usr/relnotes/samba_irix/ch1.z relnotes/ch1.z $PKG.man.relnotes\n";
+ print IDB "f 0644 root sys usr/relnotes/samba_irix/ch2.z relnotes/ch2.z $PKG.man.relnotes\n";
+ print IDB "f 0644 root sys usr/relnotes/samba_irix/ch3.z relnotes/ch3.z $PKG.man.relnotes\n";
}
else {
@copyfile = grep (/^COPY/,@allfiles);
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/SGI/mkrelease.sh samba-2.2.8/packaging/SGI/mkrelease.sh
--- samba-2.2.7a/packaging/SGI/mkrelease.sh Tue Apr 30 08:25:22 2002
+++ samba-2.2.8/packaging/SGI/mkrelease.sh Fri Feb 28 09:56:06 2003
@@ -87,7 +87,7 @@
mv bin/smbd bin/smbd.noquota
echo "===================== Making Regular versions ======================="
-make -P "CFLAGS=-O -g3 -woff 1188" all libsmbclient
+make -P "CFLAGS=-O -g3 -woff 1188" all libsmbclient bin/libsmbclient.so bin/pdbedit bin/tdbdump
errstat=$?
if [ $errstat -ne 0 ]; then
echo "Error $errstat building sources\n";
diff -u -r --new-file --exclude=CVS samba-2.2.7a/packaging/SGI/samba.rc samba-2.2.8/packaging/SGI/samba.rc
--- samba-2.2.7a/packaging/SGI/samba.rc Tue Apr 30 08:25:23 2002
+++ samba-2.2.8/packaging/SGI/samba.rc Fri Mar 14 15:34:47 2003
@@ -17,7 +17,7 @@
nmbd_group=`cat /usr/samba/var/locks/nmbd.pid`
ps -p $nmbd_group | grep nmbd > /dev/null
if [ $? -eq 0 ]; then
- /usr/bin/kill -15 -$nmbd_group
+ /usr/bin/kill -15 $nmbd_group
fi
fi
}
diff -u -r --new-file --exclude=CVS samba-2.2.7a/source/Doxyfile samba-2.2.8/source/Doxyfile
--- samba-2.2.7a/source/Doxyfile Fri Feb 1 16:21:38 2002
+++ samba-2.2.8/source/Doxyfile Fri Feb 28 09:56:06 2003
@@ -5,7 +5,15 @@
#---------------------------------------------------------------------------
PROJECT_NAME = Samba
PROJECT_NUMBER = HEAD
+
+# NOTE: By default, Doxygen writes into the dox/ subdirectory of the
+# invocation directory. If you want to put it somewhere else, for
+# example, to write straight into a webserver directory, then override
+# this variable in a configuration concatenated to this one: Doxygen
+# doesn't mind variables being redefined.
+
OUTPUT_DIRECTORY = dox
+
OUTPUT_LANGUAGE = English
EXTRACT_ALL = YES
EXTRACT_PRIVATE = YES
@@ -15,8 +23,8 @@
BRIEF_MEMBER_DESC = YES
REPEAT_BRIEF = YES
ALWAYS_DETAILED_SEC = NO
-FULL_PATH_NAMES = NO
-STRIP_FROM_PATH = *source
+FULL_PATH_NAMES = YES
+STRIP_FROM_PATH = $(PWD)/
INTERNAL_DOCS = YES
CLASS_DIAGRAMS = YES
SOURCE_BROWSER = YES
@@ -41,10 +49,11 @@
MAX_INITIALIZER_LINES = 30
OPTIMIZE_OUTPUT_FOR_C = YES
SHOW_USED_FILES = YES
+REFERENCED_BY_RELATION = YES
#---------------------------------------------------------------------------
# configuration options related to warning and progress messages
#---------------------------------------------------------------------------
-QUIET = NO
+QUIET = YES
WARNINGS = NO
WARN_IF_UNDOCUMENTED = NO
WARN_FORMAT = "$file:$line: $text"
@@ -52,7 +61,7 @@
#---------------------------------------------------------------------------
# configuration options related to the input files
#---------------------------------------------------------------------------
-INPUT = .
+INPUT = .
FILE_PATTERNS = *.c \
*.h \
*.idl
@@ -75,11 +84,11 @@
# configuration options related to the HTML output
#---------------------------------------------------------------------------
GENERATE_HTML = YES
-HTML_OUTPUT = html
+HTML_OUTPUT = .
HTML_HEADER =
HTML_FOOTER =
HTML_STYLESHEET =
-HTML_ALIGN_MEMBERS = NO
+HTML_ALIGN_MEMBERS = YES
GENERATE_HTMLHELP = NO
GENERATE_CHI = NO
BINARY_TOC = NO
@@ -121,9 +130,9 @@
#---------------------------------------------------------------------------
GENERATE_XML = NO
#---------------------------------------------------------------------------
-# Configuration options related to the preprocessor
+# configuration options related to the preprocessor
#---------------------------------------------------------------------------
-ENABLE_PREPROCESSING = YES
+ENABLE_PREPROCESSING = NO
MACRO_EXPANSION = NO
EXPAND_ONLY_PREDEF = NO
SEARCH_INCLUDES = YES
@@ -133,16 +142,16 @@
EXPAND_AS_DEFINED =
SKIP_FUNCTION_MACROS = YES
#---------------------------------------------------------------------------
-# Configuration::addtions related to external references
+# configuration::additions related to external references
#---------------------------------------------------------------------------
TAGFILES =
GENERATE_TAGFILE =
ALLEXTERNALS = NO
PERL_PATH = /usr/bin/perl
#---------------------------------------------------------------------------
-# Configuration options related to the dot tool
+# configuration options related to the dot tool
#---------------------------------------------------------------------------
-HAVE_DOT = YES
+HAVE_DOT = NO
CLASS_GRAPH = YES
COLLABORATION_GRAPH = YES
TEMPLATE_RELATIONS = YES
@@ -156,7 +165,7 @@
GENERATE_LEGEND = YES
DOT_CLEANUP = YES
#---------------------------------------------------------------------------
-# Configuration::addtions related to the search engine
+# configuration::additions related to the search engine
#---------------------------------------------------------------------------
SEARCHENGINE = NO
CGI_NAME = search.cgi
diff -u -r --new-file --exclude=CVS samba-2.2.7a/source/Makefile.in samba-2.2.8/source/Makefile.in
--- samba-2.2.7a/source/Makefile.in Tue Dec 10 08:58:00 2002
+++ samba-2.2.8/source/Makefile.in Fri Feb 28 09:56:06 2003
@@ -24,6 +24,8 @@
LINK=$(CC) $(FLAGS) $(LDFLAGS)
INSTALLCMD=@INSTALL@
+INSTALLCLIENTCMD_SH=@INSTALLCLIENTCMD_SH@
+INSTALLCLIENTCMD_A=@INSTALLCLIENTCMD_A@
VPATH=@srcdir@
srcdir=@srcdir@
@@ -101,7 +103,7 @@
LPROGS = $(WINBIND_PAM_PROGS) $(WINBIND_LPROGS)
PROGS = $(PROGS1) $(PROGS2) $(MPROGS) bin/nmblookup
TORTURE_PROGS = bin/smbtorture bin/msgtest bin/masktest bin/locktest bin/locktest2
-SHLIBS = libsmbclient
+SHLIBS = @LIBSMBCLIENT@
SCRIPTS = $(srcdir)/script/smbtar $(srcdir)/script/findsmb
@@ -400,7 +402,7 @@
WINBINDD_OBJ = \
$(WINBINDD_OBJ1) $(NOPROTO_OBJ) $(PASSDB_OBJ) \
- $(LIBNMB_OBJ) $(PARAM_OBJ) $(UBIQX_OBJ) $(LIB_OBJ) \
+ $(PARAM_OBJ) $(UBIQX_OBJ) $(LIB_OBJ) \
$(LIBSMB_OBJ) $(LIBMSRPC_OBJ) $(RPC_PARSE_OBJ) \
$(GROUPDB_OBJ) $(PROFILE_OBJ) \
$(NECESSARY_BECAUSE_SAMBA_DEPENDENCIES_ARE_SO_BROKEN_OBJ)
@@ -426,13 +428,13 @@
all : CHECK $(SPROGS) $(PROGS) $(WINBIND_PROGS) $(WINBIND_SPROGS) $(LPROGS)
# The following "everything" is NOT needed except by Samba developers - so do not use this!
-everything : CHECK $(SPROGS) $(PROGS) $(SHLIBS) nsswitch smbwrapper smbtorture debug2html smbfilter nsswitch/libnss_wins.so
+everything : CHECK $(SPROGS) $(PROGS) $(SHLIBS) nsswitch smbwrapper smbtorture debug2html smbfilter
pam_smbpass : CHECK bin/pam_smbpass.@SHLIBEXT@
smbwrapper : CHECK @WRAPPROG@ @WRAP@ @WRAP32@
-libsmbclient : CHECK bin/libsmbclient.@SHLIBEXT@ bin/libsmbclient.a
+libsmbclient : CHECK bin/libsmbclient.a @LIBSMBCLIENT_SHARED@
torture : CHECK $(TORTURE_PROGS)
@@ -460,6 +462,8 @@
nsswitch : CHECK $(WINBIND_PROGS) $(WINBIND_SPROGS) $(LPROGS)
+wins : CHECK nsswitch/libnss_wins.@SHLIBEXT@
+
.SUFFIXES:
.SUFFIXES: .c .o .po .po32 .lo
@@ -645,7 +649,7 @@
bin/libsmbclient.@SHLIBEXT@: $(LIBSMBCLIENT_PICOBJS) bin/.dummy
@echo Linking libsmbclient shared library $@
- @$(SHLD) @LDSHFLAGS@ -o $@ $(LIBSMBCLIENT_PICOBJS) $(LIBS) \
+ @$(SHLD) @LDSHFLAGS@ -o $@ $(LIBSMBCLIENT_PICOBJS) $(LDFLAGS) $(LIBS) \
@SONAMEFLAG@`basename $@`.$(LIBSMBCLIENT_MAJOR)
bin/libsmbclient.a: $(LIBSMBCLIENT_PICOBJS) bin/.dummy
@@ -723,7 +727,8 @@
@$(SHELL) $(srcdir)/script/installswat.sh $(SWATDIR) $(srcdir)
installclientlib:
- -$(INSTALLCMD) bin/libsmbclient.so
+ -$(INSTALLCLIENTCMD_SH) bin/libsmbclient.@SHLIBEXT@
+ -$(INSTALLCLIENTCMD_A) bin/libsmbclient.a
-$(INSTALLCMD) -d ${prefix}/include
-$(INSTALLCMD) include/libsmbclient.h ${prefix}/include
diff -u -r --new-file --exclude=CVS samba-2.2.7a/source/acconfig.h samba-2.2.8/source/acconfig.h
--- samba-2.2.7a/source/acconfig.h Tue Dec 10 08:58:00 2002
+++ samba-2.2.8/source/acconfig.h Fri Feb 28 09:56:06 2003
@@ -222,3 +222,4 @@
#undef HAVE_SENDFILEV
#undef HAVE_SENDFILEV64
#undef SOLARIS_SENDFILE_API
+#undef LDAP_SET_REBIND_PROC_ARGS
diff -u -r --new-file --exclude=CVS samba-2.2.7a/source/client/client.c samba-2.2.8/source/client/client.c
--- samba-2.2.7a/source/client/client.c Wed Dec 4 11:16:34 2002
+++ samba-2.2.8/source/client/client.c Fri Mar 14 15:34:47 2003
@@ -54,6 +54,8 @@
#define CLIENT_TIMEOUT (30*1000)
#define SHORT_TIMEOUT (5*1000)
+int timeout_msec = 0;
+
/* value for unused fid field in trans2 secondary request */
#define FID_UNUSED (0xFFFF)
@@ -71,8 +73,6 @@
/* clitar bits end */
-mode_t myumask = 0755;
-
BOOL prompt = True;
int printmode = 1;
@@ -92,9 +92,9 @@
/* timing globals */
off_t get_total_size = 0;
-int get_total_time_ms = 0;
+unsigned int get_total_time_ms = 0;
off_t put_total_size = 0;
-int put_total_time_ms = 0;
+unsigned int put_total_time_ms = 0;
/* totals globals */
static double dir_total;
@@ -644,8 +644,9 @@
struct timeval tp_start;
int read_size = io_bufsize;
uint16 attr;
- size_t size;
- off_t nread = 0;
+ size_t old_size = 0;
+ SMB_BIG_UINT size = 0;
+ SMB_BIG_UINT nread = 0;
GetTimeOfDay(&tp_start);
@@ -671,9 +672,8 @@
return;
}
-
if (!cli_qfileinfo(cli, fnum,
- &attr, &size, NULL, NULL, NULL, NULL, NULL) &&
+ &attr, &old_size, NULL, NULL, NULL, NULL, NULL) &&
!cli_getattrE(cli, fnum,
&attr, &size, NULL, NULL, NULL)) {
DEBUG(0,("getattrib: %s\n",cli_errstr(cli)));
@@ -1877,10 +1877,10 @@
*/
struct
{
- char *name;
+ const char *name;
void (*fn)(void);
- char *description;
- char compl_args[2]; /* Completion argument info */
+ const char *description;
+ const char compl_args[2]; /* Completion argument info */
} commands[] =
{
{"?",cmd_help,"[command] give help on a command",{COMPL_NONE,COMPL_NONE}},
@@ -1993,7 +1993,7 @@
static void process_command_string(char *cmd)
{
pstring line;
- char *ptr;
+ const char *ptr;
/* establish the connection if not already */
@@ -2110,7 +2110,7 @@
****************************************************************************/
static void process_stdin(void)
{
- char *ptr;
+ const char *ptr;
while (1) {
fstring tok;
@@ -2148,11 +2148,11 @@
/*****************************************************
return a connection to a server
*******************************************************/
-struct cli_state *do_connect(char *server, char *share)
+struct cli_state *do_connect(const char *server, const char *share)
{
struct cli_state *c;
struct nmb_name called, calling;
- char *server_n;
+ const char *server_n;
struct in_addr ip;
fstring servicename;
char *sharename;
@@ -2187,6 +2187,8 @@
}
c->protocol = max_protocol;
+ if (timeout_msec)
+ c->timeout = timeout_msec;
if (!cli_session_request(c, &calling, &called)) {
char *p;
@@ -2561,8 +2563,6 @@
pstrcpy(workgroup,lp_workgroup());
load_interfaces();
- myumask = umask(0);
- umask(myumask);
if (getenv("USER")) {
pstrcpy(username,getenv("USER"));
@@ -2628,8 +2628,11 @@
}
while ((opt =
- getopt(argc, argv,"s:O:R:M:i:Nn:d:Pp:l:hI:EU:L:t:m:W:T:D:c:b:A:")) != EOF) {
+ getopt(argc, argv,"s:O:R:M:i:Nn:d:Pp:l:hI:EU:L:t:m:W:T:D:c:b:A:z:")) != EOF) {
switch (opt) {
+ case 'z':
+ timeout_msec = atoi(optarg);
+ break;
case 's':
pstrcpy(servicesf, optarg);
break;
diff -u -r --new-file --exclude=CVS samba-2.2.7a/source/client/clitar.c samba-2.2.8/source/client/clitar.c
--- samba-2.2.7a/source/client/clitar.c Tue Apr 30 08:26:18 2002
+++ samba-2.2.8/source/client/clitar.c Fri Mar 14 15:34:47 2003
@@ -45,10 +45,10 @@
struct file_info_struct
{
- size_t size;
+ SMB_BIG_UINT size;
uint16 mode;
- int uid;
- int gid;
+ uid_t uid;
+ gid_t gid;
/* These times are normally kept in GMT */
time_t mtime;
time_t atime;
@@ -118,19 +118,19 @@
extern BOOL readbraw_supported;
extern int max_xmit;
extern pstring cur_dir;
-extern int get_total_time_ms;
-extern int get_total_size;
+extern unsigned int get_total_time_ms;
+extern off_t get_total_size;
extern int Protocol;
int blocksize=20;
int tarhandle;
-static void writetarheader(int f, char *aname, int size, time_t mtime,
- char *amode, unsigned char ftype);
+static void writetarheader(int f, const char *aname, SMB_BIG_UINT size, time_t mtime,
+ const char *amode, unsigned char ftype);
static void do_atar(char *rname,char *lname,file_info *finfo1);
static void do_tar(file_info *finfo);
-static void oct_it(long value, int ndgs, char *p);
-static void fixtarname(char *tptr, char *fp, int l);
+static void oct_it(SMB_BIG_UINT value, int ndgs, char *p);
+static void fixtarname(char *tptr, const char *fp, int l);
static int dotarbuf(int f, char *b, int n);
static void dozerobuf(int f, int n);
static void dotareof(int f);
@@ -168,14 +168,14 @@
/****************************************************************************
Write a tar header to buffer
****************************************************************************/
-static void writetarheader(int f, char *aname, int size, time_t mtime,
- char *amode, unsigned char ftype)
+static void writetarheader(int f, const char *aname, SMB_BIG_UINT size, time_t mtime,
+ const char *amode, unsigned char ftype)
{
union hblock hb;
int i, chk, l;
char *jp;
- DEBUG(5, ("WriteTarHdr, Type = %c, Size= %i, Name = %s\n", ftype, size, aname));
+ DEBUG(5, ("WriteTarHdr, Type = %c, Size = %.0f, Name = %s\n", ftype, (double)size, aname));
memset(hb.dummy, 0, sizeof(hb.dummy));
@@ -207,17 +207,17 @@
hb.dbuf.name[NAMSIZ-1]='\0';
safe_strcpy(hb.dbuf.mode, amode, strlen(amode));
- oct_it(0L, 8, hb.dbuf.uid);
- oct_it(0L, 8, hb.dbuf.gid);
- oct_it((long) size, 13, hb.dbuf.size);
- oct_it((long) mtime, 13, hb.dbuf.mtime);
+ oct_it((SMB_BIG_UINT)0, 8, hb.dbuf.uid);
+ oct_it((SMB_BIG_UINT)0, 8, hb.dbuf.gid);
+ oct_it((SMB_BIG_UINT) size, 13, hb.dbuf.size);
+ oct_it((SMB_BIG_UINT) mtime, 13, hb.dbuf.mtime);
memcpy(hb.dbuf.chksum, " ", sizeof(hb.dbuf.chksum));
memset(hb.dbuf.linkname, 0, NAMSIZ);
hb.dbuf.linkflag=ftype;
for (chk=0, i=sizeof(hb.dummy), jp=hb.dummy; --i>=0;) chk+=(0xFF & *jp++);
- oct_it((long) chk, 8, hb.dbuf.chksum);
+ oct_it((SMB_BIG_UINT) chk, 8, hb.dbuf.chksum);
hb.dbuf.chksum[6] = '\0';
(void) dotarbuf(f, hb.dummy, sizeof(hb.dummy));
@@ -418,7 +418,7 @@
/****************************************************************************
(Un)mangle DOS pathname, make nonabsolute
****************************************************************************/
-static void fixtarname(char *tptr, char *fp, int l)
+static void fixtarname(char *tptr, const char *fp, int l)
{
/* add a '.' to start of file name, convert from ugly dos \'s in path
* to lovely unix /'s :-} */
@@ -450,7 +450,7 @@
/****************************************************************************
Convert from decimal to octal string
****************************************************************************/
-static void oct_it (long value, int ndgs, char *p)
+static void oct_it (SMB_BIG_UINT value, int ndgs, char *p)
{
/* Converts long to octal string, pads with leading zeros */
@@ -621,7 +621,7 @@
static void do_atar(char *rname,char *lname,file_info *finfo1)
{
int fnum;
- uint32 nread=0;
+ SMB_BIG_UINT nread=0;
char ftype;
file_info2 finfo;
BOOL close_done = False;
@@ -643,6 +643,7 @@
finfo.mtime = finfo1 -> mtime;
finfo.atime = finfo1 -> atime;
finfo.ctime = finfo1 -> ctime;
+ finfo.name = finfo1 -> name;
}
else {
finfo.size = def_finfo.size;
@@ -652,13 +653,14 @@
finfo.mtime = def_finfo.mtime;
finfo.atime = def_finfo.atime;
finfo.ctime = def_finfo.ctime;
+ finfo.name = def_finfo.name;
}
if (dry_run)
{
- DEBUG(3,("skipping file %s of size %d bytes\n",
+ DEBUG(3,("skipping file %s of size %12.0f bytes\n",
finfo.name,
- (int)finfo.size));
+ (double)finfo.size));
shallitime=0;
ttarf+=finfo.size + TBLOCK - (finfo.size % TBLOCK);
ntarf++;
@@ -709,9 +711,9 @@
}
else
{
- DEBUG(3,("getting file %s of size %d bytes as a tar file %s",
+ DEBUG(3,("getting file %s of size %.0f bytes as a tar file %s",
finfo.name,
- (int)finfo.size,
+ (double)finfo.size,
lname));
/* write a tar header, don't bother with mode - just set to 100644 */
@@ -719,7 +721,7 @@
while (nread < finfo.size && !close_done) {
- DEBUG(3,("nread=%d\n",nread));
+ DEBUG(3,("nread=%.0f\n",(double)nread));
datalen = cli_read(cli, fnum, data, nread, read_size);
@@ -736,7 +738,7 @@
if (nread > finfo.size) {
datalen -= nread - finfo.size;
- DEBUG(0,("File size change - truncating %s to %d bytes\n", finfo.name, (int)finfo.size));
+ DEBUG(0,("File size change - truncating %s to %.0f bytes\n", finfo.name, (double)finfo.size));
}
/* add received bits of file to buffer - dotarbuf will
@@ -756,7 +758,7 @@
/* pad tar file with zero's if we couldn't get entire file */
if (nread < finfo.size) {
- DEBUG(0, ("Didn't get entire file. size=%d, nread=%d\n", (int)finfo.size, (int)nread));
+ DEBUG(0, ("Didn't get entire file. size=%.0f, nread=%.0f\n", (double)finfo.size, (double)nread));
if (padit(data, sizeof(data), finfo.size - nread))
DEBUG(0,("Error writing tar file - %s\n", strerror(errno)));
}
@@ -789,8 +791,8 @@
if (tar_noisy)
{
- DEBUG(0, ("%10d (%7.1f kb/s) %s\n",
- (int)finfo.size, finfo.size / MAX(0.001, (1.024*this_time)),
+ DEBUG(0, ("%12.0f (%7.1f kb/s) %s\n",
+ (double)finfo.size, finfo.size / MAX(0.001, (1.024*this_time)),
finfo.name));
}
@@ -998,9 +1000,10 @@
static int get_file(file_info2 finfo)
{
- int fnum = -1, pos = 0, dsize = 0, rsize = 0, bpos = 0;
+ int fnum = -1, pos = 0, dsize = 0, bpos = 0;
+ SMB_BIG_UINT rsize = 0;
- DEBUG(5, ("get_file: file: %s, size %i\n", finfo.name, (int)finfo.size));
+ DEBUG(5, ("get_file: file: %s, size %.0f\n", finfo.name, (double)finfo.size));
if (ensurepath(finfo.name) &&
(fnum=cli_open(cli, finfo.name, O_RDWR|O_CREAT|O_TRUNC, DENY_NONE)) == -1) {
@@ -1091,7 +1094,7 @@
ntarf++;
- DEBUG(0, ("restore tar file %s of size %d bytes\n", finfo.name, (int)finfo.size));
+ DEBUG(0, ("restore tar file %s of size %.0f bytes\n", finfo.name, (double)finfo.size));
return(True);
}
@@ -1121,18 +1124,18 @@
*/
static char * get_longfilename(file_info2 finfo)
{
- int namesize = finfo.size + strlen(cur_dir) + 2;
+ int namesize = strlen(finfo.name) + strlen(cur_dir) + 2;
char *longname = malloc(namesize);
- int offset = 0, left = finfo.size;
+ SMB_BIG_INT offset = 0, left = finfo.size;
BOOL first = True;
DEBUG(5, ("Restoring a long file name: %s\n", finfo.name));
- DEBUG(5, ("Len = %d\n", (int)finfo.size));
+ DEBUG(5, ("Len = %.0f\n", (double)finfo.size));
if (longname == NULL) {
DEBUG(0, ("could not allocate buffer of size %d for longname\n",
- (int)(finfo.size + strlen(cur_dir) + 2)));
+ namesize));
return(NULL);
}
@@ -1868,7 +1871,7 @@
if (tar_type=='c' && (dry_run || strcmp(argv[Optind], "/dev/null")==0))
{
if (!dry_run) {
- DEBUG(0,("Output is /dev/null, assuming dry_run"));
+ DEBUG(0,("Output is /dev/null, assuming dry_run\n"));
dry_run = True;
}
tarhandle=-1;
diff -u -r --new-file --exclude=CVS samba-2.2.7a/source/client/smbspool.c samba-2.2.8/source/client/smbspool.c
--- samba-2.2.7a/source/client/smbspool.c Tue Dec 10 08:58:14 2002
+++ samba-2.2.8/source/client/smbspool.c Fri Feb 28 09:56:18 2003
@@ -210,12 +210,12 @@
{
if (getenv("CLASS") == NULL)
{
- perror("ERROR: Unable to connect to SAMBA host, will retry in 60 seconds...");
+ fprintf(stderr, "ERROR: Unable to connect to SAMBA host, will retry in 60 seconds...");
sleep (60);
}
else
{
- perror("ERROR: Unable to connect to SAMBA host, trying next printer...");
+ fprintf(stderr, "ERROR: Unable to connect to SAMBA host, trying next printer...");
return (1);
}
}
diff -u -r --new-file --exclude=CVS samba-2.2.7a/source/client/smbumount.c samba-2.2.8/source/client/smbumount.c
--- samba-2.2.7a/source/client/smbumount.c Tue Dec 10 08:58:14 2002
+++ samba-2.2.8/source/client/smbumount.c Wed Feb 5 10:25:25 2003
@@ -15,6 +15,10 @@
#include
#include
+#include
+#include
+#include
+
/* This is a (hopefully) temporary hack due to the fact that
sizeof( uid_t ) != sizeof( __kernel_uid_t ) under glibc.
This may change in the future and smb.h may get fixed in the
@@ -43,9 +47,9 @@
__kernel_uid_t mount_uid;
if (fid == -1) {
- fprintf(stderr, "Could not open %s: %s\n",
- mount_point, strerror(errno));
- return -1;
+ /* fprintf(stderr, "Could not open %s: %s\n",
+ mount_point, strerror(errno)); */
+ return 1; /* maybe try again */
}
if (ioctl(fid, SMB_IOC_GETMOUNTUID, &mount_uid) != 0) {
@@ -65,6 +69,92 @@
return 0;
}
+#define MAX_READLINKS 32
+/* myrealpath from mount, it could get REAL path under a broken connection */
+char *myrealpath(const char *path, char *resolved_path, int maxreslth)
+{
+ int readlinks = 0,m,n;
+ char *npath,*buf;
+ char link_path[PATH_MAX + 1];
+
+ npath = resolved_path;
+
+ if(*path != '/')
+ {
+ if(!getcwd(npath, maxreslth - 2))
+ return NULL;
+ npath += strlen(npath);
+ if(npath[-1] != '/')
+ *(npath++) = '/';
+ else
+ {
+ *npath++ = '/';
+ path++;
+ }
+ }
+
+ while(*path != '\0')
+ {
+ if(*path == '/')
+ {
+ path++;
+ continue;
+ }
+ if(*path == '.' && (path[1] == '\0' || path[1] == '/'))
+ {
+ path++;
+ continue;
+ }
+ if(*path == '.' && path[1] == '.' &&
+ (path[2] == '\0' || path[2] == '/'))
+ {
+ path += 2;
+ while(npath > resolved_path + 1 &&
+ (--npath)[-1] != '/');
+ continue;
+ }
+ while(*path != '\0' && *path != '/')
+ {
+ if(npath-resolved_path > maxreslth - 2)
+ return NULL;
+ *npath++ = *path++;
+ }
+ if(readlinks++ > MAX_READLINKS)
+ return NULL;
+ *npath = '\0';
+ n = readlink(resolved_path, link_path, PATH_MAX);
+ if(n < 0)
+ {
+ if(errno != EINVAL) return NULL;
+ }
+ else
+ {
+ link_path[n] = '\0';
+ if(*link_path == '/')
+ npath = resolved_path;
+ else while(*(--npath) != '/');
+ m = strlen(path);
+ if((buf = malloc(m + n + 1)) == NULL)
+ {
+ fprintf(stderr,"Not enough memory.\n");
+ return NULL;
+ }
+ memcpy(buf, link_path, n);
+ memcpy(buf + n, path, m + 1);
+ path = buf;
+ }
+ *npath++ = '/';
+ }
+ if(npath != resolved_path + 1)
+ {
+ while(npath > resolved_path && npath[-1] == '/')
+ npath--;
+ if(npath == resolved_path) return NULL;
+ }
+ *npath = '\0';
+ return resolved_path;
+}
+
/* Make a canonical pathname from PATH. Returns a freshly malloced string.
It is up the *caller* to ensure that the PATH is sensible. i.e.
canonicalize ("/dev/fd0/.") returns "/dev/fd0" even though ``/dev/fd0/.''
@@ -73,7 +163,8 @@
static char *
canonicalize (char *path)
{
- char *canonical = malloc (PATH_MAX + 1);
+ char *npath,*canonical = malloc (PATH_MAX + 1);
+ int i;
if (!canonical) {
fprintf(stderr, "Error! Not enough memory!\n");
@@ -87,11 +178,18 @@
if (path == NULL)
return NULL;
-
- if (realpath (path, canonical))
+
+/* if (realpath (path, canonical)) */
+ if(myrealpath(path, canonical, PATH_MAX))
return canonical;
pstrcpy (canonical, path);
+ if((i = strlen(canonical)) > 1 && i <= PATH_MAX)
+ {
+ path = canonical + i;
+ while(*(--path) == '/')
+ *path = '\0';
+ }
return canonical;
}
@@ -122,14 +220,34 @@
exit(1);
}
- if (umount_ok(mount_point) != 0) {
- exit(1);
+ if ((fd = umount_ok(mount_point)) != 0) {
+ if(fd == 1)
+ {
+ if((fd = umount_ok(mount_point)) != 0)
+ {
+ if(fd == 1)
+ {
+ fprintf(stderr, "Could not open %s: %s\n",
+ mount_point, strerror(errno));
+ }
+ exit(1);
+ }
+ }
+ else exit(1);
}
+#if !defined(MNT_DETACH)
+ #define MNT_DETACH 2
+#endif
+
if (umount(mount_point) != 0) {
- fprintf(stderr, "Could not umount %s: %s\n",
- mount_point, strerror(errno));
- exit(1);
+ /* fprintf(stderr, "Could not umount %s: %s\n,Trying lazy umount.\n",
+ mount_point, strerror(errno)); */
+ if(umount2(mount_point,MNT_DETACH) != 0)
+ {
+ fprintf(stderr, "Lazy umount failed.\n");
+ return 1;
+ }
}
if ((fd = open(MOUNTED"~", O_RDWR|O_CREAT|O_EXCL, 0600)) == -1)
diff -u -r --new-file --exclude=CVS samba-2.2.7a/source/configure samba-2.2.8/source/configure
--- samba-2.2.7a/source/configure Mon Dec 9 19:01:00 2002
+++ samba-2.2.8/source/configure Fri Feb 28 09:56:18 2003
@@ -791,6 +791,8 @@
+
+
# compile with optimization and without debugging by default
CFLAGS="-O ${CFLAGS}"
@@ -808,7 +810,7 @@
# Extract the first word of "gcc", so it can be a program name with args.
set dummy gcc; ac_word=$2
echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
-echo "configure:812: checking for $ac_word" >&5
+echo "configure:814: checking for $ac_word" >&5
if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
else
@@ -838,7 +840,7 @@
# Extract the first word of "cc", so it can be a program name with args.
set dummy cc; ac_word=$2
echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
-echo "configure:842: checking for $ac_word" >&5
+echo "configure:844: checking for $ac_word" >&5
if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
else
@@ -889,7 +891,7 @@
# Extract the first word of "cl", so it can be a program name with args.
set dummy cl; ac_word=$2
echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
-echo "configure:893: checking for $ac_word" >&5
+echo "configure:895: checking for $ac_word" >&5
if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
else
@@ -921,7 +923,7 @@
fi
echo $ac_n "checking whether the C compiler ($CC $CFLAGS $LDFLAGS) works""... $ac_c" 1>&6
-echo "configure:925: checking whether the C compiler ($CC $CFLAGS $LDFLAGS) works" >&5
+echo "configure:927: checking whether the C compiler ($CC $CFLAGS $LDFLAGS) works" >&5
ac_ext=c
# CFLAGS is not in ac_cpp because -g, -O, etc. are not valid cpp options.
@@ -932,12 +934,12 @@
cat > conftest.$ac_ext << EOF
-#line 936 "configure"
+#line 938 "configure"
#include "confdefs.h"
main(){return(0);}
EOF
-if { (eval echo configure:941: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
+if { (eval echo configure:943: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
ac_cv_prog_cc_works=yes
# If we can't run a trivial program, we are probably using a cross compiler.
if (./conftest; exit) 2>/dev/null; then
@@ -963,12 +965,12 @@
{ echo "configure: error: installation or configuration problem: C compiler cannot create executables." 1>&2; exit 1; }
fi
echo $ac_n "checking whether the C compiler ($CC $CFLAGS $LDFLAGS) is a cross-compiler""... $ac_c" 1>&6
-echo "configure:967: checking whether the C compiler ($CC $CFLAGS $LDFLAGS) is a cross-compiler" >&5
+echo "configure:969: checking whether the C compiler ($CC $CFLAGS $LDFLAGS) is a cross-compiler" >&5
echo "$ac_t""$ac_cv_prog_cc_cross" 1>&6
cross_compiling=$ac_cv_prog_cc_cross
echo $ac_n "checking whether we are using GNU C""... $ac_c" 1>&6
-echo "configure:972: checking whether we are using GNU C" >&5
+echo "configure:974: checking whether we are using GNU C" >&5
if eval "test \"`echo '$''{'ac_cv_prog_gcc'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
else
@@ -977,7 +979,7 @@
yes;
#endif
EOF
-if { ac_try='${CC-cc} -E conftest.c'; { (eval echo configure:981: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }; } | egrep yes >/dev/null 2>&1; then
+if { ac_try='${CC-cc} -E conftest.c'; { (eval echo configure:983: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }; } | egrep yes >/dev/null 2>&1; then
ac_cv_prog_gcc=yes
else
ac_cv_prog_gcc=no
@@ -996,7 +998,7 @@
ac_save_CFLAGS="$CFLAGS"
CFLAGS=
echo $ac_n "checking whether ${CC-cc} accepts -g""... $ac_c" 1>&6
-echo "configure:1000: checking whether ${CC-cc} accepts -g" >&5
+echo "configure:1002: checking whether ${CC-cc} accepts -g" >&5
if eval "test \"`echo '$''{'ac_cv_prog_cc_g'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
else
@@ -1058,7 +1060,7 @@
# SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff"
# ./install, which can be erroneously created by make from ./install.sh.
echo $ac_n "checking for a BSD compatible install""... $ac_c" 1>&6
-echo "configure:1062: checking for a BSD compatible install" >&5
+echo "configure:1064: checking for a BSD compatible install" >&5
if test -z "$INSTALL"; then
if eval "test \"`echo '$''{'ac_cv_path_install'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
@@ -1115,7 +1117,7 @@
# Extract the first word of "$ac_prog", so it can be a program name with args.
set dummy $ac_prog; ac_word=$2
echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
-echo "configure:1119: checking for $ac_word" >&5
+echo "configure:1121: checking for $ac_word" >&5
if eval "test \"`echo '$''{'ac_cv_prog_AWK'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
else
@@ -1146,7 +1148,7 @@
LD=ld
echo $ac_n "checking if the linker ($LD) is GNU ld""... $ac_c" 1>&6
-echo "configure:1150: checking if the linker ($LD) is GNU ld" >&5
+echo "configure:1152: checking if the linker ($LD) is GNU ld" >&5
if eval "test \"`echo '$''{'ac_cv_prog_gnu_ld'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
else
@@ -1163,7 +1165,7 @@
# Extract the first word of "passwd", so it can be a program name with args.
set dummy passwd; ac_word=$2
echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
-echo "configure:1167: checking for $ac_word" >&5
+echo "configure:1169: checking for $ac_word" >&5
if eval "test \"`echo '$''{'ac_cv_path_passwd_program'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
else
@@ -1200,10 +1202,10 @@
if test "x$CC" != xcc; then
echo $ac_n "checking whether $CC and cc understand -c and -o together""... $ac_c" 1>&6
-echo "configure:1204: checking whether $CC and cc understand -c and -o together" >&5
+echo "configure:1206: checking whether $CC and cc understand -c and -o together" >&5
else
echo $ac_n "checking whether cc understands -c and -o together""... $ac_c" 1>&6
-echo "configure:1207: checking whether cc understands -c and -o together" >&5
+echo "configure:1209: checking whether cc understands -c and -o together" >&5
fi
set dummy $CC; ac_cc="`echo $2 |
sed -e 's/[^a-zA-Z0-9_]/_/g' -e 's/^[0-9]/_/'`"
@@ -1215,16 +1217,16 @@
# We do the test twice because some compilers refuse to overwrite an
# existing .o file with -o, though they will create one.
ac_try='${CC-cc} -c conftest.c -o conftest.o 1>&5'
-if { (eval echo configure:1219: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; } &&
- test -f conftest.o && { (eval echo configure:1220: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; };
+if { (eval echo configure:1221: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; } &&
+ test -f conftest.o && { (eval echo configure:1222: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; };
then
eval ac_cv_prog_cc_${ac_cc}_c_o=yes
if test "x$CC" != xcc; then
# Test first that cc exists at all.
- if { ac_try='cc -c conftest.c 1>&5'; { (eval echo configure:1225: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }; }; then
+ if { ac_try='cc -c conftest.c 1>&5'; { (eval echo configure:1227: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }; }; then
ac_try='cc -c conftest.c -o conftest.o 1>&5'
- if { (eval echo configure:1227: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; } &&
- test -f conftest.o && { (eval echo configure:1228: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; };
+ if { (eval echo configure:1229: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; } &&
+ test -f conftest.o && { (eval echo configure:1230: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; };
then
# cc works too.
:
@@ -1258,20 +1260,20 @@
echo $ac_n "checking that the C compiler understands volatile""... $ac_c" 1>&6
-echo "configure:1262: checking that the C compiler understands volatile" >&5
+echo "configure:1264: checking that the C compiler understands volatile" >&5
if eval "test \"`echo '$''{'samba_cv_volatile'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
else
cat > conftest.$ac_ext <
int main() {
volatile int i = 0
; return 0; }
EOF
-if { (eval echo configure:1275: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
+if { (eval echo configure:1277: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
rm -rf conftest*
samba_cv_volatile=yes
else
@@ -1321,7 +1323,7 @@
fi
echo $ac_n "checking host system type""... $ac_c" 1>&6
-echo "configure:1325: checking host system type" >&5
+echo "configure:1327: checking host system type" >&5
host_alias=$host
case "$host_alias" in
@@ -1342,7 +1344,7 @@
echo "$ac_t""$host" 1>&6
echo $ac_n "checking target system type""... $ac_c" 1>&6
-echo "configure:1346: checking target system type" >&5
+echo "configure:1348: checking target system type" >&5
target_alias=$target
case "$target_alias" in
@@ -1360,7 +1362,7 @@
echo "$ac_t""$target" 1>&6
echo $ac_n "checking build system type""... $ac_c" 1>&6
-echo "configure:1364: checking build system type" >&5
+echo "configure:1366: checking build system type" >&5
build_alias=$build
case "$build_alias" in
@@ -1394,7 +1396,7 @@
echo $ac_n "checking config.cache system type""... $ac_c" 1>&6
-echo "configure:1398: checking config.cache system type" >&5
+echo "configure:1400: checking config.cache system type" >&5
if { test x"${ac_cv_host_system_type+set}" = x"set" &&
test x"$ac_cv_host_system_type" != x"$host"; } ||
{ test x"${ac_cv_build_system_type+set}" = x"set" &&
@@ -1421,7 +1423,7 @@
# Try to work out if this is the native HPUX compiler that uses the -Ae flag.
*hpux*)
echo $ac_n "checking whether ${CC-cc} accepts -Ae""... $ac_c" 1>&6
-echo "configure:1425: checking whether ${CC-cc} accepts -Ae" >&5
+echo "configure:1427: checking whether ${CC-cc} accepts -Ae" >&5
if eval "test \"`echo '$''{'ac_cv_prog_cc_Ae'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
else
@@ -1451,7 +1453,7 @@
#
case `uname -r` in
*9*|*10*)
- CPPFLAGS="$CPPFLAGS -D_HPUX_SOURCE -D_POSIX_SOURCE -D_ALIGNMENT_REQUIRED=1 -D_MAX_ALIGNMENT=4"
+ CPPFLAGS="$CPPFLAGS -D_HPUX_SOURCE -D_POSIX_SOURCE -D_ALIGNMENT_REQUIRED=1 -D_MAX_ALIGNMENT=4 -DMAX_POSITIVE_LOCK_OFFSET=0x1ffffffffffLL"
cat >> confdefs.h <<\EOF
#define USE_BOTH_CRYPT_CALLS 1
EOF
@@ -1474,7 +1476,7 @@
;;
*11*)
- CPPFLAGS="$CPPFLAGS -D_HPUX_SOURCE -D_POSIX_SOURCE -D_LARGEFILE64_SOURCE -D_ALIGNMENT_REQUIRED=1 -D_MAX_ALIGNMENT=4"
+ CPPFLAGS="$CPPFLAGS -D_HPUX_SOURCE -D_POSIX_SOURCE -D_LARGEFILE64_SOURCE -D_ALIGNMENT_REQUIRED=1 -D_MAX_ALIGNMENT=4 -DMAX_POSITIVE_LOCK_OFFSET=0x1ffffffffffLL"
cat >> confdefs.h <<\EOF
#define _HPUX_SOURCE 1
EOF
@@ -1578,19 +1580,45 @@
esac
;;
#
+# VOS may need to have POSIX support and System V compatibility enabled.
+#
+ *vos*)
+ case "$CPPFLAGS" in
+ *-D_POSIX_C_SOURCE*)
+ ;;
+ *)
+ CPPFLAGS="$CPPFLAGS -D_POSIX_C_SOURCE=199506L"
+ cat >> confdefs.h <<\EOF
+#define _POSIX_C_SOURCE 199506L
+EOF
+
+ ;;
+ esac
+ case "$CPPFLAGS" in
+ *-D_SYSV*|*-D_SVID_SOURCE*)
+ ;;
+ *)
+ CPPFLAGS="$CPPFLAGS -D_SYSV"
+ cat >> confdefs.h <<\EOF
+#define _SYSV 1
+EOF
+
+ esac
+ ;;
+#
# Tests needed for SINIX large file support.
#
*sysv4*)
if test $host = mips-sni-sysv4 ; then
echo $ac_n "checking for LFS support""... $ac_c" 1>&6
-echo "configure:1587: checking for LFS support" >&5
+echo "configure:1615: checking for LFS support" >&5
old_CPPFLAGS="$CPPFLAGS"
CPPFLAGS="-D_LARGEFILE64_SOURCE $CPPFLAGS"
if test "$cross_compiling" = yes; then
SINIX_LFS_SUPPORT=cross
else
cat > conftest.$ac_ext <
@@ -1602,7 +1630,7 @@
#endif
}
EOF
-if { (eval echo configure:1606: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
+if { (eval echo configure:1634: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
then
SINIX_LFS_SUPPORT=yes
else
@@ -1633,14 +1661,14 @@
#
*linux*)
echo $ac_n "checking for LFS support""... $ac_c" 1>&6
-echo "configure:1637: checking for LFS support" >&5
+echo "configure:1665: checking for LFS support" >&5
old_CPPFLAGS="$CPPFLAGS"
CPPFLAGS="-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE $CPPFLAGS"
if test "$cross_compiling" = yes; then
LINUX_LFS_SUPPORT=cross
else
cat > conftest.$ac_ext <
@@ -1678,7 +1706,7 @@
}
EOF
-if { (eval echo configure:1682: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
+if { (eval echo configure:1710: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
then
LINUX_LFS_SUPPORT=yes
else
@@ -1711,14 +1739,14 @@
*hurd*)
echo $ac_n "checking for LFS support""... $ac_c" 1>&6
-echo "configure:1715: checking for LFS support" >&5
+echo "configure:1743: checking for LFS support" >&5
old_CPPFLAGS="$CPPFLAGS"
CPPFLAGS="-D_LARGEFILE64_SOURCE -D_GNU_SOURCE $CPPFLAGS"
if test "$cross_compiling" = yes; then
GLIBC_LFS_SUPPORT=cross
else
cat > conftest.$ac_ext <
@@ -1730,7 +1758,7 @@
#endif
}
EOF
-if { (eval echo configure:1734: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
+if { (eval echo configure:1762: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
then
GLIBC_LFS_SUPPORT=yes
else
@@ -1760,21 +1788,21 @@
esac
echo $ac_n "checking for inline""... $ac_c" 1>&6
-echo "configure:1764: checking for inline" >&5
+echo "configure:1792: checking for inline" >&5
if eval "test \"`echo '$''{'ac_cv_c_inline'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
else
ac_cv_c_inline=no
for ac_kw in inline __inline__ __inline; do
cat > conftest.$ac_ext <&5; (eval $ac_compile) 2>&5; }; then
+if { (eval echo configure:1806: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
rm -rf conftest*
ac_cv_c_inline=$ac_kw; break
else
@@ -1800,7 +1828,7 @@
esac
echo $ac_n "checking how to run the C preprocessor""... $ac_c" 1>&6
-echo "configure:1804: checking how to run the C preprocessor" >&5
+echo "configure:1832: checking how to run the C preprocessor" >&5
# On Suns, sometimes $CPP names a directory.
if test -n "$CPP" && test -d "$CPP"; then
CPP=
@@ -1815,13 +1843,13 @@
# On the NeXT, cc -E runs the code through the compiler's parser,
# not just through cpp.
cat > conftest.$ac_ext <
Syntax Error
EOF
ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
-{ (eval echo configure:1825: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
+{ (eval echo configure:1853: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
if test -z "$ac_err"; then
:
@@ -1832,13 +1860,13 @@
rm -rf conftest*
CPP="${CC-cc} -E -traditional-cpp"
cat > conftest.$ac_ext <
Syntax Error
EOF
ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
-{ (eval echo configure:1842: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
+{ (eval echo configure:1870: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
if test -z "$ac_err"; then
:
@@ -1849,13 +1877,13 @@
rm -rf conftest*
CPP="${CC-cc} -nologo -E"
cat > conftest.$ac_ext <
Syntax Error
EOF
ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
-{ (eval echo configure:1859: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
+{ (eval echo configure:1887: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
if test -z "$ac_err"; then
:
@@ -1880,12 +1908,12 @@
echo "$ac_t""$CPP" 1>&6
echo $ac_n "checking for ANSI C header files""... $ac_c" 1>&6
-echo "configure:1884: checking for ANSI C header files" >&5
+echo "configure:1912: checking for ANSI C header files" >&5
if eval "test \"`echo '$''{'ac_cv_header_stdc'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
else
cat > conftest.$ac_ext <
#include
@@ -1893,7 +1921,7 @@
#include
EOF
ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
-{ (eval echo configure:1897: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
+{ (eval echo configure:1925: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
if test -z "$ac_err"; then
rm -rf conftest*
@@ -1910,7 +1938,7 @@
if test $ac_cv_header_stdc = yes; then
# SunOS 4.x string.h does not declare mem*, contrary to ANSI.
cat > conftest.$ac_ext <
-
+