Re: kern/44950: fcntl(F_MAXFD) returns bogus values

[christos%zoulas.com@localhost (Christos Zoulas)]

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

From: christos%zoulas.com@localhost (Christos Zoulas)
To: Julio Merino <jmmv%julipedia.org@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost, 
        gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, 
martin%NetBSD.org@localhost
Subject: Re: kern/44950: fcntl(F_MAXFD) returns bogus values
Date: Wed, 11 May 2011 10:43:00 -0400

 On May 11, 10:20am, jmmv%julipedia.org@localhost (Julio Merino) wrote:
 -- Subject: Re: kern/44950: fcntl(F_MAXFD) returns bogus values
 
 | On 5/11/11 8:53 AM, Christos Zoulas wrote:
 | >
 | > Fix the test so that it runs a loop to close file descriptors from 0 to the
 | > descriptor soft limit
 | 
 | I think atf-run should be doing this before execing the test program, if 
 | only for consistency reasons.  You can open a PR against me if you agree 
 | so I don't forget!
 
 I am not sure which way to go there. Make the startup environment
 more complicated in the name of consistency, or have tests that
 care for a particular setup make sure that the setup they care
 about is consistent?
 
 I.e. a file descriptor test should make sure that descriptors are
 consistent, a resource limit test should do the same for resources,
 etc. Otherwise the startup can end up being expensive, plus it
 might be exercising the same functions that test is supposed to.
 
 And where does it stop? Do we reset process group, tty process
 groups, current working directory, environment, signal handlers,
 sysv ipc stuff, resource limits, timers, ...
 
 christos