I'm running SuSE-6.3 on my PC with kernel version 2.2.18 and have enjoyed troublefree performance until a few days ago, when the "shutdown" process ceased to work. After the customary lines: URGENT: broadcast message from root: System going down IMMEDIAETLY! ... for maintenance; bounce, bounce... that appear on the console after invoking "halt", "reboot" or "shutdown -h now", the following message is now added: Sending SIGTERM to mortals... This line is repeated once again after some minutes, but nothing more happens. The only solution is to use the reset button (or power down). On reboot, everything works normally (after the inevitable partition checks) until it's time to shutdown or reboot again. Any help will be gratefully received! TIA -- Robin Cosby
Why are you shuting down the system.
Linux is not windows you don't need to reboot every 2 days.
If you have not done an upgrade to the system, kernel, or
some other piece of key software then there is no reason to reboot.
Leave the system up.
Thank You
Ron Blanchett
Monroe Bank & Trust
Assistant Network Administrator
Phone: 242-1811
e-mail: ron.blanchett@mbandt.com
----- Original Message -----
From:
I'm running SuSE-6.3 on my PC with kernel version 2.2.18 and have enjoyed troublefree performance until a few days ago, when the "shutdown" process ceased to work. After the customary lines:
URGENT: broadcast message from root: System going down IMMEDIAETLY! ... for maintenance; bounce, bounce...
that appear on the console after invoking "halt", "reboot" or "shutdown -h now", the following message is now added:
Sending SIGTERM to mortals...
This line is repeated once again after some minutes, but nothing more happens.
The only solution is to use the reset button (or power down). On reboot, everything works normally (after the inevitable partition checks) until it's time to shutdown or reboot again.
Any help will be gratefully received!
TIA
-- Robin Cosby
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Just a short response... Because a system that is up 24/24 7/7 consumes more power than one that is down most of the day. Leaving a system running al the times shortens the lifetime of your hardware, specially the disks... And if you keep a system as long as I (for instance) do, that matters. (plus I'd like to keep my electrical bills down a little).
>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 23/02/2001, 14:10:25, "Ron Blanchett"
Why are you shuting down the system. Linux is not windows you don't need to reboot every 2 days. If you have not done an upgrade to the system, kernel, or some other piece of key software then there is no reason to reboot.
Leave the system up.
Thank You Ron Blanchett Monroe Bank & Trust Assistant Network Administrator Phone: 242-1811 e-mail: ron.blanchett@mbandt.com
Hi, On Fri, 23 Feb 2001, Guy Van Sanden wrote:
Because a system that is up 24/24 7/7 consumes more power than one that is down most of the day.
True.
Leaving a system running al the times shortens the lifetime of your hardware, specially the disks...
Not true at all. The most stressing part for hardware is turning it on. Especially hard disks have a significant lower life time, if they are being turned on and off all the time. LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany Nothing is foolproof, idiots are too ingenious.
On Friday 23 February 2001 08:48, Lenz Grimmer wrote:
Hi,
On Fri, 23 Feb 2001, Guy Van Sanden wrote:
Because a system that is up 24/24 7/7 consumes more power than one that is down most of the day.
True.
Leaving a system running al the times shortens the lifetime of your hardware, specially the disks...
Not true at all. The most stressing part for hardware is turning it on. Especially hard disks have a significant lower life time, if they are being turned on and off all the time.
LenZ
Exactly! I ran my own consulting business for 15 years and for 99% of the calls my clients gave me concerning hardware matters the problem showed up on the power on cycle. Of course, turning off a box can product inductive spikes that damage components as well, but you'll never know it till you power up again. About the only times I encountered hardware problems on running boxes was when they were hit by lightening induced voltage and/or current spikes. Or, they were dropped. A monitor is least susceptible to power cycle failure and has a longer MTBF than components with moving parts, so I will turn the monitor off or use the power saver features. My monitor draws nearly half the wattage my setup requires. JLK -- Athiests believe they know there is no god. Agnostics know they believe there is no god. Thiests believe there is a god. Christians believe in God through His Son, Jesus Christ.
Leave the system up.
Nice idea, but while I'm no member of Friends of the Earth, you're p***ing away a lot of power leaving a system up for weeks if it has no other users than you and you're only on it a couple of hours a day. Great for convenience, less great for the ole global warming ... Again, non-North Americans pay two, three or four hundred percent of US prices for power, which can come into the equation as well. Didn't I hear California is actually running out of power? Switch them off, people, unless someone needs them on, it takes you all of 3 mins to boot. Best to all, Fergus On Friday 23 February 2001 13:10, you wrote:
Why are you shuting down the system. Linux is not windows you don't need to reboot every 2 days. If you have not done an upgrade to the system, kernel, or some other piece of key software then there is no reason to reboot.
Leave the system up.
Nice idea, but while I'm no member of Friends of the Earth, you're
p***ing
away a lot of power leaving a system up for weeks if it has no other users
<etc etc...snipped> Never mind the arguments about how long you "should" leave your system up and running. Has anyone got any ideas about the system hang problem that this started with? I too have the same problem. When I shutdown (nevermind why) then the box hangs when trying to unmount all the filesystems. Is this where your problem was? So anyone with any ideas - I'm sure I'm not alone in saying we'd love to hear from you. Regards, Mark
Hi Mark: On Friday 23 February 2001 09:29, you wrote:
I too have the same problem. When I shutdown (nevermind why) then the box hangs when trying to unmount all the filesystems. Is this where your problem was? So anyone with any ideas - I'm sure I'm not alone in saying we'd love to hear from you.
I found these in the support data base: "Reboot on Shutdown" http://sdb.suse.de/sdb/en/html/mjb_reboot_on_halt.html and "System hangs during shutdown/Error messages from wall" http://sdb.suse.de/sdb/en/html/bk_shutdownfails.html this latter one applies to the ancient SuSE 6.0 but it may shed some light on the problem. -- Cheers, Jonathan
What about us who all run lap-tops where the options for suspend etc etc aren't always fully functional?
On Fri, 23 Feb 2001, Ron Blanchett wrote:
Why are you shuting down the system. Linux is not windows you don't need to reboot every 2 days. If you have not done an upgrade to the system, kernel, or some other piece of key software then there is no reason to reboot.
Wow, that is about the poorest advice I have ever seen. So even if the guys has a problem he shouldn't troubleshoot it? He should just forget about it and never shut his computer down? And you're right, Linux is not Windows, that's why he should figure out why his system is not shutting down properly.
Leave the system up.
Considering that advice is coming from a non-snipping of irrelevant material, top-posting OE user I hope the original questioner passes on that advice and somebody comes up with something useful for him. Greg Thomas http://www.2fortheroad.net
I'm running SuSE-6.3 on my PC with kernel version 2.2.18 and have enjoyed troublefree performance until a few days ago, when the "shutdown" process ceased to work. After the customary lines:
URGENT: broadcast message from root: System going down IMMEDIAETLY! ... for maintenance; bounce, bounce...
that appear on the console after invoking "halt", "reboot" or "shutdown -h now", the following message is now added:
Sending SIGTERM to mortals...
This line is repeated once again after some minutes, but nothing more happens.
the messages... Bounce bounce... and the use of the word mortals ... I guess someone must have been messing arround with this box. check the content of /etc/rc.d/halt... maybe against the original file if possible. Can Anyone on the list, who's running SuSE 6.3 send a working copy of that file to him?
I'm running SuSE-6.3 on my PC with kernel version 2.2.18 and have enjoyed troublefree performance until a few days ago, when the "shutdown" process ceased to work. After the customary lines:
URGENT: broadcast message from root: System going down IMMEDIAETLY! ... for maintenance; bounce, bounce...
that appear on the console after invoking "halt", "reboot" or "shutdown -h now", the following message is now added:
Sending SIGTERM to mortals...
This line is repeated once again after some minutes, but nothing more happens.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
I agree that it looks like someone's been messing with shutdown, but looking in the source for it <code> #ifdef AEROSMITH if (fromshutdown && !strcmp(utmp->ut_user, "tyler")) fputs("Oh hello Mr. Tyler - going DOWN?\r\n", tp); #endif </code> :) On Monday 26 February 2001 17:32, Guy Van Sanden wrote:
the messages...
Bounce bounce... and the use of the word mortals ...
I guess someone must have been messing arround with this box.
check the content of /etc/rc.d/halt... maybe against the original file if possible.
Can Anyone on the list, who's running SuSE 6.3 send a working copy of that file to him?
I'm running SuSE-6.3 on my PC with kernel version 2.2.18 and have enjoyed troublefree performance until a few days ago, when the "shutdown" process ceased to work. After the customary lines:
URGENT: broadcast message from root: System going down IMMEDIAETLY! ... for maintenance; bounce, bounce...
that appear on the console after invoking "halt", "reboot" or "shutdown -h now", the following message is now added:
Sending SIGTERM to mortals...
This line is repeated once again after some minutes, but nothing more happens.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
participants (11)
-
Anders Johansson -
Fergus Wilde -
Francesco Scaglioni -
Greg Thomas -
Guy Van Sanden -
Jerry Kreps -
Jonathan Drews -
Lenz Grimmer -
Mark Daglish -
robin＠cosby.demon.co.uk -
Ron Blanchett