Re: Deluge not reporting hash-checks properly
Posted: Mon Feb 12, 2024 1:13 am
I'm still unclear here as to the order this is all done.
So - session.state is managed by Deluge and contains the parameters to set libtorrent's operations, yes? While libtorrent's session state information is not unique, it seems Deluge's creation of a file named "session.state" and then using the data in this file to configure the session environment is unique to Deluge.
When you make changes via ltconfig it is clearly modifying the ltconfig.conf file, but is it also modifying session.state?
I'm confused on this point because you say ltconfig knows nothing about session.state, but Deluge also doesn't know anything about ltconfig (as it is a plugin), right?
Can you also specify what specifically would be problematic if one were to delete the session.state as part of Deluge's startup or shutdown process? It would seemingly have to rebuild the ltconfig settings, which I presume it does through what is stored in ltconfig.conf, but does it properly do this on the first restart after session.state is removed? Or is there a race condition where this file would need to be recreated first and then Deluge started again? What other settings (apart from those stored in .conf files) are stored in session.state?
What negative/unexpected effects would occur if no session.state existed upon Deluge launch?
So - session.state is managed by Deluge and contains the parameters to set libtorrent's operations, yes? While libtorrent's session state information is not unique, it seems Deluge's creation of a file named "session.state" and then using the data in this file to configure the session environment is unique to Deluge.
When you make changes via ltconfig it is clearly modifying the ltconfig.conf file, but is it also modifying session.state?
I'm confused on this point because you say ltconfig knows nothing about session.state, but Deluge also doesn't know anything about ltconfig (as it is a plugin), right?
Can you also specify what specifically would be problematic if one were to delete the session.state as part of Deluge's startup or shutdown process? It would seemingly have to rebuild the ltconfig settings, which I presume it does through what is stored in ltconfig.conf, but does it properly do this on the first restart after session.state is removed? Or is there a race condition where this file would need to be recreated first and then Deluge started again? What other settings (apart from those stored in .conf files) are stored in session.state?
What negative/unexpected effects would occur if no session.state existed upon Deluge launch?