Restarting Xserver from cli

[David Curtis]

On Wed, 18 Mar 2009 08:18:05 -0400
Bart Silverstrim <bsilver at chrononomicon.com> wrote:

> David Curtis wrote:
> 
> > To me, removing C-A-B to limit this issue, is a sound decision.  
> 
> Not for people like me who have used Linux for many moons now, and when 
> X locks up that is one of the first methods to regain some form of 
> control...what's the alternative if you don't have another system to try 
> SSH'ing into it and checking processes? I'm not trying to argue that 
> things stay the way they are because of mere tradition, but only that it 
> was a way to recover from an error, and the odds of "accidentally" 
> hitting it are slim. In theory someone only needs to be bitten once by 
> some ass on an IRC channel to know not to do that again (and get a 
> lesson on trusting strange people on faceless networks, probably).

Sure, I agree. So now the 'slim chance' is protected against, and you and other knowledgeable people upon upgrade or install of Jaunty will: 'sudo apt-get install dontzap' 'dontzap --disable' and all will be well and good in the world again.
 
> 
> There comes a point where people need to stop protecting everything with 
> bubble wrap and let mistakes happen; it's how people learn. As long as 
> the problem isn't something "unreasonable" (accidentally hitting C-A-B? 
> What are the odds?)...and who would be experimenting on their computer 
> while working on their grand master thesis due the next day without a 
> backup? Someone who deserves a reboot (or restart of X)?
> 
> Just my opinion which of course is as valuable as the electrons burned 
> reading this...
 
  Energy can be neither created nor destroyed...

I guarantee come May we will be giving this advice out (dontzap) over and over and over.
-- 
David Curtis <dcurtis at uniserve.com>