Garrett Wollman wrote:
starting two kadminds, one for each realm, specifying an alternate port, but that didn't work either as there is no way to specify a different changepw port on the command line.
We have this working by starting one kadmind instance for each realm.
kdchost# kadmind -r REALM1 kdchost# kadmind -r REALM2
In kdc.conf we have for instance
REALM1 {
...
kadmind_port = 4001
kpasswd_port = 4501
}REALM2 {
...
kadmind_port = 4002
kpasswd_port = 4502}
What am I missing? Any workarounds? Is this fixed in the most recent release?
- -GAWollman
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD)
iD8DBQE/VlSjI+eG6b7tlG4RAgwXAKCuCozNKZqwriNCXriD3djRX3PjXACdFXYc EBrLDzDdjqXEbieVUQPqEyI= =QRNa -----END PGP SIGNATURE-----
________________________________________________ Kerberos mailing list [EMAIL PROTECTED] https://mailman.mit.edu/mailman/listinfo/kerberos
