[Jax.PM] child proc output

[William C. (Bill) Jones]

On Wednesday, October 9, 2002, at 10:11  AM, J Proctor wrote:

> In the bigger picture, it's difficult to imagine what could corrupt the
> counter file under those circumstances, unless (a) the time 
> interval is so
> short it's stepping on itself, or (b) you've got multiple things 
> trying to
> use the data, and your system doesn't do file locking in any sane way.
> That would be most of them, by the way.  If you have multiple processes
> that need to get at them, you might be better off stuffing the 
> numbers in
> a database somewhere.


On Solaris file locking is flakey - you would need to create your 
own mutex/semaphore to test whether another process is writing to 
the file.  Like CGI processes will likely all try to write to the 
same file at inopportune times...

-Sx-
_________________________________________________________
"Well, in general, the thing I don't like about other
computer languages is that they're not Perl." -Larry Wall