Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#30 NamedEvent bug?

Platform_Specific
closed
nobody
5
2012-09-14
2006-09-05
Caleb Epstein
No

Platform: Linux 2.6.8

See attached program. Run these steps as follows in
separate windows which I'll call 1 and 2:

Window 1. run "named-event wait"
Window 2. run "named-event"

The copy in window 1 should block and shutdown cleanly
once the second command is run.

Now run "named-event wait" again in either window. The
process will exit immediately and will never
successfully block on the NamedEvent again unless one
removes the associated semaphore from the system with
"ipcrm".

I don't really quite grok how semop and friends work,
but is this correct/expected behavior? I hope not, as
I'd like to use a NamedEvent as an application shutdown
trigger but I can't really rely on the current behavior.

Discussion

  • Caleb Epstein
    Caleb Epstein
    2006-09-05

    NamedEvent set/wait test

     
    Attachments
  • Caleb Epstein
    Caleb Epstein
    2006-09-05

    Logged In: YES
    user_id=36183

    Indeed this seems to be a UNIX-only problem. The same code
    works as expected on Windows (e.g. "named-event wait" always
    waits).

     
  • Logged In: YES
    user_id=1148207

    fixed in 1.2.3