Start here

Home
About Klocwork
What's new
Fixed issues
Release notes
Installation

Reference

C/C++ checkers
Java checkers
C# checkers
MISRA C 2004 checkers
MISRA C++ 2008 checkers
MISRA C 2012 checkers
MISRA C 2012 checkers with Amendment 1
Commands
Metrics
Troubleshooting
Reference

Product components

C/C++ Integration build analysis
Java Integration build analysis
Desktop analysis
Refactoring
Klocwork Static Code Analysis
Klocwork Code Review
Structure101
Tuning
Custom checkers

Coding environments

Visual Studio
Eclipse for C/C++
Eclipse for Java
IntelliJ IDEA
Other

Administration

Project configuration
Build configuration
Administration
Analysis performance
Server performance
Security/permissions
Licensing
Klocwork Static Code Analysis Web API
Klocwork Code Review Web API

Community

View help online
Visit RogueWave.com
Klocwork Support
Rogue Wave Videos

Legal

Legal information

Failed to lock file or directory: No locks available

When run, several Klocwork commands lock a file or directory that is located in the user home directory. For example, the kwauth command locks the ltoken file located in the .klocwork directory and the kwgcheck command locks the config directory.

The Network File System (NFS) has a file locking mechanism that can cause problems with Klocwork tools. To avoid file locking errors, do not locate your home directory on an NFS file system, or implement one of the following workarounds.

Workaround #1: Change the location of the Klocwork user home folder by setting -Duser.home in the Java options environment variable before running Klocwork commands, for example:
export _JAVA_OPTIONS="$_JAVA_OPTIONS -Duser.home=<path-to-non-NFS-filesystem>"
Workaround #2: Create a symbolic link to the .klocwork directory on a local file system, for example:
mkdir /space/kwhome
ln -s /space/kwhome $HOME/.klocwork