psa@otter.hpl.hp.com (Patrick Arnold) (01/16/89)
One possibility is that your DISPLAY environment variable is set to unix:0. For some reason which I haven't managed to isolate this causes a kernel panic and shuts down the system (pretty spectacularly). The fix is to set the DISPLAY environment variable to `hostname`:0. For example if your hostname (as returned by the hostname command) is parnold then export DISPLAY=parnold:0 for ksh setenv DISPLAY parnold:0 for csh DISPLAY=parnold:0 export DISPLAY for sh should allow it to run. Maybe someone could enlighten me as to why a user program can have such a catastrophic on a system. Patrick.
fkittred@bbn.com (Fletcher Kittredge) (01/18/89)
Bet it has something to do this the lack of Unix domain sockets under HP-UX. Most Unix-based X implementations use sockets for communications between clients and servers on the same system, i.e. when DISPLAY is "unix:0". regards, fletcher Fletcher E. Kittredge fkittred@bbn.com
harry@hpcvlx.HP.COM (Harry Phinney) (01/18/89)
> One possibility is that your DISPLAY environment variable is set to unix:0. > For some reason which I haven't managed to isolate this causes a kernel > Maybe someone could enlighten me as to why a user > program can have such a catastrophic on a system. > Patrick. Because of a bug. If a program such as GNUemacs does an ioctl() to the u-domain socket which the socket code doesn't support, it can cause the kernel to panic. Our product-version libX11.a traps these bogus ioctl() calls, and future versions of the HP-UX kernel will not exhibit this unfortunate behavior. Harry Phinney