[systemd-devel] Why are core dumps named vgcore.*?

Hi! I'm developing a program that dumps core on some failed assertions. I noticed that the core dumps are created in the user directory as vgcore.. Where does the name vgcore come from? And is it OK to remove just those files, or does coredumpctl store additional infos? Regards, Ulrich

Re: [systemd-devel] What is the recommended way of announcing a TCP port?

If you only care about processes on the same system – why not put the actual socket in /run, as an AF_UNIX socket? That's mostly what /run is for. On Tue, Jun 15, 2021, 04:18 John Ioannidis wrote: > I have an instanced service that gets started and stopped by another > service: *alice.service *r

Re: [systemd-devel] What is the recommended way of announcing a TCP port?

You might consider having systemd itself create the listening sockets and then pass them into the service; if you did that, then systemd would already know the port number that was allocated for the socket. On Mon, Jun 14, 2021 at 9:17 PM John Ioannidis wrote: > > I have an instanced service that

[systemd-devel] What is the recommended way of announcing a TCP port?

I have an instanced service that gets started and stopped by another service: *alice.service *runs the equivalent of *systemsctl start alice@foo.service, systemctl start alice@bar.service, systemctl stop alice@cat.service*, and so on. Each of the instanced services runs a little http service so its

Re: [systemd-devel] Running systemd unprivileged in Docker container

On 6/14/21 08:20, Lennart Poettering wrote: On Fr, 11.06.21 16:55, Johannes Ernst (johannes.er...@gmail.com) wrote: I can run a full Arch system (with systemd as PID 1) in a Docker container in Docker privileged mode: sudo docker run -i -t --privileged archlinux /usr/lib/systemd/systemd b

Re: [systemd-devel] Running systemd unprivileged in Docker container

On Fr, 11.06.21 16:55, Johannes Ernst (johannes.er...@gmail.com) wrote: > I can run a full Arch system (with systemd as PID 1) in a Docker container in > Docker privileged mode: > sudo docker run -i -t --privileged archlinux /usr/lib/systemd/systemd > but privileged mode is, well, a bit privi

Re: [systemd-devel] Alais for SMTP providers

On Sa, 12.06.21 03:33, Kenneth Porter (sh...@sewingwitch.com) wrote: > I just finished adding a custom service to send an email on system > shutdown/startup, based on this article: > > > > I ended up coding an After for

Re: [systemd-devel] systemd.socket man pages update suggestion

On Do, 10.06.21 13:44, Ted Toth (txt...@gmail.com) wrote: > SELinuxContextFromNet= >Takes a boolean argument. When true, systemd will attempt to >figure out the SELinux label used for the instantiated >service from the information handed by the peer over the >

[systemd-devel] Antw: Re: Antw: [EXT] Block systemd from adding new services

>>> Andy Pieters schrieb am 14.06.2021 um 10:09 in Nachricht : > On Mon, 14 Jun 2021 at 09:05, Ulrich Windl < > ulrich.wi...@rz.uni-regensburg.de> wrote: > >> >> The better solution would have been to pick a stronger password IMHO. >> >> >> Or rather turn off password authentication. If you must

Re: [systemd-devel] Antw: [EXT] Block systemd from adding new services

On Mon, 14 Jun 2021 at 09:05, Ulrich Windl < ulrich.wi...@rz.uni-regensburg.de> wrote: > > The better solution would have been to pick a stronger password IMHO. > > > Or rather turn off password authentication. If you must have automation, use RSA keys, if not, and really want to keep passwords, a

Re: [systemd-devel] Are Pathnames in /tmp/systemd-private-foo predictable?

On Mon, Jun 14, 2021 at 09:59:24AM +0200, Lennart Poettering wrote: > It's the boot ID, i.e. /proc/sys/kernel/random/boot_id. We include it > in the name so that we can distinguish such dirs of the current boot > from those of earlier boots (which can be retained because of abnormal > shutdown or s

[systemd-devel] Antw: [EXT] Block systemd from adding new services

>>> Saint Michael schrieb am 13.06.2021 um 15:32 in >>> Nachricht : > One of the most dramatic hacks to 50+ servers of mine is a bitcoin miner, > xmrig. It installs a service file at /etc/systemd/system, enables it and > kills the machine. > Nobody knows how it propagates. I think that SSHD has b

Re: [systemd-devel] Are Pathnames in /tmp/systemd-private-foo predictable?

On So, 13.06.21 21:04, Marc Haber (mh+systemd-de...@zugschlus.de) wrote: > Hi, > > I am wondering where the 32 xdigit number in pathnames like > > systemd-private-27aa635a15cf4da0a7ebda10f25c3950-chrony.service-9DShFi/ > > comes from. I always had the impression that it's the systemd/dbus > machin