-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew DeFaria wrote:
| Robert Pendell wrote:
|> I don't see this as a bug. The same behavior can be observed on a
|> NetBSD machine when Putty is closed using that method or if my
|> connection to the server drops. I usually have to log back in and
Robert Pendell wrote:
I don't see this as a bug. The same behavior can be observed on a
NetBSD machine when Putty is closed using that method or if my
connection to the server drops. I usually have to log back in and
check for processes that are still running from my previous session.
And yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
NightStrike wrote:
| On 4/5/08, Andrew DeFaria <[EMAIL PROTECTED]> wrote:
| [snip lots of useless arguing]
|
| Look, use whatever you want, I don't really care. If you like
| cygwin's ssh, wonderful! I don't. Putty provides me the flexibility
| I n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Borchert wrote:
| I just installed Cygwin with OpenSSH and got it setup on Windows Server
| 2003.
| When I use Putty on a remote machine to connect to the server, the
| server starts a bash.exe processes.
| When I close Putty (alt-f4) the ba
On Sat, Apr 05, 2008 at 01:37:57PM -0400, NightStrike wrote:
>On 4/5/08, Andrew DeFaria <[EMAIL PROTECTED]> wrote:
>[snip lots of useless arguing]
>The takeaway is that if bash isn't handling a SIGHUP properly (As
>Paul-Kenji pointed out), then that is an issue that can't be ignored
>by saying "jus
NightStrike wrote:
Look, use whatever you want, I don't really care. If you like cygwin's
ssh, wonderful! I don't. Putty provides me the flexibility I need to
access many ssh features on a regular basis for the things that I do,
and is 3 clicks away from downloading/running on any system I use
Paul-Kenji Cahier wrote:
I have personally been using puttycyg here(or to be exact a homemade
build that incorporates both puttycyg and many other putty patches)
for optimal use.
That way I can use putty as a normal term and when I need to ssh, I
just use the normal ssh cygwin client from a p
On 4/5/08, Andrew DeFaria <[EMAIL PROTECTED]> wrote:
[snip lots of useless arguing]
Look, use whatever you want, I don't really care. If you like
cygwin's ssh, wonderful! I don't. Putty provides me the flexibility
I need to access many ssh features on a regular basis for the things
that I do, a
NightStrike wrote:
I personally use putty because the putty console window is superb,
How is it "superb"? I agree, the DOS box window sucks. I, however, use
rxvt, which is, IMHO, superb!
and because it allows incredibly easy access to all of the many
features of an ssh client.
Really? What feat
On 4/5/08, Andrew DeFaria <[EMAIL PROTECTED]> wrote:
> NightStrike wrote:
> > Killing putty with Alt-F4 is the same as losing connectivity, or putty
> crashing (rare as that is), or any of several other scenarios where there is
> abnormal termination. Does bash remain running under any abnormal
> t
NightStrike wrote:
Killing putty with Alt-F4 is the same as losing connectivity, or putty
crashing (rare as that is), or any of several other scenarios where
there is abnormal termination. Does bash remain running under any
abnormal termination? If so, that's a bug. If not, what makes things
l
On 4/5/08, Corinna Vinschen <[EMAIL PROTECTED]> wrote:
> On Apr 4 18:58, Christian Borchert wrote:
> > I just installed Cygwin with OpenSSH and got it setup on Windows Server
> > 2003.
> > When I use Putty on a remote machine to connect to the server, the server
> > starts a bash.exe processes.
>
On Apr 4 18:58, Christian Borchert wrote:
> I just installed Cygwin with OpenSSH and got it setup on Windows Server
> 2003.
> When I use Putty on a remote machine to connect to the server, the server
> starts a bash.exe processes.
> When I close Putty (alt-f4) the bash.exe processes remains on t
13 matches
Mail list logo
