Your message dated Thu, 28 Dec 2006 18:02:17 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: fsh
Version: 1.2-2
Severity: normal
For reasons that I can't determine, the change to os.close(2) on the
child, in order to ensure proper daemonisation, does not work on one
of my systems.
It works on my debian laptop, fshing to itself and other hosts. But
fails elsewhere. There are only 2 things I can think of: the version
of python used, and the fact that in the former case, the client is
openssh, and in the latter, it is commercial-ssh.
python version:
28600,2> python -V
Python 2.3.4
openssh version:
28603,5> ssh -V
OpenSSH_3.8.1p1 Debian-8.sarge.4, OpenSSL 0.9.7e 25 Oct 2004
But it fails on another host (not debian):
122645,9> fsh localhost hostname -f
Tunnel closed.
Traceback (most recent call last):
File "/home/office/tconnors/software/Linux-i686/bin/fsh", line 8, in ?
fsh.main()
File "/home/office/tconnors/software/Linux-i686/share/fsh/fsh.py", line 395,
in main
fshd_timeout)
File "/home/office/tconnors/software/Linux-i686/share/fsh/fsh.py", line 247,
in docmd
rem = remote(method, login, use_l_flag, server, command, fshd_timeout)
File "/home/office/tconnors/software/Linux-i686/share/fsh/fsh.py", line 55,
in __init__
time.sleep(1)
KeyboardInterrupt
python version:
122647,11> python -V
Python 2.2.2
openssh version:
122648,12> ssh -V
ssh: SSH Secure Shell 3.1.0 (non-commercial version) on i686-pc-linux-gnu
If it turns out that one of these are at fault, no conflicts is
currently specified in the .deb - perhaps there should be one?
Of course, if there is a real code problem, it'd be nice to fix that
too, but I have no idea what is going wrong. An strace isn't giving me
any useful information. Perhaps I can help with further info, but I
don't know what...
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.26
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Versions of packages fsh depends on:
ii python 2.3.4-5 An interactive high-level object-o
ii ssh [rsh-client] 1:3.8.1p1-8.sarge.4 Secure rlogin/rsh/rcp replacement
-- no debconf information
--- End Message ---
--- Begin Message ---
Removed - obsoleted by openssh.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
