Hi,
I run gimp and mod_perl on a production server and trigger longer jobs
using the 'at' command so as not to keep users hanging around for a
result. Some of the runs can generate upwards of 1,000 or so images, so
the connections were timing out long before the job ever ended.
For shorter jobs,
On Sun, Oct 04, 2009 at 04:33:28PM -0400, Vio wrote:
> You're right. Keeping a running Gimp daemon in memory would most
> certainly speed things up (for subsequent calls)
This worked very well with gimp-perl and mod_perl 10 years ago.
It was relatively easy to establish a persistent connection fro
You're right. Keeping a running Gimp daemon in
memory would most certainly speed things up
(for subsequent calls)
I recall the python tutorial has some sample code
on writing simple servers in python (so, the python code
is already available, therefore I'd guess it's probably
just a matter of impo
I haven't tried mod_wsgi yet, so I'm doing it using mod_python.
(I don't see a compelling reason to dump mod_python yet, not
to mention the learning curve and potential time-cost to convert
my scripts from mod_py to mod_wsgi - I don't really know if there
are any, just guessing here...)
Invoking G
i consider myself pretty well versed with efficiency based upon server
performance and apache conforms for me pretty well in plugging in modules to
suite my needs and users demands. But I just don't see how you can use Common
Gateway Interfacing for this task. I found your thread through a search e
Thanks for the hints ...
Some interesting developments while running under sudo.
The first run:
-
sudo -u www-data gimp --no-interface --batch='(python-fu-pdf2jpg
RUN-NONINTERACTIVE
"/dd/d/app/front/PAK_live/srvr/xformx.com/run/pdf_forms/le-50.0.11.01(2008-10)d8.pdf"
)'
On 10/02/2009 05:47 PM, Vio wrote:
> gimp --no-interface --batch='(python-fu-pdf2jpg RUN-NONINTERACTIVE
> "/path/to/image/to/proces.pdf" )' --batch='(gimp-quit 1)'
>
> doesn't get executed. Or it does but fails silently - which is not
> very helpful here !!
Does it help if you set the GIMP2_DIRE
On Friday 02 October 2009 18:47:46 Vio wrote:
> This would suggest a permissions problem, but I'm not sure.
> I wonder: does Gimp need to write to the user home directory by any chance?
> In that case, 'www-data' (the apache user) doesn't have a home
> directory per se.
Gimp needs a place IIRC desi
Hello,
I've been trying to debug invoking my gimp plug-in from an apache
module for past 3 days without much success.
I'm sure others tried the same, but Google didn't help much in finding
these gems, so far.
So maybe a fresh pair of eyeballs may have other ideas ...
Ok, basically, I have a pytho
