DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 577635GY3061239 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 577635GY3061239 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=NZFh/oFV X-Recipient: archive-cygwin@delorie.com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A5DC93858C66 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1754546584; bh=049s+XPlOHbdVzCpqIPozsv4GK8bu3Och1wIxJOIDEk=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=NZFh/oFVpMXOnRrYw+bCJ+r82z4QP+DFhJD4Le49ngX2O0GQgRTwm2HUiXePuaf5Y s9dk1ecl7jBfs71vncHx4oqpJGQjogflHY1kSMdyVkL+KT5WCSDwXbuzfjhkrm/fml 2sez8LAZx1I3AWFy5kS59Z2nhlkG307tVb4rPZ9I= X-Original-To: cygwin@cygwin.com Delivered-To: cygwin@cygwin.com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D8B723858D21 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org D8B723858D21 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1754546523; cv=none; b=D+Hc+WHgdpYmvvnMZwV0/9SqIamuJCaqU9E/Nz4OBfaABwueHHcdNkqT5UZGGAdeGLMqTWOaACrVVOhQpBVTsDNtKtCO2UmcA+Itcu/+PgcnvxhWZ8jVnjbvxaKDjzEVLfG50ZNiNQhJSBYIrN2B5L/3xToIXLZTG/n9Cnzfijo= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1754546523; c=relaxed/simple; bh=9OpU29uYVf/6zpHJYTpUhtLaWfhSnORB772O9xClAuo=; h=Date:From:To:Subject:Message-Id:Mime-Version:DKIM-Signature; b=WhZ5r8B2BVKJQJreGFtWkrVpcJkCTY+xsmvdxv93EQppEqFeu1DHj4FTCjLLLFvbJpHwMCCRK5Qs/Es5rkqF0pFaiHFHszY289Tw5sb+dJ7yuDXjDrw1gtpK+TF0i6ndGorY2xb6cz2pxEausGNg15nNifbyc5Pj/CPe9xLaNyM= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D8B723858D21 Date: Thu, 7 Aug 2025 15:01:59 +0900 To: cygwin@cygwin.com Subject: Re: Screen : The screen session creaeted by ssh and local console seems separated Message-Id: <20250807150159.b562773d6524021dfe153740@nifty.ne.jp> In-Reply-To: <730588d6e22d4284b49f15ee853dcd7cae21594247a844718d3025c696f69141SA1P220MB16569712CB359D8E14F2E7F9B12CA@SA1P220MB1656.NAMP220.PROD.OUTLOOK.COM> References: <20250807131611.3e7ddc20a0dbc9432e1ba974@nifty.ne.jp> <20250807132154.d38418f36df0bde3c4a67562@nifty.ne.jp> <730588d6e22d4284b49f15ee853dcd7cae21594247a844718d3025c696f69141SA1P220MB16569712CB359D8E14F2E7F9B12CA@SA1P220MB1656.NAMP220.PROD.OUTLOOK.COM> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Takashi Yano via Cygwin Reply-To: Takashi Yano Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com Sender: "Cygwin" On Thu, 7 Aug 2025 05:56:12 +0000 L 2750558108 wrote: > But if that's the case, I won't be able to achieve the functionality I want. > > The actual scenario is as follows: my friend set up a server host and runs a console server program on it. I hope to remotely access his host via ssh at any time and use his server program console (including viewing historical messages and inputting commands), while he can also directly use the console of this program on the server host. > > By the way, I found that the situation described in this post (https://stackoverflow.com/questions/67443908/behavior-of-screen-over-ssh-cygwin-screen-detachment) is exactly the same as what I encountered while looking for help. What cygwin version are you using? -- Takashi Yano -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple