From: mar@uebemc.siemens.de (Markus Roesch)
To: zsh-workers@math.gatech.edu
Cc: mar@uebemc.siemens.de
Subject: Zsh-2.6beta11: Zombies on Sparc 4-CPU machines
Date: Thu, 9 Nov 1995 12:06:43 +0100 [thread overview]
Message-ID: <9511091106.AA27016@graphix> (raw)
Dear "zsh-wokers" (whoever that may be ...):
I've been working with zsh for some time now and I feel
really comfortable with it. It does a great job!
However, I've got problems with any zsh version from 2.5.x (including
the latest 2.6beta11) running on Sun Sparc workstations (Solaris2.3 or 2.4),
especially on Sparc-20 machines with 4 CPUs:
When zsh is not terminated via a regular exit or logout
(but rather via killing an xterm window or a rlogin session remotely)
it hangs up as a "zombie" (I guess that's the reason to call it z-sh :-))
and consumes all of the CPU time in a kind of endless loop.
Sometimes the superuser can kill this process, but sometimes the
whole machine has to be restartet. This is really annoying!
Is this a known bug (or a feature) ??
I did a ./configure sparc-sun-solaris2.3
the make-ing and the installation of zsh went fine.
I followed the hints in FAQ to substitute the login csh by a login zsh
(via exec <path>/zsh -l) since I can not install zsh as root on our machines.
Currently I am setting the following options in my .zshrc:
set -o autolist -o automenu +o bgnice -o ignoreeof -o histignoredups \
-o histnostore -o listambiguous +o markdirs -o menucomplete -o notify \
-o pushdignoredups
What am I doing wrong here ??
Any answer will be greatly appreciated!
Thanx in advance!
Markus.
----
Dr. Markus Roesch E-Mail: mar@uebemc.siemens.de __o
SIEMENS AG, OEN TR EC 24 Phone: +49-89-722-21895 _`\<,_
Hofmannstr. 51, D-81359 Munich, Germany_______Fax: +49-89-722-26768_____(_)/ (_)
reply other threads:[~1995-11-09 11:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9511091106.AA27016@graphix \
--to=mar@uebemc.siemens.de \
--cc=zsh-workers@math.gatech.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).