directing logs to a broadcast address results in "sendto: Permission denied"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sysklogd (Debian) |
Fix Released
|
Unknown
|
|||
sysklogd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: sysklogd
If you modify your /etc/syslog.conf to have a line like:
*.crit @192.168.0.255
restart sysklogd, and then run:
logger -p local0.crit -t foo "message"
you'll observe in /var/log/
Apr 24 04:14:29 host syslogd 1.5.0#1ubuntu1: restart.
Apr 24 04:15:13 host syslogd: sendto: Permission denied
It appears this is because syslog isn't enabling broadcast on the socket it is using. See:
http://
Observed in Ubuntu 8.04 and Debian Etch (I haven't tested 8.10; will you guys open an upstream ticket or shall I? I haven't checked to see if one already exists in the DBTS).
Being able to send logs to a broadcast address is supposedly something that is supposed to work, according to various third party documents on configuring syslog (not syslog-ng).
tags: | added: udd-find |
Changed in sysklogd (Debian): | |
status: | Unknown → New |
Changed in sysklogd (Debian): | |
status: | New → Fix Released |