> What I want to do is copy the passwd and shadow files over to the
> secondary server (a sparc 4 sol 2.4) and place them in say
> /etc/raddb/bk.passwd and bk.shadow
>
> What do I need to modify in the Livingston Radius code to read from
> as specific file other than /etc/shadow and /etc/password.
This depends on your system, the libraries it uses, and on how much code
you want to write. If you have a function that can basically say "hey,
use this other passwd/shadow file for future getpw/getsp calls" then it's
pretty easy to do. If you don't, then you have some options...you can try
setting up a chrooted environment for the secondary radiusd, or write your
own passwd/shadow lookup functions.
> Another questions, since the shadow file contains both username and password
> is it possible to use only that shadow file, or do I need also passwd.
My hacked radiusd2 only needs /etc/raddb/shadow for doing authentication
(and of course the other standard radiusd files).
------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/hr.
________Finger jlewis@inorganic5.fdt.net for PGP public key_______