On Wed, Aug 04, 2004 at 04:45:35PM +0800, John Summerfield wrote:
> Paul Gear wrote:
> >Paul Johnson wrote:
> >>[EMAIL PROTECTED] writes:
> >>>I am new to debina. I have certain services running like lpd rpc etc. In
> >>>RedHat there is a command chkconfig with which i can start/ top services
> >>>for certain run levels or completely stop it from running.
> >>>
> >>
> >>Well, first off, you only have installed an extremely minimal base
> >>system plus anything you've chosen to install. This isn't Hed Rat,
> >>Debian doesn't install a bunch of useless stuff by default.
> >>
> >
> >That is *SO* not the point. chkconfig is a simple way to turn on and
> >off at boot time the important services that you explicitly want to have
> >on. It also provides a convenient overview of which ones are on and off
> >in which levels.
> >
ls /etc/rc* # ???
>
> It also uses the vendor-designed sequencing information. The Debian
> equivalent throws that information so the poor old sysadmin who turns
> stuff off this way has t o puzzle out something that will work when its
> time to reenable it..
Debian doesn't follow the same line described for RH here. That
doesn't make it harder/worse than RH, but it does require a sysadmin to
understand the system s/he is working with, just as anyone using RH has
to learn RH's approach.
The information one needs to reset a service disabled using update-rc.d
is easily pulled from the installation scripts:
grep update-rc.d /var/lib/dpkg/info/* | grep ppp | grep postinst
I'd suggest that _any_ changes made to one's box along these lines
should always be documented in some fashion as a sanity check anyway.
I personally use script, and in this case would have done something
like the following:
script ~/pppRCremove
ls -l /etc/rc*/*ppp* # list the links for future reference
update-rc.d -f ppp remove
exit
> Take this list from a Debian box:
> Numbat:/etc/rc2.d# ls -o
> total 0
> lrwxrwxrwx 1 root 18 2004-08-02 12:01 S10sysklogd -> ../init.d/sysklogd
> lrwxrwxrwx 1 root 15 2004-08-02 12:01 S11klogd -> ../init.d/klogd
> lrwxrwxrwx 1 root 13 2004-08-02 12:01 S14ppp -> ../init.d/ppp
> lrwxrwxrwx 1 root 15 2004-08-02 12:01 S20exim4 -> ../init.d/exim4
> lrwxrwxrwx 1 root 15 2004-08-02 12:01 S20inetd -> ../init.d/inetd
> lrwxrwxrwx 1 root 17 2004-08-02 12:01 S20makedev -> ../init.d/makedev
> lrwxrwxrwx 1 root 17 2004-08-02 12:01 S20postfix -> ../init.d/postfix
> lrwxrwxrwx 1 root 13 2004-08-02 12:01 S20ssh -> ../init.d/ssh
> lrwxrwxrwx 1 root 15 2004-08-02 12:01 S25mdadm -> ../init.d/mdadm
> lrwxrwxrwx 1 root 13 2004-08-02 12:01 S89atd -> ../init.d/atd
> lrwxrwxrwx 1 root 14 2004-08-02 12:01 S89cron -> ../init.d/cron
> lrwxrwxrwx 1 root 19 2004-08-02 12:01 S99rmnologin -> ../init.d/rmnologin
> lrwxrwxrwx 1 root 23 2004-08-02 12:01 S99stop-bootlogd ->
> ../init.d/stop-bootlogd
> Numbat:/etc/rc2.d#
>
>
> If I disable ppp for some time, then want to reenable it I have to
> remember to start it before other processes that might require it to be up.
That is part of the job of the package maintainer, and is stored in the
dpkg scripts noted above. This is Debian's analog to the
"vendor-designed" stored information you refer to below. It helps to
understand the .deb system and use it to one's advantage when needed.
> On RHL this info is stored on the script so that when I turn the
> facility back on, it will be done in the right sequence.
See above.
> btw It's not entirely clear to me that this order is correct.
The tools are there to change it. If you think it should be changed,
try it on your box for a while first, then contact the maintainers/file
a bug if you feel you've found a better/more rational way. If there is
some question about the order, I expect a guru on the list would answer
it.
Kenward
--
In a completely rational society, the best of us would aspire to be
_teachers_ and the rest of us would have to settle for something less,
because passing civilization along from one generation to the next
ought to be the highest honor and the highest responsibility anyone
could have. - Lee Iacocca
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
