Seems to me that if Livingston added that code to Radius, it would make
two's life much easer but people in group three would have more work due
to the fact they have to switch to a new method or disable it in the new
code and put their hacks back in. Hacks they may have spent a lot of time
on and are proud of. :-)
I fall into camp 3, I keep track of who is online, have a web page that
lets others see a list and pretty graphic charts and the web server also
can display custom information to customers because it can map IP address
to a user name. If Livingston comes out with a new system, I have to
change all those programs to work with it or stay with my old code.
Personally, I don't really care which way they go... if they don't add it,
I have less work. If they do add it, I'll have a lot of work but it will
probably be more efficient and standard. What I WOULD really like to see
is hooks to make adding things like that easier. How about adding a !info
login with a separate password that you could only display info and not
change it? Currently the only way to do pmwho and similar is to have the
system password encoded in a file/program somewhere, yuck.
If Livingston does add multiple login restrictions, they should just have
a routine they call when it detects a duplicate login. Then it would be
an easy change the ISP could make to cause it to kick the oldest off,
refuse the current, bill extra, send nasty email... that's not hard, it is
the keeping track of who is on and who should not be allowed that is.
-- IanSmith@ncinter.net System Administrator - North Coast Internet - http://www.ncinter.net/