-
puffybufI had to give up with OpenBSD monerod . it kept crashing and corrupting my entire DB. So I'm emulating Linux on obsd and running it there :) Runs much better too, no slow downs and freezing my system
-
m-relay<ofrnxmr:xmr.mx> Even if you changed the db sync mode to something like fast:async?
-
puffybufyea it would still freeze up now and then. I just don't have the skills to debug it. Async would keep my system from freezing, but all operations on that HD would stop for 30 seconds or so until it finished.
-
puffybufI got a new HD and did a read-write badblocks test on it. And ran memtest
-
puffybufI think it's the code (and OS)
-
falsePreTextHi, the docs for wallet-rpc is somewhat vague regarding mixin and ring_size values. I understand that since the latest hard fork the ring_size is fixed in the "network" and thus setting these should not be applicable? Looking at the feather wallet source code they go with a 11 for mixin as a constant.
-
m-relay<ofrnxmr:xmr.mx> Its ignored for new txs
-
m-relay<ofrnxmr:xmr.mx> i think it might apply when spending old (v1?) Outputs
-
falsePreTextthanks
-
m-relay<jeffro256:monero.social> Can we add #10111 to the merge queue soon, please? A lot of crypto depends on that commit and it seems to have received decent review given its relatively small size
-
m-relay<datahoarder:monero.social> monerod with --rpc-login test:test2
-
m-relay<datahoarder:monero.social> doesn't work:
-
m-relay<datahoarder:monero.social> ```
-
m-relay<datahoarder:monero.social> curl --verbose -H "Connection: close" --digest -u test:test2 --digest 127.0.0.1:18081/get_info
-
m-relay<datahoarder:monero.social> ```
-
m-relay<datahoarder:monero.social> works:
-
m-relay<datahoarder:monero.social> ```
-
m-relay<datahoarder:monero.social> curl --verbose --digest -u test:test2 --digest 127.0.0.1:18081/get_info
-
m-relay<datahoarder:monero.social> ```
-
m-relay<datahoarder:monero.social> RPC expects the connection to be kept open/reused for context. But if connection is not reused, the context is started anew and it can never have successful auth.
-
m-relay<ofrnxmr:xmr.mx> Cc [@vtnerd:monero.social](https://matrix.to/#/@vtnerd:monero.social) for rereview
-
m-relay<datahoarder:monero.social> This is not RFC 2617 as mentioned in the code. RFC 2617 does not require connection to be kept open or reused
-
m-relay<datahoarder:monero.social> Seems monero-project/monero #8871 was hitting the same issue