This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: Re: Login Script
From: Nick Urbanik <nicku@iohk.com>
Date: Tue, 16 Mar 1999 22:27:12 +0800
deedsmis@ris.net wrote:
> In Red Hat 5.2, where exactly is the login script?
There are many.
Those that execute at boot time are in /etc/rc.d -- in particular,
/etc/rc.d/rc.sysinit and then /etc/rc.d/rc.local. There are many files in
/etc/rc.d/init.d which are started and stopped as the machine changes "run
levels" as it boots, is shut down, (or any other time it changes run level
:-) You choose which programs ("services" to NT people) are run at startup
by running a program ntsysv which creates symbolic links that you can find in
the /etc/rc.d area.
Then when you log in, the files /etc/profile, /etc/bashrc, ~/.bash_profile,
~/.bashrc are run.
And there are lots more scripts. Okay--so why do you ask? What problem do
you want to solve?
===
Subject: Re: Services on startup
From: "Steve \"Stevers!\" Coile" <scoile@redhat.com>
Date: Thu, 1 Jul 1999 08:55:50 -0400 (EDT)
On Thu, 1 Jul 1999, Nicola Lamarca wrote:
> how can I make a script (which starts several daemons) run on
> startup in a way like the ones in /etc/rc.d/init.d/*.
>
> I don't want to include this script in rc.local !
Put your script in /etc/rc.d/init.d. Then create symbolic links
in /etc/rc.d/rc3.d and rc5.d that point to the script in init.d.
The links should start with an upper-case "S", followed by two digits,
then a name. For instance, "S99mystuff". The "S" indicates that the
link should be followed when starting the system. The "99" determines
when during the boot process the script will execute. Lower numbers
occur sooner. Note that the number should be two digits, so prepend a
zero to single-digit numbers (e.g. "03").
The system startup process feeds the programs
===
Subject: Re: Starting Local - on boot up
From: Jan Carlson <janc@iname.com>
Date: Thu, 10 Jun 1999 14:25:20 -0400
Brian Schneider wrote:
>
> I just did an install of 6.0 and when I boot after starting all the other
> processes it shows a Starting Local line and just sits. If I hit return it
> finishes booting into X just fine. What is this Starting Local?
It is running your /etc/rc.d/rc.local script. That one runs last.
Check for rc.local.rpmsave. If it exists, compare it to rc.local
and make any changes needed.
===
Subject: Re: What starts the default xdm in Redhat ?
From: Jan Carlson <janc@iname.com>
Date: Fri, 09 Jul 1999 12:33:40 -0400
Paul Wilkins wrote:
>
> Mahmut Fettahlioglu wrote
> >It is started in run level 5. You may disable xdm by switching default
> >runlevel in /etc/inittab from 5 to 3, or typing 3 as a kernel parameter
> >in LILO.
>
> Okay, I want to start the login manager.
> After checking the /etc/inittab file I find that it's already on a
> runlevel of 5.
> Changing the runlevel to 3, rebooting, changing back to 5 then rebooting
> again doesn't start the login manager.
>
> How can I get the login manager going? Is it a setting elsewhere which
> could be interfering? Bad files?
Here are the two lines you need in /etc/inittab, for Red Hat 6:
id:5:initdefault:
[several lines not shown]
x:5:respawn:/etc/X11/prefdm -nodaemon
Check to see if you have something not just right.
If it still doesn't work, check /var/log/messages.
Also, does it work to simply type startx
when you are in run level 3?
===
Subject: Re: 6.0 Woes
From: Steve Borho <sborho@ststech.com>
Date: Wed, 30 Jun 1999 10:06:22 -0500
On Wed, Jun 30, 1999 at 11:00:36PM -0400, Dennis wrote:
> Yes, why do they insist on reinventing the wheel every release? Its
> not like they are making it better.
>
> Is there an outline of the system startup somewhere (specifically
> where things get put and how they are run at startup time)? GUIs are
> nice, but sometimes you just need to know how things work when you
> have to do something special. Isn't that the open source concept?
> What good is having source if you cant figure out how to make it
> run?
Some of it is documented here:
http://www.redhat.com/corp/support/docs/sysconfig.html
The rest is documented in the source :^)
===
Subject: Re: dhcp (change to dhcp.conf file)
From: Eric Sisler <esisler@westminster.lib.co.us>
Date: Wed, 08 Dec 1999 19:14:50 -0700
Barry K. Myrvold <bmyrvold@concentric.net> wrote:
>I have a simple question. I made a change to my dhcp.conf file.
>According to the man page to get dhcp working with the new conf file
>I have to use a SIGTERM and the appropriate pid. How do I do this?
>What command do I issue?
Most services/daemons can be restarted by one of the following:
# /etc/rc.d/init.d/name_of_service restart
- or -
# /etc/rc.d/init.d/name_of_service stop
# /etc/rc.d.init.d/name_of_service start
It's generally easier than using 'kill -HUP pid_of_service'. Take a look
at the various scripts in /etc/rc.d/init.d and see what other options they
have - some have a "status" option. Other programs, notably squid, have
switches for the actual binary like so:
squid -k reconfigure
>If I do this while the network is running,
>will it affect the various machines, printers, etc. on the network?
Unless you've hosed your dhcpd.conf file, it won't be down long enough to
matter - a few seconds at most.
>In
>the future, where should I look for this type of general information?
A variety of places - the man pages, the init scripts mentioned above and
possibly /usr/doc/name_of_service are good places to start.
===