[systemd-devel] Cannot mount anything after recovering and redoing boot mbr

I suspect that somebody here knows why, but all mounts now fail... well all but /. Has anyone run across this before? What did I miss? I accidentally messed up my boot mbr. and I did a rescue cd and chroot in order to rerun grub2-mkconfig and do a grub2-install. Now the system boots to a

Re: [systemd-devel] I have lots of sockets tied to pid 1 (systemd) in CLOSE-WAIT, anyway to get rid of these?

On 06/19/2018 05:21 PM, Christopher Cox wrote: Not sure what happened, but on one of our CentOS 7 host we had like 64 socket connects owned by pid 1 (systemd) in CLOSE-WAIT state.  And systemctl -a shows a bunch of lines like: check_mk@11305-10.32.50.31:6556-10.32.3.10:55106.service

Re: [systemd-devel] Illegal CPUID instruction causes systemd core dump

On 12/28/2017 01:26 PM, Reindl Harald wrote: ...snippity >> Am 28.12.2017 um 20:07 schrieb tedheadster: The Linux kernel still supports the 486 so we have to code around this case, even if it is ancient hardware don't get me wrong - i am for 15 years now in the IT and my first PC in

Re: [systemd-devel] I have lots of sockets tied to pid 1 (systemd) in CLOSE-WAIT, anyway to get rid of these?

On 06/20/2018 06:33 AM, Lennart Poettering wrote: On Di, 19.06.18 17:21, Christopher Cox (c...@endlessnow.com) wrote: Not sure what happened, but on one of our CentOS 7 host we had like 64 socket connects owned by pid 1 (systemd) in CLOSE-WAIT state. And systemctl -a shows a bunch of lines

[systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

I need to be able to execute a script before anything gets shutdown. That is, when somebody does a "reboot", "shutdown" or "poweroff", I need this script to run first, and for it to finish before everything gets whacked. I know the following isn't "right"... I've tried so many different

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

versions too. Has anyone tried to do something (I'm on CentOS latest) with maybe an extra target (post default.target)... possible. I need something that "works". I hope this helps! Cheers, Filipe On Wed, Jan 16, 2019 at 10:47 AM Christopher Cox <mailto:c...@endlessnow.com>>

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

On 01/16/2019 10:44 PM, Christopher Cox wrote: On 01/16/2019 12:51 PM, Filipe Brandenburger wrote: If you want to run it early in the shutdown process, then keep DefaultDependencies=yes, in which case it will run before the base dependencies start to get stopped. If you need some other

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

On 1/17/19 11:59 AM, Lennart Poettering wrote: On Do, 17.01.19 11:17, Christopher Cox (c...@endlessnow.com) wrote: [Install] WantedBy=multi-user.target In my case, my script rolls through the currently running processes, looking for certain ones, determines listening port (ss) and gets

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

On 1/17/19 11:54 AM, Reindl Harald wrote: Am 17.01.19 um 18:51 schrieb Christopher Cox: On 1/17/19 11:21 AM, Reindl Harald wrote: Am 17.01.19 um 18:17 schrieb Christopher Cox: On 1/17/19 11:01 AM, Lennart Poettering wrote: Hmm, what kind of processes are you missing? user session stuff? How

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

On 1/16/19 11:10 PM, Reindl Harald wrote: that all is not really new and was not better with sysvinit, it only was slow enough, full of sleep/usleep hacks and so most of the time by luck worked but with no guarantess anyways What I said it that synchronous execution of a script was possible

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

On 1/17/19 5:50 AM, Lennart Poettering wrote: With that you can now put together a unit that is terminated relatively early on during shutdown: just make it "After=multi-user.target graphical.target default.target", so that it gets activated at boot very late, and thus deactivated at shutdown

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

On 1/17/19 11:01 AM, Lennart Poettering wrote: On Do, 17.01.19 10:18, Christopher Cox (c...@endlessnow.com) wrote: On 1/17/19 5:50 AM, Lennart Poettering wrote: With that you can now put together a unit that is terminated relatively early on during shutdown: just make it "After=

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

On 1/17/19 12:09 PM, Christopher Cox wrote: On 1/17/19 11:54 AM, Reindl Harald wrote: Am 17.01.19 um 18:51 schrieb Christopher Cox: On 1/17/19 11:21 AM, Reindl Harald wrote: Am 17.01.19 um 18:17 schrieb Christopher Cox: On 1/17/19 11:01 AM, Lennart Poettering wrote: Hmm, what kind

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

On 1/17/19 2:42 PM, Lennart Poettering wrote: On Do, 17.01.19 14:35, Christopher Cox (c...@endlessnow.com) wrote: On 1/17/19 2:25 PM, Lennart Poettering wrote: On Do, 17.01.19 12:38, Christopher Cox (c...@endlessnow.com) wrote: it defaults to YES and the whole discussions as that changed

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

On 1/17/19 2:25 PM, Lennart Poettering wrote: On Do, 17.01.19 12:38, Christopher Cox (c...@endlessnow.com) wrote: it defaults to YES and the whole discussions as that changed where about nohup'd processes long ago Changing it to "no"... I'll let you know if this fi

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

On 1/17/19 11:21 AM, Reindl Harald wrote: Am 17.01.19 um 18:17 schrieb Christopher Cox: On 1/17/19 11:01 AM, Lennart Poettering wrote: Hmm, what kind of processes are you missing? user session stuff? How do you shut down? Note that display managers are likely to terminate the user sessions

Re: [systemd-devel] vt220 default for serial console still relevant?

On 7/13/20 4:08 PM, Barry wrote: On 11 Jul 2020, at 20:31, Daan De Meyer wrote:  > TERM=linux means Linux console, but that's just too much, as it not > only implies a multitude of ESC sequences specific to the Linux > console, but also indicates that certain ioctls might work. In our own

Re: [systemd-devel] vt220 default for serial console still relevant?

On 7/14/20 3:19 AM, Lennart Poettering wrote: On Mo, 13.07.20 18:16, Christopher Cox (c...@endlessnow.com) wrote: No vt220 does not support colour. I used to work on one and it is monochrome hardware. Xterm and konsole support extensions beyond vt220 that add in the colour support. Not sure

Re: [systemd-devel] vt220 default for serial console still relevant?

mpany I was contracting to, it was too expensive) Daan On Tue, 14 Jul 2020 at 18:22, Christopher Cox <mailto:c...@endlessnow.com>> wrote: On 7/14/20 3:19 AM, Lennart Poettering wrote: > On Mo, 13.07.20 18:16, Christopher Cox (c...@endlessnow.com <mailto:c...@endle

Re: [systemd-devel] vt220 default for serial console still relevant?

On 7/14/20 4:27 PM, Mantas Mikulėnas wrote: On Tue, Jul 14, 2020 at 9:48 PM Daan De Meyer > wrote: I just tried vt241 and didn't get colorized output in konsole. I looked around a bit and it doesn't really seem supported at all by terminal emulators

Re: [systemd-devel] Suppressing spam error messages in the system journal

On 10/22/20 9:55 AM, Dave Howorth wrote: On Thu, 22 Oct 2020 15:27:58 +0200 Reindl Harald wrote: Am 22.10.20 um 12:59 schrieb Lennart Poettering: On Do, 22.10.20 11:11, David C. Partridge (david.partri...@perdrix.co.uk) wrote: 1) Is there any way in journald.conf to perform a message

Re: [systemd-devel] Xorg or Wayland Environment

On 9/21/21 9:13 AM, Michael Biebl wrote: Just curious: Can someone familiar with KDE/Plasma tell us, if they nowadays (can) use "systemd --user" to manage a login session. Seems to be the case on openSUSE Leap 15.3 So, I'll say yes. Am Di., 21. Sept. 2021 um 12:52 Uhr schrieb Ed Greshko

Re: [systemd-devel] the need for a discoverable sub-volumes specification

On 11/3/21 12:52 PM, Chris Murphy wrote: There is a Discoverable Partitions Specification http://systemd.io/DISCOVERABLE_PARTITIONS/ The problem with this for Btrfs, ZFS, and LVM is a single volume can represent multiple use cases via multiple volumes: subvolumes (btrfs), datasets (ZFS), and