[18:37] Today's goal: hack+build seesaw on RPi [18:43] (Would that be the part governing job handling?) [19:07] Actually, hm. Looking through these scripts - it might be best to just roll a fresh OS, set up dependencies, adjust make-data-disk, and let rip [19:51] Scratch that - simply running the scripts falls apart :( [19:51] ~D: [20:10] I'm wondering: would it be useful to have statically linked Wget+Lua binaries? [20:11] Because that would let it run on any system, without installing or compiling anything, correct? [20:11] as long as you ship the libs [20:11] alard: Might be, esp. since it'll run alongside vanilla wget [20:11] I thought that the idea was that the libs are in the binary? [20:11] hmmm not sure [20:11] :D [20:12] then yes, go ahead. [20:12] But I have little experience with that, so it may be a naive idea. [20:13] Hm, so I have Warrior theoretically running, but nothing's showing up when I try and connect [20:13] ok i've asked some clever people :D [20:13] Er, connect to the device locally* [20:13] connect to the device? how so? [20:13] Oh, you can't connect to the pi? [20:14] Smiley: not via HTTP, no [20:14] It doesn't start sshd by default. [20:14] or tornado. [20:14] seesaw =! the web front end. [20:14] afaik. [20:14] Wait, really? [20:14] seesaw == the web front end. [20:14] Kind of odd - I got the "point your browser to xxxx:8001" [20:14] you need to start tornado? [20:14] Or does it pull it in? [20:14] run-pipeline and run-warrior both start a web server. [20:14] alard: ah ok :/ [20:14] then weird. [20:15] shaqfu: Are you connecting to localhost? [20:16] alard: No, device on my LAN [20:16] Here we go - needed to start warrior-runner and not boot [20:16] Ah, you're talking about the warrior scripts. [20:16] Yeah [20:16] go ahead alard with statical linking, it makes sense [20:16] just see what size teh binary comes out at. [20:17] 2.5 MB or so. [20:17] Oh, hey, it runs now [20:17] shaqfu: nice [20:18] shaqfu: Ah, yes, I remember. The boot script is for tty1, it updates the code, shows the splash screen. It tells 'you can start now' to the warrior-runner on tty2. [20:19] Gotcha [20:19] wooo [20:19] (aw - I didn't expect "stop the warrior" to send a halt :( [20:19] https://github.com/ArchiveTeam/warrior-preseed/blob/master/warrior-preseed.cfg#L757-L758 [20:20] Always check the scripts you're running. :) There's a --real-shutdown option that does that. [20:20] urgh [20:20] i really really wanna figure out AMI at some point [20:20] just so dang lazy and so much going on xD [20:20] can someone else jhust do it for me :D [20:21] alard: thankfully the other job I was running was trivial :) [20:21] Seems to be running fine now - just need to make install wget-lua [20:21] But it looks like it shouldn't be too painful to roll a disk image with everything nice and set up [20:22] shaqfu: interested if it's any good ;D [20:22] Mostly just setting up dependencies and clearing out some funkiness with the Pi [20:22] ram could be a big issue depending. [20:22] e.g., lspci breaking [20:22] but if you run the small projects, should be nice [20:22] shaqfu: btw what distro you used as a base? [20:23] Smiley: Raspbian [20:23] alard: what happens if /data runs out of room? does it purge+return the job to queue+take a new one? [20:23] I'm still waiting to hear gentoo runs nicely, and then I'll likely get one [20:23] I'd expect it to blow up in spectacular fashion. [20:24] shaqfu: If Wget fails it should remove the files from that item and start again, I think. [20:24] alard: start the job again, or get a new one? [20:24] No, job fails, remove job, get a new one. [20:24] alard: will his pi rebot every 7 days now? [20:25] Gotcha; awesome. Was just concerned if I hit a runaway job [20:25] I'd think wget would OOM before that. [20:26] doesn't it cache all the links it hasn't yet followed? [20:26] With --real-shutdown it reboots after 7 days, otherwise: no. [20:26] ah ok [20:32] Seems like most of the issues are rising from the scripts expecting the warrior user [20:33] Which are a huge pain now, but not later :) [20:36] alard: do you have any estimates on RAM use for small-medium jobs? [20:37] e.g. anything under 16GB or so, since I doubt many Pis can hold more than that [21:20] Static Wget+Lua: 4.8M. [21:20] warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking [21:20] warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking [21:20] warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking [21:37] Hm, wget-lua isnt building... [21:41] Oh, it expects lua5.1 [22:03] Strange; still isn't building... [23:01] Can the warrior do video jobs? I got a list of 1700 videos [23:01] We would use a python script to grab the video [23:02] 1 video per request [23:02] I am just thinking aloud because getting video is going to be more common [23:42] Weird. I put wget-lua in warrior-code2/wget-lua/, but it won't see it [23:49] omf_: it'd be a nice framework to have.