Your message dated Tue, 17 Apr 2001 22:11:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#24660: mserver: Is tcpconn working?
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 16 Jul 1998 14:02:27 +0000
Received: (qmail 30730 invoked from network); 16 Jul 1998 14:02:24 -0000
Received: from ns2.dipa.de ([EMAIL PROTECTED])
by debian.novare.net with SMTP; 16 Jul 1998 14:02:24 -0000
Received: from marvin.dipa.de.local ([EMAIL PROTECTED] [192.168.1.42])
by ns2.dipa.de (8.8.8/8.8.8/Debian/GNU) with ESMTP id QAA05448
for <[EMAIL PROTECTED]>; Thu, 16 Jul 1998 16:02:20 +0200
Message-ID: <[EMAIL PROTECTED]>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Thu, 16 Jul 1998 16:02:28 +0200 (CEST)
From: Florian Hinzmann <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: mserver: Is tcpconn working?
Package: mserver
Version: 0.21-3
Hi!
Maybe part of my mail should be wishlist, not a
bug report.
At least one thing is a bug:
>bash$ tcpconn
>Segmentation fault (core dumped)
>bash$
And now a more generic question:
I have a modem connected to one Debian box
with mserver running.
Now I would like to use the modem from
another computer.
Mserver seems to work ok:
>bash$ telnet modemserver:5800
>Trying xx.xx.xx.xx...
>Connected to modemserver.
>Escape character is '^]'.
>atz
>atz
>
>OK
While connected to modemserver:5800 there is a
lockfile /var/lock/LCK..ttyS1. Everything fine
so far.
Now I would like to use minicom wich only works
with devices. After reading the tcpconn manpage
I thought 'tcpconn -d /dev/ttyp0 modemserver'
would redirect input and output to /dev/ttyp0
so I would be able to use minicom with that
device.
But if I start minicom everything I type inside
minicom is output to the terminal running tcpconn.
Isn't tcpconn meant to redirect input AND output
to a device? Is ttyp[0-9] the right device to
use?
My system is slink and up-to-date with ftp.de.debian.org.
Thanks,
Florian
-- System Information
Debian Release: 2.0
Kernel Version: Linux marvin 2.0.34 #2 Thu Jul 9 10:57:48 EST 1998 i586 unknown
Versions of the packages mserver depends on:
ii libc6 2.0.7s-1 The GNU C library version 2 (run-time files)
--
Florian Hinzmann [EMAIL PROTECTED]
---------------------------------------
Received: (at 24660-done) by bugs.debian.org; 17 Apr 2001 20:13:30 +0000
>From [EMAIL PROTECTED] Tue Apr 17 15:13:30 2001
Return-path: <[EMAIL PROTECTED]>
Received: from jagor.srce.hr [161.53.2.130] (root)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14pbqr-00072r-00; Tue, 17 Apr 2001 15:13:30 -0500
Received: from om (asy168.jmu.carnet.hr [193.198.129.48])
by jagor.srce.hr (8.9.0/8.9.0) with ESMTP id WAA22235
for <[EMAIL PROTECTED]>; Tue, 17 Apr 2001 22:13:25 +0200 (MET DST)
Received: from mvela by om with local (Exim 3.22 #1 (Debian))
id 14pbp8-0003jI-00
for <[EMAIL PROTECTED]>; Tue, 17 Apr 2001 22:11:42 +0200
Date: Tue, 17 Apr 2001 22:11:39 +0200
From: Matej Vela <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Bug#24660: mserver: Is tcpconn working?
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <[EMAIL PROTECTED]>; from [EMAIL PROTECTED] on Thu, Jul 16, 1998
at 04:02:28PM +0200
X-Accept-Language: en, hr
Sender: Matej Vela <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Hi,
I apologize for the incredibly long reply time, but both the Debian and
the upstream maintainer seem to have lost interest in mserver.
On Thu, Jul 16, 1998 at 04:02:28PM +0200, Florian Hinzmann wrote:
> Package: mserver
> Version: 0.21-3
>
[...]
> At least one thing is a bug:
>
> >bash$ tcpconn
> >Segmentation fault (core dumped)
> >bash$
This has been fixed in 0.23a-1.
> And now a more generic question:
>
[...]
> Now I would like to use minicom wich only works
> with devices. After reading the tcpconn manpage
> I thought 'tcpconn -d /dev/ttyp0 modemserver'
> would redirect input and output to /dev/ttyp0
> so I would be able to use minicom with that
> device.
> But if I start minicom everything I type inside
> minicom is output to the terminal running tcpconn.
>
> Isn't tcpconn meant to redirect input AND output
> to a device? Is ttyp[0-9] the right device to
> use?
[...]
If you read README.tcpconn carefully, you'll see that tcpconn is run on
a pty (i.e. master) device, and cu is run on a tty (i.e. slave) device:
$ tcpconn -d /dev/ptyq0 modemserver &
$ minicom -p /dev/ttyq0
However, since this approach doesn't work with Unix98 pseudo-terminals,
mserver 0.23a-2 has been extended to allocate ptys automatically:
$ minicom -p `tcpconn -d modemserver`
Thanks,
Matej
