Re: misc/48555: rc.conf handling of program=yes/no

[Bob Nestor <rnestor%tx.rr.com@localhost>]

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

From: Bob Nestor <rnestor%tx.rr.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: misc/48555: rc.conf handling of program=yes/no
Date: Mon, 27 Jan 2014 09:04:19 -0600

 Well, I don't want to come off argumentative here, but I
 used the web interface to gnats to file this report.
 It doesn't indicate that I have to wrap the lines in
 the report.  Maybe this should be filed as a bug
 in the gnats web interface.
 
 As for "program=", ok if that was to difficult to
 understand.  Try using "dirmngr=NO" and then
 executing "/etc/rc.d/dirmngr restart".  It will
 attempt to stop dirmngr first and report an
 error. You may need to start dirmngr first
 using a "dirmngr=YES" line.
 
 Or try setting the line to "#dirmngr=YES" and
 rebooting the system.  The rc.log will indicate
 an improperly configured dirmngr.
 
 And I hope this lines are short enough for
 viewing.
 
 On Jan 27, 2014, at 8:50 AM, Alan Barrett wrote:
 
 > The following reply was made to PR misc/48555; it has been noted by GNATS.
 > 
 > From: Alan Barrett <apb%cequrux.com@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: 
 > Subject: Re: misc/48555: rc.conf handling of program=yes/no
 > Date: Mon, 27 Jan 2014 16:46:47 +0200
 > 
 > On Mon, 27 Jan 2014, rnestor%tx.rr.com@localhost wrote:
 >> The man page on rc.conf indicates that a program/package may be 
 >> started on boot by including the line "program=YES" in rc.conf. 
 >> It also indicates that the program may be disabled on boot by 
 >> changing the line to "program=NO'.
 > 
 > Please use reasonable length lines; don't represent an entire 
 > paragraph as a single very long line.  I have re-wrapped your text 
 > to something less than 80 characters per line.
 > 
 >> For any line in the rc.conf file of the form "program=NO" an 
 >> error is produced on system shutdown with the text "[NO not 
 >> found".
 > 
 > I could understand an error like that for a variable that might be 
 > used as the name of a program instead of as a yes/no switch, but 
 > surely not for all variables, and the square bracket in the error 
 > message is also hard to explain.
 > 
 > Please report the exact error message, and the exact line in 
 > /etc/rc.conf.  The name of the variable is important, so please 
 > don't change it to "program".
 > 
 > --apb (Alan Barrett)
 >