sin,psin,procnto messages
sin,psin,procnto messages
I have a service waiting for messages:
rcvid = MsgReceive(...
I get messages from sin, psin and procnto(pid=1). My message structure
will not allow these messages to cause any harm, but why do they send
these messages and what is the response they require?
Francois
rcvid = MsgReceive(...
I get messages from sin, psin and procnto(pid=1). My message structure
will not allow these messages to cause any harm, but why do they send
these messages and what is the response they require?
Francois
Re: sin,psin,procnto messages
They are most likely IO_DUP and IO_FDINFO messages.
You should set the _NTO_SIDE_CHANNEL flag on your channel to indicate that your channel is not an 'fd'.
Colin
Francois Joubert wrote:
cburgess@qnx.com
You should set the _NTO_SIDE_CHANNEL flag on your channel to indicate that your channel is not an 'fd'.
Colin
Francois Joubert wrote:
--I have a service waiting for messages:
rcvid = MsgReceive(...
I get messages from sin, psin and procnto(pid=1). My message structure
will not allow these messages to cause any harm, but why do they send
these messages and what is the response they require?
Francois
cburgess@qnx.com
Re: sin,psin,procnto messages
Colin Burgess wrote:
described in the documentation.
this instance. I did not handle received messages properly as clearlyThey are most likely IO_DUP and IO_FDINFO messages.
You should set the _NTO_SIDE_CHANNEL flag on your channel to indicate
that your channel is not an 'fd'.
Colin
Francois Joubert wrote:
I have a service waiting for messages:
rcvid = MsgReceive(...
I get messages from sin, psin and procnto(pid=1). My message structure
will not allow these messages to cause any harm, but why do they send
these messages and what is the response they require?
Francois
Thank you for the info. My problem however was that I use name_attach in
described in the documentation.
Re: sin,psin,procnto messages
You can setup your own channel, and the use
dispatch_t *_dispatch_create(int chid, unsigned flags);
instead of the normal dispatch_create().
Francois Joubert wrote:
cburgess@qnx.com
dispatch_t *_dispatch_create(int chid, unsigned flags);
instead of the normal dispatch_create().
Francois Joubert wrote:
--Colin Burgess wrote:
They are most likely IO_DUP and IO_FDINFO messages.
You should set the _NTO_SIDE_CHANNEL flag on your channel to indicate
that your channel is not an 'fd'.
Colin
Francois Joubert wrote:
I have a service waiting for messages:
rcvid = MsgReceive(...
I get messages from sin, psin and procnto(pid=1). My message
structure will not allow these messages to cause any harm, but why do
they send these messages and what is the response they require?
Francois
Thank you for the info. My problem however was that I use name_attach in
this instance. I did not handle received messages properly as clearly
described in the documentation.
cburgess@qnx.com
RE: Re: sin,psin,procnto messages
When you do name_open, coid will be start from _NTO_SIDE_CHANNE, so
you should not get IO_DUP and IO_FDINFO from utilities sin, ...; am
I right?
you should not get IO_DUP and IO_FDINFO from utilities sin, ...; am
I right?
Re: sin,psin,procnto messages
qnxloader wrote:
FrancoisWhen you do name_open, coid will be start from _NTO_SIDE_CHANNE, so
you should not get IO_DUP and IO_FDINFO from utilities sin, ...; am
I right?
I received _IO_DEVCTL messages.
Re: sin,psin,procnto messages
"Francois Joubert" <sommerfj@webmail.co.za> wrote in message
news:fcod24$1c8$1@inn.qnx.com...
the 'on' utility with such code also cause these messages to be sent. I've
always had to ignore _IO_DEVCTL and _IO_DUP when using name_open().
news:fcod24$1c8$1@inn.qnx.com...
The QNX doc and examples for using name_open do seem to be incomplete. Usingqnxloader wrote:
When you do name_open, coid will be start from _NTO_SIDE_CHANNE, so
you should not get IO_DUP and IO_FDINFO from utilities sin, ...; am
I right?
I received _IO_DEVCTL messages.
the 'on' utility with such code also cause these messages to be sent. I've
always had to ignore _IO_DEVCTL and _IO_DUP when using name_open().
Re: sin,psin,procnto messages
Francois Joubert <sommerfj@webmail.co.za> wrote:
bright as they should be about not issuing queries on things that aren't
fds.
A general principle in ALL servers: if you get a message that you don't
understand/expect, return an error. I tend to prefer:
MsgError(rcvid, ENOSYS);
-David
--
David Gibbs
QNX Training Services
dagibbs@qnx.com
You shouldn't, true. But qconn, sin, pidin, etc aren't neccessarily asqnxloader wrote:
When you do name_open, coid will be start from _NTO_SIDE_CHANNE, so
you should not get IO_DUP and IO_FDINFO from utilities sin, ...; am
I right?
I received _IO_DEVCTL messages.
bright as they should be about not issuing queries on things that aren't
fds.
A general principle in ALL servers: if you get a message that you don't
understand/expect, return an error. I tend to prefer:
MsgError(rcvid, ENOSYS);
-David
--
David Gibbs
QNX Training Services
dagibbs@qnx.com