On 13 Oct 2005 09:54:44 -0700, Paul Rubin wrote:
> Jorgen Grahn <[EMAIL PROTECTED]> writes:
>> It depends on what you mean by expensive -- web servers can fork for each
>> HTTP request they get, in real-world scenarios, and get away with it.
>
> This is OS dependent. Forking on Windows is much mo
Jorgen Grahn wrote:
> > Done once, it's usually not unacceptable.
>
> In fact, I can't think of a scenario where it /would/ be unacceptable ;-)
if you're stuck on a system that doesn't use copy-on-write ?
--
http://mail.python.org/mailman/listinfo/python-list
Grant Edwards <[EMAIL PROTECTED]> writes:
> Since the NT kernel is descended from VMS, I'm not surprised
> that a fork is expensive.
Apache 2.x supports concurrency via threading as an alternative to
forking, basically in order to get acceptable performance on Windows.
--
http://mail.python.org/m
On 2005-10-13, Paul Rubin <> wrote:
> Jorgen Grahn <[EMAIL PROTECTED]> writes:
>> It depends on what you mean by expensive -- web servers can fork for each
>> HTTP request they get, in real-world scenarios, and get away with it.
>
> This is OS dependent. Forking on Windows is much more
> expensive
Jorgen Grahn <[EMAIL PROTECTED]> writes:
> It depends on what you mean by expensive -- web servers can fork for each
> HTTP request they get, in real-world scenarios, and get away with it.
This is OS dependent. Forking on Windows is much more expensive than
forking on Linux.
--
http://mail.pytho
On Tue, 11 Oct 2005 22:01:23 GMT, Dan Stromberg <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Oct 2005 03:30:23 -0700, Mystilleef wrote:
>
>> Hello,
>>
>> Thank you. That's all I needed. For some reason, I had always assumed
>> forking was an expensive process. I guess I was ill-informed.
>
> In a loop,
On Tue, 11 Oct 2005 03:30:23 -0700, Mystilleef wrote:
> Hello,
>
> Thank you. That's all I needed. For some reason, I had always assumed
> forking was an expensive process. I guess I was ill-informed.
In a loop, yes, it's expensive.
Done once, it's usually not unacceptable.
--
http://mail.pyt
Mike Meyer wrote:
> The easy way to do all these things - from C, anyway - is with
> daemon(3). That isn't wrapped as part of the Python library. The
> easiest way to solve your problem may be write a wrapper for that
> call. If daemon exists on enough systems, submitting your wrapper as a
> patch
Hello,
Thanks to all the responders and helpers on the group. I'm learning
everyday.
Thanks
--
http://mail.python.org/mailman/listinfo/python-list
Hello,
Thank you. That's all I needed. For some reason, I had always assumed
forking was an expensive process. I guess I was ill-informed.
--
http://mail.python.org/mailman/listinfo/python-list
On 10 Oct 2005 22:58:08 -0700
[EMAIL PROTECTED] wrote:
> How do I implement this in my application written in python?
Google for "python daemonize".
--
jk
--
http://mail.python.org/mailman/listinfo/python-list
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Hello,
>
> A user of my application points me to a behavior in gVim,
> the text editor, that I would like to implement in my
> application.
>
> When gVim is launched from a shell terminal, it completely
> frees the terminal. You can continue to use
[EMAIL PROTECTED] enlightened us with:
> When gVim is launched from a shell terminal, it completely frees the
> terminal. [...] How do I implement this in my application written in
> python?
Using fork() and by catching the HUP signal.
Sybren
--
The problem with the world is stupidity. Not sayin
On Mon, 2005-10-10 at 22:58 -0700, [EMAIL PROTECTED] wrote:
> Hello,
>
> A user of my application points me to a behavior in gVim,
> the text editor, that I would like to implement in my
> application.
>
> When gVim is launched from a shell terminal, it completely
> frees the terminal. You can co
14 matches
Mail list logo
