Very Computer

Last time I've tried to start X (after a reboot), I've got the
following:

     Fatal server error
     Server is already active for display 0

     giving up
     xinit: Invalid argument (errno 22): unable to connect to Xserver
     xinit: No such process (errno 3): Server error

I'm not able to start X, neither with 'startx' nor with 'xdm'. And I've
rebooted the system, switched it off etc. - with no success. I've had the
same mess some month before, and I had to reinstall everything again ...
But maybe there's an easier way to kill the pseudo-active server ?!

Any clues ?

Sven

-------------------------------------------------------------------------------

Technische Universitaet Braunschweig

Quote:

>     giving up
>     xinit: Invalid argument (errno 22): unable to connect to Xserver
>     xinit: No such process (errno 3): Server error

>I'm not able to start X, neither with 'startx' nor with 'xdm'. And I've
>rebooted the system, switched it off etc. - with no success. I've had the
>same mess some month before, and I had to reinstall everything again ...

Quote:>But maybe there's an easier way to kill the pseudo-active server ?!

=============================================================================

=============================================================================

Quote:> Last time I've tried to start X (after a reboot), I've got the
> following:
>      Fatal server error
>      Server is already active for display 0
>      giving up
>      xinit: Invalid argument (errno 22): unable to connect to Xserver
>      xinit: No such process (errno 3): Server error
> I'm not able to start X, neither with 'startx' nor with 'xdm'. And I've
> rebooted the system, switched it off etc. - with no success. I've had the
> same mess some month before, and I had to reinstall everything again ...
> But maybe there's an easier way to kill the pseudo-active server ?!
> Any clues ?

Cheers,
 Stephen.
---

Department of Computer Science, Edinburgh University, Scotland.

To Rafal and others:

I wasn't clear enough in my original posting.  I was setting the DISPLAY
variable correctly (i.e. setenv DISPLAY `hostname`:9.0 - However, it seems
that there is yet another idiosyncracy about the HP's in that you must set
another environmental variable to force the X connection through the term
connection - setenv XFORCE_INTERNET

Thanks for all the input, and a special thanks to Herb Miller with the
correct solution above!

Joe Faurote

*************************************************************************
* BNR, the company that I work for, does not support my idle ramblings. *
* The opposite, it goes without saying, is true as well.                *
*************************************************************************