Confirmed this locally. strace shows:
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(514),
sin_addr=inet_addr("192.168.15.71")}, 16) = 0
[...]
socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 1
connect(1, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = 0
sendto(1, "<38>Aug 19 19:31:26 logger:
nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn", 69, MSG_NOSIGNAL, NULL, 0) = 69
close(1) = 0
So a socket is opened to the designated server, then is not used for
writing the log message.
However, you called this a "regression". I see the same behavior with
the version of bsdutils in 14.04.0. This doesn't appear to be a
regression in 14.04, it appears to be functionality that has been broken
for two years since 14.04 released and went unnoticed until now. So I
disagree with the categorization of "high" and think this is not
something we will fix in SRU.
The bug in question is not present in 16.04 and later, therefore I'm
closing this bug as fix released.
** Changed in: util-linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614976
Title:
"logger -n" does not work on ubuntu 14.04.4 LTS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1614976/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
