Loïc Grenié thanks!! Work well! I was trying to do a script exactly
like your script! Thanks and again thanks!
--- Begin Message ---
Hi,
Le mar. 21 juin 2022 à 10:14, Conti Stefano a écrit :
> Hello! In My Debian 11 SSH timeout logoff not work! I must put in .bashrc
> of my user:
Hi,
Le mar. 21 juin 2022 à 10:14, Conti Stefano a écrit :
> Hello! In My Debian 11 SSH timeout logoff not work! I must put in .bashrc
> of my user: TMOUT=600 to loogut after 10 minutes. Work, of course, but
> close all bash terminal!
>
> This is my sshd_config with i
Le mardi 21 juin 2022 à 23:40 +0200, didier gaumet a écrit :
[...]
> - if you want to restrict the time of ssh connection and are in
> position to modify the ssh command they use (an alias in their bashrc
> for example?), perhaps you can try to force the ssh -o option with
> the ConnectTimeout par
Le mardi 21 juin 2022 à 12:52 +0200, Conti Stefano a écrit :
> If I put ClientAliveCountMax 1 with ClientAliveInterval 600 timeout
> is 1200 inmy Debian 11. I have try all combinations but at the moment
> nothing happen; session stay alive! There is somethng but i don't
> understand what keep al
On Tue, Jun 21, 2022 at 6:04 AM Greg Wooledge wrote:
> On Tue, Jun 21, 2022 at 10:05:43AM +0200, Conti Stefano wrote:
> > Hello! In My Debian 11 SSH timeout logoff not work! I must put in
> > .bashrc of my user: TMOUT=600 to loogut after 10 minutes. Work, of
> > cours
On Tue, Jun 21, 2022 at 02:02:38PM +0200, Conti Stefano wrote:
> Excuse me but i sure you that i use this practice from many years and
> always work in the past. I've a other distro, an "old" Debian 9 and a
> Centos 7 with SSH version 7.4p1 and i'm sure work all well because i
> put ClientAliveInt
However thanks for your time of course!
On Tue, Jun 21, 2022 at 10:05:43AM +0200, Conti Stefano wrote:
> Hello! In My Debian 11 SSH timeout logoff not work! I must put in
> .bashrc of my user: TMOUT=600 to loogut after 10 minutes. Work, of
> course, but close all bash terminal!
>
On Tue, Jun 21, 2022 at 10:05:43AM +0200, Conti Stefano wrote:
> Hello! In My Debian 11 SSH timeout logoff not work! I must put in
> .bashrc of my user: TMOUT=600 to loogut after 10 minutes. Work, of
> course, but close all bash terminal!
>
> This is my sshd_config with i
à 10:05 +0200, Conti Stefano a écrit :
> Hello! In My Debian 11 SSH timeout logoff not work! I must put in
> .bashrc of my user: TMOUT=600 to loogut after 10 minutes. Work, of
> course, but close all bash terminal!
>
> This is my sshd_config with info for timeout:
Le mardi 21 juin 2022 à 10:05 +0200, Conti Stefano a écrit :
> Hello! In My Debian 11 SSH timeout logoff not work! I must put in
> .bashrc of my user: TMOUT=600 to loogut after 10 minutes. Work, of
> course, but close all bash terminal!
>
> This is my sshd_config with i
Hello! In My Debian 11 SSH timeout logoff not work! I must put in
.bashrc of my user: TMOUT=600 to loogut after 10 minutes. Work, of
course, but close all bash terminal!
This is my sshd_config with info for timeout:
TCPKeepAlive no
ClientAliveInterval 600
ClientAliveCountMax 0
Any suggest?
anyone know a way to set the timeout in ssh on the
command. I have some servers that take to long to connect and ssh times out.
However I can us PuTTY and connect.
Tony
On Thu, Jul 08 at 04:15PM +0200, Dennis Stosberg wrote:
> Sure, this is not a solution this time. But maybe it is a solution
> for the next time:
>
> $ ssh [EMAIL PROTECTED]
> Welcome to remotehost
> $ screen
> $ long_task
>
> When you press C-a C-d now, you detach yourself from your screen
> se
On Thu, Jul 08 at 09:50AM -0500, Alan Shutko wrote:
> Right, it won't work for this time. But if one uses screen
> every time they log in, one will always be able to resume,
> whether it times out because of ping, whether the phone line
> gets cut, whether the client machine reboots
but not i
Steve Lamb <[EMAIL PROTECTED]> writes:
> Brad Sims wrote:
>> Nope, but thats why the fine folks at GNU made screen
>
> Screen has me so spoiled I wish I could do the same with
> individal X programs. I know I can do a whole session with VNC but
> I'd love to be able to start a program on one X s
Joost De Cock wrote:
Is there any way to pick up where I left?
No, nor should there be.
When your SSH session dies the shell you were running dies with it.
Someone else mentioned screen. It works well.
Really though, you need to find out why your SSH sessions are "timing
out". I can leave SSH se
On Thu, 2004-07-08 at 22:48, Jon Dowland wrote:
> On Thu, 8 Jul 2004 14:24:09 +0200, Joost De Cock <[EMAIL PROTECTED]> wrote:
> > On Thursday 08 July 2004 14:00, LeVA hurled the following on the wire:
> > > 2004. július 8. 13:54,
> > > Joost De Cock <[EMAIL PROTECTED]>
> > >
> > > -> [EMAIL PROTECT
Brad Sims wrote:
> Nope, but thats why the fine folks at GNU made screen
Screen has me so spoiled I wish I could do the same with individal X
programs. I know I can do a whole session with VNC but I'd love to be able to
start a program on one X session (say my VNC session) and then eventuall
On Thursday 08 July 2004 6:54 am, Joost De Cock wrote:
> I'd like to know if it's possible to pick up a shell session that was running
> over a ssh session that timed out.
Nope, but thats why the fine folks at GNU made screen
I use it all the damn time, over a ssh session that goes down at rand
LeVA <[EMAIL PROTECTED]> writes:
> That is not a solution for the original problem. If you've read that
> mail, then you should know that it was about a ping timeoutted session,
> which is irrecoverable... The solution which you are talking about, is
> for *keeping* alive that session while not
Am 08.07.2004 um 14:11 schrieb LeVA:
> > Oh, but it is, by using screen(1), for example.
> That is not a solution for the original problem. If you've read that
> mail, then you should know that it was about a ping timeoutted session,
> which is irrecoverable... The solution which you are talking
On Thu, 8 Jul 2004 14:24:09 +0200, Joost De Cock <[EMAIL PROTECTED]> wrote:
> On Thursday 08 July 2004 14:00, LeVA hurled the following on the wire:
> > 2004. július 8. 13:54,
> > Joost De Cock <[EMAIL PROTECTED]>
> >
> > -> [EMAIL PROTECTED]:
> > > Hello list,
> > >
> > > I'd like to know if it's
On Thursday 08 July 2004 14:00, LeVA hurled the following on the wire:
> 2004. július 8. 13:54,
> Joost De Cock <[EMAIL PROTECTED]>
>
> -> [EMAIL PROTECTED]:
> > Hello list,
> >
> > I'd like to know if it's possible to pick up a shell session that was
> > running over a ssh session that timed out.
2004. július 8. 14:11,
LeVA <[EMAIL PROTECTED]>
-> [EMAIL PROTECTED]:
> 2004. július 8. 14:03,
> Robert Waldner <[EMAIL PROTECTED]>
>
> -> [EMAIL PROTECTED]:
> > On Thu, 08 Jul 2004 14:00:15 +0200, LeVA writes:
> > >> I'd like to know if it's possible to pick up a shell session
> > >> that was run
2004. július 8. 14:03,
Robert Waldner <[EMAIL PROTECTED]>
-> [EMAIL PROTECTED]:
> On Thu, 08 Jul 2004 14:00:15 +0200, LeVA writes:
> >> I'd like to know if it's possible to pick up a shell session that
> >> was running over a ssh session that timed out.
>
> <...>
>
> >> Is there any way to pick up
On Thu, 08 Jul 2004 14:00:15 +0200, LeVA writes:
>> I'd like to know if it's possible to pick up a shell session that was
>> running over a ssh session that timed out.
<...>
>> Is there any way to pick up where I left?
>This is not possible (thanks God!)
Oh, but it is, by using screen(1), for ex
2004. július 8. 13:54,
Joost De Cock <[EMAIL PROTECTED]>
-> [EMAIL PROTECTED]:
> Hello list,
>
> I'd like to know if it's possible to pick up a shell session that was
> running over a ssh session that timed out.
>
> Here's what I mean:
>
> SSH into the webserver at the 7th floor (I'm on the 4th),
Hello list,
I'd like to know if it's possible to pick up a shell session that was running
over a ssh session that timed out.
Here's what I mean:
SSH into the webserver at the 7th floor (I'm on the 4th), start up something
(say apt-get dist-upgrade), next thing the phone rings, hey Angelina wha
28 matches
Mail list logo
