Error message
Error reporting reason
The reason is that it is not allowed to add comments after the same valid code line in some configuration files (such as. Conf files, which are widely seen here), which will compile and execute the following comments as the parameters passed in from the current command line; If there are no parameters in the command configuration or the format of the parameters is wrong, an error will be reported naturally
for example:
Solution
Divide the original configuration into two lines of commands and comments
Read More:
- Linux system service command error: Failed to allocate directory watch: Too many open files
- Linux: How to Solve sudo operate Error
- [Solved] Fluent error: invalid command [initialize-flow
- Shell: How to Get System Current Tme and Format it
- [Solved] Raspberry Pi Error: VNC error “No configured security type is supported by 3.3 VNC Viewer“
- Mac opens Terminal and reports an error -bash:: command not found
- How to Use Annotations in Flutter & Dart
- Grep: How to Find All the Files Containing a String in Linux
- Solve the error report of the find command: paths must precede expression
- [Solved] Linux Error: tar: Error Is Not Recoverable: Exiting Now
- [Solved] Shell error: syntax error: unexpected end of file
- Termux setting path environment variable
- Es Container Error: too many open files [How to Solve]
- Ubuntu18.04 Install ROS Error: rosdep update [How to Solve]
- Errors encountered when configuring static ip on Ubuntu 18.04
- Clean_pvnet Error: task must be specified [How to Solve]
- AFTER THE GIT SOURCE CODE IS INSTALLED, AN ERROR IS REPORTED /USR/BIN/GIT: NO SUCH FILE OR DIRECTORY
- [How to Solve] ffprobe ‘***: No such file or directory‘
- [Solved] Error in invoking target ‘agent nmhs‘ of makefile