On Mon, Nov 01, 1999 at 09:12:50PM +0200, Jukka Marin wrote:
   > > Netscape*useStderrDialog: False
   > > Netscape*useStdoutDialog: False
   > 
   > Hmm.. It's still doing it

   Soneone forgot to reload the X resources.. :-I

   Now it prints the same messages to the xterm window used to start
   Netscape - that's better.

   BUT, now Netscape froze again.  It's _not_ cleaning up the disk cache
   because there's no disk activity (according to systat vmstat).  It's
   not a network problem - Netscape doesn't even respond to the stop button.
   Netscape process is not using any CPU, it's sleeping in select(2).

[going slightly off topic]

Ya, been there...  Usually when the Java VM has started and there have
been a number of reloaded pages.


Here is another one to be aware of....

It appears that all versions of Netscape since 4.06 for some Unix
plateforms [HP-UX 10.xx and SunOS 5 for sure, perhaps others] suffer from
a bad interaction between the Java VM, SSL and the MAYSCRIPT ability.  If
those three are used together and there is more the one page reload, the
JVM will cease to operate, unless X events going on in the browser to
simulate it [i.e. moving the mouse pointer around, selecting menus,
etc...].  That is, all applets will stop running unless the hamster is
proded with X events.


   Sigh.. Internet is broken ;-)  It was much better 10 years ago.. you
   couldn't do much more than ftp or irc, but so what? :-)

Remember archie??

     -jm





Brad Spencer - brad@anduin.eldar.org   http://anduin.eldar.org
[finger brad@anduin.eldar.org for PGP public key]