On Wed, Jan 19, 2005 at 01:11:55PM -0600, Sam wrote:
I think there may be a problem in the way radwtmp is being written (at
least in the Freeradius that ships with RedHat ES3).
Testing: I copied a radwtmp file over from my old RedHat 7.2 server
(running Cistron 1.6) and both last and radlast (from Freeradius on the RH
ES3 server) read the file fine. Neither last nor radlast will read the
radwtmp file that is being created by Freeradius that ships with RH ES3.
For further testing I took the radwtmp created by Freeradius on the RH ES3
server and put it on the old 7.2 server running Cistron. It wouldn't read
it, and gave exactly the same output as I got from last and radlast on the
RH ES3 server.
Any thoughts?
Grab a hex dumper, and see what the structure is, and how it's
different from the expected. If I recall correctly, radwtmp is
written based on the wtmp format provided on the compile system,
so possibly the compilation system had a different format than
the installation system.
You could try compiling a local copy and seeing if that works.
Otherwise, if it doesn't contain anything confidential and isn't
too big, you could put a copy of it somewhere and let someone
have a poke at it to see what's wrong.
(I would, but I'm leaving for Queensland for a week tomorrow
morning so am unlikely to be in a position to check it before
then.)
--
Paul TBBle Hampson, on an alternate email client.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
