I have a Java application which performs a swish-e search using
exec(). Once in a while the swish-e process hangs in a loop that looks
like this when i run truss on it. (truss -f -p 10276)


swish-e -f <indexfile> -w quorn*


[...]
10276:  read(3, 0x0004B17C, 8192)                       = 0
10276:  llseek(3, 0, SEEK_CUR)                          = 0x7FFFF5E1
10276:  lseek(3, 0x80002612, SEEK_SET)                  Err#22 EINVAL
10276:  read(3, 0x0004B17C, 8192)                       = 0
10276:  llseek(3, 0, SEEK_CUR)                          = 0x7FFFF5E1
10276:  lseek(3, 0x80002612, SEEK_SET)                  Err#22 EINVAL
10276:  read(3, 0x0004B17C, 8192)                       = 0
[...]


Any ideas what might have happened?

The index <indexfile> is updated (copied from another host) every 2
hours. Is it possible that there could be a problem if it is replaced
exactly while the search is performed?


/Stefan Bergstrand - Polopoly AB


--