为什么我在 24.04 上使用 brasero 刻录数据 DVD 时无法选择文件系统？DVD 有默认文件系统吗？
这种情况已经持续了好几个月，但这绝对是过去一年来行为上的改变。每次发布新版本的 Chrome，我都会在 Chrome 中收到一条消息，提示更新失败，我应该重新启动浏览器来安装更新。当然，重新启动没有任何区别。
sudo apt install google-chrome-stable返回“google-chrome-stable 已经是最新版本”
apt show google-chrome-stable显示的版本号与 Chrome 相同，确认它是 apt 认为的版本。
这些都显示我安装的版本（显然是最新的）是 v129.whatever，但根据 Google 的说法，当前的稳定版本是 v131.whatever。Google 发布新版本到它出现在存储库中是否需要很长时间，还是出了什么问题？如果确实需要时间，有没有办法禁用 Chrome 中一直弹出的消息，提示它已过期？
这只是一个小小的烦恼，因为我大多数时候都使用 Opera，但仍然使用 Chrome 浏览一些“不支持” Opera 的网站。
Opera 更新得很好，今天我注意到 Chromium 通过 Discover 进行了更新，所以这似乎是 Chrome 独有的。
我正在使用 Kubuntu 24.10，但其行为至少与 24.04 相比没有变化。
编辑 1：建议的类似问题是我在发布此问题之前查看过的问题。该问题的标记答案表示apt show google-chrome-stable未找到任何结果，表明它不是从存储库安装的。我的答案确实显示了带有版本号和维护者信息的输出，因此可能不是同一个问题。
话虽如此，apt show但确实显示出来Apt-Manual-Installed: yes，这可能是问题吗？如果是这样，我该如何正确安装它，以便包管理器保持更新？
编辑 2：查看其他帖子/答案，我回想起了如何安装/更新。每次收到此警报时，我都会转到 Chrome 下载网站，下载最新的 x64 .deb 软件包并使用以下命令进行安装sudo dpkg -i ~/Downloads/google-chrome-stable_current_amd64.deb
这大概解释了手动安装标志，apt show但我相信这也应该会自动添加 Google 存储库以进行更新。有没有办法检查该部分是否有效？
编辑 3：输出sudo apt update看似没有显示 Google repos：
flim@flim:~$ sudo apt update
[sudo] password for flim:
Hit:1 http://gb.archive.ubuntu.com/ubuntu oracular InRelease
Hit:2 http://archive.ubuntu.com/ubuntu oracular InRelease
Get:3 http://archive.ubuntu.com/ubuntu oracular-updates InRelease [126 kB]
Get:4 http://gb.archive.ubuntu.com/ubuntu oracular-updates InRelease [126 kB]
Hit:5 http://gb.archive.ubuntu.com/ubuntu oracular-backports InRelease
Get:6 http://archive.ubuntu.com/ubuntu oracular-updates/main amd64 Packages [62.7 kB]
Get:7 http://gb.archive.ubuntu.com/ubuntu oracular-updates/main amd64 Packages [62.7 kB]
Get:8 http://gb.archive.ubuntu.com/ubuntu oracular-updates/universe amd64 Packages [28.1 kB]
Hit:9 http://security.ubuntu.com/ubuntu oracular-security InRelease
Fetched 406 kB in 6s (65.9 kB/s)
4 packages can be upgraded. Run 'apt list --upgradable' to see them.
flim@flim:~$
自从升级到 24.10 以来，我的登录屏幕一直闪烁，但大多数时候都会长时间关闭，而当它打开时，持续时间几乎不会长达一秒钟。
有时我会在黑屏上收到一条消息，说out of range。
我仍然可以通过输入密码登录，幸运的是焦点默认为密码输入框，一旦我进入桌面，一切都很好。
有什么想法可以让我稳定我的登录管理器，或者这是否是目前已知的无法修复的错误？
我最近将 Ubuntu 更新到了 24.04。现在当我打开 RStudio 时，出现以下错误消息：
我无法安装该软件包。我已经尝试了这篇文章bspm中的建议，但没有用。我也尝试了这篇文章。最后我阅读了有关该问题的信息并找到了这些信息，但都没有用。
显然，问题在于存储库尚未为 noble 创建 URL。
也许有一个解决方案，但是也没有用。
当我在 R 会话内部运行 install.packages("bspm") 时，我得到了这个：
Error en loadNamespace(x): no hay paquete llamado 'bspm'
Calls: loadNamespace -> withRestarts -> withOneRestart -> doWithOneRestart Ejecución interrumpida
Warning in install.packages: installation of package 'bspm' had non-zero exit status.
The downloaded source packages are in '/tmp/Rtmp04ur7K/downloaded_packages'
我最近切换到 Linux，并以 125% 的缩放比例运行它。我安装的大多数应用程序看起来都很模糊，一旦切换到 100% 缩放比例，问题就解决了，但所有东西看起来都很小，无法使用。（我可以修复 Vs Code，但 PyCharm 仍然很模糊）请帮忙。
我在我的 ubuntu vm 中安装了 opensearch 和 opensearch-dashboard。当我尝试使用以下命令找出 opensearch-dashboard 使用的资源时
top -U opensearch
我刚刚得到
Tasks: 125 total, 1 running, 124 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0,2 us, 0,1 sy, 0,0 ni, 99,6 id, 0,0 wa, 0,1 hi, 0,1 si, 0,0 st
MiB Mem : 3665,1 total, 869,7 free, 1745,8 used, 1049,5 buff/cache
MiB Swap: 0,0 total, 0,0 free, 0,0 used. 1606,2 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
70188 opensea+ 20 0 5078340 1,4g 22956 S 0,3 39,1 2:19.24 java
我认为这种信息聚合了 opensearch 和 opensearch-dashboard，我怎样才能找出仪表板使用的内存、CPU 和磁盘空间？
背景
我在两个 SSD 驱动器上安装了双启动。一个是 Windows 11，另一个是 Ubuntu Desktop 24.04。
昨天，我的 Ubuntu 系统崩溃了，我无法进入ttyshell。所以我不得不强制重启。
幸运的是，我的系统和所有 HDD/SSD 驱动器都很好。
/media不幸的是，当我像以前一样单击它时，一个 SSD 无法自动挂载。
虽然我可以手动安装它，但我仍然想知道崩溃后发生了什么。我希望当我从底部菜单单击它时，此 SSD 可以像其他 HDD/SSD 驱动器一样自动安装。
有人能给我一些建议吗？
线索
journalctl -xe
11月 13 10:20:31 usename-pc tracker-miner-fs-3[23503]: (tracker-extract-3:23503): GLib-GIO-WARNING **: 10:20:31.507: Error creating IO channel for /proc/self/mountinfo: 无效的参数 (g-io-er>
11月 13 10:20:43 usename-pc tracker-miner-fs-3[23636]: (tracker-extract-3:23636): GLib-GIO-WARNING **: 10:20:43.119: Error creating IO channel for /proc/self/mountinfo: 无效的参数 (g-io-er>
11月 13 10:20:45 usename-pc microsoft-edge.desktop[4901]: Fontconfig error: Cannot load default config file: No such file: (null)
11月 13 10:20:45 usename-pc microsoft-edge.desktop[4901]: [4947:4953:1113/102045.400351:ERROR:ssl_client_socket_impl.cc(892)] handshake failed; returned -1, SSL error code 1, net_error -100
11月 13 10:20:55 usename-pc tracker-miner-fs-3[23686]: (tracker-extract-3:23686): GLib-GIO-WARNING **: 10:20:55.780: Error creating IO channel for /proc/self/mountinfo: 无效的参数 (g-io-er>
tail /var/log/syslog
2024-11-13T10:24:30.677338+08:00 usename-pc tracker-miner-fs-3[24194]: (tracker-extract-3:24194): GLib-GIO-WARNING **: 10:24:30.676: Error creating IO channel for /proc/self/mountinfo: 无效的参数 (g-io-error-quark, 13)
2024-11-13T10:24:41.383113+08:00 usename-pc tracker-miner-fs-3[24278]: (tracker-extract-3:24278): GLib-GIO-WARNING **: 10:24:41.382: Error creating IO channel for /proc/self/mountinfo: 无效的参数 (g-io-error-quark, 13)
2024-11-13T10:24:41.425386+08:00 usename-pc microsoft-edge.desktop[4901]: [4894:4894:1113/102441.425166:ERROR:interface_endpoint_client.cc(725)] Message 0 rejected by interface blink.mojom.WidgetHost
2024-11-13T10:24:52.025510+08:00 usename-pc tracker-miner-fs-3[24369]: (tracker-extract-3:24369): GLib-GIO-WARNING **: 10:24:52.025: Error creating IO channel for /proc/self/mountinfo: 无效的参数 (g-io-error-quark, 13)
2024-11-13T10:25:01.018299+08:00 usename-pc CRON[24401]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
2024-11-13T10:25:05.211864+08:00 usename-pc tracker-miner-fs-3[24407]: (tracker-extract-3:24407): GLib-GIO-WARNING **: 10:25:05.211: Error creating IO channel for /proc/self/mountinfo: 无效的参数 (g-io-error-quark, 13)
2024-11-13T10:25:07.690463+08:00 usename-pc systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd...
2024-11-13T10:25:07.722400+08:00 usename-pc systemd[1]: fwupd-refresh.service: Deactivated successfully.
2024-11-13T10:25:07.722494+08:00 usename-pc systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd.
2024-11-13T10:25:15.936874+08:00 usename-pc tracker-miner-fs-3[24441]: (tracker-extract-3:24441): GLib-GIO-WARNING **: 10:25:15.936: Error creating IO channel for /proc/self/mountinfo: 无效的参数 (g-io-error-quark, 13)
2024-11-13T10:25:26.476227+08:00 usename-pc tracker-miner-fs-3[24464]: (tracker-extract-3:24464): GLib-GIO-WARNING **: 10:25:26.476: Error creating IO channel for /proc/self/mountinfo: 无效的参数 (g-io-error-quark, 13)
2024-11-13T10:25:37.372215+08:00 usename-pc tracker-miner-fs-3[24484]: (tracker-extract-3:24484): GLib-GIO-WARNING **: 10:25:37.371: Error creating IO channel for /proc/self/mountinfo: 无效的参数 (g-io-error-quark, 13)
2024-11-13T10:25:47.479607+08:00 usename-pc tracker-miner-fs-3[24494]: (tracker-extract-3:24494): GLib-GIO-WARNING **: 10:25:47.479: Error creating IO channel for /proc/self/mountinfo: 无效的参数 (g-io-error-quark, 13)
'smartctl' --info --health --capabilities '/dev/sdd'
martctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.0-48-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Phison Driven SSDs
Device Model: KINGSTON SA400S37480G
Serial Number: xxx
LU WWN Device Id: 5 0026b7 38301c9bc
Firmware Version: SAN20102
User Capacity: 480,103,981,056 bytes [480 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
TRIM Command: Available
Device is: In smartctl database 7.3/5528
ATA Version is: ACS-3 T13/2161-D revision 4
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Nov 13 10:37:21 2024 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x11) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0002) Does not save SMART data before
entering power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 10) minutes.
sudo fsck /dev/sdd
usename@usename-pc:~$ sudo fsck /dev/sdd
fsck，来自 util-linux 2.39.3
e2fsck 1.47.0 (5-Feb-2023)
ext2fs_open2：超级块中的幻数有错
fsck.ext2：超级块无效，正在尝试备份块...
fsck.ext2: 超级块中的幻数有错 尝试打开 /dev/sdd 时
超级块无法被读取，或它未能正确地描述一个有效的 ext2/ext3/ext4 文件系统。
如果设备有效并确实为 ext2/ext3/ext4 文件系统（而非 swap 或 ufs 等格式），
这说明超级块已经损坏，您可能需要指定备选超级块来运行 e2fsck：
e2fsck -b 8193 <设备>
或
e2fsck -b 32768 <设备>
在 /dev/sdd 中发现一个 dos 分区表
sudo blkid
usename@usename-pc:~$ sudo blkid
/dev/sdb2: UUID="081470ff--????---????--ba96-3dcd12b7a0f8" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="fa267313-4dfa-????-????-2c8fa2fe9f12"
/dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop19: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/sdd1: LABEL="code_space" BLOCK_SIZE="512" UUID="A27A6????AE5" TYPE="ntfs" PARTUUID="c832????-01"
/dev/loop17: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop25: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/sdb1: UUID="9F3B--????-" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="dfc51496-????--????--a1cb-723dc731dc8a"
/dev/loop15: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop6: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop23: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop13: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop4: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop21: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop11: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop2: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop18: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop9: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop26: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/sdc2: PARTLABEL="Microsoft reserved partition" PARTUUID="534d64be--????---????--81cc-b6f5d7c12fc7"
/dev/sdc3: BLOCK_SIZE="512" UUID="3952EC-????-7F3" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="9664f6a5--????---????---????--eeabf27b57bc"
/dev/sdc1: UUID="3C4B--????-" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="5c54a3e0-8-????--????---????--215601e8ef2b"
/dev/loop16: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop7: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop24: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/sda4: BLOCK_SIZE="512" UUID="88042-????-74B8E" TYPE="ntfs" PARTUUID="06cd5035--????---????--b611-df96c85bd394"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="10936ee2-b687--????---????--c0a0b58c79f3"
/dev/sda3: BLOCK_SIZE="512" UUID="74F4FC-????-C86A0" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="24ce83f0--????---????--a60c-7f8a928884d6"
/dev/sda1: UUID="7ADB--????-" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="830a6dbe--????---????--b32d-013e3ef39a08"
/dev/loop14: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop5: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop22: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop12: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop3: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop20: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop10: BLOCK_SIZE="131072" TYPE="squashfs"
结果
我还没弄清楚为什么我不能自动挂载，但我打算用它fstab来做这件事
我在 Ubuntu 22.04.5 LTS 服务器上。网络端口已中继。我正尝试使用 netplan 在 VLAN 202 上设置一个绑定为从属的虚拟网桥。以下不起作用：
$ cat /etc/netplan/00-bond-bridge-config.yaml
network:
version: 2
renderer: networkd
ethernets:
eno3:
dhcp4: false
eno4:
dhcp4: false
bonds:
bond0:
dhcp4: false
interfaces: [eno3, eno4]
parameters:
mode: active-backup
mii-monitor-interval: 100
vlans:
bond0.202:
id: 202
link: bond0
bridges:
br0:
dhcp4: false
interfaces: [bond0.202]
addresses: [192.168.1.2/24]
routes:
- to: default
via: 192.168.1.1
nameservers:
addresses: [1.1.1.1, 8.8.8.8]
search: []
我无法 ping 通我的 Ubuntu 主机。我的 yaml 文件中有什么错误？
看来我无法让 fail2ban 工作。
我已经启动并运行 ufw，状态如下：
~$ sudo ufw status
Status: active
To Action From
-- ------ ----
25/tcp ALLOW Anywhere
2278/tcp ALLOW Anywhere
80,143,443,465,587,993/tcp ALLOW Anywhere
110,995/tcp ALLOW Anywhere
80/tcp ALLOW Anywhere
22/tcp DENY Anywhere
25/tcp (v6) ALLOW Anywhere (v6)
2278/tcp (v6) ALLOW Anywhere (v6)
80,143,443,465,587,993/tcp (v6) ALLOW Anywhere (v6)
110,995/tcp (v6) ALLOW Anywhere (v6)
80/tcp (v6) ALLOW Anywhere (v6)
22/tcp (v6) DENY Anywhere (v6)
我没有对jail.conf文件做任何更改，只是创建了一个jail.local文件。
/etc/fail2ban/jail.local
[DEFAULT]
ignoreip = 127.0.0.1/8 ::1/128
[sshd]
#mode = normal
enabled = true
bantime = 1h
port = 2278
filter = sshd
logpath = /var/log/auth.log
maxretry = 5
[postfix]
enabled = true
bantime = 1h
mode = more
port = smtp,465,submission
filter = postfix
logpath = /var/log/mail.log
[postfix-sasl]
enabled = true
bantime = 1h
maxretry = 5
filter = postfix[mode=auth]
port = smtp,465,submission,imap,imaps,pop3,pop3s
logpath = /var/log/mail.log
~$ sudo fail2ban-client status
Status
|- Number of jail: 3
`- Jail list: postfix, postfix-sasl, sshd
~$ sudo fail2ban-client status postfix
Status for the jail: postfix
|- Filter
| |- Currently failed: 0
| |- Total failed: 0
| `- Journal matches: _SYSTEMD_UNIT=postfix.service
`- Actions
|- Currently banned: 0
|- Total banned: 0
`- Banned IP list:
我手动禁止了一个 IP：
~$ sudo fail2ban-client -vvv set postfix banip 1.2.3.4
+ 32 743F3BD1E080 fail2ban.configreader INFO Loading configs for fail2ban under /etc/fail2ban
+ 32 743F3BD1E080 fail2ban.configreader DEBUG Reading configs for fail2ban under /etc/fail2ban
+ 33 743F3BD1E080 fail2ban.configreader DEBUG Reading config files: /etc/fail2ban/fail2ban.conf
+ 33 743F3BD1E080 fail2ban.configparserinc INFO Loading files: ['/etc/fail2ban/fail2ban.conf']
+ 33 743F3BD1E080 fail2ban.configparserinc TRACE Reading file: /etc/fail2ban/fail2ban.conf
+ 33 743F3BD1E080 fail2ban.configparserinc INFO Loading files: ['/etc/fail2ban/fail2ban.conf']
+ 33 743F3BD1E080 fail2ban.configparserinc TRACE Shared file: /etc/fail2ban/fail2ban.conf
+ 34 743F3BD1E080 fail2ban INFO Using socket file /var/run/fail2ban/fail2ban.sock
+ 34 743F3BD1E080 fail2ban INFO Using pid file /var/run/fail2ban/fail2ban.pid, [INFO] logging to /var/log/fail2ban.log
+ 34 743F3BD1E080 fail2ban HEAVY CMD: ['set', 'postfix', 'banip', '1.2.3.4']
+ 73 743F3BD1E080 fail2ban HEAVY OK : 1
+ 73 743F3BD1E080 fail2ban.beautifier HEAVY Beautify 1 with ['set', 'postfix', 'banip', '1.2.3.4']
1
+ 73 743F3BD1E080 fail2ban DEBUG Exit with code 0
命令iptables -nL没有显示该IP已经被fail2ban禁止：
~$ sudo iptables -nL
Chain INPUT (policy DROP)
target prot opt source destination
ufw-before-logging-input 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-before-input 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-after-input 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-after-logging-input 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-reject-input 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-track-input 0 -- 0.0.0.0/0 0.0.0.0/0
Chain FORWARD (policy DROP)
target prot opt source destination
ufw-before-logging-forward 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-before-forward 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-after-forward 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-after-logging-forward 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-reject-forward 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-track-forward 0 -- 0.0.0.0/0 0.0.0.0/0
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ufw-before-logging-output 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-before-output 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-after-output 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-after-logging-output 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-reject-output 0 -- 0.0.0.0/0 0.0.0.0/0
ufw-track-output 0 -- 0.0.0.0/0 0.0.0.0/0
Chain ufw-after-forward (1 references)
target prot opt source destination
Chain ufw-after-input (1 references)
target prot opt source destination
ufw-skip-to-policy-input 17 -- 0.0.0.0/0 0.0.0.0/0 udp dpt:137
ufw-skip-to-policy-input 17 -- 0.0.0.0/0 0.0.0.0/0 udp dpt:138
ufw-skip-to-policy-input 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:139
ufw-skip-to-policy-input 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:445
ufw-skip-to-policy-input 17 -- 0.0.0.0/0 0.0.0.0/0 udp dpt:67
ufw-skip-to-policy-input 17 -- 0.0.0.0/0 0.0.0.0/0 udp dpt:68
ufw-skip-to-policy-input 0 -- 0.0.0.0/0 0.0.0.0/0 ADDRTYPE match dst-type BROADCAST
Chain ufw-after-logging-forward (1 references)
target prot opt source destination
LOG 0 -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 10 LOG flags 0 level 4 prefix "[UFW BLOCK] "
Chain ufw-after-logging-input (1 references)
target prot opt source destination
LOG 0 -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 10 LOG flags 0 level 4 prefix "[UFW BLOCK] "
Chain ufw-after-logging-output (1 references)
target prot opt source destination
LOG 0 -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 10 LOG flags 0 level 4 prefix "[UFW ALLOW] "
Chain ufw-after-output (1 references)
target prot opt source destination
Chain ufw-before-forward (1 references)
target prot opt source destination
ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED
ACCEPT 1 -- 0.0.0.0/0 0.0.0.0/0 icmptype 3
ACCEPT 1 -- 0.0.0.0/0 0.0.0.0/0 icmptype 11
ACCEPT 1 -- 0.0.0.0/0 0.0.0.0/0 icmptype 12
ACCEPT 1 -- 0.0.0.0/0 0.0.0.0/0 icmptype 8
ufw-user-forward 0 -- 0.0.0.0/0 0.0.0.0/0
Chain ufw-before-input (1 references)
target prot opt source destination
ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0
ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED
ufw-logging-deny 0 -- 0.0.0.0/0 0.0.0.0/0 ctstate INVALID
DROP 0 -- 0.0.0.0/0 0.0.0.0/0 ctstate INVALID
ACCEPT 1 -- 0.0.0.0/0 0.0.0.0/0 icmptype 3
ACCEPT 1 -- 0.0.0.0/0 0.0.0.0/0 icmptype 11
ACCEPT 1 -- 0.0.0.0/0 0.0.0.0/0 icmptype 12
ACCEPT 1 -- 0.0.0.0/0 0.0.0.0/0 icmptype 8
ACCEPT 17 -- 0.0.0.0/0 0.0.0.0/0 udp spt:67 dpt:68
ufw-not-local 0 -- 0.0.0.0/0 0.0.0.0/0
ACCEPT 17 -- 0.0.0.0/0 224.0.0.251 udp dpt:5353
ACCEPT 17 -- 0.0.0.0/0 239.255.255.250 udp dpt:1900
ufw-user-input 0 -- 0.0.0.0/0 0.0.0.0/0
Chain ufw-before-logging-forward (1 references)
target prot opt source destination
LOG 0 -- 0.0.0.0/0 0.0.0.0/0 ctstate NEW limit: avg 3/min burst 10 LOG flags 0 level 4 prefix "[UFW AUDIT] "
Chain ufw-before-logging-input (1 references)
target prot opt source destination
LOG 0 -- 0.0.0.0/0 0.0.0.0/0 ctstate NEW limit: avg 3/min burst 10 LOG flags 0 level 4 prefix "[UFW AUDIT] "
Chain ufw-before-logging-output (1 references)
target prot opt source destination
LOG 0 -- 0.0.0.0/0 0.0.0.0/0 ctstate NEW limit: avg 3/min burst 10 LOG flags 0 level 4 prefix "[UFW AUDIT] "
Chain ufw-before-output (1 references)
target prot opt source destination
ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0
ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED
ufw-user-output 0 -- 0.0.0.0/0 0.0.0.0/0
Chain ufw-logging-allow (0 references)
target prot opt source destination
LOG 0 -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 10 LOG flags 0 level 4 prefix "[UFW ALLOW] "
Chain ufw-logging-deny (2 references)
target prot opt source destination
LOG 0 -- 0.0.0.0/0 0.0.0.0/0 ctstate INVALID limit: avg 3/min burst 10 LOG flags 0 level 4 prefix "[UFW AUDIT INVALID] "
LOG 0 -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 10 LOG flags 0 level 4 prefix "[UFW BLOCK] "
Chain ufw-not-local (1 references)
target prot opt source destination
RETURN 0 -- 0.0.0.0/0 0.0.0.0/0 ADDRTYPE match dst-type LOCAL
RETURN 0 -- 0.0.0.0/0 0.0.0.0/0 ADDRTYPE match dst-type MULTICAST
RETURN 0 -- 0.0.0.0/0 0.0.0.0/0 ADDRTYPE match dst-type BROADCAST
ufw-logging-deny 0 -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 10
DROP 0 -- 0.0.0.0/0 0.0.0.0/0
Chain ufw-reject-forward (1 references)
target prot opt source destination
Chain ufw-reject-input (1 references)
target prot opt source destination
Chain ufw-reject-output (1 references)
target prot opt source destination
Chain ufw-skip-to-policy-forward (0 references)
target prot opt source destination
DROP 0 -- 0.0.0.0/0 0.0.0.0/0
Chain ufw-skip-to-policy-input (7 references)
target prot opt source destination
DROP 0 -- 0.0.0.0/0 0.0.0.0/0
Chain ufw-skip-to-policy-output (0 references)
target prot opt source destination
ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0
Chain ufw-track-forward (1 references)
target prot opt source destination
Chain ufw-track-input (1 references)
target prot opt source destination
Chain ufw-track-output (1 references)
target prot opt source destination
ACCEPT 6 -- 0.0.0.0/0 0.0.0.0/0 ctstate NEW
ACCEPT 17 -- 0.0.0.0/0 0.0.0.0/0 ctstate NEW
Chain ufw-user-forward (1 references)
target prot opt source destination
Chain ufw-user-input (1 references)
target prot opt source destination
ACCEPT 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:25
ACCEPT 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:2278
ACCEPT 6 -- 0.0.0.0/0 0.0.0.0/0 multiport dports 80,143,443,465,587,993
ACCEPT 6 -- 0.0.0.0/0 0.0.0.0/0 multiport dports 110,995
ACCEPT 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:80
DROP 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22
Chain ufw-user-limit (0 references)
target prot opt source destination
LOG 0 -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 5 LOG flags 0 level 4 prefix "[UFW LIMIT BLOCK] "
REJECT 0 -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable
Chain ufw-user-limit-accept (0 references)
target prot opt source destination
ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0
Chain ufw-user-logging-forward (0 references)
target prot opt source destination
Chain ufw-user-logging-input (0 references)
target prot opt source destination
Chain ufw-user-logging-output (0 references)
target prot opt source destination
Chain ufw-user-output (1 references)
target prot opt source destination
Fail2ban 服务正在运行。
~$ sudo systemctl status fail2ban.service
● fail2ban.service - Fail2Ban Service
Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; preset: enabled)
Active: active (running) since Tue 2024-11-12 21:09:28 CET; 1h 6min ago
Docs: man:fail2ban(1)
Main PID: 1001 (fail2ban-server)
Tasks: 9 (limit: 4556)
Memory: 49.7M (peak: 53.2M)
CPU: 10.557s
CGroup: /system.slice/fail2ban.service
└─1001 /usr/bin/python3 /usr/bin/fail2ban-server -xf start
Nov 12 21:09:28 crosis systemd[1]: Started fail2ban.service - Fail2Ban Service.
Nov 12 21:09:29 crosis fail2ban-server[1001]: 2024-11-12 21:09:29,352 fail2ban.configreader [1001]: WARNING 'allowipv6' not defined in 'Definition'. Using default one: 'auto'
Nov 12 21:09:30 crosis fail2ban-server[1001]: Server ready
我是不是漏掉了什么？我是不是做错了什么？
我有一个网站的两个存储库：一个用于后端，一个用于前端。我想将文件从前端复制到后端目录，以便所有内容都可以从一个地方提供。
当我build在前端运行命令时，dist/会创建一个名为的文件夹。我想将所有这些文件复制到具有相对路径的文件夹中../backend/public。此public文件夹可能已经包含一些其他文件。
index.html我当前的脚本使用和和目录的硬编码名称assets/，但随着时间的推移可能会添加更多文件，因此我想要一个通用的解决方案，将所有未改变的内容复制到dist/中../backend/public。
#!/bin/bash
cd ../backend/public
rm -rf index.html assets
cp ../../frontend/dist/index.html ./
cp -r ../../frontend/dist/assets ./assets