FS#15435 - [syslog-ng] man syslog-ng.conf(8) out of date - mark(n) setting

Attached to Project: Arch Linux
Opened by Isaac G (IsaacG) - Wednesday, 08 July 2009, 02:46 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 09 July 2009, 09:31 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

man syslog-ng.conf(5) says you can set the interval with which a MARK message is emitted with the mark(n) keyword.
Running syslog-ng with that config setting gives:
> Your configuration file uses an obsoleted keyword, please update your configuration; keyword='mark', change='mark_freq'

The man page needs updating? Or is this upstream?

Name : syslog-ng
Version : 3.0.1-6
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Thursday, 09 July 2009, 09:31 GMT
Reason for closing:  Won't fix
Additional comments about closing:  report sent upstream (thanks!),
we don't fix man pages by ourselves
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 08 July 2009, 03:37 GMT
  • Field changed: Summary (man syslog-ng.conf(8) out of date - mark(n) setting → [syslog-ng] man syslog-ng.conf(8) out of date - mark(n) setting)
  • Field changed: Category (Documentation → Upstream Bugs)
Upstream issue, please report to is. This is also present in the latest upstream version 3.0.3.
Comment by Isaac G (IsaacG) - Wednesday, 08 July 2009, 04:34 GMT
Their online documentation does say that mark(n) is deprecated in favor of mark_freq(n).
I sent an email to documentation@balabit.com

Loading...