Hi,
logfetch of today's snapshot (4.2-RC-20060712.1) eats a lot of CPU while blocking the rest of local tests.
last pid: 8946; load averages: 1.00, 0.54, 0.60 11:11:38 318 processes: 314 sleeping, 2 running, 2 on cpu CPU states: 39.5% idle, 55.9% user, 1.2% kernel, 3.5% iowait, 0.0% swap Memory: 4096M real, 1814M free, 1686M swap in use, 17G swap free
PID USERNAME LWP PRI NICE SIZE RES STATE TIME CPU COMMAND8841 bb 1 10 0 1112K 880K cpu/0 1:18 48.09% logfetch 18229 dhenchoz 11 49 0 81M 71M run 3:03 3.02% mozilla-bin 22447 root 1 34 0 36M 32M run 3:48 2.11% Xsun 24038 root 1 49 0 80M 77M sleep 28:21 1.29% Xsun 8264 root 1 54 0 3136K 2000K cpu/2 0:01 1.21% top 22671 dfrise 1 49 0 18M 13M sleep 0:27 0.87% gnome-terminal 22663 dfrise 1 55 0 10M 8000K sleep 0:27 0.67% metacity 28415 dfrise 11 59 0 81M 68M sleep 3:21 0.56% mozilla-bin 24266 dhenchoz 1 59 0 9976K 7752K sleep 1:08 0.20% metacity 22665 dfrise 1 59 0 17M 14M sleep 0:18 0.20% gnome-panel 11600 nalkema 1 49 0 21M 16M sleep 15:53 0.09% gnome-terminal 15914 root 1 49 0 35M 32M sleep 0:24 0.09% Xsun 24270 dhenchoz 1 59 0 17M 12M sleep 1:00 0.07% gnome-panel 10504 root 1 49 0 254M 251M sleep 129:14 0.07% Xsun 22661 dfrise 1 59 0 3808K 2680K sleep 0:01 0.05% gnome-smproxy
How can I force it to generate a core file?
Dominique UNIL - University of Lausanne
On Mon, Jul 17, 2006 at 11:14:42AM +0200, Dominique Frise wrote:
logfetch of today's snapshot (4.2-RC-20060712.1) eats a lot of CPU while blocking the rest of local tests.
Yes, there is a problem with logfetch. Thought I had it solved, but I got reports yesterday that it wasn't fixed entirely. So it's back on the "known problems" list for the rel. candidate.
How can I force it to generate a core file?
kill -ABRT <pid-of-logfetch>
Regards, Henrik
Think this is my problem
Regards Lars
----- Original Message ----- From: "Henrik Stoerner" <henrik at hswn.dk> To: <hobbit at hswn.dk> Sent: Monday, July 17, 2006 11:24 AM Subject: Re: [hobbit] logfetch broken
On Mon, Jul 17, 2006 at 11:14:42AM +0200, Dominique Frise wrote:
logfetch of today's snapshot (4.2-RC-20060712.1) eats a lot of CPU while blocking the rest of local tests.
Yes, there is a problem with logfetch. Thought I had it solved, but I got reports yesterday that it wasn't fixed entirely. So it's back on the "known problems" list for the rel. candidate.
How can I force it to generate a core file?
kill -ABRT <pid-of-logfetch>
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Installed todays (18/7) snapshot. Client-tests still purple.
Regards Lars
----- Original Message ----- From: "lars ebeling" <lars.ebeling at leopg9.no-ip.org> To: <hobbit at hswn.dk> Sent: Tuesday, July 18, 2006 6:02 AM Subject: [hobbit] Snapshot 17/7 client-test went purple
Think this is my problem
Regards Lars
----- Original Message ----- From: "Henrik Stoerner" <henrik at hswn.dk> To: <hobbit at hswn.dk> Sent: Monday, July 17, 2006 11:24 AM Subject: Re: [hobbit] logfetch broken
On Mon, Jul 17, 2006 at 11:14:42AM +0200, Dominique Frise wrote:
logfetch of today's snapshot (4.2-RC-20060712.1) eats a lot of CPU while blocking the rest of local tests.
Yes, there is a problem with logfetch. Thought I had it solved, but I got reports yesterday that it wasn't fixed entirely. So it's back on the "known problems" list for the rel. candidate.
How can I force it to generate a core file?
kill -ABRT <pid-of-logfetch>
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
participants (3)
-
Dominique.Frise＠unil.ch
-
henrik＠hswn.dk
-
lars.ebeling＠leopg9.no-ip.org