defunct

what does kill exactly do? I have a parent process which is creating 100 (as an example) child processes one after another. At the end of any child's job, I kill the child with kill(pid_of_child, SIGKILL) and I cannot see that in ps output. But if something goes wrong with the parent process and I exit from the parent process with exit(1) (at this point only 1 child is there - I can check tht in ps ), at that point I see a lot of <defunct> processes whose ppid is pid of parent process. How is that possible? did kill not kill the child processes entirely? kill doesn't kill anything . It sends

I'm implementing a producer-consumer pattern in python using multiprocessing.Pool and multiprocessing.Queue . Consumers are pre-forked processes that uses gevent to spawn multiple tasks. Here is a trimmed down version of code: import gevent from Queue import Empty as QueueEmpty from multiprocessing import Process, Queue, Pool import signal import time # Task queue queue = Queue() def init_worker (): # Ignore signals in worker signal.signal( signal.SIGTERM, signal.SIG_IGN ) signal.signal( signal.SIGINT, signal.SIG_IGN ) signal.signal( signal.SIGQUIT, signal.SIG_IGN ) # One of the worker task

I'm having some extremely frustrating difficulty installing the bigrf R package. I have tried the following: install.packages('bigrf',repo='https://github.com/aloysius-lim/bigrf.git',type='source') ^^with dev mode on install_github("aloysius-lim","bigrf") install.packages("bigrf",source=true) These have all been tried on R build 2.14 (which bigrf was built on), 2.15, 3.0.2 and 3.1.1 I am getting a not available for build x' every time. Is bigrf defunct? I have seen a couple of posts here on SO which have used various builds of R requesting help with bigrf. the solutions IO have tried came from

I have a legacy stylesheet that is now full of unused styles. The problem is identifying the necessary from the unnecessary. Are there any tools to help with this? Fenton CSS Usage is a great Firefox add-in. You can browse multiple pages and it will work out which rules haven't been used on any of them - so it is more accurate than a tool that scans a single page. Mike You could try the Firefox Dust-Me Selectors add-on. Install Google's pagespeed plugin for firebug: http://code.google.com/speed/page-speed/ Then in Firebug, open the 'pagespeed' tab and, with 'performance' selected, click