[esworp]

**b r a i n s s s***
ok, had to do that.

Seriously.. take a look at http://www.esworp.net/zombies.jpg and see for yourself.

I get three new OBEXAgent zombies everytime I unplug and replug in the bluetooth adapter (d-link usb). My rig looks like this: visor via cradle, t68i via bluetooth, and sometime I sync to .mac. Even with the zombie action, bluetooth still works, but after osx discovers the cellphone 5 or 6 times (like if I got to the bathroom and come back; that counts as one), the OBEX's start to max out the maximum allowable process count, and I have to reboot.

(Pretty wierd trying to "ls" in the terminal and be told you've used up all your processes.. like I forgot to pay my g4 bill or something)

Any clues?

I notice that whenever I initiate a bluetooth connection to send an image (as in http://www.esworp.net/cellcam/cellcam.html ) to the computer, I get four new Zombie OBEXAgents.. it's important to note that the transfer works fine nonetheless. What doesn't work is iSync if the sync is initiated with any Zombies present; if it's making hte bluetooth connection as part of the sync process, the zombies pop up, but the sync works properly.

If this is a unresolvable bug (which would suck...) is there a way to kill the zombie processes short of a reboot? Obviously, since they'er owned by root, I can't knock em out in the proces viewer, and using a kill -9 or -HUP gives me a no such process type of reply.

[int69h]

Zombie processes are already dead, hence the term. They stay in the process table because their parent forgot to wait() on them.

[Tritium]

If you can find out what the parent process id is, you can kill it and the zombie children will go away... that doesn't solve the root of your problem but it's better than rebooting