RE: Anyone have problems with shutdown not working properly?

"Stewart M. Ives" <[email protected]>
Newsgroups gmane.linux.redhat.release.enigma
Message-ID <[email protected]>
[email protected] wrote:
> Hello,
> I have a Compaq ML530 Server running Redhat 7.2 and when I do a
> "shutdown" it will not run all of the shutdown scripts linked in the

shutdown??  I'll have to look that command up.  I think the last time I
used that command was 2 years ago when I had to change the batteries in the
UPS.  I didn't know you ever had to shut down a linux server.  Nice of them
to include such a command for those strange times when you actually do have
to shutdown the server.  Besides changing the batteries in the UPS the only
other time I can even think of shutting down the server is in the even of a
flood.

Now windoz, that's another story.  I'm VERY familiar with that "Shut
Down..." command.  Use it all the time.  Gee, it's even spelled
differently.

I'll get back to you on your question.

stew

> /etc/rc5.d directory.  I'm specifically looking for it to do a
> Continuus shutdown.  It boots up fine and goes to runlevel 5 like it
> should but the shutdown doesn't work properly.  Also when you watch
> the shutdown from the console you don't see all of the shutdown
> messages - it cuts from X to the hardware boot-up screen, i.e. memory
> check, Raid check, etc.  I have checked /var/log/messages and the
> last messages are: Mar 11 19:00:27 tcontinuus syslog: klogd shutdown
> succeeded Mar 11 19:00:27 tcontinuus exiting on signal 15 Anyone seen
> this before in RH7.2? Regards, Mike
> ---
> Mike Shaw            VOICE: +1 (317)306-3084
> Raytheon Technical Services
> UNIX Administrator     FAX:  +1 (317)306-4253
> INET: [email protected]


---
Outgoing SofTEC USA mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.461 / Virus Database: 260 - Release Date: 3/10/2003
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.