> To be sure, are you actually talking about the "mqueue" from <mqueue.h> ? > Because this is api I want to use. > The filesystem is not mandatory but it would be useful for me to keep track > of the created message queues. I'm talking about Message Queues, one of forms of classical IPC, aparrently I wasn't aware of new real-time message queues recently introduced. Since this is fairly recent it seems like it's not virtualized yet ( AFAIK virtuozoo team does such large jobs only on requests from larger paying customers, for example IPC message queues were needed for DB2 using customets ), though you should be able to use it from VE's (without mounting mqueue filesystem). But since it's not virtualized, mqueues would be visible to all guests and the host too, like this:
lenny64:/# /home/eyck/mqueue mq_unlink(): success. mq_open(): success. mq_unlink(): success. mq_open(): success. mq_unlink(): success. mq_open(): success. mq_unlink(): success. mq_open(): success. mq_unlink(): success. mq_open(): success. mq_unlink(): success. mq_open(): success. mq_unlink(): success. mq_open(): success. mq_unlink(): success. mq_open(): success. mq_unlink(): success. mq_open(): success. mq_unlink(): success. ... on the host: venom:/# ls /dev/mqueue/ -l total 0 -rwxr-x--- 1 root root 80 Aug 20 17:12 mqueue__1 -rwxr-x--- 1 root root 80 Aug 20 17:12 mqueue__2 -rwxr-x--- 1 root root 80 Aug 20 17:12 mqueue__3 -rwxr-x--- 1 root root 80 Aug 20 17:12 mqueue__4 -rwxr-x--- 1 root root 80 Aug 20 17:12 mqueue__5 -rwxr-x--- 1 root root 80 Aug 20 17:12 mqueue__6 -rwxr-x--- 1 root root 80 Aug 20 17:12 mqueue__7 -rwxr-x--- 1 root root 80 Aug 20 17:12 mqueue__8 -rwxr-x--- 1 root root 80 Aug 20 17:12 mqueue__9 (I mounted mqueue on the host only to be able to see the queues, they seem to be working ok without mqueue fs mounted) -- Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9 Total Existance Failure _______________________________________________ Users mailing list [email protected] https://openvz.org/mailman/listinfo/users
