How much do I need to worry about this?

Fairlight fairlite at fairlite.com
Tue May 12 12:36:44 PDT 2009


Simon--er, no...it was Nancy Palmquist--said:
> Are you running a WINDOWS version of filePro?  I had the impressing you 
> were running a Unix/Linux version from the talk of Samba.

Samba can be used both ways.  You can mount Windows shares to the *nix
box, or you can create a *nix share for a Windows box to use.

> The errors were like SegViolations on Unix and reported like you see 
> above.  It always seemed to be caused by the system being unable to 
> write fast enough.

That shouldn't be possible, given buffered I/O.  SegV is always memory
mismanagement anyway.  But to get things out of whack enough to do that,
you'd have to make reading/writing non-blocking and get things out of sync.
More likely than not you'd simply be reading incorrect data and still not
generating any segv.  It's in what you do with the data that you might
cause a segv.  But with buffered I/O?  No, not seeing it off the top of my
head.

mark->
-- 
"I'm not subtle. I'm not pretty, and I'll piss off a lot of people along
the way. But I'll get the job done" --Captain Matthew Gideon, "Crusade"


More information about the Filepro-list mailing list