Last Modified: Nov 14, 2022
See more info
Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 12.1.4, 22.214.171.124
Opened: Feb 24, 2016
TMSH writes to the ~/.tmsh-history-username file whenever a command is issued. Running concurrent instances of TMSH can result in a race condition in writing this file.
Updating the history file fails, so the file does not reflect the actual history of the commands that have been issued.
Running multiple instances can cause one instance of TMSH to lock the history file while the other is trying to access it, resulting in an error.
Only run a single instance of TMSH.
Running concurrent TMSH instances no longer results in error in access to history file.