Am I missing something? With the switch from 3.20 to 4.05, I discovered that all my clients were deferring communication for ~20 hours. With the Windows clients it's a simple matter to force an update/connection retry for the project. I would assume that the Linux client's -update_prefs arg would behave in a similar manner, but it doesn't force a connection.

Do I have to touch a file or something or am I doomed to losing a day of runtime here?

trane

You can fiddle with the appropriate field in client_state.xml

Try

Phil

What I meant was

Try <min_rpc_time>




Phil
Liverpool, UK

@Phil

Does doing an edit on the min_rpc_time work?
And when you edit this field is the change permanent?

It seems to work, providing your client is not running when you edit it. The change is not permenant, it only affects the current 'hold'.


Phil
Liverpool, UK

> Try

Phil,

I don't understand the numbers in this field. Can you explain it to me, or give me a clue as to what I should put in here, as I'm having the same problem as Trane, only my client is waiting a further 3 days!

Cheers,

Jim.

---

> I don't understand the numbers in this field. Can you explain it to me, or

They're seconds.

> give me a clue as to what I should put in here, as I'm having the same problem
> as Trane, only my client is waiting a further 3 days!

Shut down the core client, change the field to 0 and, presto, you'll connect.

trane

---