it's really not possible for a pipe to have a buffer size of 0
fpathconf says it returns "the maximum number of bytes which will be written atomically to a pipe."
I took that to mean it returns the available buffer size. The documentation isn't clear, but I'm favouring your interpretation.
My local man page simply says "returns the size of the pipe buffer", confirming your interpretation.
In reply to Re^3: Why does fpathconf give "bad file descriptor"?
by ikegami
in thread Why does fpathconf give "bad file descriptor"?
by madscientist
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |