On Thu, Jun 10, 2010 at 9:17 AM, Rainer Gerhards <[email protected]> wrote: > >> The only limit to the number of files currently open should be the >> open files limit provided by the OS. > > ummm... think that sockets take form the same camp, so there must be a limit. > Also, even with a timeout, some files may be dormant for at least a couple of > minutes (or seconds -- user option).
Well yes - but those pool sizes are defined through max listeners and max sessions, so we could have anything that was left over. >>I am curious: how is an output >> file identified at present? > > via it's name, so search is relatively expensive Sounds like the cache should be implemented as a hash table. :) >> I don't fully understand how the async writer interacts with an action >> thread yet... is it a one-action-many-writers relationship? > > right now, it is one-on-one, as the action is guarded by the action lock (and > remember that on my list is removing that lock for select actions, omfile > being one of them!). The async writer is simply set to do async-io, it's > essentially double-buffering in mainframe terms (and the current > implementation isn't even very efficient). So... just to clarify the separation of work, the async writer buffers and writes, and that's it? -Aaron _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
