|
From: | Derek Robert Price |
Subject: | Re: user.c, user.h |
Date: | Wed, 14 Aug 2002 09:07:05 -0400 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020606 |
Andrey Aristarkhov wrote:
-----Original Message----- From: Derek Robert Price [mailto:derek@ximbiot.com]I still think it should be modeled more after the getpwnam() typesystempasswd functions and return a pointer to a structure containing allthefields from the file so that the data can be cached and the passwdfileYou are right. There must be a struct like this struct cvs_passwd {won't need to be reaccessed for every field.char * username; char * passwd; char * alias; /* from CVSROOT/users */ char * notify_name; } cvspasswd_t;and corresponded functioncvspasswd_t * getcvspwent(const char * user, const char * passwd_file);or even better cvspasswd_t * getcvspwent(const char * user, int file_type /*PASSWD_LOCAL | PASSWD_ROOT */); PASSWD_LOCAL is for ~/.cvspasswd and PASSWD_ROOT is for CVSROOT/passwd
Let's name them like the system functions. The system getpwent() iterates over the entries in the file, returning a new passwd structure with each call. getpwnam() looks up a single passwd structure by user name.
Unless my grasp of NT terminology is worse than I think, under local mode on UNIX, the caller principal is assumed to be the user name.Doessomething prevent that under NT?Sorry for some uncertainty. I meant that user's caller prinicipal andCVS user name could be deferent.
What is written in the log file on commit in local mode under NT then? Derek -- *8^) Email: derek@ximbiot.com Get CVS support at http://ximbiot.com -- I will not instigate revolution. I will not instigate revolution. I will not instigate revolution... - Bart Simpson on chalkboard, _The Simpsons_
[Prev in Thread] | Current Thread | [Next in Thread] |