top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

remote desktop session - CentOS

+1 vote
405 views

I have a server that I want to setup confluence on. The server is accessed via ssh with keys. I was wondering if I need to install Xorg and a windows manager in order to access it remotely (I'm just starting into the confluence documentation now). It seems as though I would, but I'd like to avoid having the graphical desktop on this server if possible.

posted Sep 17, 2013 by Deepankar Dubey

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

I'm not familiar with Confluence but its highly doubtful that you would need any X server on your server, assuming you're going to access any X based applications running on that server remotely. Remember, the X server manages the *local hardware* (the computer you are sitting in front of) while an X client can be anywhere.
I don't know what X clients you plan to run (Confluence appears to be a web application), but if its for some sort of X based administration utility, then no. You'd run that utility on the sever and export its display back to your workstation.

answer Sep 17, 2013 by anonymous
Similar Questions
0 votes

I was wondering if their is a way to have multiple desktop environment on a fedora system without one messing with other. Anytime you have multiple desktop environment on a system they will start writing each others configuration files messing up with themes. Not to mention populated application menus.

Would it be possible to create different users for different desktop environment? Or something like that.

+1 vote

I have running centos 6 server in my head quarters and branch offices. I need to access file server files in both location using VPN. How to setup vpn server in both location and how to access it.

Could any one help me.

0 votes

The system log (/var/log/messages) of a CentOS 7.2 system has frequently-repeated message line pairs like:

Jul 18 14:00:01 localhost systemd: Started Session 307 of user root.
Jul 18 14:00:01 localhost systemd: Starting Session 307 of user root.

where the session number increases each time.

Looking around on this, e.g. Red Hat Bugzilla bug 727315, it looks like it's when crond starts a task; it looks like it might be fixed - I would think that would be in CentOS but don't know how to find/compare the Fedora and CentOS systemd versions to know for sure.

I found a post on a workaround - in /etc/systemd/system.conf to change the line:

#LogLevel=info

to:

LogLevel=notice

I did that and rebooted, and it has stopped the messages.

I'm worried though that this may have knocked out something of actual interest from the syslog.

So my question is, is there a better way? A way that info messages could go to some other log, or better yet, a way that those particular "session" messages, and only those, could go to some other log or be filtered out?

...