From: Henning Hraban Ramm <texml@fiee.net>
To: mailing ConTeXt users list for <ntg-context@ntg.nl>
Subject: SOLVED: too many open files
Date: Thu, 15 Aug 2013 21:48:09 +0600 [thread overview]
Message-ID: <EAC7C721-8AB4-4B52-A3B8-86A4087A3289@fiee.net> (raw)
Hi again,
in my current songbook project I use t-filter with LilyPond as shown in http://wiki.contextgarden.net/LilyPond with latest beta MkIV on OSX.
Every line (system) of notes is included as its own PDF to leave the page breaking to ConTeXt. But since I have some hundred songs with each a few lines, it sums up...
I guess ConTeXt keeps every externalfigure open, since I get this error:
pages > flushing realpage 70, userpage 70
(c_helpmesee.tex
structure > sectioning > TitelKlein @ level 2 : 0.83 -> Help Me See
GNU LilyPond 2.16.2
ERROR: In procedure open-file:
ERROR: Too many open files: "/Applications/music/LilyPond.app/Contents/Resources/bin/../share/guile/1.8/ice-9/r4rs.scm"
LILYPOND > name='lilytemp/prd_alle-temp-lilypond-c_helpmesee.pdf'
LILYPOND > including system no.1
LILYPOND > including system no.2
LILYPOND > including system no.3
LILYPOND > including system no.4
LILYPOND > including system no.5
) (c_hochaufdem.tex </Users/hraban/workspace/liederheft/lilytemp/prd_alle-temp-lilypond-c_helpmesee-1.pdf> </Users/hraban/workspace/liederheft/lilytemp/prd_alle-temp-lilypond-c_helpmesee-2.pdf> </Users/hraban/workspace/liederheft/lilytemp/prd_alle-temp-lilypond-c_helpmesee-3.pdf> </Users/hraban/workspace/liederheft/lilytemp/prd_alle-temp-lilypond-c_helpmesee-4.pdfI/O Error: Couldn't open file '/Users/hraban/workspace/liederheft/lilytemp/prd_alle-temp-lilypond-c_helpmesee-4.pdf': Too many open files.
!LuaTeX error: xpdf: reading PDF image failed
==> Fatal error occurred, no output PDF file produced!
It works with songbook excerpts (some 30 songs). I don't understand if the error is really from LilyPond or from LuaTeX (I guess the former), and how I would be able to increase the number of possible files (in bash on OSX 10.8.4). So probably it's more a general Unix question than a ConTeXt one, but anyway...
ANALYSIS:
$ ulimit -n
256
$ sysctl kern.maxfiles
kern.maxfiles: 12288
$ sysctl kern.maxfilesperproc
kern.maxfilesperproc: 10240
SOLUTION:
$ ulimit -S -n 2048
(Properly describing a problem often helps to solve it. I send this for the records, in case someone runs into the same.)
Greetlings, Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2013-08-15 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 15:48 Henning Hraban Ramm [this message]
2013-08-15 16:09 ` Hans Hagen
2013-08-15 16:23 ` Aditya Mahajan
2013-08-17 15:13 ` Henning Hraban Ramm
2016-06-19 19:47 ` Mojca Miklavec
2016-06-19 21:49 ` Hans Hagen
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=EAC7C721-8AB4-4B52-A3B8-86A4087A3289@fiee.net \
--to=texml@fiee.net \
--cc=ntg-context@ntg.nl \
/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).