Re: How to avoid corrupt inittab!

Do you have a question? Post it now! No Registration Necessary

Translate This Thread From English to

Threaded View
The decision is made from either a web interface or a script/program
from a telnet/debug port session.
For example i want to be able to choose to use NTP or not and add this
to automatic start.
The rc-scripts are placed in a read-only filesystem so i can't
write/change anything there while linux is up and running.
Also i want the INIT process to take care of the start-up of programs
and i think it only parses through inittab.

Quoted text here. Click to load it

Re: How to avoid corrupt inittab!
Hallo Goran,

snipped-for-privacy@home.se (Goran) schrieb in

Quoted text here. Click to load it

Starting programs from the inittab is mostly not a good idea, because
there is no shell context. You should prefer starting things from rc-
scripts or, as i did, from an application bootloader, which looks in
a seperat file, what to load. This prgram is started from inittab.

Regards, Kurt

--
PiN - Präsenz im Netz GITmbH
Kurt Harders
We've slightly trimmed the long signature. Click to see the full one.
Re: How to avoid corrupt inittab!
Usually this is done with rc scripts.

Here a single file is called in the beginning and same defines one or
more environment variable values (e.g. a RunLevel or something you
define in a propriety way). This can be used by the following scripts to
do decisions.

-Michael

Re: How to avoid corrupt inittab!
Quoted text here. Click to load it

i have used runlevels to decide what daemons etc. should be started.
the biggest advantage of runlevels are, that you can change the
running programs during your running systems...

it is very useful, if you have x11 installed on a simple linux-box and
you only want to use it for administration purposes...
3 lines to enter and you have a "normal" system for your work ;o)

MMilitsch

Site Timeline