Chiliparrot has quit [Ping timeout: 264 seconds]
abathur has joined #nix-darwin
infinisil has joined #nix-darwin
<infinisil> Man, launchd is a dork
<infinisil> How can it be so hard to get something to start on computer startup
<infinisil> (I'm not looking for advice on that btw, I have given up on launchd, I'm just running the command in a terminal now)
<johnw> it's not hard at all in fact
hedgie has quit [Read error: Connection reset by peer]
hedgie_ has joined #nix-darwin
abathur has quit [Ping timeout: 245 seconds]
veske has joined #nix-darwin
Chiliparrot has joined #nix-darwin
veske has quit [Quit: This computer has gone to sleep]
hmpffff has joined #nix-darwin
__monty__ has joined #nix-darwin
__monty__ has quit [Ping timeout: 268 seconds]
__monty__ has joined #nix-darwin
veske has joined #nix-darwin
veske has quit [Quit: This computer has gone to sleep]
<infinisil> johnw: It's not hard if you know how to do it yes
<infinisil> (as with everything)
hedgie_ has quit [Read error: Connection reset by peer]
hedgie has joined #nix-darwin
__monty__ has quit [Ping timeout: 246 seconds]
__monty__ has joined #nix-darwin
<disasm> we're mimicking the nixos-org-configurations setup for mac build slaves with IOHK. The one problem we're running into is our macs keep going to sleep. Does anyone know how to automate them not going to sleep? We tried `caffeinate -s` in `apply.sh` but it still sleeps
<disasm> We're using mojave as base image if that makes a difference
jtojnar has joined #nix-darwin
<cransom> `systemsetup -getcomputersleep` and if not never, `systemsetup -setcomputersleep Never`
hedgie_ has joined #nix-darwin
hedgie has quit [Ping timeout: 244 seconds]
hedgie_ has quit [Remote host closed the connection]
hedgie has joined #nix-darwin
<disasm> we tried that, doesn't work on mojave
<disasm> we found the caffeinate process ran in apply.sh gets terminated when apply.sh finishes
<disasm> We created a launchd daemon to launch caffeinate with restart=Always
<disasm> testing it now
<cransom> i'll sell you some arduinos that wiggle the mouse every 5 minutes
<disasm> would it make sense to have the number of build users configurable? With the heavy weight of OSX's garbage dscl commands, it takes a long time to install nix initially on a system (minutes) because it's creating 32 build users (hard coded, not configurable)
<gchristensen> I think there was some important reason 32 was set
Chiliparrot has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
jtojnar_ has joined #nix-darwin
<LnL> nix fails hard if max-jobs is higher then the available build users and having a larger pool doesn't hurt
<LnL> hardcoding -jX isn't uncommon in tools, especially if it's something where higher concurrency won't really hurt like substitutes
jtojnar has quit [Ping timeout: 272 seconds]
jtojnar_ is now known as jtojnar
__monty__ has quit [Ping timeout: 245 seconds]
__monty__ has joined #nix-darwin
Chiliparrot has joined #nix-darwin
hmpffff has quit [Quit: Bye…]
__monty__ has quit [Ping timeout: 245 seconds]
__monty__ has joined #nix-darwin
Chiliparrot has quit [Quit: Textual IRC Client: www.textualapp.com]
__monty__ has quit [Ping timeout: 246 seconds]
__monty__ has joined #nix-darwin
Chiliparrot has joined #nix-darwin
abathur has joined #nix-darwin
__monty__ has quit [Quit: leaving]
abathur has quit [Ping timeout: 268 seconds]