Just remember to budget about three times as much $$ for CPU cycles if you
use rlogind (or in.pmd) to run uucp over. Rough benchmarking showed that the
rlogind that passed that data from the TCP/IP connection to the uucico
program took three times as many CPU cycles as the uucico itself did. I.e.
you can support four times as many uucico's if you run them directly by
using the uucp deamon (uucpd.c or ruucpd.c).
}I've seen several people saying this. I wonder if it's because you're
}using RADIUS? I don't know.
}
}I'm not right now, but plan to, but in any case, here's how I'm handling it
}without double passwords:
}
}Just treat the UUCP account as any other user name (I do this in the
}password table), set to autologin to the UUCP host. That way, the PM never
}asks for the password to begin with (I have ALL the dialup users set this
}way, btw -- the only passwords I have the PM handle right now is PPP
}accounts).
Two problems with this approach. First you have to keep all of the password
tables on all of your PM's in synch which can be a bit of a problem after
you get more than a couple. Second what do you do when you signup more
people than can fit in the password table. It's designed to support a small
corporate environment where the user base is small and stable. Radius is
required where you have a large and dynamically changing user base that is
spread across multiple PM's.
When I get a PM I set it's IP address. Point it at radius for authorization
and accounting. Point it at a loghost. Clone the ports for simple login
setup. And turn it on. Only very rarely do we touch anything on the PM's.
All setup WRT to users is done in one place, on one machine, the radius
server.
-- Stuart Lynne <sl@wimsey.com> 604-933-1000 <http://www.wimsey.com> PGP Fingerprint: 28 E2 A0 15 99 62 9A 00 88 EC A3 EE 2D 1C 15 68