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

[matthew green <mrg%eterna.com.au@localhost>]

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

From: matthew green <mrg%eterna.com.au@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: martin%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
    roland.illig%gmx.de@localhost
Subject: re: install/56303: On a fresh installation, /tmp on sparc64 is not sticky
Date: Tue, 13 Jul 2021 19:29:40 +1000

 >  The other part is that apparently
 >  
 >  	progress -zf $(set).tar.xz tar --chroot $(path) -xpf -
 >  
 >  does not return failure properly. Sounds like a progress(1) or gizp(1)
 >  bug to me.
 
 i just tested gzip(1) with RLIMIT_AS set to various values to see
 what the failure mode is.
 
 too low, shell can't exec and $? is 1, and prints eg:
 
    Cannot map anonymous memoryCannot allocate memory: Cannot allocate memory
 
 as it begins to be enough to start executing, failure occurs while
 mapping shlibs, eg:
 
    gzip: Shared object "libz.so.1" not found
 
 or
 
    /usr/lib/liblzma.so.2: Shared object "libpthread.so.1" not found
 
 eventually gzip itself runs and fails, returning 2:
 
    gzip: malloc failed: Cannot allocate memory
 
 doing similar with progress also gives me either 1 or 2 failures.
 
 
 i don't think it is either gzip or progress.  at least, the normal
 methods they could fail seem to be working here.
 
 
 .mrg.