Nejc S wrote:
Hello,
Afaic this only happens on a power loss or otherwise unclean shutdown
but I used the reboot command from the shell (in a background (sleep
Don't use reboot, use shutdown -r now. I also had the same problem once
(had to get physical access to the box to fix it)
Gunther Mayer wrote:
Don't use reboot, use shutdown -r now. I also had the same problem
once
(had to get physical access to the box to fix it) and it was because
of
the reboot.
Thanks. I guess I'll use shutdown -r now then in future. If it still
happens then I'll post again...
On Thu, Sep 11, 2008 at 04:12:09PM +0200, Michel Talon wrote:
Gunther Mayer wrote:
Don't use reboot, use shutdown -r now. I also had the same problem
once
(had to get physical access to the box to fix it) and it was because
of
the reboot.
Thanks. I guess I'll use
Mike Bristow said:
What's this stuff? shutdown -r is implemented using reboot.
Only when you give it -o. Otherwise it sends a signal to init,
and init manages the shutdown.The code you quote is only
run if -o is given
But the code is init implementing reboot is the same as in the
Hello,
Afaic this only happens on a power loss or otherwise unclean shutdown
but I used the reboot command from the shell (in a background (sleep
Don't use reboot, use shutdown -r now. I also had the same problem once
(had to get physical access to the box to fix it) and it was because of
the
Hi guys,
I recently updated my FreeBSD 6.3 on our server to the latest patch with
freebsd-update and seeing that it involved some kernel patches on 64bit
I had to reboot. So I carried out an automated reboot during low-load
times but alas, the box never came back up again.
After gaining