remote consoles in Linux/Solaris

By OK -

  • Remote logins are also known as "shell access"
-------------

Advanced Lights Out Management (ALOM)

ALOM is the new standard System Controller (SC) for remote out-of-band management for all current and future VSP servers. 
ALOM functions allow for monitoring, logging, alerting and for basic control of the system. ALOM is particularly useful for remotely managing a server in a typical "lights out" environment. 
To gain access to the server's console, enter the command 'console' or if there is already an active ALOM/RSC console session, enter the command 'console -f'. On ALOM systems, to return to the ALOM card, enter key sequence “#.” and then type 'logout'. On RSC systems, to return to the RSC car, enter key sequence “~.” and then type 'logout'.
-----------------------
Sun ILOM Remote Console is a Java application that allows you to remotely redirect and control the following devices on the host server:
  • Keyboard
  • Video console display
  • Mouse devices
  • Storage devices or images (CD/DVD)
------------------------
Perle IOLAN Terminal Servers and Console Servers are ideal for managing remote Solaris consoles having the following features;
-------------------------
The RHEL 6 remote desktop functionality is based on technology called Virtual Network Computing (VNC) a
Another useful way to check whether this package is installed is to run the following command from a terminal window (Applications -> System Tools -> Terminal):
rpm -q vino
If the rpm command reports package vino is not installed then the next step is to perform the installation. This can be performed either using the Add/Remove Software tool, launched by selecting Applications -> Add/Remove Software. Within the Add/Remove Software tool, search for vino, select the checkbox next to the item in the results list and click on Apply to install the package. Alternatively, to install from a terminal window, enter the following:
su -
yum install vino

To access a remote desktop using vncviewer, execute the following command in a terminal window:
vncviewer hostname:0



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