Path: utzoo!attcan!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: korb@techsun1.cray.com (Bill Korb)
Newsgroups: comp.sys.sun
Subject: Re: SunOS 4.1 bombs exiting SunView or OpenWindows
Keywords: SunOS
Message-ID: <820@brchh104.bnr.ca>
Date: 12 Dec 90 17:28:18 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 20
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n384, Replies: v9n391
X-Sun-Spots-Digest: Volume 9, Issue 399, message 12
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

| In article <565@brchh104.bnr.ca> jle@cfm.brown.edu (Jon  Elion) writes:
| >We recently upgraded our Sun 3/470 to a Sun 4 (installing a 4/330 board).
| >As part of this process, we also upgraded from SunOS 4.0.3 to SunOS 4.1.
| >On most (but not all) occasions that we exit SunView, the system chokes
| >and goes into an automatic reboot.
|
| You may want to check your .login and .logout files.  You may be executing
| something which was compiled for a Sun-3.  Also check the paths for every
| thing you are executing,  you may have kept a path to Sun-3 code
| somewhere.  If you ever try running Sunview as a Sun-3 executeable in a
| SparcStation you will get almost the exact result you described.

We saw the same thing when I upgraded our SLC from 4.0.3 to 4.1.  Sun
admits it is an OS bug and is working on a fix.

Bill Korb
System Administrator
Cray Research, Inc.
Chippewa Falls, WI
william.korb@cray.com