Hi,
I appreciate any help what could cause iofunc_write_verify() to return
EISDIR error.
The on-line manual
Hi,
I appreciate any help what could cause iofunc_write_verify() to return
EISDIR error.
The on-line manual
[Sorry earlier my email got cut off:]
I appreciate any help what could cause iofunc_write_verify() to return
EISDIR error
The on-line manual
http://www.qnx.com/developer/docs/momentics_nc_docs/neutrino/lib_ref/i/iofun
c_write_verify.html
states that it checks the permission against the ocb->ioflag and it is set
to 3 which is
_IO_FLAG_RD and _IO_FLAG_WR
Regards.
-chang
“Chang Im” <chim@cisco.com> wrote in message
news:albejk$l2k$1@inn.qnx.com…
Hi,
I appreciate any help what could cause iofunc_write_verify() to return
EISDIR error.The on-line manual
Chang Im <chim@cisco.com> wrote:
I appreciate any help what could cause iofunc_write_verify() to return
EISDIR error
If the iofunc_attr_t refers to a directory (EISDIR after all). A user
cannot directly write to a directory. This is just a sanity check, as
iofunc_open() should have forbid the user from setting up a writable fd
to a directory in the first place (should have returned EISDIR from
there too, so if your resource manager allowed/ignored this then it is
not handling the open() message properly).