Everyone,
I have installed Centos 7.0 on my homework machine in order to take a test drive with it, and am low on the learning curve with it at this point. I have a small Gateway SX2855-UB12P.
I have a critical hurdle in that when I try a reboot or when I do a 'shutdown now -r' command the system will start a reboot process but hangs right after the os choices are presented.
My install process started with the server version, and I added the gnome desktop latter. I also changed the boot level to 5.
Has anyone else had this problem, or any suggestions as to a remedy.
Thanks,
Greg Ennis
Everyone,
I have installed Centos 7.0 on my homework machine in order to take a test drive with it, and am low on the learning curve with it at this point. I have a small Gateway SX2855-UB12P.
I have a critical hurdle in that when I try a reboot or when I do a 'shutdown now -r' command the system will start a reboot process but hangs right after the os choices are presented.
My install process started with the server version, and I added the gnome desktop latter. I also changed the boot level to 5.
Has anyone else had this problem, or any suggestions as to a remedy.
Thanks,
Greg Ennis
----------------------------------------
I failed to mention that I can reboot it by powering it down (no need to remove the plug) by pressing and holding the power button which turns everything off, and then hitting the power button again. After this it will boot. Obviously this makes testing this machine remotely impossible.
Greg
On Sun, 23 Nov 2014 13:07:47 -0600 Gregory P. Ennis wrote:
I also changed the boot level to 5.
Do you mean the runlevel? If so, are you sure that you changed it correctly?
Centos 7 doesn't use runlevels set in inittab like previous versions did. I see that fact is actually noted in /etc/inittab, along with the expected way to do it.
Date: Sun, 23 Nov 2014 13:50:17 -0600
On Sun, 23 Nov 2014 13:07:47 -0600 Gregory P. Ennis wrote:
I also changed the boot level to 5.
Do you mean the runlevel? If so, are you sure that you changed it correctly?
Centos 7 doesn't use runlevels set in inittab like previous versions did. I see that fact is actually noted in /etc/inittab, along with the expected way to do it. ---------------------------------------------------------------------------------------------
Frank,
Yes, you are correct, I changed the run level and not boot level to 5 and did so by using the command :
ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
Also, I appreciate everybody's input on this, but I am still at a loss as to how to fix this. Without being able to reboot, it sure makes the set up difficult.
Does anyone else have any ideas??
Greg
On Thu, 2014-11-27 at 18:50 -0600, Gregory P. Ennis wrote:
Date: Sun, 23 Nov 2014 13:50:17 -0600
On Sun, 23 Nov 2014 13:07:47 -0600 Gregory P. Ennis wrote:
I also changed the boot level to 5.
Do you mean the runlevel? If so, are you sure that you changed it correctly?
Centos 7 doesn't use runlevels set in inittab like previous versions did. I see that fact is actually noted in /etc/inittab, along with the expected way to do it.
Frank,
Yes, you are correct, I changed the run level and not boot level to 5 and did so by using the command :
ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
Also, I appreciate everybody's input on this, but I am still at a loss as to how to fix this. Without being able to reboot, it sure makes the set up difficult.
Does anyone else have any ideas??
Greg
I have tried some additional changes that have not made a difference.
I disabled selinux - that made no difference I stopped and disabled firewalld - that made no difference.
I can boot this machine after I turn it off and then back on, but when I try to do a shutdown now -r, the system hangs right after picking the OS that is desired "CentOS Linux..........".
After the machine is turned off the boot process occurs normally after this choice and I get two penguins in the upper left hand corner, and the boot proceeds. When I do a shutdown now -r, I do not get to the penguins and the machine hangs forever until I either unplug it or press the power button for 5 seconds.
Any help would be appreciated!!!
Greg
On Thu, 2014-11-27 at 22:04 -0600, Gregory P. Ennis wrote:
On Thu, 2014-11-27 at 18:50 -0600, Gregory P. Ennis wrote:
Date: Sun, 23 Nov 2014 13:50:17 -0600
On Sun, 23 Nov 2014 13:07:47 -0600 Gregory P. Ennis wrote:
I also changed the boot level to 5.
Do you mean the runlevel? If so, are you sure that you changed it correctly?
Centos 7 doesn't use runlevels set in inittab like previous versions did. I see that fact is actually noted in /etc/inittab, along with the expected way to do it.
Frank,
Yes, you are correct, I changed the run level and not boot level to 5 and did so by using the command :
ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
Also, I appreciate everybody's input on this, but I am still at a loss as to how to fix this. Without being able to reboot, it sure makes the set up difficult.
Does anyone else have any ideas??
Greg
I have tried some additional changes that have not made a difference.
I disabled selinux - that made no difference I stopped and disabled firewalld - that made no difference.
I can boot this machine after I turn it off and then back on, but when I try to do a shutdown now -r, the system hangs right after picking the OS that is desired "CentOS Linux..........".
After the machine is turned off the boot process occurs normally after this choice and I get two penguins in the upper left hand corner, and the boot proceeds. When I do a shutdown now -r, I do not get to the penguins and the machine hangs forever until I either unplug it or press the power button for 5 seconds.
Any help would be appreciated!!!
Greg
-----------------------------------------------------------
Everyone,
I did not get much of a response on the list so I filed a bug report. I wanted to document the bug report for anyone else that is having a reboot problem.
https://bugs.centos.org/view.php?id=7949
Greg Ennis
On 01/12/14 18:36, Gregory P. Ennis wrote:
On Thu, 2014-11-27 at 22:04 -0600, Gregory P. Ennis wrote:
On Thu, 2014-11-27 at 18:50 -0600, Gregory P. Ennis wrote:
Date: Sun, 23 Nov 2014 13:50:17 -0600
On Sun, 23 Nov 2014 13:07:47 -0600 Gregory P. Ennis wrote:
I also changed the boot level to 5.
Do you mean the runlevel? If so, are you sure that you changed it correctly?
Centos 7 doesn't use runlevels set in inittab like previous versions did. I see that fact is actually noted in /etc/inittab, along with the expected way to do it.
Frank,
Yes, you are correct, I changed the run level and not boot level to 5 and did so by using the command :
ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
Also, I appreciate everybody's input on this, but I am still at a loss as to how to fix this. Without being able to reboot, it sure makes the set up difficult.
Does anyone else have any ideas??
Greg
I have tried some additional changes that have not made a difference.
I disabled selinux - that made no difference I stopped and disabled firewalld - that made no difference.
I can boot this machine after I turn it off and then back on, but when I try to do a shutdown now -r, the system hangs right after picking the OS that is desired "CentOS Linux..........".
After the machine is turned off the boot process occurs normally after this choice and I get two penguins in the upper left hand corner, and the boot proceeds. When I do a shutdown now -r, I do not get to the penguins and the machine hangs forever until I either unplug it or press the power button for 5 seconds.
Any help would be appreciated!!!
Greg
Everyone,
I did not get much of a response on the list so I filed a bug report. I wanted to document the bug report for anyone else that is having a reboot problem.
https://bugs.centos.org/view.php?id=7949
Greg Ennis
Seems little point in filing a bug report when you have no idea what the issue is. Bugs are not a means of troubleshooting nor a support forum. However, you did get my attention so lets see if we can stimulate some further interest in troubleshooting this.
So the system will perform a cold reboot, but not a warm reboot. Sounds like a hardware issue to me.
Any clues in /var/log/messages ?
Tried updating the BIOS?
Any hardware firmwares being loaded?
On Mon, 01 Dec 2014 18:50:42 +0000 Ned Slider wrote:
So the system will perform a cold reboot, but not a warm reboot. Sounds like a hardware issue to me.
I had a computer that did that a few years ago. It would reboot about every third time you started it up, otherwise it would hang.
Didn't bother me too much since I rarely rebooted it.
On Mon, Dec 1, 2014 at 12:59 PM, Frank Cox theatre@melvilletheatre.com wrote:
On Mon, 01 Dec 2014 18:50:42 +0000 Ned Slider wrote:
So the system will perform a cold reboot, but not a warm reboot. Sounds like a hardware issue to me.
I had a computer that did that a few years ago. It would reboot about every third time you started it up, otherwise it would hang.
Didn't bother me too much since I rarely rebooted it.
I'd recommend checking to see if there are any firmware updates for the system motherboard.
On Mon, 2014-12-01 at 18:50 +0000, Ned Slider wrote:
On 01/12/14 18:36, Gregory P. Ennis wrote:
On Thu, 2014-11-27 at 22:04 -0600, Gregory P. Ennis wrote:
On Thu, 2014-11-27 at 18:50 -0600, Gregory P. Ennis wrote:
Date: Sun, 23 Nov 2014 13:50:17 -0600
On Sun, 23 Nov 2014 13:07:47 -0600 Gregory P. Ennis wrote:
I also changed the boot level to 5.
Do you mean the runlevel? If so, are you sure that you changed it correctly?
Centos 7 doesn't use runlevels set in inittab like previous versions did. I see that fact is actually noted in /etc/inittab, along with the expected way to do it.
Frank,
Yes, you are correct, I changed the run level and not boot level to 5 and did so by using the command :
ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
Also, I appreciate everybody's input on this, but I am still at a loss as to how to fix this. Without being able to reboot, it sure makes the set up difficult.
Does anyone else have any ideas??
Greg
I have tried some additional changes that have not made a difference.
I disabled selinux - that made no difference I stopped and disabled firewalld - that made no difference.
I can boot this machine after I turn it off and then back on, but when I try to do a shutdown now -r, the system hangs right after picking the OS that is desired "CentOS Linux..........".
After the machine is turned off the boot process occurs normally after this choice and I get two penguins in the upper left hand corner, and the boot proceeds. When I do a shutdown now -r, I do not get to the penguins and the machine hangs forever until I either unplug it or press the power button for 5 seconds.
Any help would be appreciated!!!
Greg
Everyone,
I did not get much of a response on the list so I filed a bug report. I wanted to document the bug report for anyone else that is having a reboot problem.
https://bugs.centos.org/view.php?id=7949
Greg Ennis
Seems little point in filing a bug report when you have no idea what the issue is. Bugs are not a means of troubleshooting nor a support forum. However, you did get my attention so lets see if we can stimulate some further interest in troubleshooting this.
So the system will perform a cold reboot, but not a warm reboot. Sounds like a hardware issue to me.
Any clues in /var/log/messages ?
Tried updating the BIOS?
Any hardware firmwares being loaded?
Ned,
Thanks for your response!!!
Sorry, if posting a bug report was the wrong venue !!!
There are no messages in the message logs that I could identify as problems, but the system fails before the OS is active.
I have not updated the BIOS, and do not know how to do this... but this is my testing machine so I am more than open to doing this. I am using a Gateway SX2855-UB12P. I will take a look at the Gateway site; if there are tutorials you could point me to I would appreciate it.
The only hardware that has been added has been a usb ethernet connection so that I have the motherboard nic card and the usb nic connection. I wanted to use this setup to test the firewalld capabilities for a network gateway. The machine does not have a monitor, and is without a mouse or keyboard.
It should be noted that this machine previously had CentOS 6 with a 3T Seagate drive that worked without a problem, but recently developed a disc failure. I replaced the drive with a 4T WesternDigital drive and installed CentOs 7.0 from a DVD.
Thanks again for your help!!!
Greg
On Tue, 2014-12-02 at 12:34 -0600, Gregory P. Ennis wrote:
On Mon, 2014-12-01 at 18:50 +0000, Ned Slider wrote:
On 01/12/14 18:36, Gregory P. Ennis wrote:
On Thu, 2014-11-27 at 22:04 -0600, Gregory P. Ennis wrote:
On Thu, 2014-11-27 at 18:50 -0600, Gregory P. Ennis wrote:
Date: Sun, 23 Nov 2014 13:50:17 -0600
On Sun, 23 Nov 2014 13:07:47 -0600 Gregory P. Ennis wrote:
I also changed the boot level to 5.
Do you mean the runlevel? If so, are you sure that you changed it correctly?
Centos 7 doesn't use runlevels set in inittab like previous versions did. I see that fact is actually noted in /etc/inittab, along with the expected way to do it.
Frank,
Yes, you are correct, I changed the run level and not boot level to 5 and did so by using the command :
ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
Also, I appreciate everybody's input on this, but I am still at a loss as to how to fix this. Without being able to reboot, it sure makes the set up difficult.
Does anyone else have any ideas??
Greg
I have tried some additional changes that have not made a difference.
I disabled selinux - that made no difference I stopped and disabled firewalld - that made no difference.
I can boot this machine after I turn it off and then back on, but when I try to do a shutdown now -r, the system hangs right after picking the OS that is desired "CentOS Linux..........".
After the machine is turned off the boot process occurs normally after this choice and I get two penguins in the upper left hand corner, and the boot proceeds. When I do a shutdown now -r, I do not get to the penguins and the machine hangs forever until I either unplug it or press the power button for 5 seconds.
Any help would be appreciated!!!
Greg
Everyone,
I did not get much of a response on the list so I filed a bug report. I wanted to document the bug report for anyone else that is having a reboot problem.
https://bugs.centos.org/view.php?id=7949
Greg Ennis
Seems little point in filing a bug report when you have no idea what the issue is. Bugs are not a means of troubleshooting nor a support forum. However, you did get my attention so lets see if we can stimulate some further interest in troubleshooting this.
So the system will perform a cold reboot, but not a warm reboot. Sounds like a hardware issue to me.
Any clues in /var/log/messages ?
Tried updating the BIOS?
Any hardware firmwares being loaded?
Ned,
Thanks for your response!!!
Sorry, if posting a bug report was the wrong venue !!!
There are no messages in the message logs that I could identify as problems, but the system fails before the OS is active.
I have not updated the BIOS, and do not know how to do this... but this is my testing machine so I am more than open to doing this. I am using a Gateway SX2855-UB12P. I will take a look at the Gateway site; if there are tutorials you could point me to I would appreciate it.
The only hardware that has been added has been a usb ethernet connection so that I have the motherboard nic card and the usb nic connection. I wanted to use this setup to test the firewalld capabilities for a network gateway. The machine does not have a monitor, and is without a mouse or keyboard.
It should be noted that this machine previously had CentOS 6 with a 3T Seagate drive that worked without a problem, but recently developed a disc failure. I replaced the drive with a 4T WesternDigital drive and installed CentOs 7.0 from a DVD.
Thanks again for your help!!!
Greg
Ned,
I have printed the bios of this machine below. I reviewed the American Megatrends website, but have not identified whether an upgrade has been created for this bios, or how to install it. This machine was a Windows7 machine originally with a 500G drive, that I removed and replaced with the 3T Seagate drive that failed.
[root@HmWk ~]# dmidecode -t bios -q BIOS Information Vendor: American Megatrends Inc. Version: P01-B2 Release Date: 08/16/2011 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 4096 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 4.6
BIOS Language Information Language Description Format: Long Installable Languages: 1 en|US|iso8859-1 Currently Installed Language: en|US|iso8859-1
Greg
On 02/12/14 18:34, Gregory P. Ennis wrote:
On Mon, 2014-12-01 at 18:50 +0000, Ned Slider wrote:
On 01/12/14 18:36, Gregory P. Ennis wrote:
On Thu, 2014-11-27 at 22:04 -0600, Gregory P. Ennis wrote:
On Thu, 2014-11-27 at 18:50 -0600, Gregory P. Ennis wrote:
Date: Sun, 23 Nov 2014 13:50:17 -0600
On Sun, 23 Nov 2014 13:07:47 -0600 Gregory P. Ennis wrote:
I also changed the boot level to 5.
Do you mean the runlevel? If so, are you sure that you changed it correctly?
Centos 7 doesn't use runlevels set in inittab like previous versions did. I see that fact is actually noted in /etc/inittab, along with the expected way to do it.
Frank,
Yes, you are correct, I changed the run level and not boot level to 5 and did so by using the command :
ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
Also, I appreciate everybody's input on this, but I am still at a loss as to how to fix this. Without being able to reboot, it sure makes the set up difficult.
Does anyone else have any ideas??
Greg
I have tried some additional changes that have not made a difference.
I disabled selinux - that made no difference I stopped and disabled firewalld - that made no difference.
I can boot this machine after I turn it off and then back on, but when I try to do a shutdown now -r, the system hangs right after picking the OS that is desired "CentOS Linux..........".
After the machine is turned off the boot process occurs normally after this choice and I get two penguins in the upper left hand corner, and the boot proceeds. When I do a shutdown now -r, I do not get to the penguins and the machine hangs forever until I either unplug it or press the power button for 5 seconds.
Any help would be appreciated!!!
Greg
Everyone,
I did not get much of a response on the list so I filed a bug report. I wanted to document the bug report for anyone else that is having a reboot problem.
https://bugs.centos.org/view.php?id=7949
Greg Ennis
Seems little point in filing a bug report when you have no idea what the issue is. Bugs are not a means of troubleshooting nor a support forum. However, you did get my attention so lets see if we can stimulate some further interest in troubleshooting this.
So the system will perform a cold reboot, but not a warm reboot. Sounds like a hardware issue to me.
Any clues in /var/log/messages ?
Tried updating the BIOS?
Any hardware firmwares being loaded?
Ned,
Thanks for your response!!!
Sorry, if posting a bug report was the wrong venue !!!
There are no messages in the message logs that I could identify as problems, but the system fails before the OS is active.
I have not updated the BIOS, and do not know how to do this... but this is my testing machine so I am more than open to doing this. I am using a Gateway SX2855-UB12P. I will take a look at the Gateway site; if there are tutorials you could point me to I would appreciate it.
You'd have to check the Gateway website to see if a bios update is available to download for your model. Instructions are normally included / available.
The only hardware that has been added has been a usb ethernet connection so that I have the motherboard nic card and the usb nic connection.
Just to eliminate the easy option first, does unplugging the USB ethernet adapter (before rebooting) solve the problem?
wanted to use this setup to test the firewalld capabilities for a network gateway. The machine does not have a monitor, and is without a mouse or keyboard.
It should be noted that this machine previously had CentOS 6 with a 3T Seagate drive that worked without a problem, but recently developed a disc failure. I replaced the drive with a 4T WesternDigital drive and installed CentOs 7.0 from a DVD.
I wouldn't think the drive swap would make a difference.
Thanks again for your help!!!
Greg
On 11/23/2014 10:58 AM, Gregory P. Ennis wrote:
Everyone,
I have installed Centos 7.0 on my homework machine in order to take a test drive with it, and am low on the learning curve with it at this point. I have a small Gateway SX2855-UB12P.
I have a critical hurdle in that when I try a reboot or when I do a 'shutdown now -r' command the system will start a reboot process but hangs right after the os choices are presented.
My install process started with the server version, and I added the gnome desktop latter. I also changed the boot level to 5.
Has anyone else had this problem, or any suggestions as to a remedy.
Thanks,
Greg Ennis
Centos 7 runs systemd ,so may need to use 'systemctl reboot' to reboot and 'systemctl poweroff' to shutdown system. I suggest to read systemctl manpage ( towards the end)
hope this helps.
On Sun, 23 Nov 2014 12:02:17 -0800 Edward M wrote:
Centos 7 runs systemd
This actually bring up an interesting question that I've not yet seen an answer to:
What is the equivalent of runlevel 1 on Centos 7 and how do you get there?
if you look in /lib/systemd/system
runlevel1.target is a link to rescue.target
I think the command is
systemctl isolate rescue.target
(or runlevel1.target if you prefer)
On Sun, Nov 23, 2014 at 3:15 PM, Frank Cox theatre@melvilletheatre.com wrote:
On Sun, 23 Nov 2014 12:02:17 -0800 Edward M wrote:
Centos 7 runs systemd
This actually bring up an interesting question that I've not yet seen an answer to:
What is the equivalent of runlevel 1 on Centos 7 and how do you get there?
-- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sun, 23 Nov 2014 15:46:59 -0500 Tony Schreiner wrote:
if you look in /lib/systemd/system
runlevel1.target is a link to rescue.target
I think the command is
systemctl isolate rescue.target
(or runlevel1.target if you prefer)
How would you get there from the grub commandline?
haven't actually done it but I'm pretty sure you can still add 1 to the grub2 vmlinuz line
documentation also suggests systemd.unit=rescue.target
On Sun, Nov 23, 2014 at 3:53 PM, Frank Cox theatre@melvilletheatre.com wrote:
On Sun, 23 Nov 2014 15:46:59 -0500 Tony Schreiner wrote:
if you look in /lib/systemd/system
runlevel1.target is a link to rescue.target
I think the command is
systemctl isolate rescue.target
(or runlevel1.target if you prefer)
How would you get there from the grub commandline?
-- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sun, 23 Nov 2014 14:53:14 -0600 Frank Cox wrote:
How would you get there from the grub commandline?
And three seconds after writing that, I found this:
Try passing these arguments on the kernel command line via GRUB : systemd.unit=multi-user.target systemd.unit=emergency.target
From here: https://bbs.archlinux.org/viewtopic.php?id=161576
So I guess that answers that question.
On 11/23/2014 01:01 PM, Frank Cox wrote:
On Sun, 23 Nov 2014 14:53:14 -0600 Frank Cox wrote:
How would you get there from the grub commandline?
And three seconds after writing that, I found this:
Try passing these arguments on the kernel command line via GRUB : systemd.unit=multi-user.target systemd.unit=emergency.target
From here: https://bbs.archlinux.org/viewtopic.php?id=161576
So I guess that answers that question.
Or On Grub2 Default screen press 'e' Goto 'linux' line with arrow keys, then press 'end' key to reach end of line, at the end of line add space, then write 1 (your runlevel number) Press Ctrl +x or F10 to boot
On 11/23/2014 12:02 PM, Edward M wrote:
On 11/23/2014 10:58 AM, Gregory P. Ennis wrote:
Everyone,
I have installed Centos 7.0 on my homework machine in order to take a test drive with it, and am low on the learning curve with it at this point. I have a small Gateway SX2855-UB12P.
I have a critical hurdle in that when I try a reboot or when I do a 'shutdown now -r' command the system will start a reboot process but hangs right after the os choices are presented.
My install process started with the server version, and I added the gnome desktop latter. I also changed the boot level to 5.
Has anyone else had this problem, or any suggestions as to a remedy.
Thanks,
Greg Ennis
Centos 7 runs systemd ,so may need to use 'systemctl reboot' to reboot and 'systemctl
poweroff' to shutdown system. I suggest to read systemctl manpage ( towards the end)
I think the shutdown command on CentOS 7 already reflects that.
# ls -l /usr/sbin/shutdown lrwxrwxrwx. 1 root root 16 Oct 23 16:52 /usr/sbin/shutdown -> ../bin/systemctl # ls -l /usr/sbin/reboot lrwxrwxrwx. 1 root root 16 Oct 23 16:52 /usr/sbin/reboot -> ../bin/systemctl
On 11/23/2014 12:20 PM, Thomas Eriksson wrote:
On 11/23/2014 12:02 PM, Edward M wrote:
On 11/23/2014 10:58 AM, Gregory P. Ennis wrote:
Everyone,
I have installed Centos 7.0 on my homework machine in order to take a test drive with it, and am low on the learning curve with it at this point. I have a small Gateway SX2855-UB12P.
I have a critical hurdle in that when I try a reboot or when I do a 'shutdown now -r' command the system will start a reboot process but hangs right after the os choices are presented.
My install process started with the server version, and I added the gnome desktop latter. I also changed the boot level to 5.
Has anyone else had this problem, or any suggestions as to a remedy.
Thanks,
Greg Ennis
Centos 7 runs systemd ,so may need to use 'systemctl reboot' to reboot and 'systemctl
poweroff' to shutdown system. I suggest to read systemctl manpage ( towards the end)
I think the shutdown command on CentOS 7 already reflects that.
# ls -l /usr/sbin/shutdown lrwxrwxrwx. 1 root root 16 Oct 23 16:52 /usr/sbin/shutdown -> ../bin/systemctl # ls -l /usr/sbin/reboot lrwxrwxrwx. 1 root root 16 Oct 23 16:52 /usr/sbin/reboot -> ../bin/systemctl
Thanks for the tip. I always use systemctl command, was not aware it was linked.