topic Re: /usr/bin/cu CTRL-C not quitting in Operating System - Linux

/usr/bin/cu CTRL-C not quitting

John Waller — Thu, 25 Nov 2004 12:32:47 GMT

I have installed uucp 1.07.78 uucp package on a SuSE 9.0 professional system, kernel 2.4.21-99-smp4G. Everything works OK except when I use cu to dial a remote system I cannot use CTRL-C to quit if the line is busy or does not answer. The output when dialing is

/usr/bin/cu -I /etc/uucp/config -x6 john
./cu: fconn_open: Opening port ACU1 (speed 19200)
./cu: fconn_set: Changing setting to 0, 0, 2
./cu: fcsend: Writing "AT\r"
./cu: icexpect: Looking for 2 "OK"
./cu: icexpect: Got "AT\r\r\nOK" (found it)
./cu: fcsend: Writing "ATDT" \T "537334\r"
./cu: icexpect: Looking for 7 "CONNECT"
./cu: icexpect: Got "\r\nATDT537334\r./cu: Got interrupt signal
./cu: Got interrupt signal

Any ideas as I don't have the problem when I use the same modem on an HP-UX 11.00 system.

Re: /usr/bin/cu CTRL-C not quitting

Bojan Nemec — Thu, 25 Nov 2004 15:53:42 GMT

John,

I try on my RedHat 9 uucp 1.06.1. The results are same, no CTRL-C.
As a workarround you can use CTRL-Z follow by a kill %1 .
Maybe this workarround will be sufficient for you.

Bojan

Re: /usr/bin/cu CTRL-C not quitting

Stuart Browne — Thu, 25 Nov 2004 19:22:47 GMT

Odd.. Does ~. dump out at this point? It should be too early for the ~ commands to work, but if it's doing signal capturing like this, then it might have started capturing ~ events too.

Re: /usr/bin/cu CTRL-C not quitting

John Waller — Fri, 26 Nov 2004 02:38:14 GMT

Many thanks for the responces.
Yes the Ctrl-Z would work but simple users use these modems for supporting an application on remote sites. If I start telling them tricks like Ctrl-Z we could have lots of background jobs running on Customers machines. Also I believe that if you dial to an HP system and CTRL-Z then forget to kill %1 before logging out it puts a lock on the port that rprevents you from re-connecting.
Stuart, in answer to your question, no ~. does not work. The only other way out I have found is Ctrl-\ but like the Ctrl-Z I don't like he idea of letting that into the open if other options are available.
I thought I saw on the Web some source for the cu command which talked about allowing and ignoreing interrupts but I can't find the page again. I've downloaded the UUCP source myself but can't find it.

Re: /usr/bin/cu CTRL-C not quitting

Stuart Browne — Sun, 28 Nov 2004 18:09:04 GMT

I guess you should be looking for when it 'trap''s the signal, and make it later in the dialing sequence..

I've not looked myself, sorry I can't be of more help.