Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

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

by BrowserUk (Pope)
on Dec 21, 2012 at 04:32 UTC ( #1009857=note: print w/replies, xml ) Need Help??


in reply to Re: Safe to open+close for every write, without locking?
in thread 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 (Monk) 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).

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1009857]
help
Chatterbox?
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (7)
As of 2016-12-05 15:25 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    On a regular basis, I'm most likely to spy upon:













    Results (87 votes). Check out past polls.