git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 郑向昕 <pandazxx@gmail.com>
To: git@vger.kernel.org
Subject: Re: [Bug report] too many open files while cvsimport
Date: Mon, 24 Feb 2014 10:12:35 +0800	[thread overview]
Message-ID: <CABAQQMni8BY5AWZm_reH3e3nf8zkTCJYqzewrjcHg-jW82FaYA@mail.gmail.com> (raw)
In-Reply-To: <CABAQQMkSe6k9nNk3m6HSYmguuOvzp7n06dWNBRbaCxqGO=WEAQ@mail.gmail.com>

Hi

git reports "Unknown: error  Too many open files" when importing cvs
repository using cvsimport. The repository is kind of middle size one,
around 5000 files, thousands commits.

Command line is:
# git cvsimport -k -L 2

current ulimit:

# ulimit -a
-t: cpu time (seconds)              unlimited
-f: file size (blocks)              unlimited
-d: data seg size (kbytes)          unlimited
-s: stack size (kbytes)             10240
-c: core file size (blocks)         0
-m: resident set size (kbytes)      unlimited
-u: processes                       32767
-n: file descriptors                10000
-l: locked-in-memory size (kbytes)  32
-v: address space (kbytes)          unlimited
-x: file locks                      unlimited
-i: pending signals                 32767
-q: bytes in POSIX msg queues       819200
-e: max nice                        0
-r: max rt priority                 0

System: RHEL i386

# git --version
git version 1.9.0

I build git from source.

Best Regards,
Xiangxin Zheng
Best Regards,
Xiangxin Zheng


2014-02-21 13:48 GMT+08:00 郑向昕 <pandazxx@gmail.com>:
> Hi
>
> git reports "Unknown: error  Too many open files" when importing cvs
> repository using cvsimport. The repository is kind of middle size one,
> around 5000 files, thousands commits.
>
> Command line is:
> # git cvsimport -k -L 2
>
> current ulimit:
>
> # ulimit -a
> -t: cpu time (seconds)              unlimited
> -f: file size (blocks)              unlimited
> -d: data seg size (kbytes)          unlimited
> -s: stack size (kbytes)             10240
> -c: core file size (blocks)         0
> -m: resident set size (kbytes)      unlimited
> -u: processes                       32767
> -n: file descriptors                10000
> -l: locked-in-memory size (kbytes)  32
> -v: address space (kbytes)          unlimited
> -x: file locks                      unlimited
> -i: pending signals                 32767
> -q: bytes in POSIX msg queues       819200
> -e: max nice                        0
> -r: max rt priority                 0
>
> System: RHEL i386
>
> # git --version
> git version 1.9.0
>
> I build git from source.
>
> Best Regards,
> Xiangxin Zheng

           reply	other threads:[~2014-02-24  2:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CABAQQMkSe6k9nNk3m6HSYmguuOvzp7n06dWNBRbaCxqGO=WEAQ@mail.gmail.com>]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABAQQMni8BY5AWZm_reH3e3nf8zkTCJYqzewrjcHg-jW82FaYA@mail.gmail.com \
    --to=pandazxx@gmail.com \
    --cc=git@vger.kernel.org \
    /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 NNTP newsgroup(s).