OpenCSW Bug Tracker


Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0004411 [syslog_ng] packaging minor always 2010-05-04 03:44 2014-03-24 00:47
Reporter flod View Status public  
Assigned To
Priority normal Resolution open  
Status new  
Summary 0004411: delivered configuration file shows warnings
Description I have no idea if it is possible to convert the syslogd micking configuration file to a newer format. I am just curious about the warnings when installing the package without changing the configuration.

Additional Information [ May 4 03:20:00 Disabled. ]
[ May 4 03:20:00 Rereading configuration. ]
[ May 4 03:20:00 Enabled. ]
[ May 4 03:20:00 Executing start method ("/var/opt/csw/svc/method/svc-cswsyslog_ng start") ]
syslog-ng service starting.
Configuration file has no version number, assuming syslog-ng 2.1 format. Please add @version: maj.min to the beginning of the file;
WARNING: global: the default value of chain_hostnames is changing to 'no' in version 3.0, please update your configuration accordingly;
Your configuration file uses an obsoleted keyword, please update your configuration; keyword='sync', change='flush_lines'
WARNING: input: sources do not remove new-line characters from messages by default in version 3.0, please add 'no-multi-line' flag to your configuration if you want to retain this functionality;
WARNING: template: the default value for template-escape is changing to 'no' in version 3.0, please update your configuration file accordingly;
[ May 4 03:20:01 Method "start" exited with status 0 ]
[ May 4 03:21:02 Stopping because service disabled. ]
[ May 4 03:21:02 Executing stop method ("/var/opt/csw/svc/method/svc-cswsyslog_ng stop") ]
[ May 4 03:21:02 Method "stop" exited with status 0 ]
--
CSWsyslogng 3.0.5,REV=2010.02.27
Tags No tags attached.
Attached Files

- Relationships

-  Notes
(0010768)
maciej (reporter)
2014-03-24 00:47

There is no point in waiting for this bug to be fixed. If you want it fixed, you (yes, you the reader) need to fix it yourself. If you're not already a package maintainer at OpenCSW, you can look at the 35 minute long tutorial[1] to get started - then you can offer your patch to package maintainers. You can find OpenCSW people on the users mailing list[2] and on the #opencsw channel on IRC on Freenode[3].

[1] Packaging tutorial http://youtu.be/JWKCbPJSaxw [^]
[2] OpenCSW users mailing list https://lists.opencsw.org/mailman/listinfo/users [^]
[3] #opencsw on Freenode http://www.opencsw.org/support/irc-channel/ [^]


Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker