Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Background in two parts:

  1. I have not tried this due to not having a local machine on which to try currently.
  2. I've a hung, remote server where I can ssh-in, but have only partial sudo access (can send kills, but that's about it).

With the background out of the way, will SIGHUP'ing the init (PID 0) process cause a reboot?

If not, is there a way of accomplishing a reboot without engaging the "real" admin? ie, I'm a delegated in this context.

share|improve this question
up vote 1 down vote accepted

kill -INT 1 reboot the server properly. Find on link text

I just try and it works. It needs root account to be active. Normal users have a "Operation not permitted", happily !

Thanks Google !

share|improve this answer
well, there you go - figures that my google-fu was weak today :) – warren Sep 28 '09 at 8:59
I guess I'm still wondering how "safe" it is, but thanks :) – warren Sep 28 '09 at 9:07
Safe ? If your account is safe, the reboot is safe (it launch the reboot procedure, no crash of the server). The security here is on the root account (or sudo) not on the reboot action – Dom Sep 28 '09 at 10:24
by "safe" I mean is it going to result in a partial reboot / have to call a tech in the remote dc to hit the power button – warren Sep 28 '09 at 12:29

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.