Re^2: Safe to open+close for every write, without locking?

If performance is your primary criteria, you'd be much better off creating a demon that opens a fifo, have your processes write their lines to the fifo and have the demon write them to disk in 64k chunks.

(Isn't that called a syslog under *nix?)

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

RIP Neil Armstrong

Comment on Re^2: Safe to open+close for every write, without locking?

Replies are listed 'Best First'.
Re^3: Safe to open+close for every write, without locking? by sedusedan (Pilgrim) on Dec 21, 2012 at 05:55 UTC
Like Log::Dispatch::FileRotate, my module will/might be used by CGI scripts (multiple writers, potentially lots of concurrent writers, one-off processes, no daemon).	[reply]