X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-6.html;h=54ffbbc24bb7928800b87a55d911597c638d7921;hb=cfa4c1acfabeda359815ca58670b4dde4f260a79;hp=a63feeb86b62d68ba2ed2b9362f6375df673024c;hpb=6b892fb053b8a1c28e68d7dd34d6bb006bc18bc5;p=spider.git diff --git a/html/adminmanual-6.html b/html/adminmanual-6.html index a63feeb8..54ffbbc2 100644 --- a/html/adminmanual-6.html +++ b/html/adminmanual-6.html @@ -2,7 +2,7 @@ - The DXSpider Administration Manual v1.49: Information, files and useful programs + The DXSpider Administration Manual v1.50: Information, files and useful programs @@ -273,6 +273,33 @@ ID and password. You also at this point need to set $allow=1 to complete the setup. Many thanks to Fred Lloyd, the proprieter of qrz.com for allowing this access.

+

6.9 Connecting logging programs +

+ +

There appear to be very few logging programs out there that support telnet +especially the popular ones like LogEQF, Turbolog etc. This can make it +difficult to connect to your own cluster! +The way to do it is to make the logging program think it has a TNC attached +to a com port on the logging PC and 'push' a linux login out to it. +This is achieved very simply by the use of agetty. +

+

All that is required is to add a line in /etc/inittab to have the client +ready for a connection on the com port of your choice. Remember that in +Linux, the com ports start at ttyS0 for com1, ttyS1 for com2 etc. +

+

+
+c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
+
+
+

+

Add this after the standard runlevel lines in /etc/inittab. The above +line works on ttyS1 (com2). Now as root, issue the command telinit q +and it should be ready for connection. All that is required is a 3 wire +serial lead (tx, rx and signal ground). Tell you logging program to use +8n1 at 9600 baud and you should see a Linux login prompt. Login as normal +and then telnet from there to the cluster. +

Next Previous