🚀 go-pugleaf

I can not answer your specific question, but I too have noticed
hand-ups, core dumps, obtuce messages, etc. I seems that one
needs to know a lot of system stuff to run Explorer effectively.
Which is to be expected for the power and flexibility it offers.
So here are some observations. Let's have people add their own and
maybe we can start a FAQ.

Check these things when things go haywire:
   df  - check to see that your not running out of Arena or swap space
   tail -40 /usr/adm/SYSLOG  - this keeps a log of system errors

If your getting messages such as "Can not connect to named pipe", or
a slew of others. Go to another window and pwd, ls, df, etc might
give you a message such as too many open files. You need to rebuild
the kernel with better system variables - see /usr/explorer/unsupported/
Installation. Worse yet, anytime you install something?, the operating
system, you need to redo this.

Finally, I have noticed that explorer just won't work when you set
up the arena in a NFS mounted file system. I had it set to my scratch
disk which was fine, until I logged onto our 320/VGX which is cross-
mounted and uses the same ~/.explorerc file. They may actual document
this, but this is a reminder.

Let's see, any others?

Roger Crawfis
Lawrence Livermore National Laboratory
(crawfis@llnl.gov)