Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: /proc slows % echo /**//etc/r(/N)

X-seq: zsh-users 29540
From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
To: Ray Andrews <rayandrews@xxxxxxxxxxx>
Cc: zsh-users@xxxxxxx
Subject: Re: /proc slows % echo /**/*/etc/r*(/N)
Date: Sun, 21 Jan 2024 17:02:14 -0800
Archived-at: <https://zsh.org/users/29540>
In-reply-to: <134e5295-418e-4872-a251-1f9745afdd55@eastlink.ca>
List-id: <zsh-users.zsh.org>
References: <62da1cec-bcc9-49ed-8f5f-ad428fdd3f20@eastlink.ca> <CAH+w=7ZQioZ5BgYMYzsp+8aqB2iq4Tm3Fm_WHMpGYPVbn+u8bg@mail.gmail.com> <a80a4cb0-4baa-458f-8b6f-dbb98dad00fa@eastlink.ca> <CAH+w=7Ze6yHSJWwGaA9Gb4HsJGXcZjZNnCZ1+37O5mAUa1-aNw@mail.gmail.com> <134e5295-418e-4872-a251-1f9745afdd55@eastlink.ca>

On Sun, Jan 21, 2024 at 4:07 PM Ray Andrews <rayandrews@xxxxxxxxxxx> wrote:
>
> Shouldn't there be an error msg in such cases?

Are you sure there wasn't, somewhere above all that output?  As far as
I can tell there's no way it actually could have finished.  If it
didn't run out of memory, the lengths of some of the generated paths
must have exceeded the system PATH_MAX and stopped the descent that
way.

> Some message would have alerted me to the reality of the loop.

A symlink loop is not detectable without extraordinary measures such
as recording and testing the inode number of every directory visited.

Follow-Ups:
- Re: /proc slows % echo /**/*/etc/r*(/N)
  - From: Ray Andrews

References:
- /proc slows % echo /**/*/etc/r*(/N)
  - From: Ray Andrews
- Re: /proc slows % echo /**/*/etc/r*(/N)
  - From: Bart Schaefer
- Re: /proc slows % echo /**/*/etc/r*(/N)
  - From: Ray Andrews
- Re: /proc slows % echo /**/*/etc/r*(/N)
  - From: Bart Schaefer
- Re: /proc slows % echo /**/*/etc/r*(/N)
  - From: Ray Andrews

Messages sorted by: Reverse Date, Date, Thread, Author

Re: /proc slows % echo /**/*/etc/r*(/N)

Re: /proc slows % echo /**//etc/r(/N)