Report forwarded to debian-bugs-dist@lists.debian.org, Peter Tobias <tobias@et-inf.fho-emden.de>:
Bug#9713; Package netstd.   debian-bugs-dist@lists.debian.orgPeter Tobias <tobias@et-inf.fho-emden.de>  Sorry, this message was lost when this bug report was restored from a backup.   Acknowledgement sent to j.sigbrandt@elec.gla.ac.uk:
New bug report received and forwarded. Copy sent to Peter Tobias <tobias@et-inf.fho-emden.de>.   j.sigbrandt@elec.gla.ac.uk  Sorry, this message was lost when this bug report was restored from a backup.   Received: (at submit) by bugs.debian.org; 10 May 1997 13:58:23 +0000 Received: (qmail 6304 invoked from network); 10 May 1997 13:58:22 -0000 Received: from analogue.elec.gla.ac.uk (root@130.209.176.88) by master.debian.org with SMTP; 10 May 1997 13:58:22 -0000 Received: from elec.gla.ac.uk ([127.0.0.1]) by analogue.elec.gla.ac.uk with esmtp (ident jay using rfc1413) id m0wQCf6-0002ZjC (Debian Smail-3.2 1996-Jul-4 #2); Sat, 10 May 1997 14:58:12 +0100 (BST) Message-Id: X-Mailer: exmh version 1.6.9 8/22/96 To: submit@bugs.debian.org Subject: bizarre behaviour with rlogin(?) Reply-To: j.sigbrandt@elec.gla.ac.uk Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_6704366720" Date: Sat, 10 May 1997 14:58:09 +0100 From: "J.Sigbrandt" Package: netstd Version: analogue 2.12_1 (rlogin client) control7 2.13_1 (rlogin server) Hi there, After installing frozen, I've noticed some bizarre behaviour from my rlogined rxvts ... they seem to disappear!!. rxvt seems to be fine other wise, so my suspicions are with rlogin. Here is the output of 'last', (modified to show only the rxvts that were running rlogin from analogue to control7) Notice that only 4 are more than one hour. The rest are either less or between 01:00-01:25. That is really weird (and confirms my suspicion that they keep dying). After further testing it seems they die if having remained idle for 1 hour. Last night (Sat 10 May) I started 10 rxvts and they all died exactly 1 hour later. (there is no idle daemon on either machine) Anyway, this message is simply to alert ppl that something is wrong. I'll keep digging at the problem myself. Regards, jay jay ttyp7 analogue.elec.gl Sat May 10 00:51 - 01:51 (01:00) jay ttyp8 analogue.elec.gl Sat May 10 00:51 - 01:51 (01:00) jay ttypa analogue.elec.gl Sat May 10 00:51 - 01:51 (01:00) jay ttyp9 analogue.elec.gl Sat May 10 00:51 - 01:51 (01:00) jay ttyp6 analogue.elec.gl Sat May 10 00:50 - 01:51 (01:00) jay ttyp4 analogue.elec.gl Sat May 10 00:50 - 01:51 (01:00) jay ttyp5 analogue.elec.gl Sat May 10 00:50 - 01:51 (01:00) jay ttyp3 analogue.elec.gl Sat May 10 00:50 - 01:51 (01:00) jay ttyp2 analogue.elec.gl Sat May 10 00:50 - 01:50 (01:00) jay ttyp1 analogue.elec.gl Sat May 10 00:50 - 01:50 (01:00) jay ttyp0 analogue.elec.gl Fri May 9 23:43 - 01:50 (02:07) jay ttyp0 analogue.elec.gl Fri May 9 16:26 - 17:37 (01:10) jay ttyp0 analogue.elec.gl Fri May 9 12:22 - 13:24 (01:02) jay ttyp0 analogue.elec.gl Thu May 8 20:26 - 21:51 (01:25) jay ttyp0 analogue.elec.gl Thu May 8 11:41 - 12:41 (01:00) jay ttyp0 analogue.elec.gl Wed May 7 15:28 - 16:30 (01:02) jay ttyp0 analogue.elec.gl Mon May 5 19:50 - 13:24 (1+17:33) jay ttyp0 analogue.elec.gl Mon May 5 18:26 - 19:27 (01:01) jay ttyp0 analogue.elec.gl Mon May 5 16:19 - 17:21 (01:01) jay ttyp0 analogue.elec.gl Mon May 5 15:40 - 15:45 (00:04) jay ttyp0 analogue.elec.gl Sun May 4 23:35 - 00:39 (01:03) jay ttyp0 analogue.elec.gl Sun May 4 19:36 - 20:41 (01:04) jay ttyp0 analogue.elec.gl Sat May 3 21:20 - 21:21 (00:01) jay ttyp0 analogue.elec.gl Sat May 3 20:14 - 21:19 (01:05) jay ttyp0 analogue.elec.gl Sat May 3 16:55 - 17:56 (01:01) jay ttyp0 analogue.elec.gl Sat May 3 14:43 - 15:48 (01:05) jay ttyp1 analogue.elec.gl Fri May 2 16:47 - 11:00 (18:12) jay ttyp0 analogue.elec.gl Fri May 2 13:45 - 11:00 (21:14) jay ttyp1 analogue:0.0 Thu May 1 22:58 - 23:03 (00:04) jay ttyp0 analogue.elec.gl Thu May 1 22:57 - 22:58 (00:00) The command that starts the rxvt, from my .fvwmrc is: Exec "control7" exec rxvt -bg SlateGrey -fg white -T control7 \ -e rlogin control7 & Which doesn't seem to be too esoteric ;) analogue is running 1.2 whereas control7 is running 1.3beta   Reply sent to tobias@et-inf.fho-emden.de:
You have taken responsibility.   tobias@et-inf.fho-emden.de  Sorry, this message was lost when this bug report was restored from a backup.   Done: "Peter Tobias" <tobias@server.et-inf.fho-emden.de>; Maintainer for netstd is Peter Tobias <tobias@et-inf.fho-emden.de>.

Message received at 9713-done@bugs.debian.org:


Received: (at 9713-done) by bugs.debian.org; 19 Jun 1997 22:33:23 +0000
Received: (qmail 10784 invoked from network); 19 Jun 1997 22:33:21 -0000
Received: from server.et-inf.fho-emden.de (192.129.16.1)
  by master.debian.org with SMTP; 19 Jun 1997 22:33:20 -0000
Received: (from tobias@localhost) by server.et-inf.fho-emden.de (8.8.5/8.7.3) id AAA13564; Fri, 20 Jun 1997 00:30:07 +0200
Message-Id: <199706192230.AAA13564@server.et-inf.fho-emden.de>
Subject: Re: Bug#9713: bizarre behaviour with rlogin(?)
To: j.sigbrandt@elec.gla.ac.uk
Date: Fri, 20 Jun 1997 00:30:06 +0200 (MET DST)
From: "Peter Tobias" <tobias@server.et-inf.fho-emden.de>
Cc: 9713-done@bugs.debian.org
Reply-To: tobias@et-inf.fho-emden.de
In-Reply-To: <m0wel5h-0002ZsC@analogue.elec.gla.ac.uk> from "J.Sigbrandt" at Jun 19, 97 06:33:47 pm
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit

J.Sigbrandt wrote:
> > > Tried changing the shell in my /etc/passwd to bash
> > > The problem did not occur!!! (either starting manually or starting
> > > via fvwm)
> > 
> > It seems to me that this is a tcsh problem and not a rlogin problem.
> 
> Yes.

Ok, I'll close the bug-report with this mail. Thank you for your time.


Thanks,

Peter

-- 
Peter Tobias <tobias@et-inf.fho-emden.de> <tobias@debian.org> <tobias@linux.de>
PGP ID EFAA400D, fingerprint = 06 89 EB 2E 01 7C B4 02  04 62 89 6C 2F DD F1 3C 


Notification sent to j.sigbrandt@elec.gla.ac.uk:
Bug acknowledged by developer.   j.sigbrandt@elec.gla.ac.uk  Sorry, this message was lost when this bug report was restored from a backup.