4 ms·
I would desire the yes command to be as slow as possible while still performing its basic function of automatically confirming questions that come up during an
by VintageCool 9y ago
I would desire the yes command to be as slow as possible while still performing its basic function of automatically confirming questions that come up during an installation.
This is because I clusterssh into 40 machines and hey I haven't formally accepted them into my known_hosts file yet so I type "yes" to acknowledge them, but whoops I had already accepted two of them so now they are spitting out the letter 'y' as fast as they possibly can and now I have to wait for all of that output to transfer over the wire onto my machine despite pressing ctrl+c a minute ago.
- Blackthorn 9y agoThen just use yes | head -50? There's no need to artificially slow it down when there are more reasonable means of capping output than relying on SIGINT.
- kqr 9y agoyes | head -50 will not accept new signatures into known_hosts.
- boomlinde 9y agoI'm not familiar with clusterssh, but assuming that it passes flags to ssh you can add `-o StrictHostKeyChecking=no`. Of course, the parameter does what it says, but the security implications are really the same as for blindly yessing your way through. The best is to pre-populate your hosts file using ssh-keyscan.
- VintageCool 9y agoOh, thank you. I was unaware of ssh-keyscan.