search for: allow_list

I''m finding that I''m writing sets of very similar scenarios to check access permissions for each of my actions. Does anyone have suggestions on how to dry this up: Given an existing Account And a logged in Admin When the user visits account/manage Then he should get access Given an existing Account And a logged in Manager When the user visits account/manage Then he should get

...============================================================== RCS file: /data/cvs/rsync/proto.h,v retrieving revision 1.128 diff -u -p -r1.128 proto.h --- proto.h 14 Aug 2001 02:04:49 -0000 1.128 +++ proto.h 22 Aug 2001 04:15:12 -0000 @@ -3,6 +3,7 @@ int allow_access(char *addr, char *host, char *allow_list, char *deny_list); char *auth_server(int fd, int module, char *addr, char *leader); void auth_client(int fd, char *user, char *challenge); +int make_backup(char *fname); void create_batch_file_ext(); void set_batch_file_ext(char *ext); void write_batch_flist_file(char *buff, int bytes_to_write...

...1.1.6 retrieving revision 1.4 diff -c -b -r1.1.1.6 -r1.4 *** proto.h 2001/10/19 04:09:57 1.1.1.6 --- proto.h 2001/11/19 20:31:47 1.4 *************** *** 1,7 **** /* This file is automatically generated with "make proto". DO NOT EDIT */ int allow_access(char *addr, char *host, char *allow_list, char *deny_list); ! char *auth_server(int fd, int module, char *addr, char *leader); void auth_client(int fd, char *user, char *challenge); int make_backup(char *fname); uint32 get_checksum1(char *buf1,int len); --- 1,7 ---- /* This file is automatically generated with "make proto&quo...

> Just curious: what about the rsync+ patch? Thanks for the reminder. I've just committed Jos's rsync+ patch onto the "branch_mbp_rsyncplus_merge" branch. If it works OK and nobody screams I will move it across onto the main tree tomorrow or Wednesday. I see the patch doesn't add documentation about the new options to the man page, so we should fix that in the future.