Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 22580 - Cannot create IPC message queues with key 123456
Cannot create IPC message queues with key 123456
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2000-12-20 09:39 EST by Need Real Name
Modified: 2008-08-01 12:22 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-30 11:38:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2000-12-20 09:39:07 EST
The perl program below fails with error message : permission denied;

      1 use IPC::SysV qw( IPC_PRIVATE
      2                   IPC_CREAT
      3                   S_IRWXU
      4                   S_IRWXG
      5                   S_IRWXO );
      6 use IPC::Msg;
      8 $msg = new IPC::Msg( 123456, IPC_CREAT | S_IRWXU | S_IRWXG |
S_IRWXO ) or
      9    die "New IPC::Msg: $!\n";
     10 $msg->snd( 1, "toto");

Running the program by strace, shows that it is msgget that returns the
No message queues exist at the time of execution. The program functions
with any key
different from 123456. 
If you need more info do not hesitate to contact me.

Kind regards

Comment 1 Bugzilla owner 2004-09-30 11:38:52 EDT
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

Note You need to log in before you can comment on or make changes to this bug.