主页 / user-62551

supmethods's questions

Martin Hope
supmethods
Asked: 2024-07-01 10:27:26 +0800 CST
  • 5

我正在尝试分析 systemd 进程的核心转储文件，但由于缺少符号而遇到错误。

有人可以建议需要安装哪些调试符号才能成功分析这些核心转储吗？

gdb  -e /usr/lib/systemd/systemd-journald -c core-systemd-journal--0-0-657-1718434887
GNU gdb (GDB) Red Hat Enterprise Linux 8.2-20.el8
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".

warning: core file may not match specified executable file.
[New LWP 657]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Missing separate debuginfo for /lib64/libuuid.so.1
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/d0/43572678e11cfb56aecb4ec534bc016de8d0d5.debug
Missing separate debuginfo for /lib64/libudev.so.1
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/94/5e15d6b231fc346823186cd70e886dede771ca.debug
Core was generated by `/usr/lib/systemd/systemd-journald'.
Program terminated with signal SIGABRT, Aborted.
crash
Martin Hope
supmethods
Asked: 2023-10-12 00:00:10 +0800 CST
  • 5

我想在sudo su test -c [command].

当我运行以下命令时，我得到的r1rnrnrnrrnr不是\r1\r\n\r\n\r\n\r\r\n\r：

SET_TEST_MSG='\r1\r\n\r\n\r\n\r\r\n\r'
sudo su test -c "/usr/bin/screen -dmS test bash -c \"echo $SET_TEST_MSG; exec bash\""
$PROG -n $PICKVM 0 -1 -d "$SET_TEST_MSG"

运行时如何保留反斜杠sudo su test -c [command]？

bash
Martin Hope
supmethods
Asked: 2023-07-06 16:36:29 +0800 CST
  • 5

我已经安装了用于 Windows 应用程序模拟的 Bottles。

我试图通过命令行启动应用程序，但无法自动启动应用程序。它打开了瓶子，但应用程序没有启动，需要手动启动。

我想让它工作，这样我就可以创建一个 systemd 服务，在系统启动时启动这个应用程序。操作系统是AlmaLinux 8。

这是我尝试过的命令的变体。

flatpak run com.usebottles.bottles -b NetSync -e 'C:\windows\system32\start.exe /wait C:\Program Files (x86)\BigNet\NetSync\NetSync.exe'
flatpak run com.usebottles.bottles -b NetSync -e 'C:\Program Files (x86)\BigNet\NetSync\NetSync.exe'
flatpak run com.usebottles.bottles -b NetSync -e '/home/rlee/.var/app/com.usebottles.bottles/data/bottles/bottles/NetSync/drive_c/Program Files (x86)/BigNet/NetSync/NetSync.exe'
flatpak run com.usebottles.bottles -b NetSync -e /home/rlee/.var/app/com.usebottles.bottles/data/bottles/bottles/NetSync/drive_c/Program\ Files\ \(x86\)/BigNet/NetSync/NetSync.exe
wine
Martin Hope
supmethods
Asked: 2023-01-25 04:10:54 +0800 CST
  • 5

通过执行以下操作打开 GNOME 终端后，我设法通过 SSH 连接到远程主机：

gnome-terminal -- bash -c "ssh -i ~/.ssh/virtual_machines remote@remotehost; exec bash;"

但是，一旦我通过 SSH 连接到远程主机，我想通过执行sudo su test. 我已经在 visudo 中添加了命令：

%wheel  ALL=(ALL)       NOPASSWD:/bin/su test

一旦我切换到测试，测试用户将启动一个程序并留在该程序上。

修改 .bashrc 文件不是一个选项，因为我也作为该用户使用 SSH，并且不希望程序自动启动。

ssh
Martin Hope
supmethods
Asked: 2022-07-12 15:47:13 +0800 CST
  • 0

我收到错误消息“日志提交 I/O 错误”。这是什么意思？

journal commit I/O error
EXT4-fs error (device sdb1): ext4_put_super: Couldn't clean up the journal
EXT4-fs (sdb1): Remounting filesystem read-only
EXT4-fs (sdc1): warning: checktime reached, running e2fsck is recommended
EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts:
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
session_init(service_process,82169): OK. kdev=8:3, bs=4096.
register_make_request(service_process,82169): OK. kdev=8:3, mq=0.
session_init(service_process,82169): OK. kdev=fd:1, bs=4096.
register_make_request(service_process,82169): OK. kdev=fd:1, mq=0.

当我执行 lsblk 时，我找不到 /dev/sdb。这是否意味着发生了某些事情并且 /dev/sdb 现在失败了？

linux
Martin Hope
supmethods
Asked: 2022-07-11 04:23:14 +0800 CST
  • 0

我正在尝试将电子邮件中继到 Office 365，并已将后缀配置如下：

meta_directory = /etc/postfix
shlib_directory = /usr/lib64/postfix
myhostname = mail.disorderly-order.com
mydomain = disorderly-order.com
myorigin = $mydomain
mynetworks = 127.0.0.0/8, 10.10.0.0/16
smtp_generic_maps = hash:/etc/postfix/generic
relayhost = disorderlyorder-com02e.mail.protection.outlook.com

我已按照此网站上的说明设置连接器：http: //kb.eclipseinc.com/kb/postfix-relay-office365/。我已将 relayhost 设置为 disorderlyorder-com02e.mail.protection.outlook.com，这是 MX 记录的值。

当我发送邮件时，什么都没有通过。下面是我的 journalctl 日志。我可以看到它向 [email protected] 发送电子邮件，但我没有向该地址发送任何电子邮件。我只向 [email protected] 发送了电子邮件。

Jul 10 22:04:40 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: 27A0D10136330: from=<[email protected]>, size=488, nrcpt=1 (queue active)
Jul 10 22:04:40 vxmail.livedemo.vdevops.info postfix/smtp[740108]: 27A0D10136330: to=<[email protected]>, relay=disorderlyorder-com02e.mail.protection.outlook.com[104.47.71.202]:>
Jul 10 22:04:40 vxmail.livedemo.vdevops.info postfix/cleanup[740106]: F0E0510136331: message-id=<[email protected]>
Jul 10 22:04:40 vxmail.livedemo.vdevops.info postfix/bounce[740109]: 27A0D10136330: sender non-delivery notification: F0E0510136331
Jul 10 22:04:40 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: F0E0510136331: from=<>, size=3299, nrcpt=1 (queue active)
Jul 10 22:04:40 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: 27A0D10136330: removed
Jul 10 22:04:41 vxmail.livedemo.vdevops.info postfix/smtp[740108]: F0E0510136331: to=<[email protected]>, relay=disorderlyorder-com02e.mail.protection.outlook.com[104.47.71.138]:>
Jul 10 22:04:41 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: F0E0510136331: removed
Jul 10 22:05:26 vxmail.livedemo.vdevops.info postfix/pickup[740098]: 62B9C10136330: uid=0 from=<root>
Jul 10 22:05:26 vxmail.livedemo.vdevops.info postfix/cleanup[740106]: 62B9C10136330: message-id=<[email protected]>
Jul 10 22:05:26 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: 62B9C10136330: from=<[email protected]>, size=910, nrcpt=1 (queue active)
Jul 10 22:05:26 vxmail.livedemo.vdevops.info postfix/smtp[740108]: 62B9C10136330: to=<[email protected]>, orig_to=<root>, relay=disorderlyorder-com02e.mail.protection.outlook.com>
Jul 10 22:05:27 vxmail.livedemo.vdevops.info postfix/cleanup[740106]: 0DCAC10136331: message-id=<[email protected]>
Jul 10 22:05:27 vxmail.livedemo.vdevops.info postfix/bounce[740109]: 62B9C10136330: sender non-delivery notification: 0DCAC10136331
Jul 10 22:05:27 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: 0DCAC10136331: from=<>, size=3626, nrcpt=1 (queue active)
Jul 10 22:05:27 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: 62B9C10136330: removed
Jul 10 22:05:27 vxmail.livedemo.vdevops.info postfix/smtp[740108]: 0DCAC10136331: to=<[email protected]>, relay=disorderlyorder-com02e.mail.protection.outlook.com[104.47.71.202]:>
Jul 10 22:05:27 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: 0DCAC10136331: removed
Jul 10 22:06:26 vxmail.livedemo.vdevops.info postfix/pickup[740098]: 77AA310136330: uid=0 from=<root>
Jul 10 22:06:26 vxmail.livedemo.vdevops.info postfix/cleanup[740106]: 77AA310136330: message-id=<[email protected]>
Jul 10 22:06:26 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: 77AA310136330: from=<[email protected]>, size=910, nrcpt=1 (queue active)
Jul 10 22:06:27 vxmail.livedemo.vdevops.info postfix/smtp[740108]: 77AA310136330: to=<[email protected]>, orig_to=<root>, relay=disorderlyorder-com02e.mail.protection.outlook.com>
Jul 10 22:06:27 vxmail.livedemo.vdevops.info postfix/cleanup[740106]: 233FA10136331: message-id=<[email protected]>
Jul 10 22:06:27 vxmail.livedemo.vdevops.info postfix/bounce[740109]: 77AA310136330: sender non-delivery notification: 233FA10136331
Jul 10 22:06:27 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: 233FA10136331: from=<>, size=3626, nrcpt=1 (queue active)
Jul 10 22:06:27 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: 77AA310136330: removed
Jul 10 22:06:27 vxmail.livedemo.vdevops.info postfix/smtp[740108]: 233FA10136331: to=<[email protected]>, relay=disorderlyorder-com02e.mail.protection.outlook.com[104.47.71.202]:>
Jul 10 22:06:27 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: 233FA10136331: removed
Jul 10 22:07:26 vxmail.livedemo.vdevops.info postfix/pickup[740098]: 853A310136330: uid=0 from=<root>
Jul 10 22:07:26 vxmail.livedemo.vdevops.info postfix/cleanup[740106]: 853A310136330: message-id=<[email protected]>
Jul 10 22:07:26 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: 853A310136330: from=<[email protected]>, size=910, nrcpt=1 (queue active)
Jul 10 22:07:27 vxmail.livedemo.vdevops.info postfix/smtp[740108]: 853A310136330: to=<[email protected]>, orig_to=<root>, relay=disorderlyorder-com02e.mail.protection.outlook.com>
Jul 10 22:07:27 vxmail.livedemo.vdevops.info postfix/cleanup[740106]: 2F6B810136331: message-id=<[email protected]>
Jul 10 22:07:27 vxmail.livedemo.vdevops.info postfix/bounce[740109]: 853A310136330: sender non-delivery notification: 2F6B810136331
Jul 10 22:07:27 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: 2F6B810136331: from=<>, size=3626, nrcpt=1 (queue active)
Jul 10 22:07:27 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: 853A310136330: removed
Jul 10 22:07:27 vxmail.livedemo.vdevops.info postfix/smtp[740108]: 2F6B810136331: to=<[email protected]>, relay=disorderlyorder-com02e.mail.protection.outlook.com[104.47.71.202]:>
Jul 10 22:07:27 vxmail.livedemo.vdevops.info postfix/qmgr[740099]: 2F6B810136331: removed

我还尝试为 root 用户创建到有效电子邮件地址的映射。它不起作用，因为我仍然可以在 journalctl 中看到发件人为 [email protected]。这就是我所做的。

将以下行添加到 /etc/postfix/main.cf：

smtp_generic_maps = hash:/etc/postfix/generic

将所需的电子邮件地址别名添加到 /etc/postfix/generic：

root [email protected]

创建哈希文件并重新加载后缀：

postmap /etc/postfix/generic
service postfix reload
linux postfix
Martin Hope
supmethods
Asked: 2018-10-13 03:12:23 +0800 CST
  • 1

至于这段代码片段：

AM_MAINTAINER_MODE
if test "x$enable_maintainer_mode" = xyes; then
    AC_PATH_PROG(PERL,perl)
    if test -z "$PERL"; then
        AC_MSG_ERROR([perl not found])
    fi
fi

# This should be checked before AC_PROG_CC
if test "x$CFLAGS" = x; then
    default_CFLAGS=yes
fi

if test "x$host_cpu" = xx86_64; then
    CFLAGS="-m32 $CFLAGS"
fi

我找不到有关正在测试的三个变量（x$enable_maintainer_mode、x$CFLAGS、x$host_cpu）的任何信息。这些变量是在执行宏 AM_MAINTAINER_MODE 后生成的吗？如果是这样，我在哪里可以找到有关它们的更多信息？

另外，AM_MAINTAINER_MODE 模式的目的是什么？

据我了解，默认情况下它是禁用的：

  • 如果用户运行“配置”并且不满足所有依赖项（Automake 版本、工具、库等），它将终止并且不会继续进行。
  • 如果用户运行“configure”并且满足所有依赖项，它将创建并运行生成“make”文件的 config.status 脚本
  • 用户可以使用 –enable-maintainer-mode 选项覆盖此设置。这将允许他们修改不同的 Autotool 文件（例如 configure.ac、Makefile.am），并且构建系统将尝试重新生成需要更新的文件以反映这些更改（Autotools 将查找任何过时的文件并更新它们因此）。

我明白为什么禁用此模式可能更可取。您为什么要启用此功能的任何原因？

autotools
Martin Hope
supmethods
Asked: 2018-10-04 17:30:27 +0800 CST
  • 4

我正在尝试理解以下代码片段。

host_cpu='i386'

case "$host_cpu" in
   i[[3456]]86)
       echo "host_cpu=i386"
   ;;
   x86_64)
       echo "host_cpu=x86_64"
   ;;
   *)
       echo "AC_MSG_ERROR([unsupported CPU type]) "
   ;;
esac

我自己添加了变量host_cpu='i386'来测试代码，它切换到第三种情况echo "AC_MSG_ERROR([unsupported CPU type]) "。

如果我将双括号更改i[[3456]]86)为单括号，如i[3456]86)，它将切换到第一个选项 yielding i386。这对我来说似乎是正确的。

我理解这一点，[并且[[是测试选项。测试条件似乎不适用于这里，因为切换案例期望输出一个字符。所以我假设 bash 将其作为测试条件，它需要用空格分隔，如[ a < b ]or [[ a << b ]]。因为这些 case 语句中没有空格，所以会被当作正则表达式处理。这个对吗？

所以我的问题是为什么代码编写者在这里使用了方括号？当我尝试运行代码时它不起作用，所以他们的意图是什么。

注意：代码取自configure.acGRUB 源代码中的 a。

另外 $host_cpu 和 host_cpu=i386 行似乎没有必要，你能解释一下为什么作者会这样做：

AC_CANONICAL_HOST

case "$host_cpu" in
    i[[3456]]86) host_cpu=i386 ;;
    x86_64) host_cpu=x86_64 ;;
    *) AC_MSG_ERROR([unsupported CPU type]) ;;
esac

AC_SUBST(host_cpu)
AC_SUBST(host_vendor)

我正在考虑使用 AC_SUBST($host_cpu)。你为什么不这样做呢？

bash shell