Holger Weiß

> Conversations has a XEP list, but doesn't mention XEP-0256 in it. Ah, I was referring XEP-0319.

> The migration would require a downtime, right ? Yes, it would.

The `configure` script would have to edit the preinstalled `ejabberdctl.cfg` and the systemd unit file to set the desired PID file path. I think a better solution would be to...

> The paths used are those expected to work in a systemd environment as far as I know. The `./configure` script supports custom installation paths, and many admins make use...

@mtdcr, thanks for brinding this up, but this specific issue actually isn't addressed yet: The `ejabberdctl` script still runs the VM as a child process, and systemd is not aware...

> Regarding our specific problem from what I can see this solves the problem. The thing that's _not_ yet solved is: > Currently `systemd` is not aware that `beam.smp` is...

> We probably could also exec erl I think so, too. I just didn't dare to apply that change immediately before the 21.01 release :smile:

> those must continue using the old method. Yes, that's the reason this fix isn't completely trivial (sorry I didn't mention that explicitly).

> so this is fixed then? Only partially: It works for the self-notification case [now][1] (which is probably the most interesting case in practice), but not for other whitelisted JIDs....

You can emulate the desired behavior by enabling (and optionally enforcing) MAM archiving for new rooms, and then configuring [`mod_mam`][1] to keep the archive on room destruction (by setting `clear_archive_on_room_destroy:...