Find the answer to your Linux question:
Results 1 to 3 of 3
Hello! I usually start few Wine games, which have problems with fullscreen and minimizing on a separate X server. This also allows me to run Compiz on the main X, ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jun 2010
    Posts
    7

    Killing Another X Server


    Hello!
    I usually start few Wine games, which have problems with fullscreen and minimizing on a separate X server. This also allows me to run Compiz on the main X, without affecting the performance of the game.

    However, when closing the game on the X server, I'm left with the X cursor on a black screen and this X seems to continue to run. How could I terminate it? I'm using
    Code:
    kill procid
    of the X :n, but is there any more "humane" way to do that?

    Thanks in advance.

  2. #2
    Linux Engineer GNU-Fan's Avatar
    Join Date
    Mar 2008
    Posts
    935
    Hi,

    I'm doing likewise whenever I start additional X servers. It's not that inhumane to do this, as the signal you send is "TERM", not "SIGKILL". This is basically a request to the program to finish please. It is not forced.

    Therefore you don't have to feel bad about it
    Debian GNU/Linux -- You know you want it.

  3. #3
    Just Joined!
    Join Date
    Jun 2010
    Posts
    7
    Thanks!
    Actually it seems that startx does kill the server after the last running application is closed, compared to
    Code:
     X :n
    .

  4. $spacer_open
    $spacer_close

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •