Hot answers tagged restart
The command unity can be used to restart unity. It restarts the window manager, so your open programs will stay intact and you will not be logged out. If you run the command from a terminal app, you should add & disown to detach it from the terminal. If you don't, then the unity program will become a child process of the terminal app such that when you ...
The shutdown on the cog-wheel checks if you are allowed to shutdown the machine. This is done via PolicyKit. In case of shutdown this statement in the file /usr/share/polkit-1/actions/org.freedesktop.consolekit.policy is checked: <action id="org.freedesktop.consolekit.system.stop"> <description>Stop the system</description> ...
Ubuntu is a distribution of the GNU/Linux Operationg System which in turn belongs to the Unix system family - a common architecture for a number of modern Operating Systems. Traditionally Unix used to run on mainframe computers. Central computing facilities which serve dozends or hundreds of users via remote terminals. Since all users relied on the ...
Yes. There a couple of options. 1) You can enable CTRL+SHIFT+BACKSPACE. This three keys will work like CTRL+ALT+SUPR, but they will only restart the GUI. 2) From the command line (press CTRL+ALT+F1 to get to a console) you can restart the Ubuntu display manager (which lets a user login to her preferred GUI) by entering: sudo service lightdm restart 3) ...
The restart button no longer shows up in that list. You need to select Shut Down. In the confirmation box, it asks you if you want Restart, Cancel or Shut Down Screenshots for better understanding
Should I restart when prompted? Yes, you should. For most cases, a restart is required when an update to the Linux kernel has been installed. These updates are usually security updates, and then only come into effect after a reboot. Updates to normal applications such as Firefox come into effect after you restart the program. Firefox should prompt you to do ...
The filesystem will usually go into read-only while the system is running if there is a filesystem consistency issue. This is specified in fstab as errors=remount-ro and will occur when a FS access fails or an emergency read-only remount is requested via Alt+SysRq+U. You can run: sudo fsck -Af -M to force a check of all filesystems. As one of the other ...
The best way to do this will depend on why you want Ubuntu to restart every half hour. So I recommend editing your question to explain why you wish to do this. Rebooting every 30 minutes, and warning users before each reboot: Assuming people might be using the machine, either locally or remotely, it's best to avoid restarting Ubuntu from under them ...
Gdm is still used to manage the desktop sessions, but the Upstart way is sudo service gdm restart. Update: Another option, which isn't using the terminal but using a key combination, can be found at How to set keyboard combination to kill the server?
You can run this command to take down all interfaces: sudo ifdown -a Then run this to bring them back up again: sudo ifup -a Hope that helps! See also: How to restart the networking service?
Note: this answer is from the perspective of a production environment where data loss or downtime can lead to loss of money, customers, industrial equipment malfunctioning, etc. If you are just tinkering with a Raspberry Pi at home, I'd say there's no problem... :) I would not recommend Ubuntu in its default configuration, and the (default) ext4 ...
I found this IRC log from Feb. containing a question and answer session with Peter Graner (pgraner), the Kernel Engineering Manager: <Taek> QUESTION: Is there plans or even talk about having a system update without having to restart or install third party software such as ksplice. <pgraner> Taek, the kernel will support kplice however we ...
Because Linux is commonly used as a server or similar, and SSHing into a linux box, even a normal Ubuntu laptop, is quite common. Thing is, you may not want people with SSH access to be able to shut it down, especially when there may be other remotely logged in users using it. Someone with access to the GUI — well, he can shut it down on his own ...
I love doing this by telling the Session Manager we want to reboot. This can be done without root permissions, and we get a nice window that warns us that the system is going to be rebooted -even we can cancel the reboot if we like to. The Graphical Way - Preferred Method Install gnome-schedule from the Ubuntu Software Center. If you don't want to install ...
The reason you don't need to be root to initiate a shutdown from the GUI is largely a matter of convenience for the typical desktop user. The system knows that you're the user logged in on the console, so if you shut down the computer by mistake, you can presumably turn it back on. For a user in the shell, you might very well be logged in remotely, so the ...
You don't need to open a tty. In most cases Alt-F2 still works. Just enter "unity". That's it. No & disown needed.
The commands start, stop, restart, etc., are links for initctl, and only work for upstart jobs. Calling directly the script in /etc/init.d/ will give a warning for upstart jobs, for which the use of the script is allowed for convenience, through a wrapper symlinked common script. Calling the service command always works, both for upstart jobs and for ...
The old way KDE System Settings > Input Devices > Keyboard;Advanced tab "Key sequence to kill the X server"
Here is the command that solved my problem : mount -o remount / better than a reboot or sudo fsck -Af
Sadly this is a known bug in (probably) consolekit LP #838792 The workaround for the time is sudo reboot sudo shutdown now -P
The Operating System will be fine as long as it is setup for read-only use. LiveCD's have a setup like that, so that you can power them off at anytime, and the OS will not suffer harm. On a read-write drive, ext4 filesystems are very resilient. But no matter the filesystem, any drive that is writable will be subject to corrupt files.
Finally after lot of struggling, I was able to resolve this issue. And I happily writing this answer from the same Ubuntu which I lost for few hours. If the Ubuntu is not booting up, then when the blank screen appears press Ctrl + Alt + (F1 to F6, anything) or goto recover mode to check from the command line. Then, I checked following file: sudo vi ...
Gnome: Open the keyboard preferences (Search for keyboard in Dash), go to the Layout tab and press Options. Open Key sequece to kill the X server and toggle Control + Alt + Backspace KDE: I don't run KDE so I can't verify it or make a pretty screenshot, but according to the Ubuntu Wiki, you do as follows: Open System Settings KDE 4.1 - KDE 4.5 ...
You can prevent service restarts with the Debian policy layer which works on Ubuntu as well. Example: Create a file named /usr/sbin/policy-rc.d with following content (don't forget to make the file executable): #!/bin/sh exit 101 No service¹ would be automatically started/stopped/restarted anymore. See /usr/share/doc/sysv-rc/README.policy-rc.d.gz ...
Run sudo crontab -e from the command line and add this line to the file: 0,30 * * * * reboot This tells the system to run the command reboot every 30 minutes as root. For an overview of the time syntax, see here: http://linuxmoz.com/crontab-syntax-tutorial/
You are not required to reboot the system but you have to log out and log in again. Group membership is evaluated at login time only. If you are in a situation in which logging out and back in is inconvenient (for example, an SSH session) then you can just spawn a login subshell with su - <user> (or equivalently su -l <user> or su --login ...
Ctrl+Alt+Print Screen+R,E,I,S,U,B (Hold down Ctrl, Alt, and Prnt Scrn then press REISUB in that order with about a second pause between each letter) This is a functionality that is a part of the Linux kernel (not just Ubuntu). The only catch is that you have to have the keyboard plugged into the computer (doesn't work remotely).
Good news! Apache is restarting successfully. Apache just isn't sure where you want serve from, so it's choosing your localhost by default. To prevent this message from appearing, clarify that you want to serve from localhost by adding the following line into your /etc/apache2/apache2.conf file: ServerName localhost
Traditionally this was accomplished in linux by using ctrl + alt + backspace. This has been disabled a few releases ago and it used to be easily enabled (with the dontzap package). Nowdays I restart X by using the console and type: sudo killall Xorg Then the GUI will restart and you'll get back to your login manager. Make sure to save everything first.
Only top voted, non community-wiki answers of a minimum length are eligible