possible bug: open(2) ebusy

From: Matwey V. Kornilov <hidden>
Date: 2012-02-18 06:12:22

Dear man-pages maintainers,


I am not sure that this is really bug, but look at this:

http://man7.org/linux/man-pages/man2/open.2.html
open(2) version 2011-09-08

and also look at that:

http://man7.org/linux/man-pages/man4/tty_ioctl.4.html
tty_ioctl(4) version 2008-10-29


As it stated in tty_ioctl(4), if a terminal is set into exclusive mode
by TIOCEXCL then open fails with EBUSY. It is how it really works on
my linux-system. But open(2) says nothing about returning EBUSY,
except statement about block devices in O_EXCL section. I was really
confused by this situation when I got EBUSY at open() and tried to
understand what was happening from open(2) man-page. Is it possible to
add a brief note about EBUSY and TIOCEXCL into open(2)? I think it
would be helpful for other people.


-- 
With best regards,
Matwey V. Kornilov
http://0x2207.blogspot.com
xmpp:0x2207-962d5TIgE1qHXe+LvDLADg@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help