No, scripts are slower than compiled program, and shell scripts are especially slow, for they keep running external commands.
Shell scripts are not compiled; they are interpreted (and therefore do not need to be compiled). Just type in the name of the shell script and any parameters it needs to execute.
Shell scripts are plain text files; they do not need to be compiled. To make these scripts executable, you need to add an executable flag using chmod. Consider the following example: $ chmod +x myscript
Shell scripts are interpreted files that contain commands and logic sequences to do things. They are similar to programs in that they contain logic and sequencing, and call other programs to accomplish tasks. You use shell scripts to automate tasks in Unix, run tasks periodically, create repeatable tasks, etc.
You don't Shell files/programs are not compiled. If you want to run a process through 'vi' then use the ':!' 'ex' command to shell out and execute it.
Shell scripts are used for repeatable processes, unattended operation, anything of a repetitive nature, etc. In short, they can be very valuable for just about anything.
See related link.
I presume you mean writing shell scripts that operate under the super user account - scripts are written for any reason to help automate tasks and make them much less error prone than issuing commands as a user. Running as the superuser merely means that the commands in the shell script require superuser priviledge to execute.
A shell function will do nothing unless it is explicitly called by other code, typically in a shell script. A shell script is a runnable, executable process, which can call other shell scripts and/or functions. The question might be worded backwards - it is necessary to write shell functions for shell scripts when certain logical functionality is required to be performed multiple times. Consider a shell function equivalent to a program subroutine - they operate the same way.
Shell Programs
PATH is a system variable used by the "shell" to determine where to find programs that are executable. This variable exists in similar forms on both Windows and Linux operating systems (and other related or similarly-designed systems). Removing this variable will not specifically stop the graphical user interface for the system from working correctly, but it will interfere with the execution of "shell scripts", users that attempt to use the command line interface (terminal) and programs that depend on the shell to execute child processes.
There are following shell scripts available at the below mentioned url -1. Shell Script for Log4j Log Analysis and exception reporting2. Log Monitoring Shell Script - email upon errorsHope that's what you are looking for.
The echo command echoes out any of the command line arguments given to it. It is commonly used in shell scripts to echo what portions of the shell script are doing.