|Do you know where your variables are?|
Re^2: sysseek and syswrite failsby bloonix (Monk)
|on Oct 15, 2009 at 21:42 UTC||Need Help??|
>>Double check that you're indeed using unbuffered IO everywhere. I am using sysseek, syswrite, sysread.
>>If I understand you correctly, you're forking
>>children to read:
Yes. Each child write its current status to a file that looks like a table.
>>use strace -f instead for the _real_, _complete_
The above strace output was generated with -f for each child.
>>consider to explicitly open the files separately in
>>each child (my bet - issues both for the pointer
>>AND for the locking).
Hmmm, okay, that could be the solution. The parent is forking and the children uses all opened handles of the parent.
I test it! Thanks a lot for the suggestions!
Jonny Update: removed small tags