That is right. A user's config will take precedence over the the /etc/tmdarc file BUT that is only if it is made before they use tmda-cgi. I could manually setup users and tmda-cgi will work just fine. The idea is I don't know who will use this tool. So as people use the tool, they will show other people and I don't really have much maintence on it. When new users sign up, the idea is that they will then create their own key file using tmda-cgi and be able to do a little bit more. Otherwise, for the rest of the users, it's a basic CR system.
If crypt_key_file is defined in /etc/tmdarc, tmda-cgi will NOT setup new users and that's when I get the error. If a user has a home directory and the tmda files setup before, tmda-cgi will bypass /etc/tmdarc and look at the users config.
David
[EMAIL PROTECTED] writes:
> Basically, in short, I think if there was some way to disable tmda-cgi's
> reading of the crypt_key_file in tmdarc, I think that would all that is
> needed.
I'm not sure I still have the big picture of what you're doing yet,
but... a user's config file will override /etc/tmdarc, so if you
ensure that you create a private config file for your "power users",
you can set the path to their own, private crypt_key file there. All
TMDA and tmda-cgi programs will use that key instead of the key
specified in /etc/tmdarc.
Tim
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
