Keywords: Terminal Script Execution | Permission Management | Cross-Platform Development
Abstract: This article provides a comprehensive analysis of the principles and methods for executing .sh and .bat files from the terminal. Using the Tomcat startup script as a case study, it explains why directly entering filenames results in 'command not found' errors. The content delves into core concepts such as script file permissions, path specification methods, and differences between operating systems, offering complete solutions and best practices. It also incorporates real-world development scenarios from reference materials to demonstrate the practical value of script files in projects.
Fundamental Concepts and Classification of Script Files
In software development and system administration, script files play a critical role. .sh files are primarily for Unix/Linux systems, written in Bash or other shell languages, while .bat files are Windows batch files using Windows command prompt syntax. Essentially, both are text files containing sequences of commands executed line by line through interpreters.
Deep Analysis of Terminal Execution Failures
The "-bash: startup: command not found" error encountered by users stems from the terminal's command search mechanism. When a command is entered, the system searches for executable files in directories specified by the predefined PATH environment variable. Directly typing "startup" does not trigger a search in the current directory, hence the system cannot locate the startup.sh file.
The correct execution method requires path specification. In Unix/Linux systems, "./" denotes the current directory, so executing "./startup.sh" explicitly instructs the system to find and run the script in the current directory. This mechanism ensures security (preventing accidental execution of malicious scripts) and provides clear execution paths.
Permission Management and Execution Control
Even with the correct path specified, script execution may fail due to permission issues. In Unix/Linux systems, files must have execute permissions to run as programs. Use "ls -l startup.sh" to check file permissions; if the execute permission (x) is missing, add it via "chmod +x startup.sh".
# Check file permissions
ls -l startup.sh
# If 'x' is missing in output, add execute permission
chmod +x startup.sh
# Then execute the script
./startup.shExtended Practical Application Scenarios
The local development scenario mentioned in the reference article further emphasizes the importance of script files. In collaborative development projects, scripts like "all_parse.sh" and "serve.command" automate compilation, testing, and service startup processes. This automation not only enhances development efficiency but also ensures environmental consistency.
In macOS systems, although Unix-based, some scripts may require specific handling. The user's confusion in the reference article about running "./all_parse.sh" validates the universality of path specification and permission checks. The correct approach is to navigate to the directory containing the script and execute "./all_parse.sh".
Cross-Platform Compatibility Considerations
For projects requiring cross-platform deployment, providing both .sh and .bat files is a common practice. Developers on different operating systems can use the corresponding script files to ensure environmental adaptation. Tomcat's startup scripts are a classic example, using startup.sh on Linux/macOS and startup.bat on Windows.
Best Practices and Troubleshooting
Beyond basic execution methods, adhere to these best practices: always inspect script contents for security; standardize script execution methods in team projects; manage script changes using version control systems. When encountering execution issues, troubleshoot step by step: confirm file existence, check permission settings, verify script syntax, and review system logs.
By deeply understanding script execution mechanisms and system environment configurations, developers can effectively avoid common issues like "command not found," thereby improving development efficiency and system reliability.