what info would help devs solve the checking issue?
Posted: Fri Feb 06, 2009 9:05 pm
Hey guys,
Superb product, few niggles, but hey, it didn't take 30 years to come up with Vista
What info / proceedures / logs might be useful to solve or debug the checking issue. Even in 1.1.2, after a crash, some torrents are stuck in 'checking mode'
I tried the suggested steps:
1- un-automanage the torrent (went ok)
2- pause the torrent (did this with a select all; POOF; deluge segfaulted as soon as it reached the word "sS'paused'" in ~/.config/deluge/state/torrents.state )
That one sorta "bit". Even removing that offender caused all torrents to look 'reset' as new.
One gotcha in the scheme is that I change storage into another directory (same raid5 array) according to what it might be, but still let deluge seed when needed. Lost all that info too.
So, thanks for the good work. Cool idea. and near ideal implementation.
cheers:-)
Superb product, few niggles, but hey, it didn't take 30 years to come up with Vista
What info / proceedures / logs might be useful to solve or debug the checking issue. Even in 1.1.2, after a crash, some torrents are stuck in 'checking mode'
I tried the suggested steps:
1- un-automanage the torrent (went ok)
2- pause the torrent (did this with a select all; POOF; deluge segfaulted as soon as it reached the word "sS'paused'" in ~/.config/deluge/state/torrents.state )
That one sorta "bit". Even removing that offender caused all torrents to look 'reset' as new.
One gotcha in the scheme is that I change storage into another directory (same raid5 array) according to what it might be, but still let deluge seed when needed. Lost all that info too.
So, thanks for the good work. Cool idea. and near ideal implementation.
cheers:-)