<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bash on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/bash/</link>
    <description>Recent content in Bash on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 14 May 2025 22:11:33 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/bash/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PVE host disk space monitoring - from pitfalls to UptimeKuma</title>
      <link>https://blog.margrop.net/en/post/pve-host-virtual-machine-lvm-disk-space-monitor-experience/</link>
      <pubDate>Wed, 14 May 2025 22:11:33 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/pve-host-virtual-machine-lvm-disk-space-monitor-experience/</guid>
      <description>Target Reader This article is written for readers who have just started using Proxmox VE (referred to as PVE) and want to copy the steps and get it running. The article aims to:&#xA;explain why the problem happens provide the full command at each step give troubleshooting ideas when something goes wrong 0 Background - What went wrong? The official PVE installation wizard defaults to putting the VM disk into the LVM-Thin pool (commonly pve/data)</description>
    </item>
    <item>
      <title>Ubuntu installs Frp server, non-client</title>
      <link>https://blog.margrop.net/en/post/ubuntu-install-frp-server/</link>
      <pubDate>Sat, 23 Jan 2021 13:43:20 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/ubuntu-install-frp-server/</guid>
      <description>Download and extract FRP Latest FRP release: https://github.com/fatedier/frp/releases/ cd ~ mkdir frp cd frp wget https://github.com/fatedier/frp/releases/download/v0.35.0/frp_0.35.0_linux_amd64.tar.gz tar -xvzf frp_0.35.0_linux_amd64.tar.gz cd frp_0.35.0_linux_amd64 Configure FRP Remove the default client configuration file&#xA;Create the server configuration file&#xA;cd ~/frp/frp_0.35.0_linux_amd64/ rm frpc rm frpc.ini rm frpc_full.ini ls -a sudo su rm frps.ini cat&amp;gt;/etc/frps.ini&amp;lt;&amp;lt;EOF [common] # FRP server bind port bind_port = 1000 # Set the HTTP access port to 1001 vhost_http_port = 1001 # Set the domain name (make sure it is reachable) subdomain_host = frp.</description>
    </item>
    <item>
      <title>Initialization script after Proxmox VE installation</title>
      <link>https://blog.margrop.net/en/post/proxmox-ve-init-bash-script/</link>
      <pubDate>Fri, 22 Jan 2021 16:42:46 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/proxmox-ve-init-bash-script/</guid>
      <description>&lt;p&gt;In order to facilitate the installation of PVE, I compiled the relevant commands myself. Please modify them according to your own environment.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ProxmoxVE 6.3 uses commands to back up Synology virtual machines</title>
      <link>https://blog.margrop.net/en/post/proxmoxve-use-bash-to-backup-dsm-vm/</link>
      <pubDate>Thu, 21 Jan 2021 18:16:22 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/proxmoxve-use-bash-to-backup-dsm-vm/</guid>
      <description>Since the Synology virtual machine in my ProxmoxVE runs on a LUN passthrough disk, I cannot click backup directly in the Web interface.&#xA;DSM virtual machine backup process: Stop the virtual machine -&amp;gt; Unmount the hard disk -&amp;gt; Back up the virtual machine -&amp;gt; Mount the hard disk -&amp;gt; Start the virtual machine It is really troublesome and error-prone to do this entirely through the Web interface. So I studied the command-line workflow.</description>
    </item>
  </channel>
</rss>
