Cause:
This may be due to the same user running another instance of InTime on the same machine.
A lock file called intimeruns.lck prevents user collisions. In intimeruns.lck, the format is as follows:
$ cd ~/.plunify/user10_08002770A5E2 $ cat intimeruns.lck 15974 (PID) intime (application name) user10 (username)
Resolution:
In Windows, the intimeruns.lck file is handled by the kernel automatically. The file will be deleted upon exiting InTime.
In Linux, there are instances where intimeruns.lck is not removed properly. Here is the command to check if there is another instance of InTime running. Match the user and process ID (PID 15974 in the example) to determine if the same user is already running InTime.
$ ps -ef|grep bin/intime|grep -v grep|grep -v /bin/sh user10 15974 15912 0 05:29 pts/2 00:00:00 /opt/intime/bin/intime -username user10
If there is no InTime process displayed, run the following commands to find out the content of intimeruns.lck and if necessary, remove the appropriate intimeruns.lck file so that InTime is able to launch after that.
Find the location of intimeruns.lck
$ cd ~/.plunify
$ find . -name intimeruns.lck|xargs ls -lsh|awk '{print $10}'
./user10_08002770A5E2/intimeruns.lck
./user10_126825DE0B63/intimeruns.lck
Tally the PID in intimeruns.lck. In this case, file ./user10_08002770A5E2/intimeruns.lck contains the PID 15974.
$ cd ~/.plunify
$ find . -name intimeruns.lck|xargs ls -lsh|awk '{print $10}'|xargs cat
15974
intime
user10
6681
intime
user10
Remove all intimeruns.lck files
$ cd ~/.plunify
$ rm -rf ./user10_08002770A5E2/intimeruns.lck
When all the InTime processes have been terminated, use the following commands to manually remove all intimeruns.lck files.
$ killall -9 intime
$ find . -name intimeruns.lck|xargs ls -lsh|awk '{print $10}'|xargs rm -rf
Applies to:
- Linux Operating System
- Windows Operating System
Knowledge Base ID: 4002 - Last Review: May 21, 2014 - Revision: 1.0