Josh Grosse <josh@jggimi.net> writes:
> On Fri, Jan 16, 2026 at 02:52:44PM +0100, Manuel Giraud wrote:
>> Josh Grosse <josh@jggimi.net> writes:
>>
>> > On Fri, Jan 16, 2026 at 11:49:49AM +0100, Manuel Giraud wrote:
>> >> Manuel Giraud <manuel@ledu-giraud.fr> writes:
>> >>
>> >> > Antoine Jacoutot <ajacoutot@bsdfrog.org> writes:
>> >> >
>> >> >> On Mon, Jan 05, 2026 at 11:43:35PM -0500, Josh Grosse wrote:
>> >> >>> Attached is a diff for the most recent beta, released today.
>> >> >>> Tested on amd64.
>> >> >>
>> >> >> Thanks, committed.
>> >> >
>> >> > Hi,
>> >> >
>> >> > I'm used to set transmission's download directory to another place. For
>> >> > this, I modified
>> >> > /var/transmission/.config/transmission-daemon/settings.json with the
>> >> > following (while transmission-daemon is turned off):
>> >> >
>> >> > "download-dir": "/somewhere/else",
>> >> > "incomplete-dir": "/somewhere/else",
>> >> >
>> >> > But now, when I restart transmission-daemon, it does not seem to care
>> >> > and recreate "/var/transmission/Downloads" to start downloading into it.
>> >>
>> >> Maybe this has to do with the important notice here:
>> >> https://github.com/transmission/transmission/blob/main/docs/Editing-Configuration-Files.md#gtk--daemon--cli
>> >> --
>> >> Manuel Giraud
>> >
>> > Is `"incomplete-dir-enabled": true,` ?
>>
>> It was false I have changed to true. But transmission-daemon stills
>> creates /var/transmission/Downloads. But it also seems to be confused:
>> it does not seems to remember correctly what it has already downloaded
>> and what it has not... Quite a mess.
>>
>> Anyway, it seems like a problem from upstream that hopefully will be
>> taken care of ????
>> --
>> Manuel Giraud
>
> The -qt and -gtk settings are stored in a different directory from
> -daemon. You may want to double check you aren't editing the
> wrong .json file by mistake. -daemon settings are in
> ~/.config/transmission-daemon/settings.json, while -gtk/-qt
> settings are in ~/.config/transmission/settings.json.
As you said, it is fixed now. But just to be more precise, I'm using
the transmission_daemon service (via rcctl enable transmission_daemon &&
rcctl start transmission_daemon) and it is working inside
/var/transmission by default.
> You could always delete or move your .json file out-of-the-way, which will
> recreate a default settings.json, then provision with cli options or
> with a connected -qt client, rather than a text editor. If cli or -qt provisioning
> works correctly, you'll know your manual edit was the root cause. If it won't
> work properly using the application tools, then you have found a bug, and
> you could always open a new issue with the upstream project. They would need
> your complete settings.json file, of course.
Well I don't really know because I did not do any manual editing (or
modify any options) before seeing this misbehavior. It seems to me that
upgrading from "transmission-4.1.0beta4" to "transmission-4.1.0beta5",
the transmission-daemon starts filling my /var partition while it was
happily writing elsewhere before that.
--
Manuel Giraud
No comments:
Post a Comment