Alan Wright <alan.wri...@oracle.com> writes: >> It seems way over complicated for a home lan user. And I suppose that >> isn't where it is targetted either. > > Have you tried using something based on the example on that page: > > idmap add winuser:te...@example.com unixuser:terrym
Alan, it kind of sounds like something like this could be used to map a work group to a unix users name.... The author mentions "The mapping works on both a per-user and a per-group basis and for entire Windows domains" But he doesn't mention work groups, although he does say earlier that: Create bidirectional rule-based mappings for users and groups whose Windows names do not exactly match the Solaris names. What is meant by `groups' there? The author goes quite at length about using this to lock users out.. not something that would come up in my usage, but he doesn't explain so well... at least not to my feeble mind, how this works in much detail. It never seems to say where this stuff gets recorded or anything about editing specific control files These commands look like they might take care of things at a higher level: # idmap add 'winuser:*...@example.com' 'unixuser:*' # idmap add 'wingroup:*...@example.com' 'unixgroup:*' So do you just have to give that command before every usage or at a reboot or something or does it get recorded somewhere? As you see I'm plenty confused about it. The man pages on my system are completely useless and seem to have lots of unusual characters from non-english language or something in lots of key places rendering them unusable... at least for me. I have to look them up online and then its not always clear if they pertain to openindiana or what. _______________________________________________ cifs-discuss mailing list cifs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
