NamedEvent_Unix could get missmatch key from ftok on redHawk system #2458
Description
Expected behavior
NamedEvent should connect to the same resource
Actual behavior
In the case of two processes with different life cycle, we can have key mismatch
Steps to reproduce the problem
- have a first process, creating and connecting to the named Event
- suppress.event file
- try to connect a second process to the same named Event after some time
POCO version
all
Compiler and version
all
Operating system and version
redHawk and RHEL7 based
Other relevant information
due to cron task on redHawk and probably on RHEL7/temp files are suppressed if access time is older than 10 days.
Ftok function doesn't change access time.
In the case of two processes with different life cycle, we can have a key mismatch due to .event file suppression.