Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: BUG: Zsh loses history entries since 2015
- X-seq: zsh-workers 53548
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Michael Stapelberg <stapelberg+zsh@xxxxxxxxxx>
- Cc: zsh-workers@xxxxxxx
- Subject: Re: BUG: Zsh loses history entries since 2015
- Date: Mon, 5 May 2025 08:33:24 -0700
- Archived-at: <https://zsh.org/workers/53548>
- In-reply-to: <CAH9Oa-Y3dOM88zLG=OQY_NrHwiqfBPV1SMX1=cEN09wx1SXP=Q@mail.gmail.com>
- List-id: <zsh-workers.zsh.org>
- References: <CAH9Oa-bfWAo2OLSaYYK+udd=+kg_7=712P+NudVvW-rR9Buagg@mail.gmail.com> <CAH+w=7Z9te+S5rUJRMrHChb8orHEkOWDfUQjzO2C30o_SFOkyg@mail.gmail.com> <CAH9Oa-Z-HtdHC+S_0FtDW9t8sdEJSdbPgdwV2YDuBZEgjYzCzA@mail.gmail.com> <CAH+w=7bp+YjZCkVqtingKkcXyDbEus9B53-vgAej_r_MLVn1EA@mail.gmail.com> <CAH+w=7bErAhPK9325uXP4r19So_vUPUMoCVJnNF3CPz_jRiH=w@mail.gmail.com> <CAH9Oa-a83GJXhO50UyLG1uL2JuBVKYjF5qUzQVK2Qy1ZXap9Jg@mail.gmail.com> <CAH+w=7ZgL2AJBi=3-Om6KpvF5VdyMTTSqshmC29TaNkAZ-2u3A@mail.gmail.com> <CAH+w=7bn318R6zaeKJk3gxm=CNo=w4Bo1cdNoabPw=iPi6vgRg@mail.gmail.com> <CAH9Oa-Y3dOM88zLG=OQY_NrHwiqfBPV1SMX1=cEN09wx1SXP=Q@mail.gmail.com>
On Mon, May 5, 2025 at 3:31 AM Michael Stapelberg
<stapelberg+zsh@xxxxxxxxxx> wrote:
>
> I was under the impression that there is no way to fully block interrupts.
Anything other than the SIGKILL and SIGSTOP signals can be delayed or ignored.
> For example, I could imagine that “the underlying file system disappeared”
> is one of those situations where the kernel just cannot do anything
> but interrupt,
> otherwise your program will just hang for all eternity, waiting for
> data that can never arrive.
That can in fact happen if you ignore the signals related to I/O errors.
The other side of the equation is that after a signal is handled, an
interrupted system call can be caused to either (attempt to) resume
where it left off, or to return with error state.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author