SIGSTOP also can't be caught - it's signal 7.
Cheers,
Alan.
On 8/30/06, kim aldis <kim(at)aldis.org.uk> wrote:
The man pages for signal should give you a bunch of options, but it would
depend on what you mean by clean and how XSI does it's cleanup. In theory 9
is the only uncatchable signal so you should be able to send it, say, an 11
and XSI would trap the signal and exit cleanly. This was how we would kill
si3d back on IRIX but last time I tried it in XSI it didn't work so well.
That's not to say don't give it a go.
There are many advantages to writing your own frame loop for rendering and
one of those might be that you could add something that checks on a socket
at the end of each frame for a kill command of your own. Just a thought.
> -----Original Message-----
> From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On
> Behalf Of Bernard Lebel
> Sent: 29 August 2006 19:55
> To: XSI(at)Softimage.COM
> Subject: Killing XSIBATCH with a signal
>
> Hello,
>
> Anyone knows if there is a way to kill the XSIBATCH process with a
> signal to XSIBATCH?
>
> Right now we kill it by terminating the process explicitely, using
> killall -9 XSIBATCH and the likes. However I'd like to know if you can
> send a signal to XSIBATCH so it can exit cleanly (with a return value).
>
>
> Thanks
> Bernard
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in
> body:
> unsubscribe xsi
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
