00:05:48 <darsie> I hope the prune needs more than 20 GB extra.
00:17:56 <Mochi101> yes, monero-blockchain-prune
00:18:27 <Mochi101> it'll prune your blockchain data and then it'll stay pruned.
00:18:53 <Mochi101> If I recall correctly you'll have to delete the old, non-pruned chain manually
00:19:39 <darsie> Oh, so I *will* run out of disk space ...
00:19:47 <Mochi101> yes
00:19:51 <Mochi101> :D
00:20:50 <darsie> ok, I'll stop it, then.
00:21:24 <Mochi101> Other way would be to delete the chain and resync pruned
00:21:41 <darsie> with the cli client?
00:21:48 <Mochi101> https://www.getmonero.org/resources/moneropedia/pruning.html
00:21:49 <Mochi101> yes
00:22:25 <Mochi101> Run monerod with --prune-blockchain
00:22:51 <darsie> ah, that's not even a client.
00:22:56 <Mochi101> So delete the blockchain.. then run ./monerod --prune-blockchain
00:23:02 <Mochi101> It's the daemon
00:23:43 <Mochi101> sorry... not the cli... monerod
00:25:45 <darsie> monerod is doing :)
00:29:41 <darsie> 2021-12-05 00:29:23.110 I Synced 163556/2507837 (6%, 2344281 left, 2% of total synced, estimated 8.3 hours left)
00:43:38 <Mochi101> darsie, that'll do it for you.
00:43:50 <Mochi101> then you can run the GUI and it'll stay pruned
00:43:56 <darsie> yay :)
01:33:18 <selsta> 00:29 <nioc> I don't use the GUI but think there is an option  <-- there is now if you sync for the first time
01:34:39 <darsie> thx. too late, though.
01:47:06 <nioc> w0w
01:47:26 <nioc> Did I remember something?
01:51:15 <darsie> nioc: Ahh, right, you mentioned that at first, but then I tried something else ...
01:58:40 <nioc> Vague directions based on vague memories 
01:58:52 <nioc> So helpful lol 
09:24:28 <darsie> looks like a good sync resume after tonights hibernation: https://paste.debian.net/1222111/
10:57:21 <merope> Oh wow, you went into hibernation without even stopping the daemon? Bold move
10:58:36 <merope> Generally speaking, you might want to avoid that - if your blockchain file gets corrupted because the application stopped mid-write, you will have to redo the sync from scratch
11:07:57 <darsie> Is there a way to verify?
11:15:06 <darsie> Generally everything continues to work fine after resume. Well, except network connections.
11:16:54 <darsie> And if a network in an hour long sync would make it fail that would be bad design.
11:17:04 <darsie> network issue*
11:18:50 <merope> Not a network issue, but an issue while writing the data to disk
11:19:21 <merope> If the sync is resuming without issue, then you should be fine
11:26:10 <darsie> Yeah, but I don't seem to have issues with writing to disk due to hibernation, generally.
11:26:52 <darsie> I hibernate every night.
11:26:59 <darsie> my computer and myself :)
15:55:55 <darsie> How can monerod use 613% cpu on an quad core i7-3770?
15:56:11 <raecarruth> o_0
15:56:21 <darsie> Does it have two virtual cpus/core?
15:57:29 <darsie> mhm, 8 cpus. 4 virtual, I think.
15:57:49 <darsie> Using all the power available is good.
15:58:26 <darsie> Fan started blowing.
15:58:50 <darsie> only temporarily
16:06:25 <orly_owl> monero keeps you warm
16:07:23 <nioc> can confirm
16:13:47 <hyc> keeps my cats warm. me not so much.
16:15:03 <hyc> mebbe I should build a footrest out of an array of ARM64 boxes mounted to an aluminum sheet
16:17:23 <orly_owl> arm doesnt produce as much heat as x86 though
16:25:29 <Epsilon> A box of Pentium 4s should keep an entire house warm
16:30:01 <nioc> should market in Japan as a kotatsu
16:34:43 <hyc> even tho it's for the heat production, I'd still prefer to maximize hashes/watt while doing it
16:35:43 <hyc> you can run the array of arm64 boxes using just the aluminum sheet as a heatsink, no fans required
16:35:56 <hyc> x86 if you don't mount a fan the chip will burn itself up
21:17:29 <Guest211111> hello
21:18:58 <Guest211111> where is monero mining
21:19:12 <Guest211111> monero mining channel
21:32:24 <merope> It's not on liberq chat afaik
21:32:27 <merope> Only matrix and telegram 
21:32:33 <merope> #xmrmine:matrix.org 
21:33:03 <merope> https://t.me/xmrmine
22:22:19 <nioc> https://twitter.com/monerujowallet/status/1467612366812684292
22:28:50 <jgreth> \leave
22:28:57 <jgreth> hm
23:19:21 <darsie> 2021-12-05 23:05:50.537 I SYNCHRONIZED OK
23:19:25 <darsie> Does that mean it's ok?
23:24:28 <nioc> darsie: should also show 100% and current block height of 2508517
23:24:33 <nioc> and counting
23:25:00 <merope> well yeah, otherwise it wouldn't be saying OK :P
23:26:05 <nioc> I like to check only because it will say xxx/xxx  yet be at 99%
23:26:16 <nioc> after it says OK
23:26:31 <nioc> .status
23:26:31 <Wallet> nioc: Daemon status: • XMR:ON (2m)
23:26:56 <nioc> not much info there Wallet 
23:27:19 <nioc> some time after it saus OK
23:28:07 <nioc> so yes it is ok but everyday I use the status command to make sure that it still is
23:29:19 <darsie> https://paste.debian.net/1222174/
23:30:48 <merope> yep all good
23:31:07 <nioc> thumbs_up
23:31:13 <darsie> There were worries hibernating during sync could do harm.
23:31:58 <merope> either hibernation is safer than I thought, or you got lucky - either way, you're good for the time being
23:32:05 <darsie> :)
23:34:02 <darsie> But, damn, I'm down to 21 GB free disk space again. lmdb is just 42 G. Where's the rest?
23:34:18 <darsie> du to the rescue ...
23:36:30 <selsta> pruned blockchain?
23:36:44 <nioc> y
23:36:49 <selsta> blockchain is only inside the lmdb folder
23:37:03 <darsie> ./monerod --prune-blockchain
23:37:27 <darsie> And it's only 42 G. Not the previous 114 G.
23:39:13 <darsie> ahh, I looked at an old df -h output ...
23:39:48 <darsie> all ok, 91 GB free.
23:45:01 <darsie> With CPU mining I might find a block in 10 years average.