[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ranger::pwosf

Title:PATHWORKS for OSF/1
Notice:see also NOTED::PWDOSWINV5 (PW client) & TURRIS::DIGITAL_UNIX
Moderator:CPEEDY::LONG
Created:Thu Apr 22 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1874
Total number of notes:6870

1331.0. "GROUPQUOTA" by TRNOIS::62468::airulo (benvenuto) Thu Jan 11 1996 06:44

T.RTitleUserPersonal
Name
DateLines
1331.1no, dunix group != lm groupSYSMGT::RMCDONOUGHTue Jan 16 1996 12:3327
1331.2IGNOREUNIX or mapuser/mapgroup ?CHEFS::BARRETTOMon Feb 17 1997 10:3617
    This is the same problem that my customer wants to try and resolve.
    However it appears that it is possible to get rid of the DOS-XXX from
    the group field in the DUNIX file by setting IGNOREUNIX=NO in the
    LANMAN.INI file. see note 1343.
    
    However, I would like to know why the group is set to SYSTEM in the
    case of note 1343. Is it that the PATHWORKS process has a default group 
    that it will use ?
    
    What are the effects of setting IGNOREUNIX on the group field ?
    
    Why are we unable to set the groups for a LM created file to that of 
    the DUNIX directory or DUNIX user. Would the mapuser or mapgroup (I
    don't think this is yet implemented in PWOSF V5/V6) help the situation.
    
    regards,
    Tony