From: Karl Eichwalder <ke@gnu.franken.de>
Cc: ding@gnus.org
Subject: Re: DoS message
Date: Sun, 11 Nov 2001 20:16:08 +0100 [thread overview]
Message-ID: <sheln5jeyv.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <ey7ksxkubu.fsf@vsu.ru> (Vladimir Volovich's message of "Sun, 11 Nov 2001 21:59:01 +0300")
Vladimir Volovich <vvv@vsu.ru> writes:
> was your system responsive enough?
Yes, no problem at all (besides the beeping); but it took me wonders.
> my system almost freezes: switching to another window takes ages
> (minutes)... typing charecters in other windows takes dozens of
> seconds too.
>
> i wonder why does this happen???
Me, too. I'm sure our heros here will tell us the next time.
--
ke@suse.de (work) / keichwa@gmx.net (home): |
http://www.suse.de/~ke/ | ,__o
Free Translation Project: | _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
prev parent reply other threads:[~2001-11-11 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-11 17:40 Vladimir Volovich
2001-11-11 18:42 ` Karl Eichwalder
2001-11-11 18:59 ` Vladimir Volovich
2001-11-11 19:16 ` Karl Eichwalder [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=sheln5jeyv.fsf@tux.gnu.franken.de \
--to=ke@gnu.franken.de \
--cc=ding@gnus.org \
--cc=keichwa@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).