00:43:20 <sethsimmons> Is there a way to only make monerod when running make release-static?
00:44:47 <iDunk> ^C after cmake completes config, make -C build/Linux/branch/release daemon
00:45:11 <sethsimmons> thanks
00:45:26 <iDunk> Or just make -C build/Linux/branch/release daemon if not building from a clean state.
04:01:11 <sethsimmons> <iDunk "^C after cmake completes config,"> Is there a way to do this non-interactively?
04:01:24 <sethsimmons> Trying to save some time on Docker image builds and don't want any binaries except monerod
04:39:19 <luigi1111w> .merges
04:39:20 -xmr-pr- 6975 6989 7112 7113 7119 7137 7149 7204 7236 7240 7245 7260 7295
08:13:28 <kayront> anyone else getting very chatty "SYNCHRONIZED OK" messages? 9 in the last 1.5min for me
11:12:41 <selsta> kayront: not here but I run the ban list
11:58:34 <kromgrul> nnedmoney90: Let me quote your hero. 'How do I ban FUK? AAAHHHH I don't remember. youtube.com/watch?v=mdLfkhxIH5Q Keep tryin' champion.
13:16:00 <kayront> selsta: me too, albeit a somewhat outdated one. would that (the messages) be a symptom of misbehaving peers?
13:17:55 <selsta> I don't know as I don't see them on my node yet.
21:53:11 <guest-random1124> Hi there, monero blockchain pruning with the tool takes very long. How can i built in some kind of progress display in the prune function in blockchain_prune.cpp?
21:54:22 <guest-random1124> I created a file where copy_table actions till properties were done, but prune() takes very long
21:57:10 <selsta> guest-random1124: it generally is recommended to sync from scratch with pruning enabled
21:57:21 <selsta> it will most likely be quicker than pruning afterwards
21:59:07 <guest-random1124> Well but i already have a complete blockchain
22:00:12 <guest-random1124> Complete full blockchain
22:09:48 <guest-random1124> Complete sync took a whole week. I do not want to repeat that again
22:16:20 <Mmmmmmmmmm> A whole week =#
22:16:36 <Mmmmmmmmmm> Are you writing down the blockchain on paper?
22:17:41 <guest-random1124> Haha sometimes I have the feeling like that. My notebook is from 2016. not the newest hardware but i also think it should not take that long
22:19:19 <guest-random1124> When I sync it starts very fast, but till 60% it gets slower and slower
22:28:55 <guest-random1124> Sry was disconnected
22:29:12 <guest-random1124> Please repeat if messages during disconnect
22:33:04 <Mmmmmmmmmm> Why don't you use a remote-node?
22:38:38 <guest-random1124> Well I want to contribute the network. But machine utilization is more than I thought
22:55:41 <moneromooo> You're best off resyncing. The in-place pruning is inefficient enough with large databases that resyncing is the best option.
22:56:18 <moneromooo> It used to be OK when the db was smaller. Not the case anymore.
23:31:37 <guest-random1124> @moneromooo i do not use in place pruning. I use the tool, is it very long running anyway?
23:37:18 <guest-random1124> If I understand you right the pruning tool is not good anymore?
23:39:39 <gingeropolous> the pruning tool is good. it just works best if its enabled from the start
23:40:02 <gingeropolous> if you prune *after* synchronizing, the tool has to do more work than if you did it during synchronization guest-random1124
23:41:57 <guest-random1124> Ok. But why?
23:42:28 <guest-random1124> Network connection is slower than hard drive