Home | History | Annotate | Download | only in contrib

Lines Matching refs:userId

47   -u  passes the client-side userId to the cvs_acls script
57   user          - userId to be allowed or restricted
182 can do restrictions based on the client-side userId rather than the
183 server-side userId (usually 'cvs').
256    a) The first option is to use the $ENV{"USER"}, server-side userId
259       up a new "cvsadmin" userId and group on the pserver machine.  
271    b) The second option is to use the client-side userId as the basis for
273       can run as userId 'cvs' and no 'root' userId is required.  If you have
274       a 'passwd' file that lists 'cvs' as the effective run-time userId for
281       Just by switching the CVSROOT var from CVSROOT=:pserver:<userId>... to 
282       CVSROOT=:ext:<userId>..., users can switch over to SSH access without
299          "-u $USER" passes the client-side userId to cvs_acls 
740 # If @ARGV contains a "-u" entry, use that as the effective userId.  In this 
741 # case, the userId is the client-side userId that has been passed to this 
745 # Otherwise, pull the userId from the server-side environment.
747     my $userId = "";
766 	# Passing in a client-side userId?
769 	    $userId = shift @ARGV;
770 	    print("$$ client-side \$userId set to: $userId.\n") if $debug;
782     # No client-side userId passed? then get from server env
783     if (!$userId) {
784         $userId = $ENV{"USER"} if !($userId = $ENV{"LOGNAME"});
785 	    print("$$ server-side \$userId set to: $userId.\n") if $debug;
788     print("$$ processArgs returning \$userId: $userId.\n") if $debug;
789     return $userId;