Most of the Linux commands given in this wiki space assume basic familiarity with Linux and Bash (Bourne Again SHell). Bash is is typically the default shell on most distros. For ITC personnel who have less experience with Linux, you may trip over some "simple" things. This page contains a number of tips which may help get your head and fingers used to bash.
For OpenVMS Admins
If you're experienced with OpenVMS, you will hate bash (for a while, or for a long time). You'll miss things like /LOG and /CONFIRM doing the same thing on every command. You'll be annoyed that everything is case-sensitive. You'll wonder why your typing 'cat' (or maybe 'dog') to TYPE a file and 'less' to page through a file. For while, you may try to customize your
~/.bashrc file to have aliases that make it seem like DCL (I know, I tried).
My best advice, learned the hard way, is just let it go. The world didn't learn the lessons that DCL could have taught it. However, what bash and the GNU utilities lack in expressiveness and consistency, it more than makes up for in raw power and flexibility. It may take years, but you'll eventually learn to appreciate the bash/GNU combo and get proficient at it. Fortunately, Google knows the answer to every bash question you're ever going to have. Use it.
Here are a few links with a mapping from between VMS and Linux:
Part of the reason that I created the
ssdt-utils image is so that we could distribute utilities to you that would ease your way into linux (and so I didn't have to document so many arcane commands). See Install and Update SSDT Utils package.
The ssdt-utils container, among other things, creates a
utils alias in your process which allow you to executed bunded commands. When you execute a utils command, a temporary container is created which maps your current working directory to
/tmp in the container. You can then use utilities to operate on your current directory. For example, to edit a file in your current directory with
~/.bashrc file is like the LOGIN.COM on VMS. You should already have one. But it's a "hidden" file (because it starts with a dot). You can edit the file with
The free command displays information about both the physical and swap memory; free also includes buffer information. This can give a quick view of memory usage on the system. There are a few options used for the display of memory. For example, -m displays the memory in megabytes. The -h option will display it in more "human readable" format. To show a total line, use the -t option. To display a specific number of times, use the -c option (this requires the -s option). The -s seconds option will continuously display the result seconds apart (this one requires a specific seconds parameter). Note that the -s option does not appear to work in Ubuntu 16.04 (there is a workaround using -c), but does work in earlier versions. This is a reported bug.
Options can be used together. Examples:
The top command in Ubuntu is used to monitor processes. See this link for more information on the top command.
key equivalent-key-combinations Up alt + \ or alt + k Down alt + / or alt + j Left alt + < or alt + h Right alt + > or alt + l (lower case L) PgUp alt + Up or alt + ctrl + k PgDn alt + Down or alt + ctrl + j Home alt + Left or alt + ctrl + h End alt + Right or alt + ctrl + l
How to add another column to the top command results
In this example, we add Swap to the list. Original top command
Press "f" to go into Field Management mode
Use alt + j (or down key) to get to SWAP
Select it with d (note you can also deselect using d)
To select it for moving, use alt + l (or right)
Use alt + k to move it up (or the up key)
To commit, press enter (or alt + h or the left key)
Press q to quit the format mode. Top now looks like this:
If you want top to use this configuration the next time it is used, press W to write (uppercase W).
Apply a filter to top
To apply a filter, enter a lower case letter o to bring up the filter dialog. then filter on COMMAND=java for example. Note the filter is just for the current session; it does not "stick" for the next time.
If you have filters already applied and would like to clear the current filters you can simply press the '=' (equals) key from the main screen.
Finding a specific Docker container PID
The top command lists statistics and other per PIDs. When trying to monitor system issues, it can be beneficial to know specific processes associated with docker containers. Use this command:
Major/Minor Page Faults - Monitoring
Without going into a lot of detail it is sufficient to say that major/minor page faults can be a good indicator of how the system is performing and, more specifically, where the system is retrieving data from that are required for processes. Major page faults occur when a process makes a request to the system for a resource that is not available in shared memory. Therefore, the disk must be read and the information loaded from storage. In contrast, the minor page fault is when a process makes a request to the system for a resource that it doesn't yet have a reference to but is already available in shared memory. Access to this data is much faster because the information is already loaded into memory and simply needs to be made available to the process. More information on this can be found at the following link:
One useful command to examine major/minor page faults on a Linux system using the ps command is the following:
This command leverages the ps command's support for field selection to display major/minor fault counts for a specific command/process.
Swappiness is how often the swap file is used. If it is set to zero, there will be no swapping unless the system runs out of memory. If it's set at 100, programs will be swapped to disk almost immediately. Swappiess is expressed as a percent of the memory. When using higher memory systems, it is generally a good idea (depending on the types of programs/processes running on the server) to reduce swappiness and thus reduce swapping to the disk. The default setting for swappiness on Ubuntu is 60. With a high memory system, you may want to adjust this as low as 10. For more details on swappiness, see here. Due to the high memory availability, we changed the swappiness to 10.
Generally, change the setting live, and once that appears to be working as expected, make the permanent change.
To change the swappiness on the system and have it take effect immediately
Permanent - keeps it on reboot
To ensure the swappiness does not revert to the default value on reboot, edit the /etc/sysctl.conf file and add this line:
vm.swappiness = 10
Linux is case sensitive, including commands and filename. Also, most linux terminals use auto complete. This can be quite a time savings when you don't remember the exact name of the file.