Re: misc/52371: startup complains about fdflags

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

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

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: misc/52371: startup complains about fdflags
Date: Thu, 06 Jul 2017 16:21:15 +0700

     Date:        Thu,  6 Jul 2017 03:10:00 +0000 (UTC)
     From:        edgar%pettijohn-web.com@localhost
     Message-ID:  <20170706031000.23C767A2AC%mollari.NetBSD.org@localhost>
 
 
   | During startup rc complains twice about fdflags not existing.
   | I couldn't find a manual for fdflags to know what its supposed to do.
 
 It is a new sh built-in command from Christos, which manipulates the
 kernel flags for a fd - here (and 99% of uses probably) to turn on, or
 off, close on exec.
 
 The purpose in /etc/rc is to avoid fd's that are for rc internal use
 (for gathering the command output for the log files, etc) being left
 open when commands are run.
 
 It is (will be) in NetBSD 8, but is not in NetBSD 7, and NetBSD 7
 rc scripts should not be using it.   It is documented in the NetBSD 8
 version of sh(1) (and later, of course.)
 
 If a usage of fdflags somehow crept into the NetBSD 7 rc scripts, that
 is a mistake, and should be reverted.
 
 Simply removing it (as you did) is fine - it means that fds will leak
 into (some) daemon processes, but that is nothing new.
 
 kre