ChanServ changed the topic of #nixus to: Nixus is an experimental deployment tool for NixOS systems - https://github.com/Infinisil/nixus - https://logs.nix.samueldr.com/nixus/
veleiro has joined #nixus
veleiro` has joined #nixus
veleiro has quit [Ping timeout: 240 seconds]
veleiro` is now known as veleiro
veleiro has joined #nixus
veleiro has quit [Changing host]
veleiro has quit [Remote host closed the connection]
veleiro has joined #nixus
cole-h has quit [Ping timeout: 240 seconds]
cole-h has joined #nixus
veleiro has quit [Remote host closed the connection]
veleiro has joined #nixus
cole-h has quit [Ping timeout: 240 seconds]
<veleiro> im trying to figure out what waitConfirm does
<veleiro>
<veleiro> what is <>(pipe)
<veleiro> wait for input or output?
<infinisil> veleiro: It waits until switch-active is called
<infinisil> Which is done periodically by the deployment script
<veleiro> ok thanks!
<veleiro> I cant figure out this ssh connection refused problem
<infinisil> veleiro: Ah is this you who opened the github issue?
<infinisil> Usually such a problem indicates that there's a problem with the ssh config, such as not having set up the correct public key
<infinisil> But if that's not the case, it could be that the successTimeout is top low, which can happen with slow disks
<veleiro> yes
<veleiro> my guess is its the ssh config, working on trying it somewhere else currently
<veleiro> that's why I was trying to find out more about the state of my NixOS
<veleiro> Earlier this year I tried to rename my primary user but i did it wrong
<veleiro> and ended up with a profile across 2 profiles
<veleiro> i often see password key dialogues that refer to the old account
<veleiro> thanks!
<infinisil> veleiro: In case you want to try the success timeout thing, that would be `nodes.myNode.successTimeout = 60` (default is 20 (seconds))
<veleiro> yep, already tried that