The key provided by ftok is notoriously unreliable. Depending on the version, it is and algorithm based on an inode number and a project code.
The inode number is unreliable for several reasons. An inode is only unique within a partition. It is possible that two files on different paritions could have the same inode resulting in ftok returning a non-unique key - unlikely, but possible.
Inode numbers change! If a sys. admin. reorganises the partition, maybe just a backup then restore, then inodes are now different. Since message queues are "kernel persistent" (lost on a reboot), and we never reboot UNIX ;-) then programs running will use different keys to any started after the reorg. This has happened to me more than once.
So, personally I would not use ftok, but create my own safe algorithm which is repeatable on every occasion.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.