Does anyone know of any replacement naming utility besides the
migration manager for implementing qnx_name_attach/qnx_name_locate
Thanks,
RBW
Replacement for qnx_name_attach
-
David Gibbs
Re: Replacement for qnx_name_attach
Rich Wells <rbw317@yahoo.com> wrote:
name_attach() and name_open().
-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Not exactly the same...but the normal replacement is:Does anyone know of any replacement naming utility besides the
migration manager for implementing qnx_name_attach/qnx_name_locate
name_attach() and name_open().
-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
-
Guest
Re: Replacement for qnx_name_attach
David Gibbs <dagibbs@qnx.com> wrote:
receives when the client calls name_close() (it was _PULSE_CODE_DISCONNECT
IIRC).
--
__ __ ____ ____
| \/ | __ ) ___| Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |\/| | _ \___ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |_) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|_| |_|____/____/ Mobile: +49-172-3812373 D-47809 Krefeld
The only surprising thing was the system pulse, that the serverRich Wells <rbw317@yahoo.com> wrote:
Does anyone know of any replacement naming utility besides the
migration manager for implementing qnx_name_attach/qnx_name_locate
Not exactly the same...but the normal replacement is:
name_attach() and name_open().
receives when the client calls name_close() (it was _PULSE_CODE_DISCONNECT
IIRC).
--
__ __ ____ ____
| \/ | __ ) ___| Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |\/| | _ \___ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |_) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|_| |_|____/____/ Mobile: +49-172-3812373 D-47809 Krefeld
-
David Gibbs
Re: Replacement for qnx_name_attach
Karsten.Hoffmann@mbs-software.de wrote:
name_attach() describe which flags are set on the channel that it creates,
and explicitly mention the disconnect case as an example.
-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Yup, you get them. It is documented behaviour, actually. The docs forDavid Gibbs <dagibbs@qnx.com> wrote:
Rich Wells <rbw317@yahoo.com> wrote:
Does anyone know of any replacement naming utility besides the
migration manager for implementing qnx_name_attach/qnx_name_locate
Not exactly the same...but the normal replacement is:
name_attach() and name_open().
The only surprising thing was the system pulse, that the server
receives when the client calls name_close() (it was _PULSE_CODE_DISCONNECT
IIRC).
name_attach() describe which flags are set on the channel that it creates,
and explicitly mention the disconnect case as an example.
-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
-
Guest
Re: Replacement for qnx_name_attach
David Gibbs <dagibbs@qnx.com> wrote:
)
--
__ __ ____ ____
| \/ | __ ) ___| Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |\/| | _ \___ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |_) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|_| |_|____/____/ Mobile: +49-172-3812373 D-47809 Krefeld
.... and a quite useful one, too.Yup, you get them. It is documented behaviour, actually.
)--
__ __ ____ ____
| \/ | __ ) ___| Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |\/| | _ \___ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |_) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|_| |_|____/____/ Mobile: +49-172-3812373 D-47809 Krefeld