transmission 'seed time' not saved between sessions

Hi, I just noticed that the seed time that transmission show to me is totally wrong.

For example I've one torrent that I know for sure that is in seed for 1W and 4D but transmission show to me that the seed time is about 1D, that is the day I restart the transmission service. Transmission don't save the seed time during the reboot? I'm on the last 2.94+, actually ...101a, maybe is for that?

J

Apr 02 '19 17:04 Jorman

Hello Jorman,

I have the same issue here. Do you have any update to share on this case?

Regards

Jan 25 '23 10:01 firesalp

@firesalp No sorry, I had to switch to another client because I need to be "precise" with seeding time

Jan 25 '23 12:01 Jorman

I'm actually surprised that Transmission doesn't show you the total seed time per torrent.

Oct 04 '23 13:10 Pentaphon

This is still an issue on 4.0.4_4 (version as per FreeBSD ports tree install). A reboot or restart of the transmission daemon wipes the seed time for some (but not all) torrents.

Dec 05 '23 15:12 edgeman16

Just a note to mention this still occurs on 4.0.6. I have had a little bit of luck if I pause/stop all torrents prior to shutting down, but it's not consistent (and sometimes there are shutdowns/restarts where the torrents are not all paused/stopped gracefully anyways).

I'd like the "Total Seed Time" data to be accurate(ish... within a day or two at least) as I use external scripts + the API to clean up certain torrents in certain directories after they have been seeding for a certain time (length of time kept seeding varies by directory).

Aug 27 '24 15:08 edgeman16

Should be fairly easy to implement.

The download_done date is been set in the resume file. If the clients reads the time from there, like it does with last_activity .

Seems like it even get read in resume.cc line 688 :DoneDate but nothing be done with it.

Sep 21 '24 09:09 kvanbiesen