[100616.26@compuserve.com: uugetty or mgetty callback ?]

steve@work.bellingham.wa.us (steve@work.bellingham.wa.us)
Thu, 19 Oct 1995 23:16:00 +0100


This came to me, I'm forwarding it to the list because I don't
remember the upshot of the long discussion on callback those many
months ago.  Please respond directly to him.  Thanks.

Steven Work
Renaissance Labs
+1 360 647-1833, fax too
steve@work.bellingham.wa.us

-------------------- snip --------------------
Date: 19 Oct 95 06:13:00 EDT
From: Frank Hofmann <100616.26@compuserve.com>
To: Steve Work <Steve@work.bellingham.wa.us>
Subject: uugetty or mgetty callback ?

Hello Steve

I have a problem with my linux firewall. I've installed Linux Kernel 1.1.62 with
uugetty to handle the modem. This functionally very well. I use the firewall to
login in my firm network with slip. uugetty is still waiting for a call, when it
comes the modem pick up the line and make the connection with diplogin. 

My modem has a build in callback funktion. I can store a callback-number in the
memory of the modem. When i call the modem, he pick up the line and make the
handshake. When handshake is finish, the modem hangs up and will dial the stored
number in the memory of the modem. When the modem begins to dial, the init
process is initialize the uugetty process and the callback is terminated. Is it
possible, to prevent uugetty for initialize the port ? I use the respawn
funktion in /etc/gettydefs. 

Have you an idea ,how can I realise a callback funktion under linux to save tall
charge ?? Has mgetty from Gerd Doering a build in callback funktion ?

Thanks in advance
Greetings from Frank in Germany