-
Notifications
You must be signed in to change notification settings - Fork 0
Home
The original README may stand on it's own. Alas I am still learning GNUNet and am bound to find improvements on how to get this cat herded, as it were. I'll record such new discoveries here.
So...running this thing as a separate no-login-user, as a systemd service, ...and having to invent/discover how to do that along the way, has been...educational. But it's broken and I know its causing problems.
from the manpage (yeah theres manpages even though compilation fails unless you add --disable-documentation. And theyre pretty in-depth too so that's great. )
" If set to YES, ARM will only start services that are marked as system-level services (and we'll expect a second ARM to be run per-user to run user-level services). Note that in this case you must have manually created a different configuration file with the user where at least this and the START_USER_SERVICES options differ."
basically its expecting two config files! and two instances of 'gnunet-arm' running for two different users! what a holy fucking clusterfuck.
..essentially i just want to back out of the whole system-level/user-level multi-user service setup. its some usage model from the 80s where 10 dudes shared 1 machine under different logins and a complete waste of time on computers where 1 dude runs 10 machines on multiple oses.
yeah its an angry vent but ten days into trying to use this thing and its like wrestling a giant squid.
I really want to like GNUNet. Maybe i will after I make a webui that ties all these disparate things together. If i dont claw my face off before then.
Anyway. I reverted to a single-user setup and its working much better. How to get that done?:
[ ] undo all systemd association
sudo systemctl stop gnunet; sudo systemctl disable gnunet; sudo systemctl daemon-reload
[ ] fix file ownerships
sudo cp /etc/gnunet.conf ~/.config/;sudo chown user ~/.config/gnunet.conf;sudo cp /etc/.my.cnf ~;
..edit the gnunet.conf to point to itself lol, and the sql section also,
[ ] move config file back to ~/.config
[ ] fix mysqld to point to user@localhost instead of gnunet@localhost
now one can run gnunet-arm -s as a normal user and all sorts of things are working that weren't.
A gnunet-arm -I lists services that started properly, and under the multi-user setup 6 out of 5 services were in a failed state.
I'm not sure what the defaults are as they have it in ...bytes? Bits? Its so small the log is full of errors of 'WARNING IT TOOK FOUR MINUTES TO SEND 12 bytes'
I found under [ats] in the gnunet.conf that one can change this. It looks like:
[ats]
WAN_QUOTA_IN = 20000
WAN_QUOTA_OUT = 20000
...the default was 20000. I'm no bytes guru but that divided by 1000000 (how many bytes in a megabyte) gets you '0.02'. Is that 2K/sec? Why does everything feel targeted for the Commodore 64 platform around here. I changed it to what I assume is 2Mbit by adding two zeroes. So now it looks like this:
[ats]
#default was two zeroes less for both:
WAN_QUOTA_IN = 2000000
WAN_QUOTA_OUT = 2000000
...plenty more still to come. Hopefully they'll be less frustrated as I finish the 10 day? 12 day? 14 day? installation process.