写了一个简单易用的 shell 框架（下篇）

最新推荐文章于 2025-05-12 21:13:33 发布
最新推荐文章于 2025-05-12 21:13:33 发布
阅读量409 收藏 2
点赞数
CC 4.0 BY-SA版权
分类专栏： Linux Shell Bash 文章标签： linux bash
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/DBADaily/article/details/124601034
Easy Bash是一个简单的Bash库，旨在使脚本编写更轻松。它提供了变量管理、颜色输出、日志记录、选项解析等功能。通过内置选项和自动帮助消息生成，可以轻松实现详细和检查模式运行，以及自动生成配置文件。此外，还提供了日期操作和通知功能。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

Easy Bash

Easy Bash - a simple bash library to make scripting easier.
在这里插入图片描述

Easy Bash libraries

Vars

Global variables useful or used by libraries are stored here.

Below shows some examples.

Date and time vars

MONTH_STR: 202205
DATE_STR: 20220501
TIME_STR: 20220501_3_132939

Script vars

SCRIPT_DIR: /data/scripts/easybash/test
SCRIPT_FULL_NAME: test_vars.sh

logging vars

LOG_LEVEL: INFO
LOG_DIR: /data/scripts/easybash/test/logs/202205/20220501
LOG_FILE: /data/scripts/easybash/test/logs/202205/20220501/test_vars_20220501_3_132939.log

And logging color vars

export COLOR_TRACE="green"
export COLOR_DEBUG="cyan"
export COLOR_INFO="white"
export COLOR_WARN="yellow"
export COLOR_ERROR="red"
export COLOR_FATAL="red"

For more global variables, refer to lib/lib_vars.sh.

Color

Test color example script.

bash examples/test_color.sh

Colors and corresponding numbers:

(["black"]="0" ["red"]="1" ["green"]="2" ["yellow"]="3" ["blue"]="4" ["magenta"]="5" ["cyan"]="6" ["white"]="7")

echo with colors

在这里插入图片描述

echo colors functions
echo_red "echo_red"
echo_red_bold "echo_red_bold"
echo_green "echo_green"
echo_green_bold "echo_green_bold"
echo_yellow "echo_yellow"
echo_yellow_bold "echo_yellow_bold"
echo_blue "echo_blue"
echo_blue_bold "echo_blue_bold"
echo_magenta "echo_magenta"
echo_magenta_bold "echo_magenta_bold"
echo_cyan "echo_cyan"
echo_cyan_bold "echo_cyan_bold"
echo_white "echo_white"
echo_white_bold "echo_white_bold"

在这里插入图片描述

Echo colors with background.

echo_blue "echo_blue: foreground - blue, no background." "" "bold"
echo_blue "echo_blue: foreground - blue, background: yellow." "yellow" "bold"

在这里插入图片描述

echo_color

echo_color is called by echo_blue etc…

echo_color "echo_color: foreground - green, no background." "green" "" "bold"
echo_color "echo_color: foreground - green, background - red." "green" "red" "bold"

在这里插入图片描述

echo_color_by_num

echo_color_by_num is called by echo_color .

echo_color_by_num "echo_color_by_num: foreground - red, no background." "1" "" "bold"
echo_color_by_num "echo_color_by_num: foreground - red, background - blue." "1" "4" "bold"

在这里插入图片描述

Set colors

Set color for existing echos
set_color "green"
echo "set_color: foreground - green, no background."
echo "You can echo lines as usual."
echo "So that you can easilly set color for existing echos."
echo "Or set the same color for mulitple lines."
echo "reset_color"
reset_color

在这里插入图片描述

set_color "green" "" "bold"
echo "set_color foreground - green bold, no background."
echo "You can echo lines as usual."
echo "So that you can easilly set color for existing echos."
echo "Or set the same color for mulitple lines."
echo "reset_color"
reset_color

在这里插入图片描述

Set color with background in loop
declare -a la_str
la_str+=("set_color foreground - green, background - red.")
la_str+=("You can echo lines as usual.")
la_str+=("So that you can easilly set color for existing echos.")
la_str+=("Or set the same color for mulitple lines.")
la_str+=("reset_color")
for str_value in "${la_str[@]}"; do
  set_color "green" "red"
  echo "${str_value}${COLOR_RESET}"
done

在这里插入图片描述

Logging

By default, the LOG_LEVEL is INFO which will not print trace or debug messages.

You can update lib/lib_vars.sh or add option -v to set LOG_LEVEL to TRACE to get more messsages.

Test logging example script.

bash examples/test_logging.sh -v

log_trace "This is a trace message."
log_debug "This is a debug message."
log_info "This is a info message."
log_warning "This is a warning message."
log_error "This is a warning message."
log_fatal "This is a fatal message."

在这里插入图片描述

Parse

Take following script for example.

cd easybash/echo_dates
cat echo_dates.sh

#!/usr/bin/env bash
################################################################################
#
# Author: Alvin
# License: MIT
# GitHub: https://github.com/dbadaily/easybash
#
# echo dates
################################################################################

VERSION_STR="1.0.0"

current_dir="$(dirname "$(readlink -f "${BASH_SOURCE[0]}")")"

lib_dir="$(dirname "${current_dir}")"

source "${lib_dir}/lib/easybash.sh"

add_main_options() {
  ## custom options
  # add your options here
  add_options "s:" "start-date:" "START_DATE" "Y" "start date"
  add_options "e:" "end-date:" "END_DATE" "Y" "end date"

  ## common options
  # 1. options like m: or emails: can be changed
  # 2. variable names like RECIPIENTS are NOT expected to be changed as they are used in libraries
  add_options "m:" "email:" "RECIPIENTS" "N" "emails(separated by space) to receive notifications"
  add_options "S" "success-notification" "SUCCESS_NOTIFICATION_IND" "N" "indication whether to send success notifications"
  add_options "C" "check" "CHECK_MODE" "N" "don't make any changes"
  add_options "G" "generate-config" "GEN_CONFIG" "N" "generate config file if not exists"
  add_options "w" "write-values" "WRITE_VALUES" "N" "used together with -G, write values provided by command options to config file"
  add_options "H" "help" "HELP" "N" "show this help"
  add_options "V" "version" "VERSION" "N" "output version information"
  add_options "v" "verbose" "VERBOSE" "N" "verbose mode"
}

# custom function
echo_dates() {
  local lv_start_date="$1"
  local lv_end_date="$2"
  local lv_msg="Work between ${lv_start_date} and ${lv_end_date} is done."
  while [[ "${lv_start_date}" -le "${lv_end_date}" ]]; do
    echo_blue_bold "Processing for date ${lv_start_date}"
    log_trace "Work for date ${lv_start_date} done."
    lv_start_date=$(date -d "${lv_start_date} + 1 days" +'%Y%m%d')
  done
  send_msg "${lv_msg}"
}

main() {
  add_main_options
  parse_args "$@"

  # add your logic here
  if [[ "$CHECK_MODE" != "Y" ]]; then
    echo_dates "${START_DATE}" "${END_DATE}"
  elif [[ "$CHECK_MODE" == "Y" ]]; then
    log_warning "CHECK MODE. Skip echoing dates."
  fi
}

main "$@"

Easy way to add options

Options can be added as below.

add_main_options() {
  ## custom options
  # add your options here
  add_options "s:" "start-date:" "START_DATE" "Y" "start date"
  ...
}

  1. The short option is s:

  2. The long option is start-date:

  3. It will create global variable START_DATE and assign command line option value to it

  4. "Y" indicates it is a required parameter

  5. "start date" is the option description

Automatic parsing and assignment

Parsing and variable assignment can be done easily using only one line code:

parse_args "$@"

All options will be automatically parsed by getopt.

# bash echo_dates.sh -s
getopt: option requires an argument -- 's'
# bash echo_dates.sh -f
getopt: invalid option -- 'f'

It will create global variables for every option.

And assignments are done automatically, so that you can reference them easily.

bash echo_dates.sh -s 20220101 -e 20220107 -v

[2022-05-01 08:30:01 TRACE] [parse_args] lv_valid_args: ' -s '20220101' -e '20220107' -v --'
[2022-05-01 08:30:01 DEBUG] [parse_args] START_DATE=20220101
[2022-05-01 08:30:01 DEBUG] [parse_args] END_DATE=20220107
[2022-05-01 08:30:01 DEBUG] [parse_args] VERBOSE=Y

Mixed short and long options

You can use mixed short and long options.

bash echo_dates.sh --start-date 20220101 -e 20220107 -v

Generate help message automatically

It will generate help message automatically based on the options and descriptions added.

bash echo_dates.sh -H

在这里插入图片描述

Built-in options

Common options are suggested to be added to utilize various functionalaties which will be introduced further more.

For the common options,

  1. You can change both short or long option names, e.g. m: or emails: can be changed
  2. All common variable names are used in easybash libraries and their names are NOT expected to be changed unless you update all referrenced variables accordingly.
add_main_options() {
  ## custom options
  # add your options here
  ...

  ## common options
  # 1. options like m: or emails: can be changed
  # 2. variable names like RECIPIENTS are NOT expected to be changed as they are used in libraries
  add_options "m:" "email:" "RECIPIENTS" "N" "emails(separated by space) to receive notifications"
  add_options "S" "success-notification" "SUCCESS_NOTIFICATION_IND" "N" "indication whether to send success notifications"
  add_options "C" "check" "CHECK_MODE" "N" "don't make any changes"
  add_options "G" "generate-config" "GEN_CONFIG" "N" "generate config file if not exists"
  add_options "w" "write-values" "WRITE_VALUES" "N" "used together with -G, write values provided by command options to config file"
  add_options "H" "help" "HELP" "N" "show this help"
  add_options "V" "version" "VERSION" "N" "output version information"
  add_options "v" "verbose" "VERBOSE" "N" "verbose mode"
}

Run in verbose mode

By default, the LOG_LEVEL is INFO.

You can always add option -v to reset LOG_LEVEL to TRACE to debug or get more detailed information.

bash echo_dates.sh -s 20220101 -e 20220107 -v

在这里插入图片描述

Run in check mode

-C is a super helpful option borrowed from ansible to indicate check mode or dry run mode.

You are encouraged to implement check logic in your codes and always run in check mode first so that you can double check to avoid unnecessary incidents.

if [[ "$CHECK_MODE" != "Y" ]]; then
  echo_dates "${START_DATE}" "${END_DATE}"
elif [[ "$CHECK_MODE" == "Y" ]]; then
  log_warning "CHECK MODE. Skip echoing dates."
fi

bash echo_dates.sh -s 20220101 -e 20220107 -v -C

在这里插入图片描述

Check required parameters

getopt doesn’t provide a way to check whether one option is required or not.

Yet it is helpful to check mandatory parameters first.

Parameter "Y" below indicates it is a required parameter.

add_options "s:" "start-date:" "START_DATE" "Y" "start date"

Better run in check mode so that it makes no changes.

Run without all required options, it will:

  1. give warning hints about all remaining required options
  2. give a fatal message
  3. exit after the fatal message
bash echo_dates.sh -v -C

在这里插入图片描述

Run with one parameter.

bash echo_dates.sh -s 20220101 -v -C

在这里插入图片描述

Generate config file

When there are too many parameters, it might be better to use a config file.

Write the config file yourself ?

Just use -G option to generate a config file for you based on the options specified.

By default, a config file named config.sh will be created in the same folder as the script.

And the config file will be sourced if it exists.

bash echo_dates.sh -s 20220101 -e 20220107 -v -G

在这里插入图片描述

Check the contents of the config file.

cat config.sh

# start date
START_DATE=""

# end date
END_DATE=""

...

During development, you might add more options.

It will save the old config file once you generate again.
在这里插入图片描述

Generate config file with values

Generating a config file with empty values is not enough, you need to set the values automatically.

Combine options -G and -w together, it will generate config file with parameters assigned.

bash echo_dates.sh -s 20220101 -e 20220107 -v -G -w

在这里插入图片描述

cat config.sh

# start date
START_DATE="20220101"

# end date
END_DATE="20220107"

...

After having generated config file with variables assigned, you can run the script without parameters.

bash echo_dates.sh -v

在这里插入图片描述

Overwrite config file variables

While all the variables are stored in a config file, you might need to update one or more variables in some scenarios.

You can also pass some parameters via options. Variables in config file will be overwritten by options.

bash echo_dates.sh -v -e 20220103

在这里插入图片描述

Notification

You can send messages using send_msg as below to send notification so that you are informed timely.

It would be very helpful if you need to keep an eye on the process of the script running.

Send only a message or subject of email:

send_msg "${lv_subject}"

Send a message and details:

send_msg "${lv_subject}" "${lv_body}"

Email can be specified by -m .

bash echo_dates.sh -s 20220101 -e 20220107 -m "alvin@dbadaily.com"

If RECIPIENTS is not provided via options nor config file, there will a warning message and no messages will be sent.

[2022-05-01 11:35:25 WARNING] RECIPIENTS is not set or empty. option -m RECIPIENTS or --email=RECIPIENTS might be set.

send_msg is prefered over send_email .

The former easily enables to turn to other efficient ways of notification, e.g. IM.

As you can see below, send_msg calls send_email which might be overwritten.

send_email() {
  ...
    echo "${lv_body}" | mail -s "${lv_subject}" "${lv_recipient}"
  ...
}

send_msg() {
  ...
    send_email "${RECIPIENTS}" "${lv_subject}" "${lv_body}"
  ...
}

Date

Date range is helpful in scenarios like:

  1. You need to delete data of some date range
  2. You need to dump or achive data of some date range

And there are several ways to specify data range.

  1. By start date and end date
  2. By month
  3. By start date and days

With set_dates_by_args, you can easily set START_DATE and END_DATE for all above three cases.

To get all the days between START_DATE and END_DATE , there are also three ways:

  1. get_dates by START_DATE and END_DATE
lv_dates="$(get_dates "${START_DATE}" "${END_DATE}")"
print_dates "${lv_dates}"
  1. get_dates_by_args which internally uses START_DATE and END_DATE
lv_dates="$(get_dates_by_args)"
print_dates "${lv_dates}"
  1. loop_dates by START_DATE and END_DATE
loop_dates "${START_DATE}" "${END_DATE}"

Test date example script codes:

cat examples/test_date.sh

main() {
  add_main_options
  parse_args "$@"

  local lv_dates=""
  set_dates_by_args

  log_trace "calling get_dates with parameters START_DATE and END_DATE"
  lv_dates="$(get_dates "${START_DATE}" "${END_DATE}")"
  print_dates "${lv_dates}"

  log_trace "calling get_dates_by_args without parameters"
  lv_dates="$(get_dates_by_args)"
  print_dates "${lv_dates}"

  log_trace "calling loop_dates with parameter START_DATE and END_DATE"
  loop_dates "${START_DATE}" "${END_DATE}"
}

Get dates by start date and end date

bash examples/test_date.sh -s 20220101 -e 20220103 -v

[2022-05-01 08:01:20 DEBUG] [parse_args] START_DATE=20220101
[2022-05-01 08:01:20 DEBUG] [parse_args] END_DATE=20220103
[2022-05-01 08:01:20 DEBUG] [parse_args] VERBOSE=Y
[2022-05-01 08:01:20 TRACE] calling get_dates with parameters START_DATE and END_DATE
[2022-05-01 08:01:20 INFO] lv_date=20220101
[2022-05-01 08:01:20 INFO] lv_date=20220102
[2022-05-01 08:01:20 INFO] lv_date=20220103
[2022-05-01 08:01:20 TRACE] calling get_dates_by_args without parameters
[2022-05-01 08:01:20 INFO] lv_date=20220101
[2022-05-01 08:01:20 INFO] lv_date=20220102
[2022-05-01 08:01:20 INFO] lv_date=20220103
[2022-05-01 08:01:20 TRACE] calling loop_dates with parameter START_DATE and END_DATE
[2022-05-01 08:01:20 INFO] lv_start_date=20220101
[2022-05-01 08:01:20 INFO] lv_start_date=20220102
[2022-05-01 08:01:20 INFO] lv_start_date=20220103

Get dates by month

bash examples/test_date.sh -M 202201 -v

Get dates by start date and days

bash examples/test_date.sh -s 20220101 -d 3 -v

Conclusion

easybash helps you write simple, efficient and colorful scripts easily.

You no longer need to do the following manually:

  1. parse all the arguments manually
  2. set variables manually
  3. write help message manually
  4. write config file manually
  5. check whether all required parameters are set manually
  6. write logs manually

And you are able to do the following easily:

  1. add options easily
  2. parse options easily
  3. do dry run test easily
  4. write colorful logs easily
  5. write and show different levels of logs easily
  6. send messages easily

原文链接：
https://blog.csdn.net/DBADaily/article/details/124601034
您浏览的网址与此链接不一致的话，则为未授权的转载，为了更好的阅读体验，建议阅读原文。

linux shell 脚本 入门到实战详解[⭐建议收藏！！⭐]
心有鸿鹄天地，不敢妄坠人间
09-28 32万+
文章目录shell 入门到实战详解[⭐建议收藏！！⭐]关于作者**作者介绍**一、shell 入门简介1.1 什么是shell1.2 shell 编程注意事项1.3 第一个shell 脚本 hello world二、shell 环境变量讲解2.1 shell 变量详解2.2 shell 系统变量 介绍2.3 shell 环境变量 介绍2.3.1 常见的系统环境变量2.4 shell 用户环境变量 介绍2.4.1 自定义shell环境变量2.4.2 echo 打印菜单栏2.4.3 shell 中彩色输出 h
Python Scrapy：使用Scrapy Shell进行调试
Python编程之道的博客
04-25 1070
在网页抓取的过程中，我们常常会遇到各种问题，如无法正确提取数据、请求失败等。Scrapy Shell作为Scrapy框架提供的一个交互式调试工具，能够帮助开发者在不运行整个爬虫项目的情况下，快速测试和验证网页数据的提取逻辑、请求的正确性等。本文的目的就是详细介绍如何使用Scrapy Shell进行调试，范围涵盖Scrapy Shell的基本概念、使用方法、实际应用以及相关资源推荐等方面。本文将按照以下结构展开：首先介绍Scrapy Shell的核心概念与联系，包括其工作原理和架构；
写了一个简单易用的 shell 框架（上篇）
DBADaily 的博客
05-06 381
Easy Bash - a simple bash library to make scripting easier
shell框架
aipoqiu2566的博客
03-13 305
#!/bin/bash#注释#注释#环境变量相关，如下PATH=/sbin:/bin:/usr/bin:/usr/sbin #引入库函数，如下，类似于c语言的#include "*.h" . /etc/init.d/functions #获取相关配置信息，不是必须的，如test -f /etc/sysconfig/network && . /etc/sysconfi...
什么是 Shell？sh、bash、zsh傻傻分不清楚！！！
最新发布
站在知识源头搞技术
05-12 2268
Shell 是用户与操作系统内核之间的交互界面，负责将用户指令转换为内核能理解的操作，并将结果反馈给用户。它既是一种命令行解释器，也是一个脚本运行环境。Shell 的核心功能包括命令解释与执行、脚本编程支持、进程管理与环境控制、以及管道与重定向。Shell 有两种工作模式：交互式和非交互式，分别用于实时命令输入和脚本执行。常见的 Shell 类型包括 sh、bash 和 zsh，各自具有不同的历史、特性和适用场景。例如，sh 适用于跨平台脚本和资源受限环境，bash 是 Linux 系统的默认 Shell，
shell框架构建1
dong6dong6的专栏
08-20 862
一、初步认识shell 文件名：tesh.sh #!/bin/bash echo "Hello World !" 1、#！是约定的标记，告诉系统这个脚本需要什么解释器来执行，即使用哪一种shell 2、echo命令用于向窗口输出文本 两种运行方式： 1、作为可执行程序 chmod +x tesh.sh ./tesh.sh 2、作为解释器参数 /bin/bash
用 Shell 快速写一个嵌入式测试框架
嵌入式Hacker
02-08 389
哈喽，我是老吴。作为一个嵌入式底层码农，在项目初期，我经常需要测试各种 Linux 单板的稳定性和性能。例如：用 memtester 测试内存的稳定性。用 glmark-es2 测试 GP...
shell简单架构
a13568hki的博客
11-13 648
#/bin/bash read -ep "请输入keepalived所在的本地IP:" IP read -ep "请输入另一台keepalived所在的本地IP:" IP2 read -ep "请输入你创建的keepalived的VIP:" net read -ep "请输入ngixn负载的IP:" fu read -ep "请输入ngixn负载的另一条IP:" fu2 read -ep "是否...
从0开始写出一个最简单的shell（基于x210）
hdbzh的博客
08-16 1421
从0开始写出一个最简单的shell 什么是shell？ 实现的shell回显功能以及定义简单命令集 基本思路： 1.打印命令行提示符 2.获取用户输入的命令 3.解析用户输入的命令 （1）解析成功即打印出对于命令 （2）解析失败则打印出NULL 上代码: #include<stdio.h> #include<string.h> #define max_command_length 256 //定义命令行的长度 /*定义命令*/ #define led "led" #de
HTTP请求的机器人框架关键字_Python_Shell_下载.zip
04-25
Robot Framework是一个开源的、通用的自动化测试框架，它采用人类可读的关键词驱动测试方法。HTTP Library是Robot Framework的一个扩展库，专门用于执行HTTP请求，如GET、POST、PUT、DELETE等，这使得测试用例编写...
基于Java、Vue、JavaScript、HTML、Shell的Lliuhonkai项目设计源码
02-14
Lliuhonkai项目是一个融合了多种技术的综合项目，以其功能全面、交互流畅的特点，成为研究前端与后端协同工作的典型案例。 首先，Java作为后端开发的主要语言，在Lliuhonkai项目中承担着核心的角色。277个Java...
shell:一个非常轻量级的框架，用于构建shellCLI应用程序。 可在Node.js，Deno和浏览器中使用
05-22
@ author.io / shell 这是用于构建基于文本的程序（例如应用程序）的超轻量级框架。 此现在支持该库： 您可以在此（“ CLI优先”开发策略的好处）中看到正在使用的库（在浏览器和Node.js中）。 用途 有两种类型的基于文本的应用程序： 单用途（命令），这些都是可以有多个配置选项，但最终只能做一件事的工具。 示例包括 ， ， ，pettitier等。 例如，可以使用tap [options] [<files>]类的语法在文件上运行node-tap。 最终，该实用程序可以达到一个目的。 它仅运行已配置的点击过程。 多用途（用于多个命令的外壳）其他工具除了配置脚本外还可以做更多的事情。 考虑npm，它具有几个子命令（例如install ， uninstall ， info等）。 子命令通常像它们自己的单一目的工具一样工作，具有自己的唯一标志，甚至是自己的子命令。
awesome-shell：精采的Shell框架，库和软件的精选列表
02-10
真棒壳 精选的Shell框架，库和软件的精选清单。 :upside-down_face: 一个令人愉快的社区驱动的（拥有1700多个贡献者）框架，用于管理zsh配置。 包括将近300个可选插件（rails，git，OSX，hub，capistrano，brew，ant，php，python等），超过140个主题来为您的早晨增光添彩，以及一个自动更新工具，使您可以轻松保持与社区的最新更新。 节点版本管理器-符合POSIX的bash脚本，用于管理多个活动的node.js版本 :books: 控制台命令的协作备忘单 互联网广告的黑洞 - :open_book: 一组纯bash替代外部过程。 实现ACME客户端协议的纯Unix shell脚本 用户友好的命令行外壳。 autosuggestions-用于zsh的类似于鱼的自动建议 - :rocket: :white_medium_star: Zsh提示宇航员 适用于Ubuntu，Debian，CentOS和Fedora的OpenVPN R
site:模块化 shell 脚本框架 - 99% 原生 bash，1% phat！
06-21
由 SCHTUNT/SIMBOL 分叉和弃用 请注意已被弃用，取而代之的是 ； 该项目不再维护。 gh-pages自述文件 您可能正在寻找此或相应的。 自述文件 请注意，此 README 并未涵盖site是什么（在中已涵盖），而是侧重于网站开发的当前状态。 发展状况 以下是目前正在开发/开发的站点模块： 核心模块 代码完整 描述 单元 :waning_gibbous_moon: 核心单元测试模块 实用程序 :full_moon: 核心实用程序模块 帮助 :full_moon: 核心帮助模块 高铁 :waning_gibbous_moon: 核心 HGD（主机组指令）模块 网 :full_moon: 核心网络模块 GPG :full_moon: 核心 GNUPG 模块 金库 :full_moon: 核心保险库和机密管理模块 偏僻的 :waning_gibbous_moon: 站点远程访问/执行模块（ssh、ssh/sudo、tmux等） 混帐 :full_moon: 辅助 Git 助手模块 域名解析 :full_moon: 核心DNS模块 隧
Java 调用 Linux shell 命令执行框架：sshxcute
12-08
资源包含sshxcute-1.0.jar及中文使用指南； sshxcute框架简介： 软件开发与测试人员常常会在远程 Linux/UNIX 系统上执行命令或脚本，有时还会有批量执行任务的需求。常见的办法是通过本地工具（例如 Putty）连接远程计算机，输入命令执行，但是当遇到需要集成这些任务到代码或者开发、测试框架中时，往往就没有很好的解决方案了。sshxcute 就是这样一个框架工具集，它基于 JSCH 构建，允许工程师利用Java 代码通过 SSH 连接远程批量执行 Linux/UNIX 系统上的命令或者脚本，同时加入了判断成功与否，取回输出等多种实用功能。sshxcute 不管是针对软件开发、测试还是系统部署，都简化了自动化流程与系统环境部署的步骤。
实现自己的shell框架
ZD的博客
04-20 3779
#include<sys/types.h> //系统基本数据类型 #include<sys/wait.h> //waitpid() #include<unistd.h> //execvp()while(1) { type_prompt(); //输出命令提示符 read_command(command,parameters); //读命令处理命令 if(fork() == 0
ShutIt：一个基于Python的shell自动化框架
博客
06-13 667
原文：ShutIt 翻译：雁惊寒 译者注：本文通过实例简单介绍了ShutIt这个基于Python的自动化框架的使用方法。除了pexpect，我们又多了这个选择。以下是译文。ShutIt是一个易于使用的基于shell的自动化框架。它对基于python的expect库（pexpect）进行了包装。你可以把它看作是“没有痛点的expect”。它可以通过pip进行安装。Hello World让...
Shell脚本学习-Shell脚本框架
CCH2024的专栏
08-04 343
Shell脚本学习
推荐一款强大的Shell脚本开发框架：SHML
gitblog_00088的博客
05-22 523
推荐一款强大的Shell脚本开发框架：SHML shmlSHell Markup Language | Style Framework for The Terminal项目地址:https://gitcode.com/gh_mirrors/sh/shml 项目介绍 SHML是一个创新的shell框架，旨在简化和加速Shell脚本的开发过程。它借鉴了HTML与CSS的关系，为终端提供了一种直观的方...
深入理解UEFI原理：Intel框架下的统一可扩展固件接口
EFI Shell是一个命令行环境，允许用户在启动过程中执行各种任务，比如修改配置或检查硬件状态。Runtime Environment在操作系统加载后运行，支持操作系统和设备驱动程序之间的交互。 文档特别提到了Intel的UEFI ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值