[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[K12OSN] Re: K12OSN Digest, Vol 8, Issue 37



Guy,
No it's not necessary for ncpfs to work. I have the
legacy of having used Native File Access for UNIX and
have some NFS mounts that already have permissions set
based on UIDs and GIDs that are in edirectory. If you
never used Native File Access, then there is nothing
to worry about.
I wrote to Petr Vandrovec (the ncpfs package
maintainer) about this and he had this to say:

Try adding -u1000,10000,rn,gcsd (and eventually
-g1000,10000,rn for
groups).  1000-10000 is range allowed for UIDs (and
GIDs for -g...) 
stored in NDS.  rn says that when UID specified in NDS
is occupied,
no user should be created locally (pn assigns an
unused number to the
user in such case; if you want uniform environment
across systems, you
want rn). gcsd says that all user's properties in
/etc/passwd should
be regulary updated from NDS on each user login.

By default standard UNIX attributes are used:
UNIX:UID, UNIX:Primary GroupName,
UNIX:Primary GroupID, UNIX:GID, UNIX:Login Shell,
UNIX:Comments and
UNIX:Home Directory.  Or you can use special values of
L (Location)
attribute: U:XXXX to set uid, G:XXXX to set gid by
number, P:XXXX to
set gid by name, H:XXXX for home directory, S:XXXX for
shell, C:XXXX
for gecos, O:XXXX for supplemental group(s) and Z:XXXX
to set ZENFlags
(see pam_ncp_auth.c source for ZENFlags
explanation/values - it is just
32 booleans you can use for modifying pam-ncp
behavior).

Hope this helps.
                                                      
         Petr

I am going to try and implement his suggestions today
and see what happens. I'll let you know the result.
Dave



		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]