I exec stuff all the time from aolserver, all kinds of stuff. Don't
know if it's had negative impact or not. At a previous job, we had
several aolserver boxes that would exec some stuff thousands of times a
day. I'm going to recommend they try nsproxy.
Rusty
Nathan Folkman wrote:
[EMAIL PROTECTED] wrote:
On Saturday 19 August 2006 21:07, Tom Jackson wrote:
On Saturday 19 August 2006 19:12, Hossein Sharifi wrote:
(although I do plan to fix the
incorrect usage of exec as well)
So I've never heard that you can't use exec from AOLserver. How is this
supposed to be done? Where was this discussed? What would an error look
like?
Sorry to respond to my own last post, but I've been trying to find
out more about this problem of using tcl exec.
As far as I can tell, the problem is trying to use fork (in some tcl
extension that adds this) and not calling exec in the child process.
Is this even possible in exec to not call exec?
Does anyone know the status of this problem in the tcl community,
from what I have read, the solutions would not be good for AOLserver.
The best rundown, with links, is here:
<http://aspn.activestate.com/ASPN/Mail/Message/activetcl-dev/2848076>
tom jackson
--
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.
Something else to watch out for is the side effect of doing a fork()
then exec() from the main nsd process. There's a small window of time
where you can have double the memory of your main nsd process tied up
while the main nsd process space is copied. So, for example, if your
nsd runs really hot at say 1G, then you'd need at least an extra 1G,
and maybe more if you have multiple threads all trying to fork() and
exec() something. We've seen this with things like the nsdb code and
the new nsproxy code. Generally this isn't a problem, but something to
be aware of.
That said, a much better strategy is to immediately fork off an
nsproxy and do all further execs from within the nsproxy (tclsh) which
is considerably smaller then the main nsd process.
Just curious, what is it that you are looking to exec?
- n
- n
--
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.
