russo@chaos.utexas.edu (Tom Russo) (05/09/89)
We have recently installed the "maintenance tapes" to bring our IRIX up to
3.1D on 2 personal irises and a 4server8. Now 4sight seems to be broken in
a wierd way: Most of us here have user.ps files to remap keys, put up tools,
and fire up toolchests. Those of us who do have these things in our directories
now find that the tools and chests fail to come up one time in 3. The user.ps
files look like this:
---------here comes user.ps -----------
%
% User customization file.
%
/RestartActions [
{ (demochest) forkunix }
{ (clock) forkunix }
{ (wsh -n Editor -f Courier-Bold.16 -C 0,7,4,4 -c /usr/local/bin/emacs) forkunix}
{ (ical) forkunix }
{ (hostchest) forkunix}
] def
(clock) 1150 800 110 110 makepreference
(ical) 1000 800 preforigin
(wsh -n Editor -f Courier-Bold.16 -C 0,7,4,4 -c /usr/local/bin/emacs) 500 500 1000 800 makepreference
/replacekeys { % origkeyvals_array changedkeyvals_array -> -
{
/changedvals exch def
/origvals exch def
/keysdict origvals length dict def
keysdict begin
0 1 origvals length 1 sub {
dup origvals exch get changedvals
3 2 roll get def
} for
end
createevent dup begin
/Name origvals def
/Priority 2 def
/Exclusivity true def
end
expressinterest
{
awaitevent dup dup begin
/Name get keysdict exch get /Name exch def
end
redistributeevent
} loop
} fork pop pop pop
} def
% remap keys:
% caps lock (28420) mapped to control (left side) (28419)
% ~/` mapped to escape
% F1 mapped to ~`
% backspace mapped to delete
% delete mapped to backspace
[28420 28471 28562 28477 28478][28419 28423 28471 28478 28477] replacekeys
--------that was user.ps --------------
Has anyone else experienced similar problems? Is there something obviously
stupid in the user.ps? Clearly, the problem is rooted in the user.ps file,
since users without this file (most people use the same one as above) do
not have any problem with missing toolchests. We just can't see the problem.
Thanks...
+----------------------------------------------------------------------+
|Thomas Russo | russo@chaos.utexas.edu |
|Center for Nonlinear Dynamics, University of Texas at Austin |
+----------------------------------------------------------------------+moss@BRL.MIL ("Gary S. Moss", VLD/VMB) (05/09/89)
< We have recently installed the "maintenance tapes" to bring our IRIX up to
< 3.1D on 2 personal irises and a 4server8. Now 4sight seems to be broken in
< a wierd way: Most of us here have user.ps files to remap keys, put up tools,
< and fire up toolchests. Those of us who do have these things in our directories
< now find that the tools and chests fail to come up one time in 3.
I have a similar problem with IRIX 4D1-3.14711181642 (3.1A?), so I suspect
that it is not a new problem, but may have gotten worse. My /RestartActions
are defined as follows, but about every other time, the console window does
not appear, when I attempt a 'restart' from the 'Max' menu:
% specify window constraints, font and colors for console window
/RunConsole
{
(/etc/gl/startconsole -r1000 -s80,40 -m80,60 -fIris12.fm -C 0,7,4,1)
forkunix
} def
% specify customized 'wsh' procedure
/forkwsh
{
(wsh -t \$LOCHOST -r1000 -s80,60 -m80,60 -fIris12.fm -C 0,7,4,1
-n wsh)
forkunix
} def
/RestartActions [
% Caps-lock Ctrl (`/~) F1 -> Ctrl Caps-lock Esc (`/~)
[ 28420 28419 28471 28562 ] [ 28419 28420 28423 28471 ] replacekeys
{ (ical) forkunix }
{ forkwsh }
{ RunConsole }
] def
I have only included the part of my user.ps, but since this works
some of the time, and is straightforward usage, I suspect a 4Sight bug. If
someone wants to look into this, I'll gladly send them the entire source.
-mossmsc@ramoth.SGI.COM (Mark Callow) (05/11/89)
In article <12882@ut-emx.UUCP>, russo@chaos.utexas.edu (Tom Russo) writes: > We have recently installed the "maintenance tapes" to bring our IRIX up to > 3.1D on 2 personal irises and a 4server8. Now 4sight seems to be broken in > a wierd way: Most of us here have user.ps files to remap keys, put up tools, > and fire up toolchests. Those of us who do have these things in our directories > now find that the tools and chests fail to come up one time in 3. The user.ps > files look like this: There is a race condition between when the server starts listening and when StartMostThings is called in init.ps. We didn't see this until we started work on release 3.2. I'm not sure exactly what moved things into the window of vulnerability. Anyway here is a context diff which you can apply to the file /usr/NeWS/lib/NeWS/init.ps. --- Peter Broadwell Mark Callow *** old.init.ps Wed May 10 18:14:51 1989 --- init.ps Wed May 10 18:15:26 1989 *************** *** 572,577 } null framebuffer eventmgrinterest ] forkeventmgr def } def /&main {go! DebuggingServer? {executive} if} def --- 572,578 ----- } null framebuffer eventmgrinterest ] forkeventmgr def + StartMostThings } def /&main {go! DebuggingServer? {executive} if} def *************** *** 681,685 systemdict /cursorfont known {/ptr /ptr_m framebuffer setstandardcursor} if systemdict /ROOTPROC known { ROOTPROC killprocess systemdict /ROOTPROC undef } if - - StartMostThings --- 682,684 ----- systemdict /cursorfont known {/ptr /ptr_m framebuffer setstandardcursor} if systemdict /ROOTPROC known { ROOTPROC killprocess systemdict /ROOTPROC undef } if -- -Mark