zsh-users
 help / color / mirror / code / Atom feed
From: Matthew Braun <matthew@ans.net>
To: zsh-users@math.gatech.edu
Cc: michael shiplett <walrus@ans.net>
Subject: zsh login shell exits on Control-C
Date: Mon, 12 Aug 1996 14:01:43 -0400	[thread overview]
Message-ID: <199608121801.OAA11270@sassy.aa.ans.net> (raw)

I have a problem where when I login to a machine, where my shell is set
to zsh, and I type control-C it closes my connection.  But if I login
and type 'exec zsh', it won't hang up on control-C.

I am using kerberos v.4 to do my remote logins and there appears to be a
signaling problem.  It is definately the kerberos code that is
triggering this bug, because zsh does not behave this way using the
regular Berkeley r-commands or ssh to login.  This problem also happens
with /bin/sh, but not with the other shells, /bin/ksh, /bin/csh, and
/usr/local/bin/tcsh.

It appears to be a difference on how zsh treats signals for login shells
vs. doing a 'exec zsh' once logged in (even if your login sehll is
already zsh).  Although my co-worker, walrus, doesn't see the code path
that would be causing this difference after looking at the source for a
short while.

This happens using zsh-2.5.03 through zsh-3.0-pre6.  Most of my testing
was to and from a Solaris 2.5.1 machine, but the exiting problem with
kerberos/zsh happens going to a BSDI machine as well.

Any ideas?  It would be nice if zsh could be made not to exit in this
case, but we'll also be looking at the kerberos code to see if it can be
fixed there as well.

Thanks for any help,

Matthew.

=====

example:

terminator:~> krsh sassy
This rlogin session is using DES encryption for all data transmissions.

Warning: No Kerberos tickets obtained.

Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996

You have new mail.

sassy:~> <Control-C pressed>Connection closed.
terminator:~> 


                 reply	other threads:[~1996-08-12 18:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=199608121801.OAA11270@sassy.aa.ans.net \
    --to=matthew@ans.net \
    --cc=walrus@ans.net \
    --cc=zsh-users@math.gatech.edu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).