X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-6.html;h=54ffbbc24bb7928800b87a55d911597c638d7921;hb=5b621c40fa6165a9f0eaf592d24a63a174e4b902;hp=a63feeb86b62d68ba2ed2b9362f6375df673024c;hpb=fda0806cc0170c3c2060fbb14033b1fa5f06107d;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 @@
-+
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. +