Page MenuHomeFreeBSD

env: Check the status of stdout.
ClosedPublic

Authored by des on Tue, Oct 8, 10:07 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Oct 29, 7:59 AM
Unknown Object (File)
Tue, Oct 22, 12:29 PM
Unknown Object (File)
Mon, Oct 21, 4:24 PM
Unknown Object (File)
Tue, Oct 15, 6:30 AM
Unknown Object (File)
Sun, Oct 13, 1:33 PM
Unknown Object (File)
Wed, Oct 9, 7:51 AM
Unknown Object (File)
Wed, Oct 9, 4:57 AM
Unknown Object (File)
Tue, Oct 8, 7:40 PM
Subscribers

Details

Summary

Sponsored by: Klara, Inc.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

des requested review of this revision.Tue, Oct 8, 10:07 AM
markj added inline comments.
usr.bin/env/tests/env_test.sh
134

The rest of the file puts opening braces on their own lines.

140

Does it make sense to sleep for a bit first, to make sure that the other end of the pipe has time to close? Maybe I'm missing something, but this looks like it might fail only sometimes.

usr.bin/env/tests/env_test.sh
134

Yeah sorry this was copy-pasted from asa.

140

It works 100% of the time, we use the exact same procedure several other places (including asa which is where I copied this from). Timing doesn't matter because none of the output is consumed and the kernel doesn't buffer it.

This revision is now accepted and ready to land.Tue, Oct 8, 1:45 PM
This revision now requires review to proceed.Tue, Oct 8, 1:48 PM
des marked 2 inline comments as done.Tue, Oct 8, 1:49 PM
This revision is now accepted and ready to land.Tue, Oct 8, 4:59 PM
This revision was automatically updated to reflect the committed changes.