On 10/18/2013 8:52 AM, Марк Коренберг wrote:
import prctl
This is not a stdlib module.
prct.set_pdeathsig(.)
if os.getppid() == 1:
raise AlreadyDead()
What is your point?
Your signature said
>Segmentation fault
If you meant that the above code segfaults, then there is a bug in
prct
El 18/10/13 13:18, John Ladasky escribió:
What a lovely thread title! And just in time for Halloween! :^)
LOL
Couldn't that be construed as "sexism"?
Next we'll have a new long moronic thread about sexism and
discrimination in mail subjects. Which will, as usual, leave a lot of
satisfied eg
What a lovely thread title! And just in time for Halloween! :^)
--
https://mail.python.org/mailman/listinfo/python-list
import prctl
prct.set_pdeathsig(.)
if os.getppid() == 1:
raise AlreadyDead()
--
Segmentation fault
--
https://mail.python.org/mailman/listinfo/python-list
I like 2) the most. I do have access to the child. The child is a process
started with multiprocessing.Process(function). How do I _not_ set an SID?
thanks,
--mihai
On Wed, Dec 7, 2011 at 2:50 PM, Dan Stromberg wrote:
> On 12/7/11, Mihai Badoiu wrote:
> > ok, so the code is something like
On 12/7/11, Mihai Badoiu wrote:
> ok, so the code is something like
> #process A
> p = Process(...)
> p.daemon = 1
> p.start() # starts process B
> ...
>
> If process A dies (say error, or ctrl-c), or finishes, then process B also
> dies. But if process A is killed with the "kill" command
ok, so the code is something like
#process A
p = Process(...)
p.daemon = 1
p.start() # starts process B
...
If process A dies (say error, or ctrl-c), or finishes, then process B also
dies. But if process A is killed with the "kill" command, then process B
soldiers on...
Any idea on how t
I think the OP meant when the parent gets killed (by ctrl+c or similar),
not deleted. At least that's what I think when I think of a program being
killed. Is it even possible to send a signal in such a case?
Cheers,
Jack
On Fri, Dec 2, 2011 at 4:27 PM, 8 Dihedral wrote:
> Please check Erla
Please check Erlang that spawn so easily. And there are Python packages can do
the same task.
--
http://mail.python.org/mailman/listinfo/python-list
On Sat, Dec 3, 2011 at 2:57 AM, 8 Dihedral
wrote:
> Multiple thread supporting programming languages in true OOP as Erlang and
> Python do not talk about POSIX signals.
The OP talked about multiprocessing. Each thread of execution is a
separate context, and can receive signals.
ChrisA
--
On Friday, December 2, 2011 11:13:34 PM UTC+8, Chris Angelico wrote:
> On Sat, Dec 3, 2011 at 2:05 AM, Mihai Badoiu wrote:
> > In the multiprocessing module, on a Process p, by just doing p.daemon=1
> > before p.start(), we can make the child die when the parent exits. However,
> > the child does
I've been in philosophical discussions all day.
This topic title makes me cringe
:P
--
http://mail.python.org/mailman/listinfo/python-list
On Sat, Dec 3, 2011 at 2:05 AM, Mihai Badoiu wrote:
> In the multiprocessing module, on a Process p, by just doing p.daemon=1
> before p.start(), we can make the child die when the parent exits. However,
> the child does not die if the parent gets killed.
> How can I make sure the child die when
In the multiprocessing module, on a Process p, by just doing p.daemon=1
before p.start(), we can make the child die when the parent exits.
However, the child does not die if the parent gets killed.
How can I make sure the child die when the parent gets killed?
thanks,
--mihai
--
http://mail.py
14 matches
Mail list logo
