Hi Paul,
With the conftest.c you provided, strace still hang.
Check for how many calls for chdir("confdir3"), it only has 110 times, then
hang after mkdir("confdir3", 0700 ...
Is there any directory limitation that can make on a server?
sjc-ads-7913:/ws/kellythw-sjc/rcs_try/getcwd-test% tail tr
chdir("confdir3") = 0
mkdir("confdir3", 0700) = 0
chdir("confdir3") = 0
mkdir("confdir3", 0700) = 0
chdir("confdir3") = 0
mkdir("confdir3", 0700) = 0
chdir("confdir3") = 0
mkdir("confdir3", 0700) = 0
chdir("confdir3") = 0
mkdir("confdir3", 0700
% grep 'chdir("confdir3")' tr | wc -l
110
Thanks,
Kelly
If you need support for DevX Tools: http://devxsupport.cisco.com/
Specifically, for NXOS, see -
https://wiki.cisco.com/display/NEXUSPMO/ContactingNexusOpsAndTools
On 11/5/20, 9:57 AM, "Paul Eggert" <egg...@cs.ucla.edu> wrote:
On 10/27/20 8:36 AM, Kelly Wang (kellythw) wrote:
> You are right, after remove confdir3, rerun strace hang.
> Checked tr output, it stopped at bunch of mkdir and chdir and no further
steps after that.
> mkdir("confdir3", 0700) = 0
> chdir("confdir3") = 0
How many chdir("confdir3") calls were there, exactly? On my platform there
were
1367.
My guess is that the getcwd system call hung on your platform, which
suggests a
kernel or filesystem bug somewhere.
What happens if you run the attached conftest.c instead? It's the same as
before, except with an 'alarm (10)' call. As before, run it like this in
your
development directory:
rm -fr conftest3
gcc conftest.c
strace -o tr ./a.out
and see how 'tr' ends if it hangs (which I hope it doesn't).
