From: "Kelly Wang (kellythw)" <kellythw@cisco.com>
To: Paul Eggert <eggert@cs.ucla.edu>, Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: "Srini Garlapalli (sgarlapa)" <sgarlapa@cisco.com>,
"bug-rcs@gnu.org" <bug-rcs@gnu.org>,
Gnulib bugs <bug-gnulib@gnu.org>,
"Yi Yan (yyan)" <yyan@cisco.com>
Subject: Re: rcs configure hang
Date: Thu, 5 Nov 2020 21:18:55 +0000 [thread overview]
Message-ID: <97199A9C-18BE-4A6D-A988-20F06B653AF7@cisco.com> (raw)
In-Reply-To: <8f7b27d9-ce6c-3846-0065-d455ac4bd861@cs.ucla.edu>
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" <eggert@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).
next prev parent reply other threads:[~2020-11-05 21:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2B072F48-AF8B-47E0-AC5D-C9AB5E0DC4AD@cisco.com>
[not found] ` <873627odbp.fsf@gnuvola.org>
2020-10-22 22:02 ` rcs configure hang Paul Eggert
2020-10-26 16:13 ` Kelly Wang (kellythw)
2020-10-26 22:55 ` Paul Eggert
2020-10-27 15:36 ` Kelly Wang (kellythw)
2020-11-05 16:11 ` Kelly Wang (kellythw)
2020-11-05 17:57 ` Paul Eggert
2020-11-05 21:18 ` Kelly Wang (kellythw) [this message]
2020-11-05 21:36 ` Paul Eggert
2020-11-05 22:28 ` Kelly Wang (kellythw)
2020-11-05 22:52 ` Paul Eggert
2020-11-06 16:20 ` Kelly Wang (kellythw)
2020-11-06 17:40 ` Paul Eggert
2020-11-06 22:15 ` Kelly Wang (kellythw)
2020-11-09 9:14 ` Florian Weimer
2020-11-10 17:37 ` Kelly Wang (kellythw)
2021-01-11 16:19 ` Florian Weimer
2021-01-10 22:04 ` Thien-Thi Nguyen
2021-01-11 16:06 ` Kelly Wang (kellythw) via Gnulib discussion list
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=97199A9C-18BE-4A6D-A988-20F06B653AF7@cisco.com \
--to=kellythw@cisco.com \
--cc=bug-gnulib@gnu.org \
--cc=bug-rcs@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=sgarlapa@cisco.com \
--cc=ttn@gnuvola.org \
--cc=yyan@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).