I like the output of Trace 4, it makes it easy to check user inquiries as
it captures the username, IP, MAC, but the log files get very big due the
the verbose output from the EAP traffic. At the moment I just rotate the
log file a few times a day but is there a better way around that?
Thanks
On 2014-01-03 00:14, rohan.henry @cwjamaica.com wrote:
Hello,
How is a non default port specified when connecting to a remote Oracle server?
Thanks.
DBSource dbi:oracle:server
DBUsername
DBAuth
Rohan
The Oracle InstantClient configuration is in tnsnames.ora, there you specify
things like hos
Hi,
> I like the output of Trace 4, it makes it easy to check user inquiries as
> it captures the username, IP, MAC, but the log files get very big due the
> the verbose output from the EAP traffic. At the moment I just rotate the
> log file a few times a day but is there a better way around th
Hi guys,
we had the issue that our Radiator process was running but the TACACS
socket on port 49 wasn't listening.
It turned out that a restart caused this because either debians
start-stop-daemon or the init script doesn't wait until the process is
really gone and Radiator is started while the old
Hi
Happy New Year
trace 3 only has userid
Judy
--On 03 January 2014 11:06 + a.l.m.bu...@lboro.ac.uk wrote:
> Hi,
>
>> I like the output of Trace 4, it makes it easy to check user inquiries
>> as it captures the username, IP, MAC, but the log files get very big
>> due the the verbose outpu
On 01/03/2014 02:11 PM, Judy Angel wrote:
> trace 3 only has userid
Hello Judy,
try using Trace 4 and add this global configuration parameter:
PacketDumpOmitAttributes EAP-Message
See the reference manual for more, but the above parameter allows you to
list any attributes that should not be in