this post was submitted on 27 Aug 2025
455 points (94.2% liked)

linuxmemes

27012 readers
1126 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    • Β 

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    455
    LOL (anarchist.nexus)
    submitted 1 day ago by omniman@anarchist.nexus to c/linuxmemes@lemmy.world
    75 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] baltakatei@sopuli.xyz 5 points 1 day ago* (last edited 1 day ago) (2 children)

    Assuming you enter your password upon running sudo, isn't there the risk of sudo's privilege timing out if pacman takes too long to complete? I believe I tried something similar, intending to run a one-liner I could start then walk away from. However, I ended up returning to see the system not rebooted hours later.

    Or is yes somehow supposed to take care of this? Sorry, newish Debian user here who hasn't ventured outside the distribution much.

    [–] Matriks404@lemmy.world 4 points 1 day ago* (last edited 1 day ago) (1 children)

    The command after && runs only if the previous command returns non-error exit status (0), if pacman returns error the latter command won't be executed.

    Additionally there's probably a configuration option for sudo for it to not time out, but it doesn't matter since you can just use systemctl reboot as a normal user to reboot your system (at least on Debian). If that's too long I recommend to add this to your .bashrc (if you use Bash): alias reb='systemctl reboot' or something similar.

    [–] Ziglin@lemmy.world 2 points 15 hours ago

    Maybe this is just a yay thing but I think if sudo priveleges run out while downloading the files it prompts you for your password again before performing the changes. That would lead to it either trying to use the yes output or getting stuck in the password prompt, only failing in the prior.

    This entire problem could be solved by just running it as the root user.

    [–] Successful_Try543@feddit.org 5 points 1 day ago* (last edited 1 day ago) (1 children)

    Yes, 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".

    [–] somerandomperson@lemmy.dbzer0.com 3 points 1 day ago* (last edited 1 day ago)

    ~~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, unless pipefail is set.~~

    Edit: i'm blind.