Re: locking problem FreeBSD 3.4 - kermit and mgetty
Hi, On Thu, Jan 27, 2000 at 07:03:38PM +0100, Christoph Kukulies wrote: > > > But as a result mgetty gets into kermit's ways such that when a > > > modem connection is made I suddenly get a modem prompt like > > > +FCON as if someone (mgetty) is either messing with my local > > > or the remote modem while kermit opens the connection. > > > > The modem is in fax mode, and has established a fax connection. Have > > kermit send an AT+FCLASS=0 first. > > OK, this may be a repair but I'm wondering why that worked before > and now I have to take special measures. Or is it perhaps > kermit's fault? Older mgetty versions had all class 2 modems in "class 0 mode" while waiting for incoming calls, which worked very well for some Rockwell modems, and not so well for others. With class 2.0 modems, the modem always *had* to be in fax mode. Recently, I changed the settings so that some class 2 modems are also run in "class 2 mode", so maybe that triggered the problem at your end. gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany [EMAIL PROTECTED] fax: +49-89-35655025[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: locking problem FreeBSD 3.4 - kermit and mgetty
On Wed, Jan 26, 2000 at 11:13:55PM +0100, Gert Doering wrote: > Hi, > > On Tue, Jan 25, 2000 at 08:51:40PM +0100, Christoph Kukulies wrote: > > But as a result mgetty gets into kermit's ways such that when a > > modem connection is made I suddenly get a modem prompt like > > +FCON as if someone (mgetty) is either messing with my local > > or the remote modem while kermit opens the connection. > > The modem is in fax mode, and has established a fax connection. Have > kermit send an AT+FCLASS=0 first. OK, this may be a repair but I'm wondering why that worked before and now I have to take special measures. Or is it perhaps kermit's fault? > > gert > -- > USENET is *not* the non-clickable part of WWW! >//www.muc.de/~gert/ > Gert Doering - Munich, Germany [EMAIL PROTECTED] > fax: +49-89-35655025[EMAIL PROTECTED] -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: locking problem FreeBSD 3.4 - kermit and mgetty
Hi, On Tue, Jan 25, 2000 at 08:51:40PM +0100, Christoph Kukulies wrote: > But as a result mgetty gets into kermit's ways such that when a > modem connection is made I suddenly get a modem prompt like > +FCON as if someone (mgetty) is either messing with my local > or the remote modem while kermit opens the connection. The modem is in fax mode, and has established a fax connection. Have kermit send an AT+FCLASS=0 first. gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany [EMAIL PROTECTED] fax: +49-89-35655025[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
locking problem FreeBSD 3.4 - kermit and mgetty
C-Kermit 7.0.196 Beta.11, 6 Dec 1999, for FreeBSD 3.0 mgetty: experimental test release 1.1.21-Jul24 FreeBSD 3.4 I had running kermit and mgetty running happily together, one not disturbing the other (I had a mgetty running on cuaa1 (/etc/ttys)) and when I hand dialed via kermit mgetty got politely out of the way. (never cared about it - it used to work under FreeBSD 2.2.8). Now after an upgrade to FreeBSD 3.4 I added the packages above (kermit and mgetty) to have up-to-date binaries. But as a result mgetty gets into kermit's ways such that when a modem connection is made I suddenly get a modem prompt like +FCON as if someone (mgetty) is either messing with my local or the remote modem while kermit opens the connection. Clueless. Can only do a kill -TSTP 1 , kill the last mgetty and use kermit and have to kill -HUP 1 after that. -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
