journald: use the "driver" transport for logging a refused connection
Otherwise, these messages can end up in `/dev/null` when journald is run in containers as was shown in https://github.com/systemd/systemd/pull/10444#issuecomment-430927793. (cherry picked from commit c8758e72) (cherry picked from commit 852bb73e)
Loading
Please register or sign in to comment