Closed dermarens closed 7 years ago
I've not noticed this before, but I wonder if by trying to use the PID of the parent process to log against is not permitted in some situations when privileges have been dropped under systemd
.
Looks like the --id
option may need to be removed from the script.
I can confirm that removing the --id
arg from the log
function fixes this. Without removing it, the script fails and the nameserver entries are not added.
+1 at least debian doesn't like --id
to have a value
+1 arch also does not like --id
Hey there! First let me say thanks a lot for this useful script.
I just found a minor issue while following systemlogs with journalctl -fe
i used "set -x" to get some more debugging infos during the logger run.
While this fails when executed from within update-systemd-resolved i works when executed from the commandline
Console:
Journal:
Changing the script like shown below gets rid of the error
This happens using systemd-233-r1 on gentoo linux
Any ideas what might be going on here?