On Sun, Jan 16, 2005 at 11:15:35PM -0600, Sam Morris wrote:
> Hello

> After much hair pulling I have Freeradius 1.0.1 working nearly 100%. But I'm
> having issues with radutmp (at least I think that's where the trouble
> lies).

> When I do a radlast, it says this:

> [EMAIL PROTECTED] radius]# radlast
>  
> radwtmp begins Sun Jan 16 17:00:27 2005

Radlast uses radwtmp, radutmp is used by radwho...  radutmp has it's own
module, but radwtmp is written by the unix module, which I'm gonna guess
you've disabled since you're not using unix accounts to authenticate.

If that's true, you can just put the unix instance in the accounting
section, and all if will do is write to radwtmp. (Which is pretty neat,
actually. ^_^)

> This even though hundreds of people have logged in (via dialup).

> radlast <username> also shows nothing.

> So it is authenticating people and logging those authentications
> just fine. It's also writing the detail files in /var/log/radius/radacct/<nas>

> The radutmp and radwtmp files ARE getting written in /var/log/radius/<here>

I found something was creating radwtmp even though I'm not using it, but
I haven't bothered to find out _what_... I think something in the
default start script must touch it, since it seems to exist but be 0
bytes long. Presumably this is to ensure correct permissions on the
file, since I think it is by default treated like wtmp and readable by
anyone. (Like safe_radutmp and unlike radutmp instances in the default
radius.conf)

-- 
Paul "TBBle" Hampson, on an alternate email client.

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to