73
Can someone explain this command for me?
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Sep 2024
73 points (97.4% liked)
Linux
48214 readers
1188 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
I always try to consult the man pages for these kind of questions (you can search by typing '/' in the man page). Here's what the systemctl manual has to say in the specifications for the
--forceoption:Note that when --force is specified twice the selected operation is executed by systemctl itself, and the system manager is not contacted. This means the command should succeed even when the system manager has crashed.I would use the man pages but my working laptop uses Windows and since the system died i dont have any way to check them until I get home.
Thank you a lot for the answer though, that does explain a lot!
oftentimes (and this is more of a general statement) throwing into google exactly what you would otherwise type into your shell of choice should get you on the right track, ie searching for "man systemctl"
as far as the inability to reboot goes, if a regular
sudo rebootcan't bring the machine back up either then this is probably a hardware issue outside the sphere of the operating system's influence. can't say I experienced something like that myself. I guess the closest I witnessed would be a computer that when rebooted with an old USB-Keyboard plugged in just refused to get past the POST screen. The keyboard worked fine if plugged in later, but the computer couldn't reliably get through the boot process with the thing present. Maybe there's a similar variable to your setup.