This was a lockd problem with the ksh history file. The workaround is
to make sure that the ksh history file is on a local disk. Patch
100999 (22 is the latest version) is the fix.
Thanx to those who replied:
"Fuat C. Baran" <fuat@watsun.cc.columbia.edu>
Richard Elling <Richard.Elling@eng.auburn.edu>
probert@cs.ucsb.edu (Dave Probert)
mikef@ttsi.tandem.com (Mike Fox)
Dan Stromberg - OAC-DCS <strombrg@hydra.acs.uci.edu>
jamest@sybase.com (James Terry)
"D. Hugh Redelmeier" <hugh@cs.toronto.edu>
see@uebemc.siemens.de (Seeger Michael)
Richard Elling <Richard.Elling@eng.auburn.edu>
The early/informative answers are below.
Thanx,
<mike
--------------------
Date: Tue, 31 Aug 1993 08:36:06 -0400
From: 25835-transue <odt@cc.bellcore.com>
Message-Id: <199308311236.AA18040@pleak.cc.bellcore.com>
To: mwmeyer@ingres.com
Subject: Re: Ksh hanging on startup
Content-Type: X-sun-attachment
----------
X-Sun-Data-Type: text
X-Sun-Data-Description: text
X-Sun-Data-Name: text
X-Sun-Content-Lines: 45
We had a similar circumstance here during login. We solved it by
putting the histrory file in /tmp. It is known bug with ksh and
Solaris 2.x (BugID 3001069). I have attached a synopsis of the
BugID. We use automount extensively and this may affect you if
using automount even automounting a local directory as it was in
our case.
We did exactly what it says in the workaround and it eliminated the
problem.
Good Luck.
-dan
-- Dan Transue |Realmail: odt@cc.bellcore.com Bellcore |FakeMail: bellcore!cc!odt 3 Corporate Place room 2K-210 |VoiceMail: (908) 699-5223 Piscataway, NJ 08854-> From sun-managers-relay@ra.mcs.anl.gov Tue Aug 31 03:33:20 1993 -> Sender: sun-managers-relay@ra.mcs.anl.gov -> Message-Id: <9308302209.AA16206@k9.ingres.com> -> To: sun-managers@eecs.nwu.edu -> Subject: Ksh hanging on startup -> Date: Mon, 30 Aug 93 15:09:39 -0700 -> From: mwmeyer@ingres.com -> Reply-To: mwmeyer@ingres.com -> Followup-To: junk -> Content-Length: 550 -> -> Ksh on a Solaris 2.2 workstation just started hanging. Since this is -> my workstation, I find this somewhat annoying. -> -> Symptoms: -> -> Logging in with ksh as my shell, or running ksh after logging in with -> csh as my shell, ksh just hangs after running through my dot files. -> The ksh chews up all/most available cpu, and doesn't respond to -> interrupts. Moving my dot files out of the way doesn't help, it works -> for other users, and this ksh cmp's equal to ksh from another 2.2 -> system. Any pointers to other things to check would be appreciated. -> -> Thanx, -> <mike -> ---------- X-Sun-Data-Type: default X-Sun-Data-Description: default X-Sun-Data-Name: solaris2.x_ksh_problems X-Sun-Content-Lines: 17
*Bug Id: 3001069 Category: network Subcategory: locking Release summary: sol2.1_x86preoem, mars_alpha3.0, mars, s493_beta1.3 Synopsis: lockd hogs CPU if ksh user has home dir NFS mounted from 4.X system Summary: There are occasional problems locking NFS files. This problem can occur between Solaris NFS clients and either SunOS 4.x or Solaris NFS servers and usually results in lockd consuming inordinate amounts of CPU time. Once this problem occurs, it is usually necessary to reboot the machine.
A common symtom of this problem is ksh users whose history file is NFS mounted may be unable to get a shell prompt when logging in. A workaround for this is to set you HISTFILE to be a local file (e.g. export HISTFILE=/tmp/username.hist).
-------------------- Date: Tue, 31 Aug 93 11:46:47 +0200 Message-Id: <9308310946.AA00925@mistral> To: mwmeyer@ingres.com Subject: Re: Ksh hanging on startup X-Sun-Charset: US-ASCII Content-Length: 449
Hi, try patch 100999-21. This worked for us.
+---------------------------+------------------------------------+ | Andreas Schroeder | Internet: as@uebemc.siemens.de | | Siemens AG, UEB ES A 14 | InterEUnet: as@uebemc.siemens.de | | Hofmannstrasse 51 | UUCP: as@uebemc.UUCP | | 81359 Muenchen | Phone: +49 89 722 23985 | +---------------------------+------------------------------------+
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:08:09 CDT