Re: bin/56110: pkg_add can fail without an error message

[Robert Elz <kre%munnari.OZ.AU@localhost>]

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

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: bin/56110: pkg_add can fail without an error message
Date: Sat, 17 Apr 2021 05:18:11 +0700

     Date:        Fri, 16 Apr 2021 17:30:00 +0000 (UTC)
     From:        gson%gson.org@localhost (Andreas Gustafsson)
     Message-ID:  <20210416173000.CA24A1A924C%mollari.NetBSD.org@localhost>
 
 
   | Yet it had clearly failed, because the exit status was nonzero (141,
   | suggesting an EPIPE?)
 
 SIGPIPE - indicates that the process was killed by a signal (it had no chance
 to say anything).   Normally your shell would tell you about death by a signal,
 but shells tend not to make a noise about SIGPIPE exits, as they're so common.
 
   | This PR is not about the package installation failing, as that may
   | have been caused by some network connectivity issue outside pkg_add's
   | control, but about pkg_add failing to print a message indicating that
   | it failed.
 
 The only way to deal with that would be to have pkg_add catch SIGPIPE
 and write an error, or ignore it (SIG_IGN I mean, not do nothing), and
 deal with the EPIPE error it would get instead.
 
 If you're able to make this happen at will, try
 
 	trap '' PIPE
 
 before running the command, and see if that makes a difference.
 (This is not recommended as a general solution, just to confirm.)
 
 kre