Skip to content

Add explanatory header#24

Merged
philip-loggly merged 1 commit intologgly:masterfrom
philip-loggly:master
Aug 25, 2013
Merged

Add explanatory header#24
philip-loggly merged 1 commit intologgly:masterfrom
philip-loggly:master

Conversation

@philip-loggly
Copy link
Copy Markdown
Contributor

Ticket: LOGGLY-3825

@philip-loggly
Copy link
Copy Markdown
Contributor Author

Ryan -- do you think this will do it? Or do you think we need to merge these option changes with existing options?

@rhigdon
Copy link
Copy Markdown
Contributor

rhigdon commented Aug 24, 2013

Yes we need to merge existing options..

 6 options {
 7         chain_hostnames(no);
 8
 9         # The default action of syslog-ng is to log a STATS line
10         # to the file every 10 minutes.  That's pretty ugly after a while.
11         # Change it to every 12 hours so you get a nice daily update of
12         # how many messages syslog-ng missed (0).
13         stats_freq(43200);
14         # The default action of syslog-ng is to log a MARK line
15         # to the file every 20 minutes.  That's seems high for most
16         # people so turn it down to once an hour.  Set it to zero
17         # if you don't want the functionality at all.
18         mark_freq(3600);
19 };

Here is a default example. For syslog-ng

@philip-loggly
Copy link
Copy Markdown
Contributor Author

Ryan -- how do you know we need to merge options? Perhaps syslog-ng does it for us.

philip-loggly added a commit that referenced this pull request Aug 25, 2013
Configure script should enable large-message logging.
@philip-loggly philip-loggly merged commit 45e14b6 into loggly:master Aug 25, 2013
@rhigdon
Copy link
Copy Markdown
Contributor

rhigdon commented Aug 26, 2013

I did not test whether or not syslog-ng would merge options.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants