mifag

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • mifag
    Participant

    Glad to hear you’ll be working on it. Please give update on the issue in this thread; I’ll keep a check on regularly.

    For the command, do you mean I should type it in to terminal inside nx/xfce session or in a separate ssh session? If you meant inside nx/xfce session, should I do it like after closing all my other work, then substituting logout with nxserver -restart command?

     

    mifag
    Participant

    Oh, my bad then. I wrote something last week because I had trouble closing/relaunching the session but apparently I must have exited the browser without ever actually submitting it. Let me write it up again.

    Thank you @troy I now reconfigured my vps using centos 7 using same procedure (I was ready to go back to version 6 if 7 gave me errors). Apparently installing nx and editing DefaultDesktopCommand in /usr/NX/etc/node.cfg were the only two things I needed to do for nx configuration. Very simple!

    Now that I can connect to xfce session by creating window, however, I noticed unexpected behavior when exiting the session. So for example let’s first say I opened a new nx connection via new display option and do my work. I finish my work and then I want to close the GUI session by logout. It executes logout, but then I’m presented with black, blank screen instead of gracious exit of NX session. If I exit anyway and reconnect later, I’m faced with same black blank screen with top left corner briefly notifying my nx logon. I’m not asked to create new display, too. To fix this I had to kill some processes on ssh terminal. Note that I can disconnect while my xfce session is on and reconnect to see same session without a problem. The problem is when I wanted to close the xfce session(and thereby x windows processes altogether) by logout.

    Am I not supposed to log out GUI session when using NX? I just wanted to unload GUI processes from memory when I’m finished using xfce session via NX.

    If you have any suggestions for tweaking more config parameters or for the way I tried logout to fix this behavior, I’ll be happy to learn.

     

    Thanks.

    mifag
    Participant

    hmm? I don’t know why but the reply I made last Thursday or so seem vanished? I think I saw the post was waiting moderation though. I guess I’ll just have to write up another if it can’t be recovered.

    mifag
    Participant

    @kroy

    You are amazing!!

    I can now actually see desktop environment. As I was posting, I was worried that NoMachine may just not support non-major package like xfce and the problem may be impossible to solve. My VPS was such low-end(<1gb ram, <20gb ssd) that the choice was either xfce or lxde, and the latter is unsupported for centos. Yet thanks to you I don’t have to abandon my current setup.

    Just one more thing; do you know how to automate this initial setup for each reboot?

    After reboot, I currently have to

    1) ssh log on to remote server

    2) AUTHFILE=$HOME/Xvfb-0.auth

    3) Xvfb :0 -auth $AUTHFILE -screen 0 1024x768x24 &

     

    4) DISPLAY=:0 nohup /usr/bin/startxfce4 &

    5) sudo /usr/NX/bin/nxserver –restart

    before I can use NoMachine from local workstation to see the gui environment. Failure to do so will only give me “Cannot find the default environment…” message window with the previously mentioned background.

    What’s bugging me is 1) and 5) part…my putting these lines under .bashrc will still force me to log on ssh each time and especially enter password for 5) sudo part.

    How would you automate this so that occasional/accidental reboot will not require reconfiguration?

    Thanks.

Viewing 4 posts - 1 through 4 (of 4 total)