From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Re: Core 100
Date: Mon, 04 Apr 2016 11:35:52 -0500 [thread overview]
Message-ID: <570297E8.6030201@dailydata.net> (raw)
In-Reply-To: <7ced6eed589fe81f98a71b4f13e87537@mail01.ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
Ok. Since I did not remember seeing it before, I thought it might be a
bug, but it is not.
On 04/04/2016 06:39 AM, Arne Fitzenreiter wrote:
> On 2016-04-04 12:31, R. W. Rodolico wrote:
>> Any reason why it is kicking you out of an ssh session? I can see in the
>> pakfire logs that ssh is being replaced, but I thought that restarting
>> ssh somehow magically did not kill the session.
>>
> ssh is updated by the core update and must restarted to use the new
> version.
> The restart should kick the session. If not ssh hangs at terminate...
>
> core updates should always startet in a "screen" session that can continued
> with "screen -x" after new ssh login.
>
--
Rod Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net
prev parent reply other threads:[~2016-04-04 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 10:31 R. W. Rodolico
2016-04-04 11:39 ` Arne Fitzenreiter
2016-04-04 16:35 ` R. W. Rodolico [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=570297E8.6030201@dailydata.net \
--to=rodo@dailydata.net \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox