[Linux] {preferred|final} Deadline: {expires|timeout}

[Manfred.Knick]

EDIT: Original topic "FAHCoreWrapper keywords?" was sub-optimal.

TL;DR: ff to viewtopic.php?f=18&t=34077#p323980

Where do I find any documentation upon FAHCoreWrapper keywords?
Esp.: What is the unit of "-lifeline xxx" ?

[bruce]

I'm not aware of any written documentation for FAHCoreWrapper. Nevertheless, a lifeline is used to verify that another task is (still) running. Typically, if a task is responsible for starting other tasks and one task is terminated, the related tasks should also be terminated. The number xxx is probably a specific task that is currently running in your OS.

[Manfred.Knick]

Thanks!
Sorry for wildly guessing wrongly from the following recent setup:
"...:Running FahCore: .../FahCore_22 ... -lifeline 21450 -checkpoint 3 ..."

Let me re-phrase the question:
... Where (Linux) do I find e.g. the EOL limitation of a WU?
... - in the "log.txt" ?
... - in ./work/* ?
The Windows client exposes
- Assigned
- Timeout
- Expiration
but "WEB CONTROL" does not give as detailed information.

[Manfred.Knick]

In "Welcome To The F@H Support Forum" -> "9 - Importance Of Deadlines" :
viewtopic.php?p=261086&f=24#p261086 ,
PantherX uses the terms "Preferred Deadline" and "Final Deadline".

[Manfred.Knick]

Another (very unimportant) question, if you don't mind - just to learn and understand:
"WEB CONTROL" first advertises the so-long "Estimated Points" of (e.g.) > 78.800, then,
during an > 8.5 min upload, continuously runs them down to "Final credit estimate, 76663.00 points".
Why is that?
The client site is not responsible for the bandwidth limitation of the server side.

[Joe_H]

The points estimate is based on the WU download and upload times that the client has, it is not based on anything server side. Points are based on those times, not the start or finish time.

[semaphore]

The points estimate is based on the WU download and upload times that the client has, it is not based on anything server side. Points are based on those times, not the start or finish time.

This seem to be true
I had a WU that passed the timout.. .and was even close to getting to the "expiration date" (due to a Upload never find a server that could receive the result).

Anyway: I also had that points trickle down... and down... after 3 days it was expecting not to get more than the base points.
But today when server responded, and my upload went through, I got more than those "expected" points.
If it really is a leftover from slow connections (like from 2007), then it will always be wrong for me, due to having 700mbit upload speed
The servers are so bogged down so I never got higher speeds than 15mbit/s. So even if there was code logging my highest speed, the Client has not seen my top speed yet (and it is not configurable as well)

[Manfred.Knick]

... Where (Linux) do I find e.g. the EOL limitation of a WU?

WORKAROUND:
- install e.g. sqlitebrowser
- in ./work/client.db,
- - search table "Units"
- - - for values "Expires" and "Timeout"
- re-calculate the digits to human readable time format
- - with "date -d @xxxxxxxxxxx"