magic directory names in print$ share

Herb Lewis herb at sgi.com
Tue Nov 13 08:35:04 GMT 2001


"Gerald (Jerry) Carter" wrote:
> 
> On Tue, 13 Nov 2001, Tim Potter wrote:
> 
> > Right - I've debugged not creating a W32X86 directory under my print$
> > share for the last time.  (-:  It's time to fix it.
> 
> We were never supposed to create W32X86, WIN40, etc... automatically.
> Only the "0", "2", "3", etc... subdirectories.
> 
> > I propose another parameter (noooooo!) that specifies the printer
> > driver architectures that are supported for point and print which
> > defaults to just W32X86.  The first time a user connects to the share
> > if these architecture directories do not exist then they are created.
> 
> Why not just create them all by default?  It's spelled out in the
> documentation that the admin should create the directoris beforehand.
> 
> > I realise that this behaviour is documented but it's pretty silly, and
> > if I can fall in to this hole multiple times then it is going to trap
> > lots of other people as well.
> 
> This complaint has not come up on samba at samba.org that I can remember.
> If you want to do them automatically, just do them all and make them
> set the permissions to be the owner/group from the top level of the
> [print$] share.  Use the inherit permissions method to set perms.
> 
> No more parameters, please :-)
> 
> cheers, jerry
>

I agree with Jerry. Just create them all. Unfortunately there are lots
of people who don't read the instructions. This is something that could
be done easily to simplify their life.

-- 
======================================================================
Herb Lewis                               Silicon Graphics 
Networking Engineer                      1600 Amphitheatre Pkwy MS-510
Strategic Software Organization          Mountain View, CA  94043-1351
herb at sgi.com                             Tel: 650-933-2177
http://www.sgi.com                       Fax: 650-932-2177          
======================================================================




More information about the samba-technical mailing list