Comment 6 for bug 1891215

Hello,

Some days ago, I installed systemd-dbgsym_245.4-4ubuntu3.6_amd64.ddeb and set a breakpoint on function 'conservative_renameat':https://github.com/systemd/systemd/blob/main/src/basic/fs-util.c#L1504 (because of my understanding of function 'manager_write_resolv_conf':https://github.com/systemd/systemd/blob/main/src/resolve/resolved-resolv-conf.c#L324) to see what happens, but I was unsuccessful in hitting his breakpoint.

Besides, the issue has been reported upstream: https://github.com/systemd/systemd/issues/17577. Unfortunately, it was closed after someone suggested that a fix in https://github.com/systemd/systemd/pull/17535 resolved the systemd-resolved part of the issue (https://github.com/systemd/systemd/issues/17577#issuecomment-733962476), whereas in truth the combination of https://github.com/systemd/systemd/pull/17535 and its networkd counterpart did not resolve it.