Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v0.13.7] Command "system.file_allocate.set" does not exist #178

Closed
pgera opened this issue Aug 19, 2018 · 5 comments
Closed

[v0.13.7] Command "system.file_allocate.set" does not exist #178

pgera opened this issue Aug 19, 2018 · 5 comments

Comments

@pgera
Copy link

pgera commented Aug 19, 2018

OS: RHEL 7
libtorrent config: ./configure --with-posix-fallocate
rtorrent config: ./configure --with-xmlrpc-c --enable-ipv6
File system: lvm-thin + xfs

This option works with older versions of libtorrent/rtorrent on the same system

@chros73
Copy link

chros73 commented Aug 19, 2018

It's called system.file.allocate.set now (and it belongs to rtorrent not libtorrent).
What do you want to set it?

@pgera
Copy link
Author

pgera commented Aug 19, 2018

Thanks. Changing system.file_allocate.set to system.file.allocate.set solved it. No error on launch. My .rtorrent.rc was pretty old, and was using the older convention.

@pgera pgera closed this as completed Aug 19, 2018
@chros73
Copy link

chros73 commented Aug 19, 2018

Do you want to set it to 1? If so, it won't work: #152

@pgera
Copy link
Author

pgera commented Aug 19, 2018

Yes, I wanted to set it to 1 (which is what it was in my old config). Is this a new change in 0.13.7 ? Or does 0.13.6 also have the same issues ?

@chros73
Copy link

chros73 commented Aug 19, 2018

Actually it was worse in v0.13.6 (it randomly applied the behavior of both 0 and 1), in v0.13.7 it always applies 0 no matter you set.
You can try to compile rtorrent-ps-ch to try out the above mentioned partial fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants