I know this is more of a user question, but I don't think I'm going to find anyone that's going to be able to answer it other than here.
I'm using the GIMP to create custom graphics on the fly for a CMS by calling the script from the web page through ASP.NET. Now, I wouldn't blame anyone for saying, "Stop right there. That's your problem."
The problem I'm having is that I'm calling the script like this: gimp -i -b "myscript" -b "gimp-quit 0"
Immediately upon firing up the script, the Task Manger reports creation of a gimp.exe process. Then it forks another gimp.exe process. This one fires up script-fu.exe, does its thing, dies, and kills the second gimp.exe. However the first one stays running and will not quit.
On a server with hundreds of clients creating images with these scripts, within an hour I can be left with a few hundred gimp.exe processes running, which just about takes the server down!
So I have two questions:
1) Why is calling the script this way (which, btw, is the way it suggests on http://www.gimp.org/tutorials/Basic_Batch/) firing two gimp.exe processes and only killing one of them?
2) On a server where a hundred of these scripts could be running at one time, how does gimp-quit know which process to kill?
Thanks,
Roger Penn
Ignoramus extrordinaire
_______________________________________________ Gimp-developer mailing list Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
