> > In manpage I see parameter InputUDPServerRun, but in config file
> there
> > is commented out UDPServerRun. The first doesn't work, the second is
> ok.
> >
> > I suppose, that there are the same problems with tcp and repl
> > parameters.
> 
> The InputTCPServerRun and InputRELPServerRun parameters are correct.
> So, using
> UDPServerRun for UDP is inconsistent (and afaik due to historical
> reasons).
> Rainer, would it be possible to use InputUDPServerRun and make
> UDPServerRun an
> alias for InputUDPServerRun. So existing config files would remain to
> work.
> UDPServerRun could be marked as deprecated (and rsyslog could warn in
> the
> syslog/stderr). The existing docs should be updated accordingly and
> after some
> time (say 2 years from now), you could remove the old UDPServerRun
> variable.

I can do this and it sounds like the right thing to do. HOWEVER, there are a
number of these inconsistencies inside the configuration language. They were
introduced because the language evolved rather than being designed for that
purpose. So the naming conventions also evolved.

So I am not sure if we should actually duplicate all of these inconsistent
statements. That's a lot of functional duplicates (especially given the fact
that I still hope to be able to revamp the config language some time during
this year).

Thoughts are appreciated.

Rainer



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to