Well I been working on this system in some form or another for about a
month, which when done is going to be able (so I am told) to limit the
bandwidth that the connected users (be it wired or wireless clients) can
use using squid/squish/hostapd/freeradius/daloradius (so when I leave
someone
Alan DeKok-2 wrote:
Uh... packets are not signals. Use ktrace to monitor signals sent
to a process.
Well, I've now monitored an Exiting normally event using ktrace:
/var/log/radius.log:
Sat Dec 18 02:43:43 2010 : Info: Exiting normally.
/var/log/messages:
Dec 18 02:43:43 radius
Danial wrote:
Well, I've now monitored an Exiting normally event using ktrace:
That helps.
655 radiusd RET write 84/0x54
655 radiusd CALL close(0xa)
655 radiusd RET close 0
655 radiusd PSIG SIGSEGV SIG_DFL
Ugh.
It seems I can semi-reliably replicate this
Surprising, put it back to the condition it is in when you first install
it and started with the Basic configuration HOWTO and then moved on to
the SQL HOWTO and it worked for the test with the username and
password in the users file and then again with a different user in the
database. The
4 matches
Mail list logo