help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Perry Smith <pedz@easesoftware.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Is this a bug?
Date: Mon, 18 Apr 2022 20:05:04 -0700	[thread overview]
Message-ID: <CAH+w=7aF2YLcsc2upXQnMosacNZ5SffhaOa0g-W7t73zhy=iOw@mail.gmail.com> (raw)
In-Reply-To: <F5B10854-2086-43AE-9077-EC071034BFBC@easesoftware.com>

On Mon, Apr 18, 2022 at 7:02 PM Perry Smith <pedz@easesoftware.com> wrote:
> I’m on macOS 12.3.1.  I’m using zsh 5.8.1 from Home-brew.  I do `sudo -s` and now it seems I’m using the native macOS 5.8 version of zsh.

That's not a bug.  It should work to do `sudo -s $SHELL` if you want
to keep using the same shell version.

> The command `print -l /System/Volumes/Data/**/*(D)` [...]  appears to hang.  ^C doesn’t stop it.  ^Z does not suspend it.  ^\ kills the sudo and I get back to my user prompt.

This isn't entirely surprising ... those signals might fail because
your user doesn't have privilege to signal the root shell.

> But the apparent hang seems rather ugly.  Can others reproduce this?

Does there happen to be a Time Machine backup under
/System/Volumes/Data/ ?  Time Machine plays some tricks with making
hard links to directories (normally not allowed) for reasons of space
savings, but that could put **/ into an infinite loop.

  reply	other threads:[~2022-04-19  3:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19  2:02 Perry Smith
2022-04-19  3:05 ` Bart Schaefer [this message]
2022-04-19 12:33   ` Perry Smith
2022-04-19 16:53     ` Bart Schaefer
2022-04-19 17:13       ` Mikael Magnusson
2022-04-19 21:06         ` Bart Schaefer
2022-04-19 21:53           ` Mikael Magnusson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH+w=7aF2YLcsc2upXQnMosacNZ5SffhaOa0g-W7t73zhy=iOw@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=pedz@easesoftware.com \
    --cc=zsh-users@zsh.org \
    --subject='Re: Is this a bug?' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).