Troubleshooting
Problem
The getcwd() system call may erroneously return an error EACCES or EPERM under certain circumstances when set to an IBM Rational ClearCase view and running on an Oracle Solaris 10 or Solaris 11 system. This error is typically only seen when running in a Solaris 10 Non-Global Zone or Branded Zone. The exact sequence of events that causes the error depend on the underlying filesystem, so the exact use case can vary. A common example of a program which uses the getcwd() system call is the pwd command.
Symptom
The symptom of this problem is an error on Solaris 10 and Solaris 11 systems when using ClearCase, such as:
pwd: cannot determine current directory!
If the failing command is part of a build which is executing, the user may not see the actual error, but the symptom may be that the build fails.
The error may be returned from any executable which invokes the getcwd() system call.
The error is more likely to occur for applications deployed in a Solaris 10 or Solaris 11 Non-Global Zone or Branded Zone.
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
06 November 2018
UID
swg21501830