A new Linux App is available from our Beta Test page.
This App fixes the problem that actually was in the command-line parsing of the 4.12 Beta App (exit status 99, "Ending frequency not contained in SFT (sequence)").
In addition it forces immediate syncing of the checkpoint file (thanks Bikeman!), which should make the checkpointing even more reliable.
BM
BM

GNU/Linux S5R3 App 4.14 available for Beta test
)
Fixed.
BM
BM
RE: If someone from the
)
Sorry, can't say anything about this. The Core Client version that you are using cuts off the diagnostic messages that would help to find out what's wrong.
Core Client version 5.10.25 is said to have this fixed, but I don't know when it will be released to the public.
BM
BM
RE: Any hint? You can put a
)
You can put a file "EAH_NO_SYNC" in the BOINC directory and restart the Client in order not to immediately sync the file. However it would be interesting to know what's causing it. Do you know which filesystem you're using (ext2, ext3, xfs, ReiserF, whatever)?
BM
BM
RE: reiserfs, but it gives
)
Well, the immediate syncing is a new feature, currently probably unique to E@h. ReiserFS is rather unusual, in fact I have not used it for years (and not tested the App on this); this might be the reason for the problems you see. Try to switch off syncing.
BM
BM
RE: Bernd, did you read my
)
I read it. The signal handler used in 4.14 is supposed to give some more information about what's happening there. Actually I'm hoping this error occurs with a 4.14 App. Maybe you can help reproduce it?
BM
BM
RE: Not that I care much
)
We are still working on adapting the credit granting to the large variation in runtime in S5R3. Averaging over about a dozen resuts the credit/h should be similar to other projects (actually a bit more with Linux Apps since version 4.10), but for randomly picked individual results it may differ a lot from the average value.
BM
BM
Good to know. Can you ty to
)
Good to know.
Can you ty to switch off syncing on your XFS machines by putting EAH_NO_SYNC in your BOINC directory? In principle a "can't sync" message shouldn't be tragic, but it may unneccessarily fill up the stderr log.
BM
BM
RE: [edit]Just noticed it
)
Actyally you should do that. I just found that in the code of the 4.14 App the checkpoint is actually not written at all in case of a sync error (has been fixed in the current code).
BM
BM
RE: Where exactly should
)
Probably easiest is to try the new 4.16 App. It will stop syncing automatically after 5 failures.
BM
BM