Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Jeff Higgins Newsgroups: comp.lang.java.programmer Subject: Re: interruptable process? Date: Fri, 09 Oct 2015 08:38:12 -0400 Organization: A noiseless patient Spider Lines: 51 Message-ID: References: <2b8f6bec-f879-4c13-97c5-60555f9a9ccb@googlegroups.com> <1dcc94ee-d9c8-49f0-80b7-64b99c5fb102@googlegroups.com> <3aad161f-2921-4511-9d23-d177078d034e@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Fri, 9 Oct 2015 12:36:48 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="a78aad8b483612fbf45d18e918df0cca"; logging-data="5103"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18EX3ysVa4m3niFq1xUB6X+TPDr2wWz9Y0=" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0 In-Reply-To: Cancel-Lock: sha1:1zjhsDEHk6iAS9Jxr9DaUko7I0s= Xref: csiph.com comp.lang.java.programmer:32846 On 10/09/2015 05:41 AM, Martin Gregorie wrote: > On Thu, 08 Oct 2015 21:15:30 -0400, Jeff Higgins wrote: > >> On 10/08/2015 04:55 PM, Jeff Higgins wrote: >>> On 10/08/2015 04:21 PM, Jeff Higgins wrote: >>> >>>>> I don't know if all this even makes sense or there's an easier way to >>>>> start processes on a machine that can be aborted from another >>>>> machine. >>>>> >>>>> >>> I'm not really sure why Java platform anyway. >>> >>> powershell> >>> >>> >>> >>> >> If using the OS services to kill a running blender instance seems >> drastic. >> >> Maybe you can finesse it with some python scripting. >> bpy.app.handlers.html> >> >> You'll still want a way to communicate. >> Maybe Jetty or Tomcat. >> > Seems heavy. I agree. Which is why I pointed at Powershell. It doesn't make sense to me to be running this with a JVM, all Java has is ProcessBuilder. Two cooperating Windows services, a Blender Job queue service, and a Blender render service seems the simplest and most controllable. Well, plus an app for users to request and track job tickets. > > How about two user threads? One to process entries on a queue of blender > requests and the other to monitor a socket for blender requests and > action them [add/delete queue entries and, on request, kill the current > blender process]. > > Question for the OP: it appears that any user can add blender tasks to > the queue, but can any user kill the current blender task regardless of > who submitted it? > It's bad enough that an administrator can shut down my jobs, now you want to let Bob do it?