home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!umn.edu!noc.msc.net!uc.msc.edu!raistlin!shamash!ems!ateam.ems.cdc.com!bguest
- From: bguest@ateam.ems.cdc.com (Brandon Guest)
- Newsgroups: comp.unix.aix
- Subject: Creating unique IPC keys
- Message-ID: <31452@nntp_server.ems.cdc.com>
- Date: 6 Jan 93 22:18:19 GMT
- Sender: sys@ems.ems.cdc.com
- Organization: Empros Systems International, a division of Ceridian
- Lines: 35
- Nntp-Posting-Host: ateam.ems.cdc.com
-
- A question has come up here at my site on the 'best' way to assign
- keys for use in IPCs. Being somewhat ignorant on the subject, I
- suggested (along with others) that we use the ftok routine and some
- filenaming convention. A concern was raised that this does not
- always generate unique keys. After consulting InfoDestroyer, the
- only problem that was referenced was if you used different filenames
- which were linked to the same underlying file. It also reinforced
- the need to have some type of convention for use in assigning or
- generating keys for our applications.
-
- My questions are as follows:
-
- 1) In AIX are there any other instances other than the one cited
- (commonly linked files) where I could generate identical keys
- from unique file names?
-
- 2) What is the possibility/probability that I might generate a key
- in use by some other vendors application? What can I do to
- guard against this?
-
- 3) Info gave an example of one other method/convention for generating
- keys. Would others be willing to share their thoughts on this
- topic?
-
- Email replies prefered. I will summarize and post if there is enough
- interest.
-
- Thanks in advance!
-
- Brandon
- --
- H. Brandon Guest | bguest@ems.cdc.com
- Empros Systems International | (A division of Something)
- 2300 Berkshire Lane North | Voice (612) 553-4529
- Plymouth, MN 55441-3694 | Fax (612) 553-4018
-