Tuxcards + run away process

2004-01-27 Thread epilogue

Take II.:)

-
Begin forwarded message:

Date: Mon, 19 Jan 2004 20:29:12 -0500
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Tuxcards + run away process


Hello all,

I have been having problems with the program Tuxcards (ports/deskutils). 
After about 5 minutes open, it's process seems to run away (whether or not
I am actively using the program).

I have built Tuxcards from ports and also tried installing the pkg, but
both yield the same result:

last pid: 14101;  load averages:  0.59,  0.21,  0.15   
 up 0+00:34:17  20:05:28 36 processes:  4 running, 32 sleeping
CPU states: 95.3% user,  0.0% nice,  0.8% system,  3.9% interrupt,  0.0%
idle Mem: 85M Active, 91M Inact, 40M Wired, 3048K Cache, 48M Buf, 154M Free
Swap: 800M Total, 800M Free

PID USERNAME PRI NICE  SIZERES STATETIME   WCPUCPU COMMAND
14014 epi 49   0 24716K 20680K RUN  0:58 90.19% 90.19% tuxcards
172epi 28   0 41648K 40152K RUN  0:59  0.05%  0.05% XFree86
186epi  2   0 41252K 33388K poll 0:17  0.00%  0.00%  opera
...

I would like to trace the problem, but am unsure where to start.  If anyone
could point me in the right direction, it would be very much appreciated.


Thanks!
epi
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Tuxcards + run away process

2004-01-27 Thread kitsune
On Tue, 27 Jan 2004 01:49:07 -0500
[EMAIL PROTECTED] wrote:

 
 Take II.:)
 
 -
 Begin forwarded message:
 
 Date: Mon, 19 Jan 2004 20:29:12 -0500
 From: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: Tuxcards + run away process
 
 
 Hello all,
 
 I have been having problems with the program Tuxcards
 (ports/deskutils). After about 5 minutes open, it's process seems to
 run away (whether or not I am actively using the program).
 
 I have built Tuxcards from ports and also tried installing the pkg,
 but both yield the same result:
 
 last pid: 14101;  load averages:  0.59,  0.21,  0.15
   
  up 0+00:34:17  20:05:28 36 processes:  4 running, 32 sleeping
 CPU states: 95.3% user,  0.0% nice,  0.8% system,  3.9% interrupt, 
 0.0% idle Mem: 85M Active, 91M Inact, 40M Wired, 3048K Cache, 48M
 Buf, 154M Free Swap: 800M Total, 800M Free
 
 PID USERNAME PRI NICE  SIZERES STATETIME   WCPUCPU
 COMMAND 14014 epi 49   0 24716K 20680K RUN  0:58 90.19%
 90.19% tuxcards 172epi 28   0 41648K 40152K RUN 
 0:59  0.05%  0.05% XFree86 186epi 2   0 41252K
 33388K poll 0:17  0.00%  0.00%  opera...
 
 I would like to trace the problem, but am unsure where to start.  If
 anyone could point me in the right direction, it would be very much
 appreciated.

Check out ktrace. I've used a bit when trouble shooting stuff and it
can be handy at times.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Tuxcards + run away process

2004-01-19 Thread epilogue
Hello all,

I have been having problems with the program Tuxcards (ports/deskutils). 
After about 5 minutes open, it's process seems to run away (whether or not
I am actively using the program).

I have built Tuxcards from ports and also tried installing the pkg, but
both yield the same result:

last pid: 14101;  load averages:  0.59,  0.21,  0.15   
 up 0+00:34:17  20:05:28 36 processes:  4 running, 32 sleeping
CPU states: 95.3% user,  0.0% nice,  0.8% system,  3.9% interrupt,  0.0%
idle Mem: 85M Active, 91M Inact, 40M Wired, 3048K Cache, 48M Buf, 154M Free
Swap: 800M Total, 800M Free

PID USERNAME PRI NICE  SIZERES STATETIME   WCPUCPU COMMAND
14014 epi 49   0 24716K 20680K RUN  0:58 90.19% 90.19% tuxcards
172epi 28   0 41648K 40152K RUN  0:59  0.05%  0.05% XFree86
186epi  2   0 41252K 33388K poll 0:17  0.00%  0.00%  opera
...

I would like to trace the problem, but am unsure where to start.  If anyone
could point me in the right direction, it would be very much appreciated.


Thanks!
epi
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]