Reply
Thread Tools
Posts: 191 | Thanked: 29 times | Joined on Sep 2007 @ Ottawa
#11
Originally Posted by penguinbait View Post
Anybody ever figure out what this is?
I haven't seen it since that one time. I think my rps has scared it away ;-)

Craig...
__________________
N800, Think Outside Kbd, 8GB SDHC Card (OCZ, ext2), and 8GB SD Card (Patriot formatted as VFAT)
Zaurus SL-6000, IR Keyboard, 1GB SD Card
 
Posts: 17 | Thanked: 1 time | Joined on Jul 2007
#12
The kill -9 xxxx command worked for me to kill it. I followed the advice and removed privoxy (which I wasn't using anyway), and I haven't seen "sh" run away since then. ...I think it worked.

Ryan ryanwright.org
 
penguinbait's Avatar
Posts: 3,096 | Thanked: 1,525 times | Joined on Jan 2006 @ Michigan, USA
#13
Originally Posted by rrwright View Post
The kill -9 xxxx command worked for me to kill it. I followed the advice and removed privoxy (which I wasn't using anyway), and I haven't seen "sh" run away since then. ...I think it worked.

Ryan ryanwright.org
I have never used privoxy. I do get this occaisionally and it seems to be caused (from my observations on my system) Closing an xterm without exiting properly. Since I started typing exit instead of hitting the X in the window, I stopped having this issue. I could not prove this though
 
Posts: 3,841 | Thanked: 1,079 times | Joined on Nov 2006
#14
exit is good.. hitting 'x' may sometimes be bad.. but I've only seen the problem if I hit 'x' when I'm running another program in xterm, e.g. 'vi'. Kill the xterm with 'x' when in 'vi' results in 100% CPU and a runaway shell.
__________________
N800/OS2007|N900/Maemo5
-- Metalayer-crawler delenda est.
-- Current state: Fed up with everything MeeGo.
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 16:53.