In the syslogd function init(), parameters passed to cfline() are not clean when the user attempt to use a remote host entry as the source of syslog messages. Instead of a clean host name, it passes the hostname and the last program specification in the syslog.conf file. Fix: Apply the next patch from the source tree: How-To-Repeat: Put any program specification and start syslogd with -vv and -d flags, you can see the parameters passed to cfline() function in a list.
On Sun, Oct 30, 2005 at 04:22:42AM -0300, Daniel Molina Wegener wrote: D> In the syslogd function init(), parameters passed to cfline() D> are not clean when the user attempt to use a remote host entry D> as the source of syslog messages. D> D> Instead of a clean host name, it passes the hostname and the D> last program specification in the syslog.conf file. D> D> >How-To-Repeat: D> D> Put any program specification and start syslogd with -vv and -d D> flags, you can see the parameters passed to cfline() function in D> a list. This is expected behavior, it is documented in manual: A program or hostname specification may be reset by giving the program or hostname as `*'. This means, that program and hostname specifications are sticky and should be reset explicitly, if set once. Many people find this confusing (me too). I would like to change syslogd so that it resets both program and hostname to '*' after any regular configuration line. But before commiting this we need positive review from some people, and no negative review. May be current@ mailing list will be the correct choice. You should raise this question on mailing lists, if you want to discuss this issue. In this case I will set PR to analyzed state. If you agree with current documented behavior, then you can ask for PR to be closed. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE
On Tue, Nov 08, 2005 at 03:43:30PM +0300, Gleb Smirnoff wrote: > [SNIP] > > This is expected behavior, it is documented in manual: > > > A program or hostname specification may be reset by > giving the program or hostname as `*'. > Ok, the manual page indicates this method to reset the program/host specification. The patch I've sent makes this task automatically when a new specficiation is given from the syslog.conf file. > This means, that program and hostname specifications are > sticky and should be reset explicitly, if set once. Many > people find this confusing (me too). I understand... > I would like to change syslogd so that it resets both program > and hostname to '*' after any regular configuration line. > But before commiting this we need positive review from some > people, and no negative review. May be current@ mailing list > will be the correct choice. You should raise this question on > mailing lists, if you want to discuss this issue. In this case > I will set PR to analyzed state. If you agree with current > documented behavior, then you can ask for PR to be closed. Ok, Is the hackers mailing list the right place to start?. > -- > Totus tuus, Glebius. > GLEBIUS-RIPN GLEB-RIPE Regards -- . 0 . | Daniel Molina Wegener . . 0 | dmw at unete dot cl 0 0 0 | FreeBSD Power User
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped
Keyword: patch or patch-ready – in lieu of summary line prefix: [patch] * bulk change for the keyword * summary lines may be edited manually (not in bulk). Keyword descriptions and search interface: <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>