do-not-directly process not terminating

Sometimes when I exit SL normally and usually when I crash out of it, I find the 'do-not-directy' process that the secondlige shell script starts hangs about for a minute or two or even longer (with multiple crashes I can end up with several running if I don't watch my process table). This seems to be the cause of some instability and performance issues: if I kill it explicitly or wait for it to terminate itself, SL seems to go somewhat smoother.

A fresh SL login after a reboot usually works well, but whether I crash or exit with the quit menu/button I have HUGE trouble logging back in unless I reboot my system.

Tofu: what other processes does SL spawn that need to be killed (assuming some others are being left around after kill/quit) I can see the secondlife process and the do-not-directly process as obvious but are there any others I should be killing off before I attempt to relog?

...I gave up on trying to kill the dangling do-not-directly processes from the startup script it was intermittent and unreliable

i just kill the do-not-start... process suing the gnome thingie, it's the only process I stop after a Sl-crash, and almost never have problems with that...

I do the same with the KDE equivalent (KSysGuard) but seem to still get the region-connect-crash-on-subsequent-login problem often.

I am wondering if it could be a GL-initialisation issue with my crappy ATI card drivers (ATI seems to be the foundation of most of my SL -- and other GNU/Linux -- greif).

There is a guy in my college class who is a big ATI fan but can't afford to upgrade his 9600 with a new ATI 1X00 card, so I might be going nVidia sooner than I had thought