| 01:15:17 | | nekoxandu quits [Client Quit] |
| 05:45:04 | | @rewby|backup quits [Ping timeout: 252 seconds] |
| 05:46:28 | | rewby|backup (rewby) joins |
| 05:46:28 | | @ChanServ sets mode: +o rewby|backup |
| 07:51:39 | | n9nes quits [Quit: ZNC 1.8.2 - https://znc.in] |
| 07:52:16 | | n9nes joins |
| 10:53:26 | | TastyWiener95 quits [Ping timeout: 252 seconds] |
| 11:49:48 | | Guest41 joins |
| 13:41:57 | | qwertyasdfuiopghjkl quits [Remote host closed the connection] |
| 13:47:57 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 15:08:49 | | Matthww1 quits [Ping timeout: 252 seconds] |
| 15:16:47 | | Matthww1 joins |
| 15:30:45 | | qwertyasdfuiopghjkl quits [Client Quit] |
| 15:32:04 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 16:52:46 | | AK quits [Remote host closed the connection] |
| 19:12:10 | <Ryz> | From https://warriorhq.archiveteam.org/downloads/warrior3/ - regarding from https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior - the current version is 3.2, do I get the beta version of version 3.2 or the non-beta version of 3.2? |
| 19:25:17 | <TheTechRobo> | Ryz: not 100% sure but in general, "beta 3.2" generally means a pre-release of version 3.2, i.e. 3.2 is newer |
| 19:25:19 | <TheTechRobo> | could be wrong though |
| 19:25:34 | <Ryz> | Might need more than one opinion or thoughts on this ><; |
| 19:50:18 | | myself0 (myself) joins |
| 19:50:59 | | myself quits [Read error: Connection reset by peer] |
| 19:50:59 | | myself0 is now known as myself |
| 20:13:44 | | Guest41 is now known as nekoxandu |
| 20:14:17 | | myself quits [Client Quit] |
| 20:14:41 | | myself (myself) joins |
| 20:25:30 | | nekoxandu quits [Client Quit] |
| 21:28:41 | | Guest41 joins |
| 21:33:16 | | Guest41 quits [Ping timeout: 252 seconds] |
| 22:18:04 | <simon816> | Ryz, the non-beta is newer from the timestamps, which again suggests it's the release version |
| 23:09:05 | <Ryz> | Hmm, it says that the amount of hard drive space is '60GB disk usage', at least through VirtualBox; is it possible to shrink it down to 30GB of usage? |
| 23:20:20 | <myself> | I've never had it get anywhere close; my biggest warrior's vmdk has grown to a whopping 3.3GB over months |
| 23:20:26 | <Ryz> | Not certain about 10 GB of usage~ |
| 23:20:43 | <@JAA> | It depends entirely on which projects you run. |
| 23:21:10 | <@JAA> | For projects with small items, it should never use much. |
| 23:21:26 | <@JAA> | That said, virtual disk images get fragmented over time. |
| 23:21:41 | <@JAA> | I think it's covered somewhere on the wiki. |
| 23:22:26 | <Ryz> | Doesn't seem to be covered in https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior - when trying to text search 'defrag' or 'frag' |
| 23:22:41 | <myself> | I was just looking into how to make the host's write-caching as aggressive as possible to hopefully avoid wear on the underlying SSD, since the host box has more than enough RAM to hold all the everything. |
| 23:22:46 | <@JAA> | The warrior will be fine if you reduce the virtual disk size. It might just run out of space on projects with very large items (e.g. anything involving video). |
| 23:23:12 | <@JAA> | https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior#The_Warrior_virtual_machine_is_using_up_disk_space,_even_though_it's_not_running_a_project! |
| 23:25:37 | <Ryz> | Huh, fragmented, even if the hard drive it's on is an SSD? |
| 23:28:04 | <Ryz> | Hmm, sometimes I get a flow of goods, and sometimes not, I'm assuming there's some kind of credit system? |
| 23:36:06 | <@JAA> | It's random, and the tracker seems to be slightly sad at the moment. |
| 23:41:01 | <myself> | fragmentation in the logical structure of the virtual disk file is entirely unrelated to fragmentation in the cylinders-heads-sectors placement of the underlying data on disk. Logical fragmentation is conceptually related to TRIM and stuff, and restricts your ability to shrink the virtual disk file once it's grown. |