[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ghostscript-8.70-6 broke my lilypond, no more PDF

From: Matthias Kilian
Subject: Re: ghostscript-8.70-6 broke my lilypond, no more PDF
Date: Tue, 26 Apr 2011 09:03:00 +0200
User-agent: Mutt/

On Mon, Apr 25, 2011 at 05:54:24PM -0500, Ivan Kuznetsov wrote:
> > Could you try
> > to run ghostscript manually to convert it to pdf (but omit the `-q'
> > flag)? Like, just run
> >
> >        -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 \
> >        -sDEVICE=pdfwrite -sOutputFile="./song02.pdf" -c .setpdfwrite \
> >        -f ""
> >
> > from your shell.
> I just ran the above and song02.pdf was created with no errors.
> So only difference between the above command and what lilypond
> executes is the "-q" flag I see.  Why does the -q flag now fail?

I don't think it's the `-q' that causes the failure, because this
flag only makes ghostscript quiet (no startup message, no progress
information written to stdout).

My best guess is that the newer ghostscript (when run from within
lilypond) hits some resource limit like open file descriptors or
memory. But in this case it *should* have printed *some* error
message to stderr, and I've no idea why it didn't in the output you
pastet in your original mail.

Assuming that you're running a shell like ksh or bash, you can display
the current limits for file descriptors with

        ulimit -n

and the data size limit with

        ulimit -d

If those are rather small, try to increase them. For example 512 file
descriptors and 1GB data size:

        ulimit -Sn 512
        ulimit -Sd 1048576

But please note that this is just a wild guess. It may help or not.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]