On Wed, 21 Feb 2024 at 02:37, Grisha Levit <grishale...@gmail.com> wrote:
> sigaction(2) says: > > The affected system calls include open(2), read(2), write(2), > sendto(2), recvfrom(2), sendmsg(2) and recvmsg(2) on a communications > channel or a slow device (such as a terminal, but not a regular file) > > so I guess a SIGWINCH during the open(2) for ~/.bash_profile, etc. can > still get interrupted. > In most cases no, but "regular" files within mounted filesystems that themselves have a "slow" communication channel may be deemed "slow" or "fast" depending on the FS type and the mount options. This is especially true for NFS (on any platform) and FUSE (on Linux); I suspect it affects CIFS but I'd have to check. -Martin
