samba - Dec 2001 - Different [homes] behavior in 2.2.2

Is it possible to configure samba to disregard the home directory in the
passwd file when using [homes]?  Even though an alternate "path" is
set
in [homes], the service fails since the unix home directory is invalid
(nonexistent) on the server.

For example, let's say a user 'Anne' has the following passwd entry
which is valid on client workstations where her home directory maps to
/mit/anne.  She is not allowed to map her directory to the server, where
/mit/anne does not exist.

/etc/passwd looks like this:
anne:*:4321:101:Ann E User ,Anne,,,:/mit/anne:/bin/athena/tcsh

However her windows home lives in a different location:
[homes]
        comment = Homes directory for %u
        path = /u1/crltest/export/%S
        browseable = no
        read only = no
        nt acl support = no

This behavior of validating the user's home dir as set in the passwd
files appears to be new
in 2.2.2 and the latest CVS. Anyway to work around this?
- besides changing the passwd entries to look like this on the server:
anne:*:4321:101:Ann E User
,Anne,,,:/u1/crltest/export/anne:/bin/athena/tcsh

Thanks,
Philip Thompson
MIT

On Mon, Dec 17, 2001 at 11:09:28PM -0500, Phil Thompson wrote:
> Is it possible to configure samba to disregard the home directory in the
> passwd file when using [homes]?  Even though an alternate "path"
is set
> in [homes], the service fails since the unix home directory is invalid
> (nonexistent) on the server.
Hi Phil.  I've checked in a fix for this into the HEAD branch since I 
was looking at the home directory code anyway.  I'm hoping Jeremy will 
OK it for inclusion into 2.2.3.


Regards,

Tim.