Re: [AOLSERVER] Suicidal Child Process - SANE
Ian Harding wrote:
> This is kind of odd
>
> % catch [exec scanimage] foo
> Terminated
You're probably not getting what you expected. You probably menat:
% catch {exec scanimage} foo
Note: curly braces vs. square brackets.
> Is there any way to prevent this from killing my server in the
> meantime or is "catch" the biggest gun I have for that?
If you're brave and persistent, you could figure out how to set up the
nsdci module and use ns_proxy to run the command in a proxy process
outside the nsd. This way, if the command terminates the process, it'll
simply terminate the proxy and not the main nsd.
--
Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/
Panoptic Computer Network | http://panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
Re: [AOLSERVER] Suicidal Child Process - SANE
If you're running nsd 4.5, nsproxy should help insulate your nsd process from whatever's happening with scanimage... This command provides a simple, robust proxy mechanism to evaluate Tcl scripts in a separate, pipe-connected process. This approach can be useful both to isolate potentially thread-unsafe code outside the address space of a multithreaded process such as AOLserver or to enable separation and timeout of potentially misbehaving, long running scripts. On 04/12/2008, at 11:23 AM, Ian Harding wrote: This is kind of odd % catch [exec scanimage] foo Terminated When I exec scanimage from inside AOLServer, it goes ahead and shuts down the server. I figured out that it happens when the scanner is on, and ready, but does not have a document in the ADF. From the command line it looks like this $ scanimage scanimage: sane_start: Document feeder out of documents scanimage: Received signal 15 scanimage: Trying to stop scanner scanimage: Received signal 15 scanimage: Aborting There may be a "status" of some kind I can check from SANE without crashing before I try scanning but I haven't found it yet. Is there any way to prevent this from killing my server in the meantime or is "catch" the biggest gun I have for that? Thanks, - Ian -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED] > with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Suicidal Child Process - SANE
Years ago I connected to AOLserver using nscp and when I was done I would type 'exit' which caused AOLserver to shutdown (there's now a special exit command created within nscp's interp that does a no-op). There might be something similar going on here such that scanimage's termination / signal / error may be leaking through to AOLserver and causing it to quit. See what happens when you use -ignorestderr on exec. /s. On Dec 3, 2008, at 7:23 PM, Ian Harding wrote: This is kind of odd % catch [exec scanimage] foo Terminated When I exec scanimage from inside AOLServer, it goes ahead and shuts down the server. I figured out that it happens when the scanner is on, and ready, but does not have a document in the ADF. From the command line it looks like this $ scanimage scanimage: sane_start: Document feeder out of documents scanimage: Received signal 15 scanimage: Trying to stop scanner scanimage: Received signal 15 scanimage: Aborting There may be a "status" of some kind I can check from SANE without crashing before I try scanning but I haven't found it yet. Is there any way to prevent this from killing my server in the meantime or is "catch" the biggest gun I have for that? Thanks, - Ian -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED] > with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
