Omni rizzler@anarchist.nexus to linuxmemes@lemmy.worldEnglish · 1 day agoLOLanarchist.nexusimagemessage-square66fedilinkarrow-up1410arrow-down126
arrow-up1384arrow-down1imageLOLanarchist.nexusOmni rizzler@anarchist.nexus to linuxmemes@lemmy.worldEnglish · 1 day agomessage-square66fedilink
minus-squareSuccessful_Try543@feddit.orglinkfedilinkarrow-up4·edit-216 hours agoYes, in this command one liner, the system should not power off when the update took too long. Or is yes somehow supposed to take care of this? No, yes is simply answering all questions asked during the update procedure (start upgrade, replace config files, restart services) with “yes”.
minus-squaresomerandomperson@lemmy.dbzer0.comlinkfedilinkarrow-up3·edit-215 hours agoThere’s no timeout for sudo. When permitted, a process runs as root and then closes. Also, the system will still shutdown when update fails because pipes do not care if previous commands exit with a nonzero code, unless pipefail is set. Edit: i’m blind.
Yes, in this
commandone liner, the system should not power off when the update took too long.No,
yesis simply answering all questions asked during the update procedure (start upgrade, replace config files, restart services) with “yes”.There’s no timeout for sudo. When permitted, a process runs as root and then closes.Also, the system will still shutdown when update fails because pipes do not care if previous commands exit with a nonzero code, unlesspipefailis set.Edit: i’m blind.