[Xastir] Mac: odd process problem

Chip G. n1mie at ct.metrocast.net
Mon Jul 2 22:06:35 EDT 2007


I've written about this before. Never did get resolution. Now it's a  
problem again. Xastir is locking up on me after only a couple of  
hours of operation. This is a royal PITA because when it locks up I  
can't get it to quit unless I reboot the computer. I've tried kill  
and killall commands. They do NOTHING on a locked-up Xastir process  
(never had any other process refuse to quit before). Here's what it  
looks like.

> 21:43 [chip at mini:~] $ ps -acux | grep xastir
> chip     12012   0.1  1.3   126624   3396  p1- R       3:47PM    
> 2:58.20 xastir
> chip     12013   0.0  0.0        0      0  p1- Z      31Dec69    
> 0:00.00 (xastir)
> chip     12014   0.0  0.0        0      0  p1- Z      31Dec69    
> 0:00.00 (xastir)
> 21:43 [chip at mini:~] $ sudo kill -4 12012
> chip     12013   0.0  0.0        0      0  p1- Z      31Dec69    
> 0:00.00 (xastir)
> chip     12014   0.0  0.0        0      0  p1- Z      31Dec69    
> 0:00.00 (xastir)
> chip     12012   0.0  0.0        0      0  p1-  E      3:47PM    
> 0:00.00 (xastir)
> 21:44 [chip at mini:~] $

A couple of notes. Do not fixate on the kill command format used  
here. I had just randomly found that a -4 would at least get it to  
try and quit (I'm assuming that's what the parenthesis mean), no  
other command would even cause a change. I had only started one  
instance of Xastir, so I have no clue why there are three running. I  
just rebooted and all I did was start one instance of Xastir and this  
is what it says:

> 21:56 [chip at mini:~] $ ps -acux | grep xastir
> chip       304   2.1  0.1    73736    216  ??  R       9:55PM    
> 0:00.86 xastir
> chip       303   0.8  8.6   127620  22580  ??  Rs      9:55PM    
> 0:02.93 xastir
> chip       305   0.0  0.1    73736    192  ??  S       9:55PM    
> 0:00.00 xastir
> 21:56 [chip at mini:~] $

I have no idea what some of that stuff means ... time to RTFM for ps.

Three questions:
1. Why are three processes starting every time Xastir runs and what  
are the other processes doing?
2. When the process locks up, how do I get it to quit since KILL and  
KILLALL aren't working?
3. Why does the latest CVS builds on Xastir lockup after only a  
couple of hours operating?


73,
--de Chip (N1MIE) FN41bn





More information about the Xastir mailing list