If you do much work on remote servers and have ever lost your connection at an inconvenient moment, using screen can help avoid losing work. Screen is, according to the man page, “a full-screen window manager that multiplexes a physical terminal between several processes (typically interactive shells)”. Window manager may be a bit misleading, as it's not a window manager in the GUI sense, but rather it manages a number of full-screen console/shell sessions within a single console/shell.
Screen is simple to use; after you connect to the remote server, type:
$ screen -D -RR
This creates a new screen session if there isn't one or attaches to a previously created one if one exists. Now if your connection drops, you simply reconnect and enter the above command to reconnect and return to the exact point you were at when your connection was lost.
Screen has many keyboard commands for starting and controlling additional sessions; see the man page for more info.
Screen also is useful when you want to execute a long-running process and don't want to stay connected while it runs. Simply start the command, and then switch to a different session and type ~. to disconnect your SSH connection. When you return later, you can reconnect to the screen session and see the output.
You even may want to put the screen command in your .profile file so that it is started automatically when you log in. I like to have the option of not starting screen, so I have my .profile ask whether I want to start it:
read -p "Start screen? " ans ans=$(echo $ans | tr A-Z a-z) if [[ "$ans" = y || "$ans" = yes ]]; then screen -D -RR fi
The shell has a maximum length for command-line arguments. If you try to pass more than the maximum, you will receive an error:
Argument list too long
For example, to find which files contain a particular string, you normally would do the following:
grep -l STRING
But, if there are too many files, you may get the “Argument list too long” error. In that case, you could do:
ls | xargs grep -l STRING
You may have wondered how to determine certain X attributes using simple shell commands, such as the refresh rate and display resolution. You can use xrandr for that purpose:
$ xrandr --verbose SZ: Pixels Physical Refresh *0 1024 x 768 ( 333mm x 241mm ) *85 1 800 x 600 ( 333mm x 241mm ) 85 2 640 x 480 ( 333mm x 241mm ) 85 Current rotation - normal Current reflection - none Rotations possible - normal Reflections possible - none
You also can get a great deal of information with the xdpyinfo command, such as finding out what extensions are supported by the X server:
$ xdpyinfo | less
One very useful extension for video is the Xvideo extension, known as xv. The xvinfo command can give you information on this extension:
For 3-D, use the glxinfo command:
For more information about these commands see the respective man pages.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- August 2015 Issue of Linux Journal: Programming
- Django Models and Migrations
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- The Controversy Behind Canonical's Intellectual Property Policy
- Huge Package Overhaul for Debian and Ubuntu
- Shashlik - a Tasty New Android Simulator
- Embed Linux in Monitoring and Control Systems
- KDE Reveals Plasma Mobile
- diff -u: What's New in Kernel Development