Re: [systemd-devel] Antw: Re: Antw: /bin/systemctl vs /usr/bin/systemctl
On Wed, Aug 7, 2019 at 1:20 PM Reindl Harald wrote: > > BTW: what MUA uses "Antw:" so that even the "clean subject" extension > fails because it expects "Re:" or "AW:" > > Antw is short for Antwoord, which is Dutch for answer/reply, so I imagine he configured it that way to match his language ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Antw: Re: Antw: /bin/systemctl vs /usr/bin/systemctl
Am 07.08.19 um 14:12 schrieb Ulrich Windl: Dave Howorth schrieb am 07.08.2019 um 12:00 in Ubuntu: /bin/systemctl SuSE: /usr/bin/systemctl >>> >>> I guess it should be /sbin/systemctl ;-) >> >> $ systemctl status >> >> is not a privileged command. > > That's one criteria it's the only, not so long ago /sbin or /usr/sbin wasn't in PATH for normal users > the other is how early it is needed/used during boot. > (I see that many people don't want to care about that, tending to say > "Everything is needed for boot immediately ;-) I grew up where the shell in > /sbin was different from that in /usr/sbin... Only the shell in /usr/bin had > full locale support (probably also due to the fact that the locale stuff was > inside /usr...) it's *all* below /usr for years now it's not needed during boot at all and things changed a lot in the past years given that it exists in the initrd - systems don't boot and work like they did when you grew up and so it makes no sense design file system layouts like decades ago BTW: what MUA uses "Antw:" so that even the "clean subject" extension fails because it expects "Re:" or "AW:" ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Antw: Re: Antw: /bin/systemctl vs /usr/bin/systemctl
>>> Dave Howorth schrieb am 07.08.2019 um 12:00 in Nachricht <20190807110029.0bdf9...@acer-suse.lan>: > On Wed, 07 Aug 2019 07:38:47 +0200 > "Ulrich Windl" wrote: >> >>> Thomas Güttler schrieb am >> >>> 06.08.2019 um >> 16:37 in >> Nachricht <3243dc34-4eec-e3a0-c6fd-491fdfcaf...@thomas-guettler.de>: >> > I just realized that the location of systemctl varies across linux >> > distributions. >> > >> > Ubuntu: /bin/systemctl >> > SuSE: /usr/bin/systemctl >> >> I guess it should be /sbin/systemctl ;-) > > $ systemctl status > > is not a privileged command. That's one criteria; the other is how early it is needed/used during boot. (I see that many people don't want to care about that, tending to say "Everything is needed for boot immediately ;-) I grew up where the shell in /sbin was different from that in /usr/sbin... Only the shell in /usr/bin had full locale support (probably also due to the fact that the locale stuff was inside /usr...) > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Antw: /bin/systemctl vs /usr/bin/systemctl
On Wed, 07 Aug 2019 07:38:47 +0200 "Ulrich Windl" wrote: > >>> Thomas Güttler schrieb am > >>> 06.08.2019 um > 16:37 in > Nachricht <3243dc34-4eec-e3a0-c6fd-491fdfcaf...@thomas-guettler.de>: > > I just realized that the location of systemctl varies across linux > > distributions. > > > > Ubuntu: /bin/systemctl > > SuSE: /usr/bin/systemctl > > I guess it should be /sbin/systemctl ;-) $ systemctl status is not a privileged command. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Antw: /bin/systemctl vs /usr/bin/systemctl
Am 07.08.19 um 07:38 schrieb Ulrich Windl: Thomas Güttler schrieb am 06.08.2019 um > 16:37 in > Nachricht <3243dc34-4eec-e3a0-c6fd-491fdfcaf...@thomas-guettler.de>: >> I just realized that the location of systemctl varies across linux >> distributions. >> >> Ubuntu: /bin/systemctl >> SuSE: /usr/bin/systemctl > > I guess it should be /sbin/systemctl ;-) why should it? besides that "systemctl" is not only used as root and UsrMove happened years ago the seperation between sbin and bin don't make sense for years ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] startup hang at 'load/save random seed'
On Di, 06.08.19 16:23, Chris Murphy (li...@colorremedies.com) wrote: > This is a new problem I'm seeing just today on Fedora Rawhide > > 5.3.0-0.rc3.git0.1.fc31.x86_64+debug > systemd-243~rc1-1.fc31.x86_64 > > The problem doesn't happen when reverting to > systemd-242-6.git9d34e79.fc31.x86_64 > > The hang lasts about 4-5 minutes, then boot proceeds. > > Or if I head to early-debug shell and start typing, it almost > immediately clears up and boot proceeds. Should be fixed by: https://github.com/systemd/systemd/pull/13263 Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Coredump Truncation problem
Hi, One of my daemon got crashed. The coredump is generated and stored in compressed format (.xz) While analyzing the coredump in gdb, I see that the coredump got truncation. I was not able to get any backtrace out of this coredump. BFD: warning: /tmp/60515/data-manager is truncated: expected core file size >= 1034403840, found: 954998784 [Current thread is 1 (LWP 2633)] (gdb) bt full #0 0x91b3ded4 in ?? () No symbol table info available. #1 0x8abb1b6c in ?? () No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) Systemd version : 229. Size settings: ProcessSizeMax=4G ExternalSizeMax=4G Ulimit is set to unlimited Initially I thought this could be due to coredump size limit. But the ulimit is set to unlimited and ProcessSizeMax/ExternalSizeMax set to 4G. What other scenarios could lead to truncated coredump? Is there any known issue on systemd v299 related to coredump truncation? -- With Kind Regards, P R Dinesh ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] startup hang at 'load/save random seed'
See https://github.com/systemd/systemd/issues/13252 Am Mi., 7. Aug. 2019 um 00:39 Uhr schrieb Chris Murphy : > > [ 10.281769] fmac.local systemd[1]: Starting Update UTMP about > System Boot/Shutdown... > [ 10.295504] fmac.local audit[806]: SYSTEM_BOOT pid=806 uid=0 > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=' > comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" > hostname=? addr=? terminal=? res=success' > [ 10.305289] fmac.local systemd[1]: Started Update UTMP about System > Boot/Shutdown. > [ 10.305527] fmac.local audit[1]: SERVICE_START pid=1 uid=0 > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > msg='unit=systemd-update-utmp comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > [ 15.264423] fmac.local systemd[1]: systemd-rfkill.service: Succeeded. > [ 15.268231] fmac.local audit[1]: SERVICE_STOP pid=1 uid=0 > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" > hostname=? addr=? terminal=? res=success' > [ 286.296649] fmac.local kernel: random: crng init done > [ 286.301223] fmac.local kernel: random: 7 urandom warning(s) missed > due to ratelimiting > [ 286.319857] fmac.local systemd[1]: Started Load/Save Random Seed. > [ 286.322850] fmac.local audit[1]: SERVICE_START pid=1 uid=0 > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > msg='unit=systemd-random-seed comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > [ 286.323576] fmac.local systemd[1]: Reached target System Initialization. > > > I don't know why there's ratelimiting on urandom warnings, I have > printk.devkmsg=on > > This also seems relevant. > > [chris@fmac ~]$ sudo journalctl -b -o short-monotonic | grep -i seed > [8.870985] fmac.local systemd[1]: Starting Load/Save Random Seed... > [9.021818] fmac.local systemd-random-seed[619]: Kernel entropy > pool is not initialized yet, waiting until it is. > [ 286.319857] fmac.local systemd[1]: Started Load/Save Random Seed. > [ 286.322850] fmac.local audit[1]: SERVICE_START pid=1 uid=0 > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > msg='unit=systemd-random-seed comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > [chris@fmac ~]$ > > > --- > Chris Murphy > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
