Typically the path specified is that of a world-writeable spool directory with the sticky bit set on it.A typical [printers] entry looks like this: All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned.
When the connection request is made, the existing sections are scanned. If no match is found, the requested section name is treated as a username and looked up in the local password file.Sections may be designated is used to define access privileges in this case.Sections other than guest services will require a password to access them. As older clients only provide passwords and not usernames, you may specify a list of usernames to check against the password using the option in the share definition.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: The [printers] service MUST be printable - if you specify otherwise, the server will refuse to load the configuration file.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. 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).Only the first equals sign in a parameter is significant.Whitespace before or after the first equals sign is discarded.When a connection request is made, the existing sections are scanned. 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.