How to choose services to run at startup

[McDougall, Marshall (FSH)]

Shutdown it the default action when you hit CTRL+ALT+DELETE on a RH
system.  If you look at /etc/inittab you will see the following lines:
# Trap CTRL-ALT-DELETE
ca::ctrlaltdel:/sbin/shutdown -t3 -r now 

The box is working as designed, in this particular respect.

As far your other problem is concerned, you may want to start a new
thread.

Regards, Marshall

-----Original Message-----
From: redhat-list-bounces at redhat.com
[mailto:redhat-list-bounces at redhat.com] On Behalf Of Michael Scully
Sent: Friday, March 24, 2006 12:21 PM
To: 'General Red Hat Linux discussion list'
Subject: RE: How to choose services to run at startup

"Board" members:

	This brings up a related topic for me.  I'll relate a situation
I
found this past weekend.  Sorry that it takes a lengthy explanation.

	I've been having various issues with Dell 2800s and Red Hat
Enterprise 4.  The ATI driver doesn't seem to work correctly, and I've
updated all firmware that Dell has.  When you get the init 5 graphical
console up, you can no longer use CTRL+ALT+F1 (or F2,F3, etc.) to switch
back to character sessions.  The display stays frozen in the GUI screen.
You are no longer controlling it - keyboard and mouse have be redirected
to
the tty1 session, but you have no way to see things.  I can hit
CTRL+ALT+F7
to go back to the X windows session, and all will work well again.

	Anyway, I digress.  After trying some driver changes last
weekend I
rebooted, but I could not get the machine to reboot.  After all the
services
were started and displayed, the screen eventually froze after 60
seconds,
and I got stuck with a display of the text plane of the video card.  I
spent
the next hour or two trying to find what was wrong, but it didn't
actually
turn out to be hardware related.  Unbeknownst to me, a startup process
that
I had in /etc/rc.d/rc.local was hung in an endless loop, due to some
other
configuration changes that occurred since the last time I had rebooted
weeks
earlier.

	I guess this hung process kept RedHat from completing its INIT 5
initialization.  I could tell this because hitting CTRL+ALT+DELETE on
the
keyboard would immediately start shutting things down, which doesn't
happen
unless you're still starting up.  My question is whether or not this is
normal behavior.  It seems like INIT should be able to timeout a start
up
process that doesn't respond, and that seems to be the case with the
normal
/etc/init.d services.  Is /etc/rc.d/rc.local a special case?  Or does
any
script that is to be started by INIT have to have its own timeout and
exit
logic in it, lest it wedge the system?

Scully


-----Original Message-----
From: redhat-list-bounces at redhat.com
[mailto:redhat-list-bounces at redhat.com]
On Behalf Of nilesh vaghela
Sent: Thursday, March 23, 2006 7:20 PM
To: General Red Hat Linux discussion list
Subject: Re: How to choose services to run at startup

you can put startup commands in
/etc/rc.d/rc.local
something like
service squid restart

so when ever you boot the linux it will run the command script what evet
is
there in rc.local

On 3/23/06, Ong Ying Ying <yingy at pc.jaring.my> wrote:
>
> I am using Redhat 7.1 (Seawolf), Linux ver 2.4.2-2.
>
> How do I choose the services I want to run at startup? I do not know
> what program is for what? I don't have a Service Configuration for
> Redhat7.1 version.
>
> Thanks in advance.
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>



--
Nilesh Vaghela

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list