- Arch-general - lists.archlinux.org

[arch-general] systemd-zram generator
by Chris Murphy 17 Jan '20

17 Jan '20

Hi, swap-create@.service generator for zram devices https://github.com/systemd/zram-generator zram: Compressed RAM based block devices https://www.kernel.org/doc/Documentation/blockdev/zram.txt The gist is, if a configuration file exists, a /dev/zram0 device is created during early boot and marks it for use by swap.target; so all the existing systemd stuff to mkswap and swapon gets used. The nice thing is, very low overhead. RAM is not reserved for the device, it's only consumed as needed. The generator could be installed by default, but without a configuration file. In that case, it doesn't create a swap on zram device, unless the user creates a configuration file. And at some point, the distribution can decide to include a configuration file by default. I'm thinking a useful yet conservative default would be to create a device up to 1:1 with RAM, capping out around 2G-4G. That way small RAM devices, like Pi's, get a pretty big zram device. And large RAM devices just have a smallish swap for incidental usage. One issue (reported upstream in github) is getting priority supported. I don't know whether it needs to be configurable, from the config file. But it seems sane to have the generator set a high priority, so that the zram device is used first, spilling over to a conventional swap if the user creates ones. This is a project in rust. And I think once some of the issues get worked out, it would be great if distributions can converge on this implementation. Thanks, -- Chris Murphy

5 7

[arch-general] do i need to configure mkinitcpio.conf for my md array ?
by Shadrock Uhuru 16 Jan '20

16 Jan '20

Hi i have just configured my 4 disk raid 10 array with mdadm the filesystem is ext4 unencrypted and arch is installed on a separate disk do i need to reconfigure mkinitcpio.conf for my md array so that the array is assembled and started at boot, all the examples i've seen have arch installed on the raid array including the example in the wiki https://wiki.archlinux.org/index.php/RAID i have not reboot the new array yet so i would like to make sure everything necessary is configure before i do that. shadrock

4 3

[arch-general] Network UPS Tools (AUR) using usbhid
by David C. Rankin 13 Jan '20

13 Jan '20

Archdevs, Have there been any changes to startup that would impact the Network UPS Tools startup using the usbhid device? I ask because the nut-server.service that has worked for years, is now failing to come up in the normal boot process. $ upsc phoinix_ups Error: Driver not connected However restarting the service after the system is up and running everything works fine. So it's like there is a new depends for the usbhid driver startup that means it has to wait until something else is now started before it can initialize properly. Any idea what could be causing that or what nut-server.service needs to wait on before it tries to start? After kernel update, the failed log messages are: -- Reboot -- Jan 13 11:06:31 phoinix systemd[1]: Starting Network UPS Tools - power devices information server... Jan 13 11:06:32 phoinix upsd[541]: fopen /var/state/ups/upsd.pid: No such file or directory Jan 13 11:06:32 phoinix upsd[541]: /etc/ups/upsd.conf is world readable Jan 13 11:06:32 phoinix upsd[541]: /etc/ups/upsd.conf is world readable Jan 13 11:06:32 phoinix upsd[541]: listening on 127.0.0.1 port 3493 Jan 13 11:06:32 phoinix upsd[541]: listening on ::1 port 3493 Jan 13 11:06:32 phoinix upsd[541]: listening on 127.0.0.1 port 3493 Jan 13 11:06:32 phoinix upsd[541]: listening on ::1 port 3493 Jan 13 11:06:32 phoinix upsd[541]: Can't connect to UPS [phoinix_ups] (usbhid-ups-phoinix_ups): No such file or directory Jan 13 11:06:32 phoinix upsd[541]: Can't connect to UPS [phoinix_ups] (usbhid-ups-phoinix_ups): No such file or directory Jan 13 11:06:32 phoinix upsd[561]: Startup successful Jan 13 11:06:32 phoinix systemd[1]: Started Network UPS Tools - power devices information server. Jan 13 11:11:32 phoinix upsd[561]: Can't connect to UPS [phoinix_ups] (usbhid-ups-phoinix_ups): No such file or directory Then the restart works fine: Jan 13 11:19:20 phoinix systemd[1]: Stopped Network UPS Tools - power devices information server. Jan 13 11:19:20 phoinix systemd[1]: Starting Network UPS Tools - power devices information server... Jan 13 11:19:20 phoinix upsd[823]: fopen /var/state/ups/upsd.pid: No such file or directory Jan 13 11:19:20 phoinix upsd[823]: /etc/ups/upsd.conf is world readable Jan 13 11:19:20 phoinix upsd[823]: /etc/ups/upsd.conf is world readable Jan 13 11:19:20 phoinix upsd[823]: listening on 127.0.0.1 port 3493 Jan 13 11:19:20 phoinix upsd[823]: listening on 127.0.0.1 port 3493 Jan 13 11:19:20 phoinix upsd[823]: listening on ::1 port 3493 Jan 13 11:19:20 phoinix upsd[823]: listening on ::1 port 3493 Jan 13 11:19:20 phoinix upsd[823]: Connected to UPS [phoinix_ups]: usbhid-ups-phoinix_ups Jan 13 11:19:20 phoinix upsd[823]: Connected to UPS [phoinix_ups]: usbhid-ups-phoinix_ups Jan 13 11:19:20 phoinix upsd[824]: Startup successful Jan 13 11:19:20 phoinix systemd[1]: Started Network UPS Tools - power devices information server. Any ideas what to check? This just started within the last month or two. -- David C. Rankin, J.D.,P.E.

1 0

[arch-general] Small Monitoring Soulution
by siefke_listen＠web.de 12 Jan '20

12 Jan '20

Hello, is there a small tool which do monitoring the different server services? Checking ping, port check and that's it. More I not need and best with a static index.html create. I find cacti to overload and I hate php setup. Thank you for help Silvio

5 6

[arch-general] how to upgrade 2017 server ?
by Shadrock Uhuru 11 Jan '20

11 Jan '20

i have a server that has not been booted since 2017, i tried upgrading with pacman -Syu, i have post the screen output at http://paste.openstack.org/show/788264/ i thought adding Eli Schwartz' personal repository to pacman.conf would have allowed the upgrade with his Binary builds of pacman-static. is my problem still to do with the xz to zstd change or something different ? shadrock

7 7

[arch-general] Sha256sum unexpected behaviour
by Leonidas Spyropoulos 10 Jan '20

10 Jan '20

Hello, I got a weird issue with sha256sum behaviour. When creating the package with makepkg --geninteg I get a hash and when trying to build it with makepkg the hash fails. The interesting bit is --ptintsrcinfo comes up with a different hash. Anyone got some idea why this might happen? See below some debugging info ~/linux-gc$ makepkg --geninteg ==> Retrieving sources... -> Found linux-v5.4.10-arch1.tar.gz -> Found config -> Found 0001_bmq_v5.4-r1.patch -> Found 0002_enable_additional_cpu_optimizations-20190822.tar.gz ==> Generating checksums for source files... sha256sums=('bd51016d038277d2edd4e6d6def53b0ba24e0b238662d404a07a7d706ad2b5d3' 'aa77f7e3b611787f734c7e7d7503d3debf9af86ac999e8bccf533c5a854ec15b' '0b770209a72171dfd46401d67d13204a767eb1749ef522df7ea7292b83046537' '8c11086809864b5cef7d079f930bd40da8d0869c091965fa62e95de9a0fe13b5') ~/linux-gc$ makepkg --printsrcinfo pkgbase = linux-gc pkgdesc = Linux pkgver = 5.4.10 pkgrel = 1 url = https://cchalpha.blogspot.co.uk/ arch = x86_64 license = GPL2 makedepends = bc makedepends = kmod makedepends = libelf makedepends = xmlto makedepends = python-sphinx makedepends = python-sphinx_rtd_theme makedepends = graphviz makedepends = imagemagick makedepends = git options = !strip source = linux-v5.4.10-arch1.tar.gz::https://git.archlinux.org/linux.git/snapshot/li… source = config source = 0001_bmq_v5.4-r1.patch::https://gitlab.com/alfredchen/bmq/raw/master/5.4/bm… source = 0002_enable_additional_cpu_optimizations-20190822.tar.gz::https://github.co… validpgpkeys = ABAF11C65A2970B130ABE3C479BE3E4300411886 validpgpkeys = 647F28654894E3BD457199BE38DBBDC86092693E validpgpkeys = 8218F88849AAC522E94CF470A5E9288C4FA415FA sha256sums = 1fda6369ec7038c9ca1fe7aa6206977c5b8983c77e9d74e4ba458a4d042d1d31 sha256sums = aa77f7e3b611787f734c7e7d7503d3debf9af86ac999e8bccf533c5a854ec15b sha256sums = 0b770209a72171dfd46401d67d13204a767eb1749ef522df7ea7292b83046537 sha256sums = 8c11086809864b5cef7d079f930bd40da8d0869c091965fa62e95de9a0fe13b5 pkgname = linux-gc pkgdesc = The Linux kernel and modules with the BMQ CPU scheduler depends = coreutils depends = kmod depends = initramfs optdepends = crda: to set the correct wireless channels of your country optdepends = linux-firmware: firmware images needed for some devices provides = linux-gc=5.4.10 pkgname = linux-gc-headers pkgdesc = Headers and scripts for building modules for the Linux kernel depends = linux-gc provides = linux-gc-headers=5.4.10 provides = linux-headers=5.4.10 Thanks, -- Leonidas Spyropoulos A: Because it messes up the order in which people normally read text. Q: Why is it such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?

4 3

[arch-general] tzdata, about dir /usr/share/zoneinfo-leaps
by Yi Zheng 10 Jan '20

10 Jan '20

Hi, all I found that there is a 'new' dir /usr/share/zoneinfo-leaps It includes files almost the same ones in /usr/share/zoneinfo/right/ I checked the md5 of every files under those two dir. And found that they are the same ones. The only exception is /usr/share/zoneinfo/right/US/Pacific-New, which has no counterpart under zoneinfo-leaps. ls cmd told me that Pacific-New is a hard link to Pacific, Los_Angeles. [linux-repo@~ 16:47:09]$ ll -i /usr/share/zoneinfo/right/US/Pacific-New /usr/share/zoneinfo/right/US/Pacific /usr/share/zoneinfo/right/America/Los_Angeles /usr/share/zoneinfo-leaps/America/Los_Angeles 6064711 -rw-r--r-- 2 root root 3376 Nov 14 00:24 /usr/share/zoneinfo-leaps/America/Los_Angeles 924194 -rw-r--r-- 3 root root 3376 Nov 14 00:24 /usr/share/zoneinfo/right/America/Los_Angeles 924194 -rw-r--r-- 3 root root 3376 Nov 14 00:24 /usr/share/zoneinfo/right/US/Pacific 924194 -rw-r--r-- 3 root root 3376 Nov 14 00:24 /usr/share/zoneinfo/right/US/Pacific-New [linux-repo@~ 16:48:53]$ md5sum /usr/share/zoneinfo/right/US/Pacific-New /usr/share/zoneinfo/right/US/Pacific /usr/share/zoneinfo/right/America/Los_Angeles /usr/share/zoneinfo-leaps/America/Los_Angeles 638a2cacbc89f9423e07ac7500901db5 /usr/share/zoneinfo/right/US/Pacific-New 638a2cacbc89f9423e07ac7500901db5 /usr/share/zoneinfo/right/US/Pacific 638a2cacbc89f9423e07ac7500901db5 /usr/share/zoneinfo/right/America/Los_Angeles 638a2cacbc89f9423e07ac7500901db5 /usr/share/zoneinfo-leaps/America/Los_Angeles any comments on those duplicated files?

1 0

[arch-general] can't 'pacman -Syu' to xorgproto 2019.2-2
by Greg Minshall 09 Jan '20

09 Jan '20

hi. today i can't do a "pacman -Syu", and i'm still too much of a newbie to know how to approach this. i'll be grateful for any advice. the following message was mentioned recently, and maybe relates? ---- https://bugs.archlinux.org/task/64892 ---- cheers, Greg ---- {812} % sudo pacman -Syu :: Synchronizing package databases... core is up to date extra is up to date community is up to date :: Starting full system upgrade... resolving dependencies... looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: installing xorgproto (2019.2-2) breaks dependency 'xf86miscproto' required by libxxf86misc

3 4

[arch-general] QT5 upgrades broke (non-antialiased) fonts
by David Rosenstrauch 08 Jan '20

08 Jan '20

Recently, a couple of KDE apps I use - most notably kalarm - have gotten their fonts screwed up. I usually use non-antialiased fonts. But it looks like now kalarm (as well as the kde control center) is now using anti-aliased fonts. I have them set to disabled in the kde control center, but that seems to be getting ignored. I noticed some recent qt5 packages got upgraded, and am assuming that might be the culprit, though it looks like there were also some kde packages upgraded recently as well. Anyone know what might have broken / how to fix? Thanks, DR

2 4

[arch-general] DHCPv6 fails after upgrading to dhcpcd-8.1.4
by Jukka Salmi 08 Jan '20

08 Jan '20

Hello Since upgrading dhcpcd from 8.1.2-1 to 8.1.4-1 my netctl profiles which configure IPv6 using dhcpcd fail to start. One of these profiles as an example: Interface=enp0s25.100 Connection=vlan BindsToInterfaces=enp0s25 VLANID=100 DHCPReleaseOnStop=yes IP=dhcp IP6=dhcp DHCP6Client=dhcpcd These profiles worked fine before, but now I get: $ journalctl -r [...] Dec 28 00:45:35 foo network[18634]: DHCP IPv6 lease attempt failed on interface 'enp0s25.100' Dec 28 00:45:35 foo dhcpcd[18791]: dhcpcd exited Dec 28 00:45:35 foo dhcpcd[18791]: timed out Dec 28 00:45:35 foo network[18791]: timed out Dec 28 00:45:05 foo dhcpcd[18791]: enp0s25.100: pid -1887792279 deleted default route via fe80::z:y:x:w Dec 28 00:45:05 foo dhcpcd[18791]: enp0s25.100: pid -759929144 deleted route to v:u:t::/64 Dec 28 00:45:05 foo dhcpcd[18791]: enp0s25.100: adding default route via fe80::z:y:x:w Dec 28 00:45:05 foo dhcpcd[18791]: enp0s25.100: adding route to v:u:t::/64 Dec 28 00:45:05 foo dhcpcd[18791]: enp0s25.100: adding address v:u:t:s:r:q:p:o/64 Dec 28 00:45:05 foo dhcpcd[18791]: enp0s25.100: Router Advertisement from fe80::z:y:x:w Dec 28 00:45:05 foo dhcpcd[18791]: enp0s25.100: soliciting an IPv6 router [...] Downgrading dhcpcd makes this work again. Any hints? Is anybody seeing the same issue? TIA & cheers, Jukka -- This email fills a much-needed gap in the archives.

1 1