From: Suzanne H. <Suz...@st...> - 2002-04-29 17:42:15
|
In trying to get a reasonable baseline for some of our testing, we noticed that readlink04 does not seem to be happy about running on redhat 7.1. The messages it gives with both TMPDIR and TDIRECTORY set to /tmp are: [root@redhat readlink]# ./readlink04 execvp: No such file or directory readlink04 1 BROK : execvp() failed readlink04 1 FAIL : readlink() on slink_file failed, errno=2 : No such file or directory readlink04 1 FAIL : readlink() on slink_file failed, errno=2 : No such file or directory Out of curiosity, since I know that the creat_slink program (which is what is trying to be execvp'd) is actually in the same directory as the readline04 program, I entered in the full path of the creat_slink program to the variable in question, compiled, and ran it. This fixed the problem, but is obviously not something people want to be doing. So, I investigated further. The setup function, which is what uses the failing execvp call, seems to change into a temporary directory, presumably to stick the tempfiles being created into. However, it does not seem to change *back* to the original directory (saved in the bin_dir variable in the setup function) before trying to use the failing execvp call. I looked at the expected failures for the version I'm using, ltp-20020408, and while readline04 showed up as something expected to fail only a few times on long runs, it was *not* expected to fail every time. Which indicates to me that it's somehow working elsewhere. Because of this, I'm not completely confident in my diagnosis of the problem, and half wonder if there was some step I missed in my attempt to run just this test to track down the problem. I would appreciate feedback in regards to how accurate my diagnosis of the issue here is. Thanks! Suzanne Hillman |