Re: X reinit code trapped

[James v. Z. <ja...@dv...>]

So for those who's multi-X proves unstable after multiple login-logout,
this should stabilise X?

But the Ctrl-Alt-backspace test is still likely to fail if the
restarting X server fails to remove and reinit the device instance?

The paranoid sysops comment is due to the (small) potential for the X
server to be compromised and the compromise carried over between login
sessions?

Is there anything that can be done to reduce the likelyhood of an X
server failing to reinit after killed by ctrl-alt-backspace?

I don't seem to need this - my nV only configs seem to be stable, but I
suspect that odd combinations of drivers, such as an (nV binary + nV
opensource + matrox + s3) config might benefit a great deal?

J


On Thu, 2005-12-22 at 17:24, Aivils Stoss wrote:
> Hi, All!
> 
> 	All nvidia cards sometimes cannot be initialzed
> if multiple servers runs simultaneous. I create patch,
> which disable SIGHUP disaster. Of course this patch is
> not very _unix_ compatible. By defautl X server on
> SIGHUP must do all duties, be we don't like some duties.
> 	After patch applying X on SIGHUP clean up client connections.
> only. X authentification reset himself, because reread
> actual user authentification file on each client connection.
> Now X leave alone videocard on user logoff.
> Paranoidal sysops must not use this patch.
> 
> Patch attached
> 
> Aivils