From: Michael Welle <m.welle@gmx.net>
Subject: Re: Duration of gnus-change-server
Date: Thu, 27 Jan 2005 17:36:17 +0100 [thread overview]
Message-ID: <pan.2005.01.27.16.36.12.974526@gmx.net> (raw)
In-Reply-To: <86vf9igbmq.fsf@lapchly.ted.ericsson.se>
Hi Christian,
On Thu, 27 Jan 2005 16:00:45 +0100, Christian Lynbech wrote:
>>>>>> "Michael" == Michael Welle <m.welle@gmx.net> writes:
>
> Michael> Gnus is running for 16 hours now, consuming 100% cpu with a constant
> Michael> memory footprint. I am subscribed to about 40 groups and using a 1.2 MHz
> Michael> x86 machine.
>
> Presumably, your emacs process is toasted. It happens once in a while,
> later emacs versions is not entirely as robust as they used to be.
>
> Try taking a look on the process with strace, you may find that emacs
> is in rather tight loop apparently doing nothing else but calling
> gettimeofday or something similar.
The process is doing some read and write syscalls. Hm, but gnus has not
talked to the newsservers for hours now. I will wait for another hour and
than kill the beast.
Michael
PS: The machine is in the 1200 MHz class, not 1.2 MHz ;).
prev parent reply other threads:[~2005-01-27 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 12:07 Michael Welle
2005-01-27 15:00 ` Christian Lynbech
2005-01-27 16:36 ` Michael Welle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2005.01.27.16.36.12.974526@gmx.net \
--to=m.welle@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).