Hi!
I still have problems, this is my output from 'who':
admin pts/0 02:50 Apr 5 07:24:09 x.x.x.x
admin pts/1 00:00 Apr 5 09:39:05 y.y.y.y
current time:
Fri Apr 5 10:18:27 CEST 2013
shouldn't the first session be timed out? It has not just been
Are you using -K ? I wouldn't expect it to time out otherwise. As an
example I hibernate my computer nightly but connections remain alive in
the morning.
Cheers,
Matt
On 2013-04-05 16:25, Mattias Walström wrote:
Hi!
I still have problems, this is my output from 'who':
admin pts/0
2013/4/5 Matt Johnston m...@ucc.asn.au:
Are you using -K ? I wouldn't expect it to time out otherwise. As an example
I hibernate my computer nightly but connections remain alive in the morning.
I got same issue with 2012.55-1.3@debian(debian does not have 2013.56
at the moment) without -K
2013/4/5 Matt Johnston m...@ucc.asn.au:
Roy Tam roy...@gmail.com wrote:
I got same issue with 2012.55-1.3@debian(debian does not have 2013.56
at the moment) without -K switch.
Once I not issuing 'exit' command but closing putty window directly,
the session leaves alone.
That sounds exactly
I am not using Keepalive. Why is keepalive required? If reading the manual
understood that was to make sure firewalls did not close the connection.
Shouldn't a TCP socket timeout in maximum 15 minutes by itself?
Mattias
On 2013-04-05 13:18, Matt Johnston wrote:
Are you using -K ? I wouldn't
Actually.. when I looked at it again. My first session has been closed, it took
some while, but at last it seems like it was closed.
I just read more about TCP timeouts, must have mixed things up. It is rather
long, but it seems that dropbear now clean upp after itself.
Now in who, I can see
