主页 / user-908977

Ray Butterworth's questions

Martin Hope
Ray Butterworth
Asked: 2024-07-24 07:45:47 +0800 CST
  • 12

安全摄像头中的 µSD 卡突然停止录制：

  • 大部分数据都消失了（没问题）。
  • 仍然存在的数据是正确且可读的。
  • 该卡现在始终以只读方式安装（在 Chromebook、Windows 和 Ubuntu 上）。

我无法重新格式化它或用它做任何事情：

$ df
/dev/mmcblk0   vfat          117G   15G      102G  13% /media/ray/xxx

$ sudo fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 116.1 GiB, 124657860608 bytes, 243472384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

$ sudo fsck /dev/mmcblk0
fsck from util-linux 2.34
fsck.fat 4.1 (2017-01-24)
open: Read-only file system

$ sudo hdparm -r0 /dev/mmcblk0
/dev/mmcblk0:
 setting readonly to 0 (off)
 readonly      =  1 (on)
$ sudo hdparm -r0 /dev/mmcblk0
/dev/mmcblk0:
 setting readonly to 0 (off)
 readonly      =  1 (on)

$ sudo fsck /dev/mmcblk0
fsck from util-linux 2.34
fsck.fat 4.1 (2017-01-24)
open: Read-only file system

$ sudo umount /media/ray/xxx
$ sudo mount  -o rw  /dev/mmcblk0  /media/ray/xxx
mount: /media/ray/xxx: WARNING: device write-protected, mounted read-only.

请注意，这不是全尺寸的 SD 卡；没有物理写保护开关。

这张卡可以回收吗，还是垃圾？

read-only
Martin Hope
Ray Butterworth
Asked: 2023-06-18 11:27:07 +0800 CST
  • 6

$ od -t x1 <inputfile产生… 0a e2 8c a5 0a ….

它们0a是换行符，并且e2 8c a5是 Unicode 字符的 UTF-8 表示形式。

对于这个简单的情况，我可以手动完成：

[1110]0010  [10]001100  [10]100101  =  10  0011  0010  0101 = 2 3 2 5

e2 8c a5或可以转换e28ca5成什么 shell 命令行2325？

（为了完整起见，了解其他方式转换也很好。）

command-line
Martin Hope
Ray Butterworth
Asked: 2022-09-24 09:00:33 +0800 CST
  • 0

这是11.04 - UPNP 媒体服务器的副本？- 问 Ubuntu，但它的答案已经有十多年的历史了。

具体来说，我们目前有一台带有 WMP 的 Windows 笔记本电脑，作为 Yamaha RX-A780 接收器（和其他设备）的服务器。配置就像单击按钮以允许共享一样简单，但响应速度可能很慢（而且我更喜欢不使用 Windows）。

相反，我希望我的 Ubuntu 桌面成为大型/data/Music目录的音乐服务器。

我试过kodi了，它可以工作，但是：Tour - Software Recommendations Stack Exchange

  • 这是巨大的矫枉过正（我不需要电影，游戏，天气预报等）
  • 它的图形界面不直观。
  • 如何在我不想要的所有其他部分中找到我想要的特定部分并不明显。

更重要的是：

  • 它每天 24 小时持续消耗我 10% 的 CPU，即使在不使用时也是如此。
  • 当新专辑添加到目录时，它不会自动通知。

Ubuntu 是否有一些更轻量级的东西，除了在请求时提供音乐之外没有做更多的事情？

笔记：

从那以后，我注意到有一个Software Recommendations Stack Exchange站点。
那对我来说是一个更合适的地方问这个问题。

server
Martin Hope
Ray Butterworth
Asked: 2020-11-16 10:52:22 +0800 CST
  • 3

每当我登录（或解锁密码屏幕）最近安装的 20.04 系统时，/var/log/syslog报告它正在启动指纹验证守护进程：

…
Nov 15 13:29:28 ray-desktop dbus-daemon[528]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.193' (uid=1000 pid=8276 comm="/usr/bin/gnome-shell " label="unconfined")
Nov 15 13:29:28 ray-desktop systemd[1]: Starting Fingerprint Authentication Daemon...
Nov 15 13:29:28 ray-desktop dbus-daemon[528]: [system] Successfully activated service 'net.reactivated.Fprint'
Nov 15 13:29:28 ray-desktop systemd[1]: Started Fingerprint Authentication Daemon.
Nov 15 13:29:29 ray-desktop NetworkManager[86471]: <info>  [1605464969.2480] agent-manager: agent[5d99141cf1aa3382,:1.193/org.gnome.Shell.NetworkAgent/1000]: agent registered
Nov 15 13:29:29 ray-desktop dbus-daemon[8052]: [session uid=1000 pid=8052] Activating service name='org.freedesktop.FileManager1' requested by ':1.42' (uid=1000 pid=8276 comm="/usr/bin/gnome-shell " label="unconfined")
Nov 15 13:29:29 ray-desktop dbus-daemon[8052]: [session uid=1000 pid=8052] Activating service name='org.gnome.Nautilus' requested by ':1.42' (uid=1000 pid=8276 comm="/usr/bin/gnome-shell " label="unconfined")
Nov 15 13:29:29 ray-desktop dbus-daemon[8052]: [session uid=1000 pid=8052] Successfully activated service 'org.gnome.Nautilus'
Nov 15 13:29:29 ray-desktop org.gnome.Nautilus[132137]: Failed to register: Unable to acquire bus name 'org.gnome.Nautilus'
Nov 15 13:29:29 ray-desktop dbus-daemon[8052]: [session uid=1000 pid=8052] Successfully activated service 'org.freedesktop.FileManager1'
…
Nov 15 13:29:58 ray-desktop systemd[1]: fprintd.service: Succeeded.
…

这是一台没有指纹硬件的台式机，为什么要运行守护进程呢？

更重要的是，如何告诉系统不要这样做？

login authentication services
Martin Hope
Ray Butterworth
Asked: 2019-09-01 10:04:08 +0800 CST
  • 0

ras-mc-ctl --errors报告结果如下：

661 2019-08-20 08:42:29 -0400 错误：更正过滤（同一区域中的一些未报告的错误） Generic CACHE Level-3 Generic Error, mcg mcgstatus=0, mci Corrected_error 基于阈值的错误状态：黄色，mcgcap=0x00000c09 ，状态=0x8c400c400001110b，地址=0x3334c0000080b06，杂项=0x00b501c0，tsc=0x3c6571e2bbea4，walltime=0x5d5beab4，cpuid=0x000806e9，银行=0x00000008

更频繁地：

728 2019-08-31 13:35:59 -0400 错误：更正过滤（同一区域中的一些未报告的错误）Generic CACHE Level-3 Generic Error, mcg mcgstatus=0, mci Corrected_error 基于阈值的错误状态：绿色，大量更正了缓存错误。系统运行，但可能很快会导致未更正的错误，mcgcap=0x00000c09，status=0x8c2000c00001110b，addr=0x2b6b100000374cf，misc=0x0001bdc0，tsc=0x376c4b0d8828，walltime=0x5d6aafff，cpuid=009bank=x

这些消息实际上意味着什么，人们可以/应该对它们做什么？

附加信息：

  • 这是一款英特尔 NUC 7i7BNH，配备 16 Gb 内存、500G SSD 和 4K 显示器。
  • 它运行 Ubuntu 18.0，最近有“apt upgrade”。
  • BIOS 已更新到最近的 7 月版本。
  • 我没有进行任何硬件修改。

lshw -C memory显示：

*-firmware                
    description: BIOS
    vendor: Intel Corp.
    physical id: 0
    version: BNKBL357.86A.0080.2019.0725.1139
    date: 07/25/2019
    size: 64KiB
    capacity: 8128KiB
    capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int14serial int17printer acpi usb biosbootspecification uefi
*-memory
    description: System Memory
    physical id: 28
    slot: System board or motherboard
    size: 16GiB
    *-bank:0
        description: SODIMM DDR4 Synchronous Unbuffered (Unregistered) 2133 MHz (0.5 ns)
        product: CMSO16GX4M1A2133C15
        vendor: AMI
        physical id: 0
        serial: 00000000
        slot: ChannelA-DIMM0
        size: 16GiB
        width: 64 bits
        clock: 2133MHz (0.5ns)
    *-bank:1
        description: [empty]
        physical id: 1
        slot: ChannelB-DIMM0
*-cache:0
    description: L1 cache
    physical id: 2d
    slot: L1 Cache
    size: 128KiB
    capacity: 128KiB
    capabilities: synchronous internal write-back unified
    configuration: level=1
*-cache:1
    description: L2 cache
    physical id: 2e
    slot: L2 Cache
    size: 512KiB
    capacity: 512KiB
    capabilities: synchronous internal write-back unified
    configuration: level=2
*-cache:2
    description: L3 cache
    physical id: 2f
    slot: L3 Cache
    size: 4MiB
    capacity: 4MiB
    capabilities: synchronous internal write-back unified
    configuration: level=3
*-memory UNCLAIMED
    description: Memory controller
    product: Sunrise Point-LP PMC
    vendor: Intel Corporation
    physical id: 1f.2
    bus info: pci@0000:00:1f.2
    version: 21
    width: 32 bits
    clock: 33MHz (30.3ns)
    capabilities: bus_master
    configuration: latency=0
    resources: memory:dc244000-dc247fff

试验结果：

运行 memtest86 产生了一些有趣的结果：

  • 大约 5 分钟后，它显示 Intel 徽标并重新启动。
  • 同样的事情再次发生，但我设法先记录了大部分消息。
  • 第三次，它完成了一次完整的传球（大约 45 分钟），然后在第二次传球几分钟后再次坠毁。
  • 我会让它继续运行，但我怀疑它会通过 4 次传球。

第二次尝试的结果是：

Test 4: Addr: 33090D380 Expected 08080808 Actual: 18080808 CPU:2
Test 4: Addr: 33090D38C Expected 08080808 Actual: 08080818 CPU:2
Test 4: Addr: 33090D390 Expected 08080808 Actual: [???]
Test 4: Addr: 33090D394 Expected 08080808 Actual: [???]

第三次通过了第一关，显示：

截屏

请注意，地址与上次不同（尽管两者都有 4 个错误）。

error-handling cache 18.04 logs
Martin Hope
Ray Butterworth
Asked: 2019-07-28 11:54:56 +0800 CST
  • 5

/tmp我最近通过将它添加到 /etc/fstab创建了一个 RAM ：

tmpfs /tmp tmpfs rw,nosuid,nodev,noatime   0    0

一切正常，理论上系统现在运行得更快，但在启动时 /var/log/syslog 得到：

… tmp.mount: Directory /tmp to mount over is not empty, mounting anyway.

这种情况似乎是不可避免的，因为从来没有机会从 /tmp 的文件系统版本中删除文件。

浪费的空间是微不足道的，但作为一个有趣的问题，有没有简单的方法来清除隐藏在 /tmp 挂载点下的垃圾？

tmp mountpoint
Martin Hope
Ray Butterworth
Asked: 2019-07-27 04:45:41 +0800 CST
  • 2

我的 Ubuntu 18.04 系统随机冻结几秒钟，然后重新启动。有时一两个星期没关系，有时在同一天发生两次：

=====  2019-06-27 20:58:30 -0400 Thu
=====  2019-06-28 09:31:13 -0400 Fri
=====  2019-06-29 12:39:59 -0400 Sat
=====  2019-07-02 08:45:18 -0400 Tue
=====  2019-07-07 00:11:12 -0400 Sun
=====  2019-07-10 01:18:48 -0400 Wed
=====  2019-07-10 01:23:30 -0400 Wed
=====  2019-07-18 20:42:12 -0400 Thu
=====  2019-07-22 09:23:59 -0400 Mon
=====  2019-07-22 19:47:52 -0400 Mon
=====  2019-07-22 20:50:15 -0400 Mon
=====  2019-07-23 19:30:48 -0400 Tue
=====  2019-07-24 18:48:29 -0400 Wed
=====  2019-07-25 19:52:52 -0400 Thu

今晚是在我不在家的时候发生的，所以当时它基本上什么也没做。

所有软件最近都已更新（“apt update”和“apt upgrade”）。

我一直在记录重启时的温度，它通常不是特别高。例如：

Package id 0:  +65.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +65.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +64.0°C  (high = +100.0°C, crit = +100.0°C)
temp1:         +53.0°C

它有16G的内存，所以有很多可用的。

我最近更换了存储卡，看看是否可能导致它，但更改没有效果。

/var/adm/syslog 显示很少活动，然后突然显示重新启动。

这一次，在重新启动前不久，“gsd-housekeepin”有错误消息，但情况并非总是如此。

之后 (19:49:23) 再过 3 分钟没有消息，然后在 (19:52:52) 重新启动：

...
Jul 25 19:20:34 ray-desktop org.gnome.Shell.desktop[1568]: #23 0x7ffc1c6d7730 b   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f72c84b5de0 @ 71)
Jul 25 19:20:34 ray-desktop org.gnome.Shell.desktop[1568]: #24 0x562f516643f0 i   resource:///org/gnome/shell/ui/screenShield.js:854 (0x7f72abc505e8 @ 25)
Jul 25 19:20:34 ray-desktop gnome-software[1961]: no app for changed [email protected]
Jul 25 19:20:34 ray-desktop gnome-software[1961]: no app for changed [email protected]
Jul 25 19:25:01 ray-desktop CRON[26107]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 25 19:35:01 ray-desktop CRON[26181]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 25 19:45:01 ray-desktop CRON[26247]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /var/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-rtkit-daemon.service-rOQu2D: Error opening directory '/var/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-rtkit-daemon.service-rOQu2D': Permission denied
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /var/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-colord.service-3zmTxO: Error opening directory '/var/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-colord.service-3zmTxO': Permission denied
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /var/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-fwupd.service-P4UoAn: Error opening directory '/var/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-fwupd.service-P4UoAn': Permission denied
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /var/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-bolt.service-dsge7s: Error opening directory '/var/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-bolt.service-dsge7s': Permission denied
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /var/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-ModemManager.service-1PtGCs: Error opening directory '/var/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-ModemManager.service-1PtGCs': Permission denied
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /var/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-systemd-resolved.service-vNNHBN: Error opening directory '/var/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-systemd-resolved.service-vNNHBN': Permission denied
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /var/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-systemd-timesyncd.service-ftiEu9: Error opening directory '/var/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-systemd-timesyncd.service-ftiEu9': Permission denied
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /tmp/.com.google.Chrome.deklZp: Error opening directory '/tmp/.com.google.Chrome.deklZp': Permission denied
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-bolt.service-a96unv: Error opening directory '/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-bolt.service-a96unv': Permission denied
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-systemd-resolved.service-qLTayY: Error opening directory '/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-systemd-resolved.service-qLTayY': Permission denied
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-rtkit-daemon.service-kv3biJ: Error opening directory '/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-rtkit-daemon.service-kv3biJ': Permission denied
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-ModemManager.service-EO4b7C: Error opening directory '/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-ModemManager.service-EO4b7C': Permission denied
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-systemd-timesyncd.service-awJNrk: Error opening directory '/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-systemd-timesyncd.service-awJNrk': Permission denied
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-fwupd.service-SoSJWr: Error opening directory '/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-fwupd.service-SoSJWr': Permission denied
Jul 25 19:49:23 ray-desktop gsd-housekeepin[1722]: Failed to enumerate children of /tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-colord.service-EcYRyY: Error opening directory '/tmp/systemd-private-cb9f998457344f9ea2b392c8a5517e35-colord.service-EcYRyY': Permission denied
Jul 25 19:52:52 ray-desktop systemd-modules-load[257]: Inserted module 'lp'
Jul 25 19:52:52 ray-desktop blkmapd[292]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory
Jul 25 19:52:52 ray-desktop systemd-modules-load[257]: Inserted module 'ppdev'
Jul 25 19:52:52 ray-desktop systemd-modules-load[257]: Inserted module 'parport_pc'
Jul 25 19:52:52 ray-desktop systemd-modules-load[257]: Inserted module 'coretemp'
Jul 25 19:52:52 ray-desktop systemd-sysctl[290]: Couldn't write '10' to 'sysctl vm/swappiness', ignoring: No such file or directory
Jul 25 19:52:52 ray-desktop systemd[1]: Starting Flush Journal to Persistent Storage...
Jul 25 19:52:52 ray-desktop systemd[1]: Started udev Kernel Device Manager.
Jul 25 19:52:52 ray-desktop systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Jul 25 19:52:52 ray-desktop systemd[1]: Reached target Local Encrypted Volumes.
Jul 25 19:52:52 ray-desktop systemd[1]: Started Flush Journal to Persistent Storage.
Jul 25 19:52:52 ray-desktop systemd[1]: Activated swap /swapfile.
Jul 25 19:52:52 ray-desktop systemd[1]: Reached target Swap.
Jul 25 19:52:52 ray-desktop mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.3"
Jul 25 19:52:52 ray-desktop mtp-probe: bus: 1, device: 7 was not an MTP device
Jul 25 19:52:52 ray-desktop mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.2"
Jul 25 19:52:52 ray-desktop systemd-udevd[312]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jul 25 19:52:52 ray-desktop mtp-probe: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4"
Jul 25 19:52:52 ray-desktop mtp-probe: bus: 1, device: 3 was not an MTP device
Jul 25 19:52:52 ray-desktop mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.1"
Jul 25 19:52:52 ray-desktop mtp-probe: bus: 1, device: 4 was not an MTP device
Jul 25 19:52:52 ray-desktop mtp-probe: bus: 1, device: 6 was not an MTP device
Jul 25 19:52:52 ray-desktop systemd-udevd[304]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jul 25 19:52:52 ray-desktop systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jul 25 19:52:52 ray-desktop systemd[1]: Starting Load/Save RF Kill Switch Status...
Jul 25 19:52:52 ray-desktop systemd[1]: Started Load/Save RF Kill Switch Status.
Jul 25 19:52:52 ray-desktop systemd[1]: Reached target Sound Card.
Jul 25 19:52:52 ray-desktop systemd-udevd[309]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jul 25 19:52:52 ray-desktop systemd[1]: Found device Samsung_SSD_850_EVO_500GB EFI\x20System\x20Partition.
Jul 25 19:52:52 ray-desktop systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Jul 25 19:52:52 ray-desktop systemd[1]: Reached target Local File Systems (Pre).
Jul 25 19:52:52 ray-desktop systemd[1]: Starting File System Check on /dev/disk/by-uuid/046A-4D3B...
...

知道什么可能导致这种情况，或者我可以做些什么来调查？

编辑：

它又发生了，这次完全没有冻结。

我正在打字，突然出现了启动屏幕。

syslog 在此之前的两分钟内什么也没显示：

Jul 27 22:55:01 ray-desktop CRON[6661]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 27 23:04:52 ray-desktop systemd[1]: Started Run anacron jobs.
Jul 27 23:04:52 ray-desktop anacron[6716]: Anacron 2.3 started on 2019-07-27
Jul 27 23:04:52 ray-desktop anacron[6716]: Normal exit (0 jobs run)
Jul 27 23:05:01 ray-desktop CRON[6720]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 27 23:15:01 ray-desktop CRON[6770]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 27 23:17:01 ray-desktop CRON[6784]: (root) CMD (root    cd / && run-parts --report /etc/cron.hourly)
Jul 27 23:17:01 ray-desktop CRON[6785]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jul 27 23:17:01 ray-desktop CRON[6783]: (CRON) info (No MTA installed, discarding output)
Jul 27 23:24:57 ray-desktop gnome-software[1930]: no app for changed [email protected]
Jul 27 23:24:57 ray-desktop gnome-software[1930]: no app for changed [email protected]
Jul 27 23:24:57 ray-desktop gvfsd-metadata[1586]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Jul 27 23:24:57 ray-desktop gvfsd-metadata[1586]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Jul 27 23:24:57 ray-desktop gnome-shell[1518]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.81/org/ayatana/NotificationItem/software_update_available
Jul 27 23:24:57 ray-desktop gnome-shell[1518]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.81/org/ayatana/NotificationItem/livepatch
Jul 27 23:25:01 ray-desktop CRON[6846]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 27 23:27:05 ray-desktop kernel: [    0.000000] microcode: microcode updated early to revision 0xb4, date = 2019-04-01
Jul 27 23:27:05 ray-desktop kernel: [    0.000000] Linux version 4.15.0-55-generic (buildd@lcy01-amd64-029) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 (Ubuntu 4.15.0-55.60-generic 4.15.18)
Jul 27 23:27:05 ray-desktop kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=a149eb1a-46b2-4403-b5e5-4cf8b2a1bbb9 ro quiet acpi_osi=!
Jul 27 23:27:05 ray-desktop kernel: [    0.000000] KERNEL supported cpus:
Jul 27 23:27:05 ray-desktop kernel: [    0.000000]   Intel GenuineIntel
Jul 27 23:27:05 ray-desktop kernel: [    0.000000]   AMD AuthenticAMD
Jul 27 23:27:05 ray-desktop kernel: [    0.000000]   Centaur CentaurHauls
reboot crash 18.04
Martin Hope
Ray Butterworth
Asked: 2019-01-20 18:58:23 +0800 CST
  • 1

如果我的打印机关闭，lpr仍然可以正常lpq工作，在打印队列中显示作业，如果我打开打印机，作业打印正常。

但是如果我等了几个小时，lpr表明队列是空的，我的打印作业已经消失了，所以很明显有些东西会自动删除旧的打印作业。

什么控制自动删除，我如何配置它以等待更长的时间？

printing
Martin Hope
Ray Butterworth
Asked: 2018-12-31 13:03:45 +0800 CST
  • 5
% journalctl
...
Dec 14 22:37:30 ray-desktop kernel: mce: [Hardware Error]: Machine check events logged
-- Reboot --
Dec 14 22:40:08 ray-desktop kernel: microcode: microcode updated early to revision 0x8e, date = 2018-03-24
...

/var/log/kern.log 有：

...
Dec 14 22:37:30 ray-desktop kernel: [539775.847567] mce: [Hardware Error]: Machine check events logged
Dec 14 22:40:09 ray-desktop kernel: [    0.000000] microcode: microcode updated early to revision 0x8e, date = 2018-03-24
Dec 14 22:40:09 ray-desktop kernel: [    0.000000] Linux version 4.15.0-42-generic (buildd@lgw01-amd64-023) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 (Ubuntu 4.15.0-42.45-generic 4.15.18)
...

但是 Ubuntu 18.04 没有mcelog命令或/var/log/mcelog文件。

那么事件记录在哪里？

或者更一般地说，我如何确定哪些硬件出现故障？

kernel 18.04