in reply to Re^3: Best/Fast/Simple way to add a GUI to a batch process
in thread Best/Fast/Simple way to add a GUI to a batch process

Hi, thanks for that info/correction. I'm not sure if I believe it though. The last time I tried it, the server needed an X server in order to do X forwarding. Can any more knowledgable monk clarify whether a server needs X running in order to forward X thru ssh? Seaching the docs on Google dosn't reveal that detail. From what I can gather, you need to have the xauth program running on the server, but if that requires a full X install, I'm not sure. Server GUI

Update: After some thought, it dawned on me that you probably need the X server installed on the server, but not neccessarily running. Why? Because when you try to execute the remote X program, it must find the various X libraries it needs, otherwise it will complain and fail. Your remote client can't provide the needed libraries, they must be on the server. So it seems RonW you are right, the X server does not need to be running, but the libraries must be installed. So .... X installed, but not neccessarily running, would be required.


I'm not really a human, but I play one on earth. ..... an animated JAPH
  • Comment on Re^4: Best/Fast/Simple way to add a GUI to a batch process

Replies are listed 'Best First'.
Re^5: Best/Fast/Simple way to add a GUI to a batch process
by RonW (Parson) on Aug 30, 2018 at 22:08 UTC

    There are (were?) X client libraries. Last time I set up a "headless" server, I only installed the client libraries. I also configured SSH for X forwarding. I did notice that the option for installing the X server was enabled by default. I disabled that with no problems.