Or if you want to see it live, <div><br></div><div>/spider/perl/watchdbg</div><div><br></div><div>73 and Happy New Year</div><div><br></div><div>ian<br clear="all"><div>--<br>Ian J Maude, G0VGS<br>SysOp GB7MBC & HB9DRV-9 DX Clusters<br>
If you feel you would like to donate to help the running of the cluster, please visit<br><a href="http://www.gb7mbc.net" target="_blank">http://www.gb7mbc.net</a>.  My thanks in advance :)<br>

</div>
<br><br><div class="gmail_quote">On 1 January 2013 08:38, Dirk Koopman <span dir="ltr"><<a href="mailto:djk@tobit.co.uk" target="_blank">djk@tobit.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 31/12/12 22:43, Bob kc2cwt wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Wich log can you see were user are try to connect<br>
</blockquote>
<br></div>
Depending on what exactly you are wanting there is:<br>
<br>
sh/log<br>
<br>
or<br>
<br>
sh/log k2ls<br>
<br>
if you want to see the logs for a particular callsign.<br>
<br>
If you want more detailed info you can search the debug logs for stuff to do with a particular callsign. In an ssh window do:<br>
<br>
grepdbg k2ls<br>
<br>
Dirk G1TLH<div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<u></u>_________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@dxcluster.org" target="_blank">Dxspider-support@dxcluster.org</a><br>
<a href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" target="_blank">http://mailman.tobit.co.uk/<u></u>mailman/listinfo/dxspider-<u></u>support</a><br>
</div></div></blockquote></div><br></div>