> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Aaron Nichols > Sent: Wednesday, October 21, 2009 3:18 PM > To: rsyslog-users > Subject: Re: [rsyslog] Enabling $ActionFileEnableSync > causedmassiveincreaseinwrite volume (bytes/sec) to NAS - cansomeone > helpshed light? > > On Wed, Oct 21, 2009 at 1:38 AM, Rainer Gerhards > <[email protected]>wrote: > > > See my other note, but there may be a subtle misunderstanding: The > presence > > of "-" turns OFF file syncing. Absence of "-" causes a sync! So in > > > > *.* /path/to/fileWithSync > > *.* -/path/to/fileWithoutSync > > > > fileWithSync is being synced and fileWithoutSync is not! > > > > This is traditional config file syntax and probably the main reason > why *a > > lot* of real-world config files do syncs... > > > > > I understood correctly and now I'm certain I know how it should work. I > need > to do some more testing and I think I have enough information to do > that and > will come back here when I have something interesting to share. An > observation I did make when this was happening was that if > $ActionFileEnableSync was disabled (commented out) but the "-" was > missing > before the actions in the configuration, write volume to the NAS was > higher > than when we had $ActionFileEnableSync disabled and had the "-" added > before > the action (write volume was 100% higher if $ActionFileEnableSync was > OFF > and the "-" option was missing from all log actions than if > $ActionFileEnableSync was OFF and "-" was included in all log actions.)
That indeed sounds odd. Are you sure the $ActionFileEnableSync is in front of all write statements? On some systems, write statements may be included via files and if these are in front of the directive, those would be unaffected by it... Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
