-
maledictiumHi guys. I have a doubt. Whenever there is an update to monero (in this case 0.18.1.1), I always recompile the source code to the new release. My node is on another machine. Should I also move and use the resulting binary for the monerod daemon on the machine running the node?
-
grumblemobileAlways best to build on the machine you're running on if you can, unless you know they're the same libwise.
-
grumblemobileBut yes, copying binaries is ok too if it's too much hassle (eg, not enough RAM).
-
grumblemobileIn general, if it starts on the second machine, it'll be alright.
-
grumblemobileIf the second machine is an ARM without HW AES insns, you might get into trouble and need to run with... I forget... some randomx umask env var to disable usage of those.
-
maledictiumYes, they are different versions of debian (stable vs testing) so I will have to recompile due to the lib diferences anyway. My doubt was actually if I could still use the old monerod daemon on the node
-
sech1IIRC that randomx aes thing was fixed in v0.18
-
sech1or even v0.17
-
grumblemobileOld as in previous version ? Not a good idea. New "small number" increases typically fix bugs. Including security ones.
-
maledictiumor if it is always a good ideia to run the most recent version of the node in case of security vulnerabilities
-
maledictiumgrumblemobile: great! It's clarified then. Thanks
-
grumblemobilesech1: as in, it now detects HW AES at runtime ?
-
sech1yes
-
grumblemobileNice.