Tmp-Path should be user and process ID save and use a lock mechanism about rafcon

[franzlst]

The temp path was user and process id save, so please undo your commit!

For each instance of RAFCON, a new temporary directory was created, thus there are no conflicts if several instances are started (each receives its own folder) or several users are suing RAFCON, as in any case, each session receives its own folder.

Originally created by @franzlst ([email protected]) at 2016-02-23 06:46:41+00:00 (moved from RMC internal repository)

[franzlst]

A general path /tmp/rafcon can not be named user save as long as the path is owned by the creator. And if a process is launched not by the user it self this also results into a not process id save path.

In my case the user rights of the folder /tmp/rafcon are:
drwx------ 201 Rbelder dlr_Rbelder_p 4.0K Feb 22 17:47 rafcon/
May it is different on your PC?

The additional adding of a extra folder which use the process id its self plus a automatic generated path element is the aim for reliable recovery capabilities, in future.

Originally created by @Rbelder at 2016-02-23 07:25:51+00:00 (moved from RMC internal repository)

[franzlst]

As long as the actual implementation is definitely not the final one, commit acbebe15 should solve the the sub-task of user-save tmp-path in the first place.

For the final setting a structure like.

• Path = rafcon-{user_name}/{generated_temp_folder_path}/ and lock-file in this folder would be suitable
• The only missing information in lock-file would be the process-id -> in this case the lock-file directly could be named "pid" as it is common practice of other applications

Originally created by @Rbelder at 2016-02-23 08:18:03+00:00 (moved from RMC internal repository)

[franzlst]

Sub-Task 3 is now implemented for the GUI by commit ad2de37fc8c4b2831d. May it becomes extended for the core in the future, too.
Issue is closed.

Originally created by @Rbelder at 2016-05-17 16:46:20+00:00 (moved from RMC internal repository)