zsh-users
 help / color / mirror / code / Atom feed
From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: rdong1989@gmail.com
Cc: zsh-user <zsh-users@zsh.org>
Subject: Re: Fwd: sshfs crash with zsh
Date: Wed, 12 Aug 2020 11:55:52 -0400	[thread overview]
Message-ID: <20200812155552.GA77916@fullerene.field.pennock-tech.net> (raw)
In-Reply-To: <1779408280.1081846.1597227236848@mail2.virginmedia.com>

On 2020-08-12 at 01:25, Rui Dong wrote:
> I am a fan of zsh, and used it for many years. Recently I found when I
> configure the server with zsh, I could not mount the disk with sshfs. If I
> comment the "exec /bin/zsh --login" out, sshfs works again. Could you
> please help with this?

It sounds like you're trying to change your shell in user configuration
files without changing the login user's shell in the system records.
And then you're doing this in a configuration file used for all logins,
even non-interactive ones.

So when some other command tries to log in, your shell switch is
happening and discarding the actual commands to be run.

You probably want to use the `chsh` command to change the shell instead.
Or `vipw` or whatever else changes the shell in the `/etc/passwd` file:
the last field on the line for your user specifies the shell.

If you _have_ to use configuration files, then make sure that you only
change shells, or run any command which produces output to stdout or
stderr, if the shell is interactive.

How you do that depends upon the shell which is being used, and which
configuration file you edit.  Check the manual-page for guidance on
which file to be edited.

If one configuration file is used for both interactive and
non-interactive use, and there's no other file you can use, then you can
use conditional logic to wrap around the exec and only call that when
interactive.  The syntax depends upon the shell (csh, bash, whatever).
There are two traditional approaches for "what to test":

1. You can look at $PS1, as long as nothing is polluting the environment
   by exporting it: PS1 will only be set by shells when the shell is
   interactive, because this is the main variable used to define what
   your command prompt looks like.  But sloppy practices (exporting PS1)
   will ruin this.
2. The shell might have a variable which lists which options are in
   effect, and you can check for the interactive option in that.  For
   instance, with the bash shell, you might check for `i` in `$-`:

    if [[ $- == *i* ]]; then
      exec /bin/zsh --login
    fi

More than that, we can't help you with, as there are too few details in
your mail about your setup.

Regards,
-Phil


  reply	other threads:[~2020-08-12 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAg1DCMTC7tk-uTN0Twvj3pGeJRz_-3mpL6m-YrO-5cMXjsbow@mail.gmail.com>
2020-08-12 10:13 ` Peter Stephenson
2020-08-12 15:55   ` Phil Pennock [this message]
2020-08-12 17:50     ` Rui Dong

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=20200812155552.GA77916@fullerene.field.pennock-tech.net \
    --to=zsh-workers+phil.pennock@spodhuis.org \
    --cc=rdong1989@gmail.com \
    --cc=zsh-users@zsh.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.
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).