> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of [email protected] > Sent: Thursday, July 05, 2012 11:12 AM > To: [email protected] > Subject: Re: [rsyslog] separate local disk and nfs queues > > Thanks for explanation. > > I read your new blog post. Do I understand correctly that empty lines makes > a difference like this:
No, because... > > ***** > $ActionQueueType LinkedList # use asynchronous processing > $ActionQueueFileName nfsq # set file name, also enables disk mode > *.err -?Tcritical;FileFormat > *.* -?Tdefault;FileFormat > ***** > ^ both actions are queued in a disk queue named nfsd. > > ***** > $ActionQueueType LinkedList # use asynchronous processing > $ActionQueueFileName nfsq # set file name, also enables disk mode > *.err -?Tcritical;FileFormat > > *.* -?Tdefault;FileFormat > ***** > ^ first action is queued. Second action is in direct mode, because it is > separated by an empty line, what means direct mode by default. This applies in both cases, not because oft he empty line but because oft he fact that for the second action no queue params are set, which means the default (direct) is used. Rainer > > IgnasR > > On 2012.07.05 11:04, Rainer Gerhards wrote: > > I am not sure if I understood you correctly. Each action has a > > dedicated queue. This queue can be in-memory, it can be on disk and it > > can be a combination of both. There is also direct mode, which means > > by desing there is a queue but the actual driver does forward messages > > to the action without action queing. > > > > When you define actions, the queue parameters belong to the *next* > > action (in v6 this is far easier to understand and see as the queue > > params are specified within the action). In the snippet below, we have > > two actions, and each of them is configured with different queue > > settings. This results with two different sets of queue files being > > written. It is important that the queue file names are different (as > > they are), but otherwise the queues are independent. There can be as > > many disk (or DA) queues as there are actions. Note that if there is > > only a single action queue and n actions, this means only one action > > uses the disk queue, whereas n-1 actions do not use it (if nothing > > else is set, they run in direct mode). > > > > In that sense, the config looks OK to me. However, I am a bit skeptic > > on the NFS mount in general, I know several users have reported > > problems of various kinds with such configs. Maybe many more happily > > use the same ;) > > > > Hope this clarifies, Rainer > > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards
