Groups | Search | Server Info | Keyboard shortcuts | Login | Register

Groups > muc.lists.netbsd.source-changes > #156114

Re: bin/59587: ftp client ascii transfers with progress report fail

Show all headers | View raw

> Date: Thu, 15 Jan 2026 16:34:48 +1100
> From: Luke Mewburn <luke@mewburn.net>
> 
> On 26-01-15 04:19, Taylor R Campbell wrote:
>   | Alternatively: Why not use SA_RESTART, so you don't have to track down
>   | all the I/O logic that might be interrupted by a signal and arrange to
>   | run it in a loop?
> 
> Even on NetBSD, the previous use of restartable signals (SA_RESTART)
> caused issues with the implementation of -q QUITTIME.
> That's why I changed ftp 20210106 to always use interruptable
> signals for PR 55857 - as confirmed by the submitter.

Sounds like a good reason, thanks!  I hadn't looked at any surrounding
context, where there is a loop that depends on re-reading the time
after an alarm expires while waiting in read/recv/accept.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de

Back to muc.lists.netbsd.source-changes | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Re: bin/59587: ftp client ascii transfers with progress report fail Taylor R Campbell <riastradh@NetBSD.org> - 2026-01-15 03:51 +0000
  Re: bin/59587: ftp client ascii transfers with progress report fail Taylor R Campbell <riastradh@NetBSD.org> - 2026-01-15 04:19 +0000
    Re: bin/59587: ftp client ascii transfers with progress report fail Luke Mewburn <luke@mewburn.net> - 2026-01-15 16:34 +1100
      Re: bin/59587: ftp client ascii transfers with progress report fail Taylor R Campbell <riastradh@NetBSD.org> - 2026-01-15 23:56 +0000
  Re: bin/59587: ftp client ascii transfers with progress report fail Luke Mewburn <luke@mewburn.net> - 2026-01-15 16:26 +1100

csiph-web