Interrupted System Call

[Barry Wiseman]

filepro 5.0.13
SunOS 5.9

This is a busy system with hundreds of users.  They are intermittently 
experiencing a failure on one particular automatic index.  Programs 
attempting a lookup free to that file receive:

	A System Error Has Occurred
	/u/appl/filepro/payable/index.B

	Interrupted system call

The PID of the program throwing this error appears in showlock's output:

#showlock index.B
index.B:
     00000000 00000000 11684

I understand this to mean that there are zero bytes locked at offset 
zero in the file.  Huh?

The user's solution when this happens has been to manually remove the 
index and lockfile, and rebuild the index -- an alarming prospect since 
as I said hundreds of filepro programs are still running, many of which 
access this file, so this procedure surely causes as many problems as it 
solves.

Anybody know what the "Interrupted system call" could signify in this 
context?  I haven't yet had a chance to inspect the "bad" index when 
this happens.