[Bug 95191] document behavior of open(2) when path names a fifo with no readers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=95191

Michael Kerrisk <mtk.manpages@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |CODE_FIX

--- Comment #9 from Michael Kerrisk <mtk.manpages@xxxxxxxxx> ---
(In reply to Jason Vas Dias from comment #1)
> I think the fcntl documentation is also particularly misleading when it
> suggests
> that output file descriptors can be enabled to have SIGIO sent for them when 
> only O_ASYNC and not O_NONBLOCK bits are set in the FD flags .

Hello Jason,

I don't understand what you mean here. But, also, I would really prefer a
separate bug report, since this seems to be a separate issue.

I'm going to close this bug. Could you raise the above as a separate topics,
and repost example programs. But please: make the example programs as simple as
possible. I see extraneous stuff in the code you posted already, which just
makes it harder for me to work out what's going on.

Thanks,

Michael

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux