Quota problem /dev/root not existing?

[bcoker]

Richard,

Thank you for your suggestion. Your post made me think of something. So before setting the path I tried something.

I haven't been using;

 su - root

I've been using just;

 su root

I don't recall this ever being an issue before but after using dash/tack after su it works like always. I don't normally login as root either but decided to test it, and it works as normal as well. So I'm a bit confused on what I'm doing differently than what I have normally done. Maybe I'm just getting old..

Either way you helped my figure out the issue so I'm very grateful.

Thanks!

 

[zEitEr]

bash: reboot: command not found

Isn't better to use

shutdown -r now

instead of

reboot

?

I've read something about reboot, that is does hard reset on some *NIX without syncing and so on.

I personally use

shutdown -r now

whenever I need to restart a server.

 

[bcoker]

Isn't better to use

shutdown -r now

instead of

reboot

?

I've read something about reboot, that is does hard reset on some *NIX without syncing and so on.

I personally use

shutdown -r now

whenever I need to restart a server.

I think you are right zEitEr. It's just an old habit that's hard for me to break.

 

[Richard G]

Yes zEiTEr is right indeed. We also always use the shutdown -r command.

However, if it's hard for you to remember, you could delete the reboot in /sbin or if you want to keep the "hard" option, rename it to reboothard and put a reboot.sh in /sbin for example like this:

#!/bin/bash
shutdown -r now

Don't forget to make it executable.

In that case you still can use the reboot command but the server will restart the better way. And you also have the hard reboot command for when it's really necessary.

 

[bcoker]

Richard,

I should have thought of this myself. I think I may do that. It's just one of those things that I can't seem to break and usually i'm doing 10 other things so my brain just doesn't click on not doing it.

Thanks for the tip!

 

[Richard G]

It's no problem, I understand. Somethings I'm doing so many things that I don't think of, or see, another easy solution.
That's what I like about this forum. People help each other also with alternatives, and believe me, I also had my portion of "just did not think of that" myself.

You're welcome and have fun!

 

[bcoker]

For sure. I've been super happy with this community. As I have been with DA. I've hundred of hours fixing WHM and Plesk. Very few fixing with DA, and mostly anytime I did, it was my fault anyway.

 

[nobaloney]

I don't recall this ever being an issue before but after using dash/tack after su it works like always. I don't normally login as root either but decided to test it, and it works as normal as well. So I'm a bit confused on what I'm doing differently than what I have normally done. Maybe I'm just getting old..

The difference is subtle, but important.

Without the - character, su simply sets superuser (root) status, but leaves the environment unchanged.

su -, su -l, and su --login are synonymous, and create an entirely new login environment as root, root's default environment, which may be different, even dangeously different.

Jeff

 

[ditto]

Isn't better to use

shutdown -r now

instead of

reboot

?

I've read something about reboot, that is does hard reset on some *NIX without syncing and so on.

I personally use

shutdown -r now

whenever I need to restart a server.

This is new to me. Since 2009 I have always only used "reboot" command when I need to restart a server. By the way, normally I only restart a server when there is a new kernel. I have never experienced any problems when using the "reboot" command. But I will have to read more about this ...

 

[Richard G]

It might be the case that the reboot command invokes the shutdown command automatically.
I just came across this:

If halt or reboot is called when the system is not in runlevel 0 or 6, in other words when it's running normally, shutdown will be invoked instead (with the -h or -r flag). For more info see the shutdown(8) manpage.

@source: http://linux.about.com/od/commands/l/blcmdl8_reboot.htm
There are also some command line options mentioned for reboot.

 

[zEitEr]

OK, that's said here http://www.redhat.com/mirrors/LDP/LDP/GNU-Linux-Tools-Summary/html/shutting-down.html :

Shutdown ( -r = reboot) the computer immediately. It begins the reboot procedure, press CTRL-C (break-key) to stop it. After the end of the command you can also leave a message in quotation marks which will be broad-casted to all users

and

reboot

The same as shutdown -r now, doesn't take any options, simply reboots the computer immediately.

And from man pages for reboot:

Under older sysvinit releases, reboot and halt should never be called directly. From release 2.74 on halt and reboot invoke shutdown(8) if the system is not in runlevel 0 or 6. This means that if halt or reboot cannot find out the current runlevel (for example, when /var/run/utmp hasn’t been initialized correctly) shutdown will be called, which might not be what you want. Use the -f flag if you want to do a hard halt or reboot.

 

[Richard G]

Well, like you wrote, under older systems it should not be called directly.
Nowadays, it makes not much difference anymore. This is what man reboot on Centos 6 says.

DESCRIPTION
These programs allow a system administrator to reboot, halt or poweroff the system.

When called with --force or when in runlevel 0 or 6, this tool invokes the reboot(2) system call itself and
directly reboots the system. Otherwise this simply invokes the shutdown(8) tool with the appropriate argu-
ments.

However.... I rather keep using the shutdown command.