>>> Mantas Mikulenas <grawity@xxxxxxxxx> schrieb am 07.10.2020 um 08:56 in Nachricht <CAPWNY8WWdq3fhjc57BaOGPs=n44YvL_LRLU+kprtagXumhBS9Q@xxxxxxxxxxxxxx>: > On Wed, Oct 7, 2020 at 9:49 AM Ulrich Windl < > Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx> wrote: > >> Hi! >> >> I'm thinking of configuring a serial getty in SLES15 (systemd-234). First >> I found that there is no manual page describing the service, and second if >> I use "systemctl show serial-getty" ("systemctl show serial-getty@" does >> not work), I get some "funny" numbers: >> >> ... >> UID=4294967295 >> GID=4294967295 >> ... >> MemoryCurrent=18446744073709551615 >> CPUUsageNSec=18446744073709551615 >> TasksCurrent=18446744073709551615 >> IPIngressBytes=18446744073709551615 >> IPIngressPackets=18446744073709551615 >> IPEgressBytes=18446744073709551615 >> IPEgressPackets=18446744073709551615 >> ... >> CPUWeight=18446744073709551615 >> StartupCPUWeight=18446744073709551615 >> CPUShares=18446744073709551615 >> StartupCPUShares=18446744073709551615 >> ... >> >> Obviously that number is the unsigned 64-bit representation of -1, but >> considering that no such service is running, the output looks quite odd. >> If -1 means "unknown", why not use that string, or if it means >> "unlimited", why not use that string? >> > > This was fixed in systemd-235 several years ago. > https://github.com/systemd/systemd/commit/21771f338d268e06dc9a10b9b08b14ff82 > 17d4be > Thanks, good to know. > -- > Mantas Mikulėnas _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel