Mac 使用

Mac 安装 jenkins

Mac安装jenkins

  1. 首先先安装brew命令, 如之前安装过则跳过
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
  1. jenkins的安装,依赖jdk8,使用以下命令安装jdk8
brew cask install homebrew/cask-versions/adoptopenjdk8
  1. 安装jenkins, Homebrew会将软件包安装到独立目录/usr/local/Cellar,并将其文件软链接至/usr/local
brew install jenkins
  1. 命令启动/停止/重启jenkins
#启动jenkins
brew services start jenkins
#停止jenkins 
brew services stop jenkins
#重启jenkins
brew services restart jenkins
  1. 然后打开浏览器,输入localhost:8080 or ip:8080 访问,然后输入密码。
# 获取密码
cat /Users/${计算机名称}/.jenkins/secrets/initialAdminPassword

通过 homebrew 安装 jinkens 后,提示内容:

Note: When using launchctl the port will be 8080.

To start jenkins now and restart at login:

brew services start jenkins

Or, if you don't want/need a background service you can just run:

/opt/homebrew/opt/jenkins/bin/jenkins --httpListenAddress\=127.0.0.1 --httpPort\=8080

Link:

Python Conda macOS安装步骤:

brew install --cask anaconda
## setup conda environment
vim ~/.zshrc
export PATH="/opt/homebrew/anaconda3/bin:$PATH"
source ~/.zshrc
conda --version

## create empty environment
conda create -n py37 or conda create --name py37

## activate
conda activate py37 or source activate python3.7

## use x86_64 architecture channel(s)
conda config --env --set subdir osx-64

## install python, numpy, etc. (add more packages here...)
conda install python=3.7 numpy

## show all envs
conda info --envs

Link:

Mac开发记录

Mac 开发权限记录

在Mac开发中,如果需要申请权限才能运行,建议使用证书或账号(免费账号/收费账号)进行开发,否则使用(Sign To Run Locally)方式运行会导致每次代码改动后运行App都要重新进行授权(需要先删除上次的权限,再进行授权)

使用以下命令可以重置录屏屏幕权限
// 重置Mac App 权限设置
tccutil reset ScreenCapture com.xsir.packagename

Mac证书申请

2.1 Mac证书申请后,如果需要申请描述文件,需要导入Mac电脑的 UDID,添加 UDID 时注意选择为Mac平台,否则无法添加进描述文件。
Mac电脑的 UDID 获取方式:
option + 左上角菜单栏的苹果菜单,点击系统信息,在硬件概览里选择 预置UDID

2.2 Mac电脑证书导入,跟iOS 证书一致,都是导入P12文件。然后在 Provision Profile 中选择 Import Profile,之后就可以进行正常使用(通过描述文件对应证书)。

Note: 对于创建证书和描述文件的电脑,则为双击安装。如果安装后无法显示描述文件,需要重启Xcode再进行操作

Mac安装oh-my-zsh

Mac安装oh-my-zsh,可以提升Mac终端使用便利性,自动提示可以忽略大小写,安装官方教材如下:

https://ohmyz.sh/

目录

一、安装Ohmyzsh

1、执行命令:

2、手动安装

二、配置主题

三、配置插件

1、增加高亮插件zsh-syntax-highlighting

2、增加自动提示插件zsh-autosuggestions

四、推荐命令行工具

1、iterm2

2、hyper

官网:

Oh My Zsh - a delightful & open source framework for Zsh
https://ohmyz.sh/

一、安装Ohmyzsh

官网安装教程:Oh My Zsh - a delightful & open source framework for Zshzz
Oh-My-Zsh is a delightful, open source, community-driven framework for managing your ZSH configuration.
https://ohmyz.sh/#install

需要能连接到github(解决git clone超时问题见:

https://blog.csdn.net/CaptainJava/article/details/121119176
https://blog.csdn.net/CaptainJava/article/details/121119176

1、执行命令:

sh -c "$(curl -fsSL https://raw.github.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"

2、手动安装

如果链接不到这个网址 可以通过浏览器打开这个地址,把内容报错下来,或者复制一下内容报错为install.sh:

#!/bin/sh
#
# This script should be run via curl:
#   sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"
# or via wget:
#   sh -c "$(wget -qO- https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"
# or via fetch:
#   sh -c "$(fetch -o - https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"
#
# As an alternative, you can first download the install script and run it afterwards:
#   wget https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh
#   sh install.sh
#
# You can tweak the install behavior by setting variables when running the script. For
# example, to change the path to the Oh My Zsh repository:
#   ZSH=~/.zsh sh install.sh
#
# Respects the following environment variables:
#   ZSH     - path to the Oh My Zsh repository folder (default: $HOME/.oh-my-zsh)
#   REPO    - name of the GitHub repo to install from (default: ohmyzsh/ohmyzsh)
#   REMOTE  - full remote URL of the git repo to install (default: GitHub via HTTPS)
#   BRANCH  - branch to check out immediately after install (default: master)
#
# Other options:
#   CHSH       - 'no' means the installer will not change the default shell (default: yes)
#   RUNZSH     - 'no' means the installer will not run zsh after the install (default: yes)
#   KEEP_ZSHRC - 'yes' means the installer will not replace an existing .zshrc (default: no)
#
# You can also pass some arguments to the install script to set some these options:
#   --skip-chsh: has the same behavior as setting CHSH to 'no'
#   --unattended: sets both CHSH and RUNZSH to 'no'
#   --keep-zshrc: sets KEEP_ZSHRC to 'yes'
# For example:
#   sh install.sh --unattended
# or:
#   sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)" "" --unattended
#
set -e
 
# Track if $ZSH was provided
custom_zsh=${ZSH:+yes}
 
# Default settings
ZSH=${ZSH:-~/.oh-my-zsh}
REPO=${REPO:-ohmyzsh/ohmyzsh}
REMOTE=${REMOTE:-https://github.com/${REPO}.git}
BRANCH=${BRANCH:-master}
 
# Other options
CHSH=${CHSH:-yes}
RUNZSH=${RUNZSH:-yes}
KEEP_ZSHRC=${KEEP_ZSHRC:-no}
 
 
command_exists() {
  command -v "$@" >/dev/null 2>&1
}
 
# The [ -t 1 ] check only works when the function is not called from
# a subshell (like in `$(...)` or `(...)`, so this hack redefines the
# function at the top level to always return false when stdout is not
# a tty.
if [ -t 1 ]; then
  is_tty() {
    true
  }
else
  is_tty() {
    false
  }
fi
 
# This function uses the logic from supports-hyperlinks[1][2], which is
# made by Kat Marchán (@zkat) and licensed under the Apache License 2.0.
# [1] https://github.com/zkat/supports-hyperlinks
# [2] https://crates.io/crates/supports-hyperlinks
#
# Copyright (c) 2021 Kat Marchán
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
supports_hyperlinks() {
  # $FORCE_HYPERLINK must be set and be non-zero (this acts as a logic bypass)
  if [ -n "$FORCE_HYPERLINK" ]; then
    [ "$FORCE_HYPERLINK" != 0 ]
    return $?
  fi
 
  # If stdout is not a tty, it doesn't support hyperlinks
  is_tty || return 1
 
  # DomTerm terminal emulator (domterm.org)
  if [ -n "$DOMTERM" ]; then
    return 0
  fi
 
  # VTE-based terminals above v0.50 (Gnome Terminal, Guake, ROXTerm, etc)
  if [ -n "$VTE_VERSION" ]; then
    [ $VTE_VERSION -ge 5000 ]
    return $?
  fi
 
  # If $TERM_PROGRAM is set, these terminals support hyperlinks
  case "$TERM_PROGRAM" in
  Hyper|iTerm.app|terminology|WezTerm) return 0 ;;
  esac
 
  # kitty supports hyperlinks
  if [ "$TERM" = xterm-kitty ]; then
    return 0
  fi
 
  # Windows Terminal or Konsole also support hyperlinks
  if [ -n "$WT_SESSION" ] || [ -n "$KONSOLE_VERSION" ]; then
    return 0
  fi
 
  return 1
}
 
fmt_link() {
  # $1: text, $2: url, $3: fallback mode
  if supports_hyperlinks; then
    printf '\033]8;;%s\a%s\033]8;;\a\n' "$2" "$1"
    return
  fi
 
  case "$3" in
  --text) printf '%s\n' "$1" ;;
  --url|*) fmt_underline "$2" ;;
  esac
}
 
fmt_underline() {
  is_tty && printf '\033[4m%s\033[24m\n' "$*" || printf '%s\n' "$*"
}
 
# shellcheck disable=SC2016 # backtick in single-quote
fmt_code() {
  is_tty && printf '`\033[2m%s\033[22m`\n' "$*" || printf '`%s`\n' "$*"
}
 
fmt_error() {
  printf '%sError: %s%s\n' "$BOLD$RED" "$*" "$RESET" >&2
}
 
setup_color() {
  # Only use colors if connected to a terminal
  if is_tty; then
    RAINBOW="
      $(printf '\033[38;5;196m')
      $(printf '\033[38;5;202m')
      $(printf '\033[38;5;226m')
      $(printf '\033[38;5;082m')
      $(printf '\033[38;5;021m')
      $(printf '\033[38;5;093m')
      $(printf '\033[38;5;163m')
    "
    RED=$(printf '\033[31m')
    GREEN=$(printf '\033[32m')
    YELLOW=$(printf '\033[33m')
    BLUE=$(printf '\033[34m')
    BOLD=$(printf '\033[1m')
    RESET=$(printf '\033[m')
  else
    RAINBOW=""
    RED=""
    GREEN=""
    YELLOW=""
    BLUE=""
    BOLD=""
    RESET=""
  fi
}
 
setup_ohmyzsh() {
  # Prevent the cloned repository from having insecure permissions. Failing to do
  # so causes compinit() calls to fail with "command not found: compdef" errors
  # for users with insecure umasks (e.g., "002", allowing group writability). Note
  # that this will be ignored under Cygwin by default, as Windows ACLs take
  # precedence over umasks except for filesystems mounted with option "noacl".
  umask g-w,o-w
 
  echo "${BLUE}Cloning Oh My Zsh...${RESET}"
 
  command_exists git || {
    fmt_error "git is not installed"
    exit 1
  }
 
  ostype=$(uname)
  if [ -z "${ostype%CYGWIN*}" ] && git --version | grep -q msysgit; then
    fmt_error "Windows/MSYS Git is not supported on Cygwin"
    fmt_error "Make sure the Cygwin git package is installed and is first on the \$PATH"
    exit 1
  fi
 
  git clone -c core.eol=lf -c core.autocrlf=false \
    -c fsck.zeroPaddedFilemode=ignore \
    -c fetch.fsck.zeroPaddedFilemode=ignore \
    -c receive.fsck.zeroPaddedFilemode=ignore \
    -c oh-my-zsh.remote=origin \
    -c oh-my-zsh.branch="$BRANCH" \
    --depth=1 --branch "$BRANCH" "$REMOTE" "$ZSH" || {
    fmt_error "git clone of oh-my-zsh repo failed"
    exit 1
  }
 
  echo
}
 
setup_zshrc() {
  # Keep most recent old .zshrc at .zshrc.pre-oh-my-zsh, and older ones
  # with datestamp of installation that moved them aside, so we never actually
  # destroy a user's original zshrc
  echo "${BLUE}Looking for an existing zsh config...${RESET}"
 
  # Must use this exact name so uninstall.sh can find it
  OLD_ZSHRC=~/.zshrc.pre-oh-my-zsh
  if [ -f ~/.zshrc ] || [ -h ~/.zshrc ]; then
    # Skip this if the user doesn't want to replace an existing .zshrc
    if [ "$KEEP_ZSHRC" = yes ]; then
      echo "${YELLOW}Found ~/.zshrc.${RESET} ${GREEN}Keeping...${RESET}"
      return
    fi
    if [ -e "$OLD_ZSHRC" ]; then
      OLD_OLD_ZSHRC="${OLD_ZSHRC}-$(date +%Y-%m-%d_%H-%M-%S)"
      if [ -e "$OLD_OLD_ZSHRC" ]; then
        fmt_error "$OLD_OLD_ZSHRC exists. Can't back up ${OLD_ZSHRC}"
        fmt_error "re-run the installer again in a couple of seconds"
        exit 1
      fi
      mv "$OLD_ZSHRC" "${OLD_OLD_ZSHRC}"
 
      echo "${YELLOW}Found old ~/.zshrc.pre-oh-my-zsh." \
        "${GREEN}Backing up to ${OLD_OLD_ZSHRC}${RESET}"
    fi
    echo "${YELLOW}Found ~/.zshrc.${RESET} ${GREEN}Backing up to ${OLD_ZSHRC}${RESET}"
    mv ~/.zshrc "$OLD_ZSHRC"
  fi
 
  echo "${GREEN}Using the Oh My Zsh template file and adding it to ~/.zshrc.${RESET}"
 
  sed "/^export ZSH=/ c\\
export ZSH=\"$ZSH\"
" "$ZSH/templates/zshrc.zsh-template" > ~/.zshrc-omztemp
  mv -f ~/.zshrc-omztemp ~/.zshrc
 
  echo
}
 
setup_shell() {
  # Skip setup if the user wants or stdin is closed (not running interactively).
  if [ "$CHSH" = no ]; then
    return
  fi
 
  # If this user's login shell is already "zsh", do not attempt to switch.
  if [ "$(basename -- "$SHELL")" = "zsh" ]; then
    return
  fi
 
  # If this platform doesn't provide a "chsh" command, bail out.
  if ! command_exists chsh; then
    cat <<EOF
I can't change your shell automatically because this system does not have chsh.
${BLUE}Please manually change your default shell to zsh${RESET}
EOF
    return
  fi
 
  echo "${BLUE}Time to change your default shell to zsh:${RESET}"
 
  # Prompt for user choice on changing the default login shell
  printf '%sDo you want to change your default shell to zsh? [Y/n]%s ' \
    "$YELLOW" "$RESET"
  read -r opt
  case $opt in
    y*|Y*|"") echo "Changing the shell..." ;;
    n*|N*) echo "Shell change skipped."; return ;;
    *) echo "Invalid choice. Shell change skipped."; return ;;
  esac
 
  # Check if we're running on Termux
  case "$PREFIX" in
    *com.termux*) termux=true; zsh=zsh ;;
    *) termux=false ;;
  esac
 
  if [ "$termux" != true ]; then
    # Test for the right location of the "shells" file
    if [ -f /etc/shells ]; then
      shells_file=/etc/shells
    elif [ -f /usr/share/defaults/etc/shells ]; then # Solus OS
      shells_file=/usr/share/defaults/etc/shells
    else
      fmt_error "could not find /etc/shells file. Change your default shell manually."
      return
    fi
 
    # Get the path to the right zsh binary
    # 1. Use the most preceding one based on $PATH, then check that it's in the shells file
    # 2. If that fails, get a zsh path from the shells file, then check it actually exists
    if ! zsh=$(command -v zsh) || ! grep -qx "$zsh" "$shells_file"; then
      if ! zsh=$(grep '^/.*/zsh$' "$shells_file" | tail -1) || [ ! -f "$zsh" ]; then
        fmt_error "no zsh binary found or not present in '$shells_file'"
        fmt_error "change your default shell manually."
        return
      fi
    fi
  fi
 
  # We're going to change the default shell, so back up the current one
  if [ -n "$SHELL" ]; then
    echo "$SHELL" > ~/.shell.pre-oh-my-zsh
  else
    grep "^$USERNAME:" /etc/passwd | awk -F: '{print $7}' > ~/.shell.pre-oh-my-zsh
  fi
 
  # Actually change the default shell to zsh
  if ! chsh -s "$zsh"; then
    fmt_error "chsh command unsuccessful. Change your default shell manually."
  else
    export SHELL="$zsh"
    echo "${GREEN}Shell successfully changed to '$zsh'.${RESET}"
  fi
 
  echo
}
 
# shellcheck disable=SC2183  # printf string has more %s than arguments ($RAINBOW expands to multiple arguments)
print_success() {
  printf '%s         %s__      %s           %s        %s       %s     %s__   %s\n' $RAINBOW $RESET
  printf '%s  ____  %s/ /_    %s ____ ___  %s__  __  %s ____  %s_____%s/ /_  %s\n' $RAINBOW $RESET
  printf '%s / __ \%s/ __ \  %s / __ `__ \%s/ / / / %s /_  / %s/ ___/%s __ \ %s\n' $RAINBOW $RESET
  printf '%s/ /_/ /%s / / / %s / / / / / /%s /_/ / %s   / /_%s(__  )%s / / / %s\n' $RAINBOW $RESET
  printf '%s\____/%s_/ /_/ %s /_/ /_/ /_/%s\__, / %s   /___/%s____/%s_/ /_/  %s\n' $RAINBOW $RESET
  printf '%s    %s        %s           %s /____/ %s       %s     %s          %s....is now installed!%s\n' $RAINBOW $GREEN $RESET
  printf '\n'
  printf '\n'
  printf "%s %s %s\n" "Before you scream ${BOLD}${YELLOW}Oh My Zsh!${RESET} look over the" \
    "$(fmt_code "$(fmt_link ".zshrc" "file://$HOME/.zshrc" --text)")" \
    "file to select plugins, themes, and options."
  printf '\n'
  printf '%s\n' "• Follow us on Twitter: $(fmt_link @ohmyzsh https://twitter.com/ohmyzsh)"
  printf '%s\n' "• Join our Discord community: $(fmt_link "Discord server" https://discord.gg/ohmyzsh)"
  printf '%s\n' "• Get stickers, t-shirts, coffee mugs and more: $(fmt_link "Planet Argon Shop" https://shop.planetargon.com/collections/oh-my-zsh)"
  printf '%s\n' $RESET
}
 
main() {
  # Run as unattended if stdin is not a tty
  if [ ! -t 0 ]; then
    RUNZSH=no
    CHSH=no
  fi
 
  # Parse arguments
  while [ $# -gt 0 ]; do
    case $1 in
      --unattended) RUNZSH=no; CHSH=no ;;
      --skip-chsh) CHSH=no ;;
      --keep-zshrc) KEEP_ZSHRC=yes ;;
    esac
    shift
  done
 
  setup_color
 
  if ! command_exists zsh; then
    echo "${YELLOW}Zsh is not installed.${RESET} Please install zsh first."
    exit 1
  fi
 
  if [ -d "$ZSH" ]; then
    echo "${YELLOW}The \$ZSH folder already exists ($ZSH).${RESET}"
    if [ "$custom_zsh" = yes ]; then
      cat <<EOF
You ran the installer with the \$ZSH setting or the \$ZSH variable is
exported. You have 3 options:
1. Unset the ZSH variable when calling the installer:
   $(fmt_code "ZSH= sh install.sh")
2. Install Oh My Zsh to a directory that doesn't exist yet:
   $(fmt_code "ZSH=path/to/new/ohmyzsh/folder sh install.sh")
3. (Caution) If the folder doesn't contain important information,
   you can just remove it with $(fmt_code "rm -r $ZSH")
EOF
    else
      echo "You'll need to remove it if you want to reinstall."
    fi
    exit 1
  fi
 
  setup_ohmyzsh
  setup_zshrc
  setup_shell
 
  print_success
 
  if [ $RUNZSH = no ]; then
    echo "${YELLOW}Run zsh to try it out.${RESET}"
    exit
  fi
 
  exec zsh -l
}
 
main "$@"

然后给install.sh文件赋可执行权限

chmod +x install.sh

执行安装:

./install.sh

二、配置主题

自带主题示例:

https://github.com/ohmyzsh/ohmyzsh/wiki/Themes

默认主题目录:~/.oh-my-zsh/themes
自定义主题目录:~/.oh-my-zsh/custom/themes

自定义插件优先加载,如果没有再加载默认目录中的主题,建议自己下载的主题下载到自定义目录中

自带主题所在目录:

~/.oh-my-zsh/themes

设置方法:

修改配置文件

~/.zshrc

修改内容如下:

# 默认主题
# ZSH_THEME="robbyrussell"
# 随机主题
#ZSH_THEME="random"
 
ZSH_THEME="cloud"

也可以设置随机主题,每次开启窗口或者source是会自动切换,设置方式如下:

ZSH_THEME="random"

切换后会提示当前使用主题,如:

[oh-my-zsh] Random theme 'cloud' loaded

三、配置插件
说明:

默认插件目录:~/.oh-my-zsh/plugins
自定义插件目录:~/.oh-my-zsh/custom/plugins

自定义插件优先加载,如果没内有在加载默认目录中的插件,建议自己下载的插件下载到自定义目录中

以下插件可以通过手动git clone至插件目录或者通过一下命令

1、增加高亮插件zsh-syntax-highlighting

git clone https://github.com/zsh-users/zsh-syntax-highlighting.git ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-syntax-highlighting

修改~/.zshrc文件中配置:(插件间加空格)

plugins=(其他的插件 zsh-syntax-highlighting)
2、增加自动提示插件zsh-autosuggestions

git clone https://github.com/zsh-users/zsh-autosuggestions $ZSH_CUSTOM/plugins/zsh-autosuggestions

修改~/.zshrc文件中配置:

plugins=(其他的插件 zsh-autosuggestions)

最终:

plugins=(git zsh-autosuggestions zsh-syntax-highlighting per-directory-history command-not-found safe-paste history-substring-search)

插件推荐:mac上使用oh my zsh有哪些必备的插件推荐? - 知乎

四、推荐命令行工具

1、iterm2
2、hyper

Hyper™
A terminal built on web technologies
https://hyper.is/

Link: (mac安装ohmyzsh)[https://blog.csdn.net/CaptainJava/article/details/121117458]

MacOS系统的开机启动整理

缘由:

简单整理一下macOS系统开机启动的相关知识,方便以后有需要的时候参考。

正文:

参考解答:
为什么要关心MACOS系统的启动项?
  • 为了方便使用,我们希望某些软件在开机(登录)后自动启动,比如 mysql 服务;
  • 为了减少资源占用以及出于安全考虑,还有一些默认开机(登录)后启动的软件我们不想让它自动启动,很多不常用的软件以及我们没想到的程序。
LAUNCHD 是什么?
Wikipedia defines launchd as "a unified, open-source service management framework for starting, stopping and managing daemons, applications, processes, and scripts. Written and designed by Dave Zarzycki at Apple, it was introduced with Mac OS X Tiger and is licensed under the Apache License."

根据上面的描述可以认为launchd是一套统一的开源服务管理框架,它用于启动、停止以及管理后台程序、应用程序、进程和脚本。它是由Apple开发的,并在 Mac OS X Tiger 操作系统上第一次被引入,并基于 Apache License 进行授权。

launchd 是macOS系统上第一个启动的进程,该进程(/sbin/launchd)的PID为1,整个系统的其他进程都是它创建的。当launchd启动后,它会扫描 /System/Library/LaunchDaemons 和 /Library/LaunchDaemons 中的plist文件并加载他们;当输入密码登录系统后,launchd会扫描 /System/Library/LaunchdAgents、/Library/LaunchAgents、~/Library/LaunchAgents 这三个目录中的plist文件并加载它们。

LAUNCHAGENTS 和 LAUNCHDAEMONS 的异同

守护进程(Daemon)是在后台运行的程序,不需要用户输入。例如,典型的守护进程一般用于执行日常维护任务或在有设备连入时进行恶意软件扫描。(A daemon is a program running in the background without requiring user input. A typical daemon might for instance perform daily maintenance tasks or scan a device for malware when it is connected.)

一句话描述就是——对于launchd来说,Agent和Daemon的主要区别在于代理(Agent)是以当前登录用户的权限运行的,而守护进程(Daemon)是以root或通过UserName键指定的用户权限运行的。

当电脑开机,macOS系统启动后,守护进程(Daemon)就会启动;而代理(Agent)只有在用户输入密码,登录系统的图形化界面后才会启动。

不同位置的 LaunchAgents 和 LaunchDaemons 的异同:

  • ~/Library/LaunchAgents #用户agents,以当前登录用户的身份运行
  • /Library/LaunchAgents #全局agents,以当前登录用户的身份运行
  • /Library/LaunchDaemons #全局daemons,以root或指定用户的身份运行
  • /System/Library/LaunchAgents #【不要自己擅自改动的】系统agents,以当前登录用户的身份运行
  • /System/Library/LaunchDaemons #【不要自己擅自改动的】系统daemons,以root或指定用户的身份运行
PLIST文件简单说明

launchd 是通过以“.plist”后缀结尾的xml⽂件来指定⼀个 agent/daemon 的行为,我们⼀般称它为plist⽂件。根据 plist文件 存放位置的不同,我们会分别将它们视为 agent 或 daemon 。

每个plist文件都是一个任务,加载不代表立即运行,只有设置了 RunAtLoad 为true或 keepAlive 为true时,才会加载并同时启动这些任务。

下面以brew提供的 mysql.plist 文件为例学习一下「.plist文件」的编写方法:

$ cat ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>KeepAlive</key> //这个key表明你的daemon是按需启动还是需要一直运行
  <true/>
  <key>Label</key> //必须要有的key,下面的<string>为key对应的值,需要是唯一可辨识的
  <string>homebrew.mxcl.mysql</string>
  <key>ProgramArguments</key> //必须要有的key,下面的<array>为命令的路径和启动所需要的选项
  <array>
    <string>/usr/local/opt/mysql/bin/mysqld_safe</string>
    <string>--bind-address=127.0.0.1</string>
    <string>--datadir=/usr/local/var/mysql</string>
  </array>
  <key>RunAtLoad</key> //在被加载时运行
  <true/>
  <key>WorkingDirectory</key> //官方文档推荐使用 WorkingDirectory 这个key来指定工作目录
  <string>/usr/local/var/mysql</string>
</dict>
</plist>

根据文档来看,一个 plist文件 至少有 3 个关键的key需要指定:

  • Label #理论上在daemon或agent范围内部需要分别唯一可识别,但建议全局唯一
  • Program/ProgramArguments #指定要运行的程序和启动所需要的选项,建议直接用 ProgramArguments 就行
  • RunAtLoad #它决定程序是否在plist文件被加载时就运行

还有 1 个对于需要长期运行的daemon来说很关键的key是:

  • KeepAlive #它表明你的daemon是按需启动还是需要一直运行,为true则表示一直运行

其它的就很简单了,照着已有示例改改就能用。

加载 和 启动 PLIST文件 的区别

加载一个plist文件并不一定意味着启动plist文件中指定的程序。程序何时启动由plist文件中的设置决定。事实上,只有当指定了 RunAtLoad 或 KeepAlive 时,launchd才会在加载plist文件后无条件地启动指定的程序。(Loading a job definition does not necessarily mean to start the job. When a job is started is determined by the job definition. In fact, only when RunAtLoad or KeepAlive have been specified,launchd will start the job unconditionally when it has been loaded.)

LAUNCHCTL 的使用

列出所有由launchd管理的进程

launchctl list
launchctl list | grep 'keyword'

手动加载某个 .plist 文件:

launchctl load ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist
# -w选项的作用是,如果该服务被禁用了,则会在加载的同时设置为启用
launchctl load -w ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist

加载/卸载/启动/停止/移除/启用/停用/……

launchctl load|unload|start|stop|remove|enable|disable|... /path/to/name.plist

检查某个 .plist 文件的语法/格式是否正确:

plutil -lint ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist
# launchctl help
# launchctl load --help


Usage: launchctl <subcommand> ... | help [subcommand]
Many subcommands take a target specifier that refers to a domain or service
within that domain. The available specifier forms are:

system/[service-name]
Targets the system-wide domain or service within. Root privileges are required
to make modifications.

user/<uid>/[service-name]
Targets the user domain or service within. A process running as the target user
may make modifications. Root may modify any user's domain. User domains do not
exist on iOS.

gui/<uid>/[service-name]
Targets the GUI domain or service within. Each GUI domain is associated with a
user domain, and a process running as the owner of that user domain may make
modifications. Root may modify any GUI domain. GUI domains do not exist on iOS.

session/<asid>/[service-name]
Targets a session domain or service within. A process running within the target
security audit session may make modifications. Root may modify any session
domain.

pid/<pid>/[service-name]
Targets a process domain or service within. Only the process which owns the
domain may modify it. Even root may not do so.

When using a legacy subcommand which manipulates a domain, the target domain is
inferred from the current execution context. When run as root (whether it is
via a root shell or sudo(1)), the target domain is assumed to be the
system-wide domain. When run from a normal user's shell, the target is assumed
to be the per-user domain for that current user.

Subcommands:
...    
    enable          Enables an existing service.
    disable         Disables an existing service.
    kickstart       Forces an existing service to start.
...    
    kill            Sends a signal to the service instance.
...    
    runstats        Prints performance statistics for a service.
...    
    load            Recommended alternatives: bootstrap | enable. Bootstraps a service or directory of services.
    unload          Recommended alternatives: bootout | disable. Unloads a service or directory of services.
    remove          Unloads the specified service name.
    list            Lists information about services.
    start           Starts the specified service.
    stop            Stops the specified service if it is running.
...    
参考链接:

Mac上有些软件无法禁止开机启动怎么办?

MacOS:Launchd&LaunchDaemon&LaunchAgent&.plist文件编写

What is launchd?

Mac服务管理 – launchd、launchctl、LaunchAgent、LaunchDaemon、brew services详解

了解LaunchDaemons

【知识】管理 macOS 的启动项

macOS开机启动项设置

苹果全新版本macOS Ventura操作系统 macOS Ventura新功能

What are the differences between LaunchAgents and LaunchDaemons?

https://ss64.com/osx/launchctl.html

macOS: Know the difference between launch agents and daemons, and use them to automate processes

How to Catch and Remove Hidden LaunchDaemons and LaunchAgents on Mac

Creating Launch Daemons and Agents

Link:

Git 文件名为中文显示乱码处理

如果在你的项目下有许多中文文件名的文件,当你编辑某些后通过git status查看状态时会发现那些中文文件名的文件会显示成\345\267\245\344,这样一来你就不知道你到底编辑了哪些文件。 网上有人说是编码问题,修改编码为GB2312或GBK,尝试了一下是不可行的。也有人说配置core.quotepath,按照这个配置确实是可行的。

局部配置

如果想要显示成中文,则需要对git做一些配置,可以输入命令(适合所有平台):

git config core.quotepath false

此时可以查看当前项目根目录下的.git/config文件,在[core]下面多了一项配置quotepath = false。不过这个配置方法只是针对当前git项目有效,如果切换到其他项目。

也可以直接在.git/config文件中添加quotepath = false

全局配置

如果你不想在每个项目都像上面那样配置,你也可以做一个全局配置。有人说通过命令:

git config --global core.quotepath false

就可以进行全局配置,但尝试后实际上是不可行的(Windows下不行)。于是我想到的一个办法就是在git全局配置文件中进行配置,方法就类似配置.git/config文件。

找到当前系统的用户根目录下的.gitconfig文件,在配置中添加:

[core]
    quotepath = false
.gitconfig`所在路径,Windows下:`C:\Users\用户名`,Linux下:`/home/用户名`或执行命令`cd ~

注意问题

当前git项目下.git/config中的配置会覆盖全局的配置,所以当.git/config中配置了quotepath = true,全局配置了quotepath = false,查看中文文件依然还是乱码,必须需要将.git/config中的quotepath删掉或者设为false

Link: