https://bugs.winehq.org/show_bug.cgi?id=55026
--- Comment #14 from Artem S. Tashkinov aros@gmx.com --- (In reply to Fabian Maurer from comment #13)
- There's some multiplication going on, so this variable has a maximum of
around 280 seconds or something (would be nice if someone told me what's its maximum is exactly) - which is a bit of bummer.
It's a 64bit multiplication, so there isn't really a limit. Only limit is, it can't be bigger than the 32bit signed integer maximum. Unless I overlooked something, of course. Did you run into troubles using bigger numbers?
The problem with the original code you modified
timeout_t save_period = 600 * -TICKS_PER_SEC
was this being 32bit multiplication.
I don't follow, sorry. My manual method resulted in an overflow due to multiplication in 32bit mode, now you say it's a 64bit variable. I'm confused.
- wineserver only reads it on startup, so you cannot adjust it at runtime
i.e. dynamically.
As it currently is, every time the registry is saved, it re-evaluates the save-time interval. That should make it easy switching from a 30 second interval to never, but the other way round is impossible. Is that good enough, or do you have a suggestion on how to improve it? Not sure how that would reasonably work. I could monitor all changes to the registry, but that seems like a bad performance impact.
That's actually fine! I've already wasted too much of your time to ask for more.