-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 28 April 2004 09:15 am, Jan Harkes wrote:
> I'm not even sure why I put this in
> venus.conf because it doesn't really have anything to do with venus.
I suspect venus.conf should be called client.conf .... since several of the
client programs read venus.conf for configuration. A quick grep shows:
auth2/au.c: codaconf_init("venus.conf");
auth2/avenus.c: codaconf_init("venus.conf");
auth2/clog.c: codaconf_init("venus.conf");
auth2/cpasswd.c: codaconf_init("venus.conf");
auth2/ctokens.c: codaconf_init("venus.conf");
auth2/krb4.c: codaconf_init("venus.conf");
auth2/krb5.c: codaconf_init("venus.conf");
kerndep/pioctl.c: codaconf_init("venus.conf");
venus/venus.cc: codaconf_init("venus.conf");
vtools/cfs.cc: codaconf_init("venus.conf");
vtools/codacon.cc: codaconf_init("venus.conf");
vtools/hoard.cc: codaconf_init("venus.conf");
vtools/spy.cc: codaconf_init("venus.conf");
So this makes venus.conf the proper place to put in a default realm for clog.
- --Phil
- --
Phil Nelson NetBSD: http://www.netbsd.org
e-mail: [EMAIL PROTECTED] Coda: http://www.coda.cs.cmu.edu
http://www.cs.wwu.edu/nelson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
iD8DBQFAj9u7zbodwsP3RI0RAvjZAJ0fzmJw7fapggUnLZwkW02w5d5w1QCgmT7P
qIq/0ycu65hV2ax0/vB4Oss=
=R52s
-----END PGP SIGNATURE-----
