[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#182656: marked as done (snooper: i only have one computer and one modem)

Your message dated Tue, 16 Feb 2010 19:02:09 +0000
with message-id <E1NhSgT-0006lL-8T@ries.debian.org>
and subject line Bug#182656: fixed in snooper 19991202-7
has caused the Debian Bug report #182656,
regarding snooper: i only have one computer and one modem
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
182656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=182656
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: snooper
Version: 19991202-3
Severity: wishlist
Tags: upstream

here is a record of my first impressions of this program, in order for
you to beef up the docs.

i do man snooper.  i only have one computer and one modem. i read the
man page but cant figure out how to trace communication between my
computer and my modem.

$ snooper 
no device specified
08:44 1 ~$ snooper /dev/ttyS0
no device specified
08:44 1 ~$ snooper /dev/tty /dev/ttyS0
ioctl(TIOCMGET): Invalid argument
                                 08:45 1 ~$ 08:45 1 ~$ 08:45 1 ~$ stty sane
08:45 ~$ snooper /dev/ttyS0 /dev/tty 
ioctl(TIOCMGET): Invalid argument

i now suppose i should look at /usr/share/doc/snooper/
yes, i am in dialout.

more guessing about how to record e.g. what minicom etc. really says
to the modem,

$ snooper /tmp/a /dev/ttyS0
inappropriate devices specified

you see,
     "It is also possible to operate with a single serial device, using your
     console and keyboard as the second device."
is a mystery to me.

$ snooper /dev/null /dev/ttyS0
tcgetattr: Inappropriate ioctl for device
$ snooper  /dev/ttyS0 /dev/null
tcgetattr: Inappropriate ioctl for device

who knows.

     C       Make the console act as one of the serial lines. 

sounds great, if i could only start the program.

snooper /dev/ttyS0  /dev/ttyS0
works
by the way, the screen should note Q to Quit, etc. maybe

ok, in another window
$ minicom 
Device /dev/ttyS0 is locked.

ok, using snooper -u and minicom and... Segmentation fault

ok i try just snooper /dev/ttyS0  /dev/ttyS0
and no minicom and use C /dev/ttyS0 and type one char ans Segmentation
fault

ok now try C 0
same fault.

anyway maybe instead of telling me how to use the program. beef up the
docs for all to enjoy.

ok, i will find a more appropriate program via
$ apt-cache search serial|sort

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux debian 2.4.20-k7 #1 Tue Jan 14 00:29:06 EST 2003 i686
Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5

Versions of packages snooper depends on:
ii  libc6                     2.3.1-10       GNU C Library: Shared libraries an
ii  liblockdev1               1.0.1-4.1      Run-time shared library for lockin
ii  libncurses5               5.3.20021109-2 Shared libraries for terminal hand

-- no debconf information

--- End Message ---
--- Begin Message --- 
Source: snooper
Source-Version: 19991202-7

We believe that the bug you reported is fixed in the latest version of
snooper, which is due to be installed in the Debian FTP archive:

snooper_19991202-7.diff.gz
  to main/s/snooper/snooper_19991202-7.diff.gz
snooper_19991202-7.dsc
  to main/s/snooper/snooper_19991202-7.dsc
snooper_19991202-7_amd64.deb
  to main/s/snooper/snooper_19991202-7_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 182656@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stefan Bauer <stefan.bauer@cubewerk.de> (supplier of updated snooper package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Mon, 15 Feb 2010 09:51:17 +0100
Source: snooper
Binary: snooper
Architecture: source amd64
Version: 19991202-7
Distribution: unstable
Urgency: low
Maintainer: Stefan Bauer <stefan.bauer@cubewerk.de>
Changed-By: Stefan Bauer <stefan.bauer@cubewerk.de>
Description: 
 snooper    - Captures communication between two external serial devices
Closes: 182656 474336 487735
Changes: 
 snooper (19991202-7) unstable; urgency=low
 .
   * New Maintainer (Closes: #487735, #474336)
   * Acknowledge NMU changes
   * Bump Standards to 3.8.4
   * Get the package lintian clean
   * Bump debhelper dependecies to 7.0.50
   * Extended README.Debian to show howto snoop traffic with only one
     computer and a modem (Closes: #182656)
Checksums-Sha1: 
 9d212abebb34ea7dc4a366782f92da9b24bfb7b7 1037 snooper_19991202-7.dsc
 31b61dfc3eaf4247e12c0608d9ad251122335b9d 10418 snooper_19991202-7.diff.gz
 36525cf455c012efbb46ddf7ba15c2ba6f988996 19826 snooper_19991202-7_amd64.deb
Checksums-Sha256: 
 9ab5070ee46d67741d3d33aa14f25cbc2f1044d4c6b9fa2a1a419da33f85fc42 1037 snooper_19991202-7.dsc
 d83e912bc53dd8db1847537f2347188a35486c4cad5bbb7617c00594350c507e 10418 snooper_19991202-7.diff.gz
 2efc19ce37ec7837b385f97297d64a4bfa4247566e4720b52bf07526a6b733bd 19826 snooper_19991202-7_amd64.deb
Files: 
 e41eb41be49bc62d486367ffb524e6c7 1037 comm optional snooper_19991202-7.dsc
 70e763e8dc00a9708ab5aba4a5ce2baf 10418 comm optional snooper_19991202-7.diff.gz
 b856896e70e83af2842203ace3b6a65c 19826 comm optional snooper_19991202-7_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLeuksVkEm8inxm9ERArAGAJ4idat1HsRcd2B6Y3yiIA+q5iDeGwCeKJK+
Pi4v+f/M9fExaLWrlD/tkXI=
=SlGR
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: