Kbase P154347: OS-COPY fails with OS-ERROR 2
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
03/11/2009 |
|
Status: Unverified
SYMPTOM(s):
OS-COPY fails with OS-ERROR 2
Failing statement similar to:
OS-COPY VALUE(SEARCH("mysymlink/myfile")) "/home/me/myfile".
FACT(s) (Environment):
The following statement:
MESSAGE SEARCH("mysymlink/myfile").
displays:
./mysymlink/myfile
File being copied is in directory accessed through a symbolic link under the current directory("mysymlink" in the above example), which is also the users home directory ("/home/me" in the above example).
Propath is similar to:
.,/other1/other2,/home/me,/usr/dlc,/usr/dlc/bin,/other1/other2/results,/usr/dlc/tty,/usr/dlc/tty/adecomm.pl,/usr/dlc/tty/adeshar.pl,/usr/dlc/tty/adeedit.pl,/usr/dlc/tty/adecomp.pl,/usr/dlc/tty/prodict.pl,c,dlcres
When "." is removed from the propath, OS-COPY succeeds.
OS-COPY succeeds for other users with similar configurations.
FILE-INFO:FULL-PATHNAME shows the root directory ("/") being used by OpenEdge in place of the current directory.
The following statement succeeds:
OS-COMMAND SILENT cp ./myfile
The OpenEdge executable file _progres is not owned by root.
UNIX
Progress 9.x
OpenEdge 10.x
CAUSE:
_progres was started in the user's home directory, but it did not have write permission to that directory. In such a case, _progres uses the root directory as the working directory.
FIX:
Set the permissions of the directory in which _progres is started so that _progres has write access.