linux remote access tools

By OK -

1. Remmina

If you have been using the GNOME desktopenvironment, chances are you are already familiar with Remmina because it comes pre-installed on many Linux distros. Remmina is a GTK+ 3 application which consists of a main program and a bunch of plugins (RDP, VNC, NX, XDMCP, SSH, Telepathy). To connect to a remote computer you can either enter its address directly or choose it from the list of connection profiles.
linux-remote-desktop-apps-01-remmina

2. Vinagre

If you are not happy with Remmina, there is also Vinagre, another remote desktop client integrated into the GNOME environment. One of its advantages is that with it you can have multiple connections open simultaneously. Also, you can browse the network for VNC servers – just don’t abuse this privilege. Vinagre doesn’t support as many protocols as Remmina, but it supports the main ones, e.g. VNC, SSH, and RDP.
linux-remote-desktop-apps-02-vino

3. krdc

KDE fans can use any of the other remotedesktop clients, but if you prefer an app that is native to KDE, krdc is your option. krdc is a small and simple app. It might lack some advanced features, but if speed and simplicity are more important, krdc is a great choice. With it you can connect to a remote computer via RDP or VNC/RFB protocols.
linux-remote-desktop-apps-03-krdc

4. TigerVNC

TigerVNC is a more universal app because it isn’t tied to Linux only. In addition to the many Linux distributions (Fedora, OpenSUSE, FreeBSD, Arch Linux, Red Hat Enterprise Linux and SUSE Linux Enterprise) it comes with, there are also versions for 64-bit and 32-bit Windows and a universal binary for Intel-based Macs. One of the best things about TigerVNC is that it is under active development and new versions with updates, fixes, and new features are regularly released.

Comments

Post a Comment

Popular posts from this blog

HAproxy logging

By OK -
ubuntu@ubuntu:/etc/haproxy$ cat /etc/rsyslog.d/haproxy.conf # Create an additional socket in haproxy's chroot in order to allow logging via # /dev/log to chroot'ed HAProxy processes $ModLoad imudp $UDPServerRun 514 local0.* -/var/log/haproxy-0.log local1.* -/var/log/haproxy-1.log ### keep logs in localhost ## $AddUnixListenSocket /var/lib/haproxy/dev/log ------------------- ubuntu@ubuntu:/etc/haproxy$ cat /etc/haproxy/haproxy.cfg global chroot /var/lib/haproxy user haproxy group haproxy log 127.0.0.1   local0         log 127.0.0.1   local1 notice daemon frontend www     bind 192.168.40.128:8282    # haproxy public IP     default_backend as-backend    # backend used backend as-backend    balance leastconn    mode http  server as1 192.168.40.128:8082 check    # application srv 1 defaults log ...
Read more

teamcity Automatic Agent Start under Linux

By OK -
Automatic Agent Start under Linux To run agent automatically on the machine boot under Linux, configure daemon process with the  agent.sh start  command to start it and  agent.sh stop  command to stop it. Refer to an example procedure below: 1. Navigate to the services start/stop services scripts directory: cd /etc/init.d/ 2. Open the build agent service script: sudo vim buildAgent 3. Paste the following into the file : #!/bin/sh ### BEGIN INIT INFO # Provides: TeamCity Build Agent # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start build agent daemon at boot time # Description: Enable service provided by daemon. ### END INIT INFO #Provide the correct user name: USER="agentuser" case "$1" in start) su - $USER -c "cd BuildAgent/bin ; ./agent.sh start" ;; stop) su - $USER -c "cd BuildAgent/bin ; ./agent....
Read more

NFS mount add in fstab _netdev instead of default | firewall-cmd --list-all

By OK -
Redhat recommends us to add  _netdev  option for NFS file system in /etc/fstab. So that they can be mounted after starting the networking service. Alternative ways to refer to partitions: Label : LABEL=label Network ID Samba : //server/share NFS : server:/share SSHFS : sshfs#user@server:/share Device : /dev/sdxy (not recommended) Example #1 //192.168.1.134/share_name /mnt/share_name cifs username=server_user,password=server_password,_netdev 0 0 ^ Path to your share ^ Mountpoint ^ Username ^ Password ^ See note A Note A: The  _netdev  options makes sure the mount is only attempted AFTER a network connection has been established. Example #2 10.10.10.1:/vol1/fs1 /data nfs defaults,_netdev 0 0 ============================ [root@localhost ~]# firewall-cmd --list-all public   target: default   icmp-block-inversion: no   interfaces:   sources:   services: dhcpv6-client high-availabi...
Read more