主页 / unix / 问题 / 681126
Accepted
Martian2020
Asked: 2021-12-12 21:23:34 +0800 CST

如何检查 bash 脚本是否由 GUI 中的“在终端中运行”启动？

  • 772

我运行 bash 脚本。我想从终端和使用“在终端中运行”的 GUI 运行它们，并在运行 interactive 后离开bash。在这里简单地解释一下输出：添加read -rn1。

问题 X：我想要一个“干净”的解决方案，如果脚本从终端运行并且如果从 GUI 运行
，我可以在最后使用带有 bash 的相同终端来关闭它。exit我可以添加bash -i，但如果从终端运行，则需要两个exit来关闭终端。exec bash -i结果相同。

脚本中有没有办法检查它是否是通过“在终端中运行”从 GUI 启动的？

每条评论添加 1 条：

ps aux | grep aaaa # while script started from GUI was running
mint       53293  0.1  0.0  11216  3356 pts/3    Ss+  21:58   0:00 /bin/bash /home/mint/aaaaa.sh

注意到与从终端开始的区别是Ss+而不是S+.

bash gui

1 个回答

  1. Best Answer

    我假设您的 bash 脚本已命名/path/to/mybashscript.sh

    用于ps查找mybashscript.sh（$0如果在脚本中运行）；包括state/stat用于识别特定状态的列：

    ps --sort +pid -eo pid,stat,command | grep "$0" | head -1 | awk '{print $2}' | grep "s"

    或另一种过滤grep线的方法：

    ps -eo pid,stat,command | grep "$0" | grep -v grep | awk '{print $2}' | grep "s"

    根据您的评论，差异是由于添加了s：s is a session leader对于 GUI 方式，Ubuntu 没有那种从文件管理器启动脚本来检查的方式。

    从man ps，状态码如下：

    PROCESS STATE CODES
   Here are the different values that the s, stat and state output specifiers (header "STAT" or "S") will display
   to describe the state of a process:

           D    uninterruptible sleep (usually IO)
           I    Idle kernel thread
           R    running or runnable (on run queue)
           S    interruptible sleep (waiting for an event to complete)
           T    stopped by job control signal
           t    stopped by debugger during the tracing
           W    paging (not valid since the 2.6.xx kernel)
           X    dead (should never be seen)
           Z    defunct ("zombie") process, terminated but not reaped by its parent

   For BSD formats and when the stat keyword is used, additional characters may be displayed:

           <    high-priority (not nice to other users)
           N    low-priority (nice to other users)
           L    has pages locked into memory (for real-time and custom IO)
           s    is a session leader
           l    is multi-threaded (using CLONE_THREAD, like NPTL pthreads do)
           +    is in the foreground process group
    • 1

相关问题