Re: install/56303: On a fresh installation, /tmp on sparc64 is not sticky

[Roland Illig <roland.illig%gmx.de@localhost>]

The following reply was made to PR install/56303; it has been noted by GNATS.

From: Roland Illig <roland.illig%gmx.de@localhost>
To: gnats-bugs%netbsd.org@localhost, martin%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
 netbsd-bugs%netbsd.org@localhost
Cc: 
Subject: Re: install/56303: On a fresh installation, /tmp on sparc64 is not
 sticky
Date: Mon, 12 Jul 2021 23:01:42 +0200

 Am 12.07.2021 um 21:05 schrieb Andreas Gustafsson:
 >  For example, if I escape to a shell during set extraction by typing
 >  control-z, manually kill the gzip -dc process, and exit the shell,
 >  sysinst appears to continue like nothing happened and says all sets
 >  extracted successfully.  Can you reproduce this?
 
 Sounds plausible to me.  A simpler reproducer is:
 
 $ cat | head
 
 and in another shell:
 $ pkill cat
 
 After that, the pipeline 'cat | head' has exit status 0.  If I remember
 correctly, progress(1) feeds tar(1), via a pipeline, so that may be the
 same scenario.  In my example the exit status is 0 because head(1) calls
 read(2), which returns 0 without any error, and that is of course
 interpreted as EOF.
 
 Roland