[Howto] MLdonkey on TS-109/209

[fabtar]

thanks demm

[Sandokan]

@fabtar

I have just updated MLDonkey to 2.9.5 version on my TS-109 Pro nas, now i get this message in mlnet.log file:

[Ux32] Unix32.write: error, invalid argument len = 0

I get it exactly every 1 hour.

What does it mean?

For the rest it seems to work fine.

Bye!
Sandokan.

[fabtar]

@sandokan
Are you sure the old 2.9.4 has not this "log"?

are you using bundled libraries or you use your qnap system ones?

I'll look in to this.

[Sandokan]

Thank you fabtar for your quick response.

@sandokan
Are you sure the old 2.9.4 has not this "log"?

Yes, i have never seen it with 2.9.4 (full version).
I tried to restore the 2.9.4 full version and the message disappeared.

are you using bundled libraries or you use your qnap system ones?

I'll look in to this.

I'm using the qnap system libraries.
It seem mlnet is searching for something (file or folder) every hour but cannot write/find it, or receive a bad parameter (zero "len" value).
I changed only the executable mlnet and nothing else.
I get this error a couple of minutes after starting mlnet and after that i get it exactly every hour.
I tried to change some "one hour" intervals in the ini files, but the message still remain every hour.

I get this error only with the full version of mlnet 2.9.5, with the normal/normalgd/minimal, i have no errors (i get only a directconnect error, because not implemented in normal version, but specified in downloads.ini)

What could be the problem?

Thank you!
Sandokan.

[Sandokan]

Problem solved!
I don't know how i solved it, i deleted all tmp files, all ini file, mlnet rebuilded them and i reconfigured all.
Now, after using MLDonkey 2.9.5 full version for 4 - 5 hours, the Ux32 error disappeared.

For the moment all is ok.

MLDonkey is a very powerful software, if someone in the future will restore the SUI feature for ARM processors and perhaps will introduce downloading by fileTP with FTP/HTTP authentication, i think it's the best P2P multifunction software ever released.

fabtar, thank you for your interests.

see you soon!
Sandokan.

[fabtar]

A pleasure.
I'm happy to see my cores are working well.
I hope to solve issues about EABI ARM (new kernel versions and hardware) of very recent NASes which prevent to work on new Synologies and qnap-409

[SOb_S]

(locales, unicode, LANG)
[sorry for my english, russian native ]
Solution found here
we need:
1. locales_2.7-6_all.deb
2. belocs-locales-bin_2.4-2.2_armel.deb
3. locale-archive.
search Google for method to unarchive deb's in yours host system ('ar x' under Cygwin, at sample)
unpack data.tar.gz (you have one after deb unpack)
copy usr folder to /opt folder
copy locale-archive to /opt/lib/locale
make symlink from /opt/lib/locale/locale-archive to /usr/lib/locale/locale-archive
try 'locale -a', you should get long list of locales - all fine
add next to your mldonkey-start.sh
export LANG=en_US.utf8
export LANGUAGE=en_US.utf8
try run mldonkey-start.sh
you should get in log: [cO] Language EN, locale UTF-8,
all fine in my case, I get cyrillic filename on disk, not _____.avi

[QNAPAndy]

(locales, unicode, LANG)
[sorry for my english, russian native ]
Solution found here
we need:
1. locales_2.7-6_all.deb
2. belocs-locales-bin_2.4-2.2_armel.deb
search Google for method to unarchive deb's in yours host system ('ar x' under Cygwin, at sample)
unpack data.tar.gz (you have one after deb unpack)
copy usr folder to /opt folder
copy locale-archive to /opt/lib/locale
make symlink from /opt/lib/locale/locale-archive to /usr/lib/locale/locale-archive
try 'locale -a', you should get long list of locales - all fine
add next to your mldonkey-start.sh
export LANG=en_US.utf8
export LANGUAGE=en_US.utf8
try run mldonkey-start.sh
you should get in log: [cO] Language EN, locale UTF-8,
all fine in my case, I get cyrillic filename on disk, not _____.avi

Hi SOb_s,

when untar the package locales_2.7-6_all.deb, and decompress the data.tar.gz I can see 3 files and 2 directories:

etc, usr, control.tar.gz, data.tar.gz and debian-binary.

So which of these is the locale-archive you mentioned?

Thanks

[SOb_S]

…
Hi SOb_s,

when untar the package locales_2.7-6_all.deb, and decompress the data.tar.gz I can see 3 files and 2 directories:

etc, usr, control.tar.gz, data.tar.gz and debian-binary.

So which of these is the locale-archive you mentioned?

Thanks

Oops.
I think, locale-archive here.

[fabtar]

Good idea, you have suggested a good way to fix the locales issue.
I think I'll bundle locales data -lib into my megarchive both with libmagic from the 2.9.6 or 2.9.7 mldonkey release.At the moment I have few other issues to solve