On 02/08/2011 01:26 AM, Eitan Adler wrote:
if I use the *halt* command I just see the system is halted press any
key to reboot
How can I fix this?
shutdown -p now
don't use halt directly
Thanks works as expected ...
Regards,
alokat
___
Hi,
if I use the *halt* command I just see the system is halted press any
key to reboot
How can I fix this?
*
Halt* should cut off my laptop.
Regards,
alokat
___
freebsd-questions@freebsd.org mailing list
On Tue Feb 8 11, Alokat wrote:
Hi,
if I use the *halt* command I just see the system is halted press any
key to reboot
How can I fix this?
*
Halt* should cut off my laptop.
try 'shutdown -p now'
Regards,
alokat
--
a13x
___
On Tue, 2011-02-08 at 01:06 +0100, Alokat wrote:
Hi,
if I use the *halt* command I just see the system is halted press any
key to reboot
How can I fix this?
halt -p
NOTE: May require ACPI support loaded into the kernel.
--
Devin
*
Halt* should cut off my laptop.
Regards,
alokat
if I use the *halt* command I just see the system is halted press any
key to reboot
How can I fix this?
shutdown -p now
don't use halt directly
--
Eitan Adler
___
freebsd-questions@freebsd.org mailing list
On Mon, 2011-02-07 at 19:26 -0500, Eitan Adler wrote:
if I use the *halt* command I just see the system is halted press any
key to reboot
How can I fix this?
shutdown -p now
don't use halt directly
There's no technical reason to avoid using halt directly other than the
fact that
On Mon, 2011-02-07 at 19:26 -0600, Adam Vande More wrote:
On Mon, Feb 7, 2011 at 7:13 PM, Devin Teske dte...@vicor.com wrote:
There's no technical reason to avoid using halt directly other
than the
fact that shutdown sends a message to connected users while
Allow me to split hairs here.
I was taught sync;sync;sync;halt.
One for the father, one for the son, one for the holy spirit.
This, of course, in the days when I/O was slow enough that sync didn't
have time to finish before the halt, so doing it three times ensured
your file system shut down
On Mon, 07 Feb 2011 17:38:50 -0800, Devin Teske dte...@vicor.com wrote:
Of course, many of us still remember the days when it standard fare to
sync; sync; halt.
Erm... what about sync; sync; init 0? :-)
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa,
On Mon, Feb 7, 2011 at 7:13 PM, Devin Teske dte...@vicor.com wrote:
There's no technical reason to avoid using halt directly other than the
fact that shutdown sends a message to connected users while halt does
not.
--
Devin
P.S. I welcome the rebuttle as a learning experience if the above
I used to believe that until I was shown I was wrong. The easiest way to
see you're wrong is to drop to ttyv0 then do one of each like a reboot then
a shutdown -r now. In the latter case, you'll notice /etc/rc.d/ and
/usr/local/etc/rc.d/ stop scripts being processed but not so in the former.
On Mon, Feb 7, 2011 at 8:54 PM, John Levine jo...@iecc.com wrote:
I used to believe that until I was shown I was wrong. The easiest way to
see you're wrong is to drop to ttyv0 then do one of each like a reboot
then
a shutdown -r now. In the latter case, you'll notice /etc/rc.d/ and
It's quite easy to see you're wrong, just follow the steps I outlined
above. If you are correct, reboot(8) should print things like:
Stopping sshd.
to the console.
Sigh. I shut down my FreeBSD 8.1 laptop all the time with halt -p, and I
can assure you it prints all those messages.
You can
On Mon, Feb 7, 2011 at 9:31 PM, John R. Levine jo...@iecc.com wrote:
It's quite easy to see you're wrong, just follow the steps I outlined
above. If you are correct, reboot(8) should print things like:
Stopping sshd.
to the console.
Sigh. I shut down my FreeBSD 8.1 laptop all the time
On Mon, Feb 7, 2011 at 7:31 PM, John R. Levine jo...@iecc.com wrote:
It's quite easy to see you're wrong, just follow the steps I outlined
above. If you are correct, reboot(8) should print things like:
Stopping sshd.
to the console.
Sigh. I shut down my FreeBSD 8.1 laptop all the time
Hmmn, I looked at the code and by golly you're right, halt/reboot doesn't
poke init.
Nonetheless, I really do see a lot of foo stopping messages when I use
halt, presumably because the SIGTERM that halt/reboot sends has the same
effect (if not the same ordering) as the ones that the various
16 matches
Mail list logo
