Re: System V initialization

From: P Gentry (rdgentry1_at_cablelynx.com)
Date: 09/21/04 

Date: 21 Sep 2004 07:13:02 -0700

"Baho Utot" <baho-utot@philippines-island.org> wrote in message news:<pan.2004.09.20.23.00.14.192517@philippines-island.org>...
> On Sun, 19 Sep 2004 13:59:20 -0700, P Gentry wrote:
[snip]
>
> > Looking at dhclient-eth0.leases I can see that it was indeed updated at
> > boot when I acquired a new lease on boot this AM. It doesn't make good
> > sense (or seem to be good practice) to attempt to write to these files
> > at shutdown. The needed data has already been saved to disk and you
> > would run the risk of corruption when overwriting them with duplicate
> > data at shutdown. The data should be written when the lease request is
> > acknowledged and given. And you shouldn't have to do this yourself --
> > except by way of the startup init script.
>
> I can't speak to that other then to see the error it belches at shutdown.
>
> I have fixed the problem by changing the order of the scripts in rc6.d.
> The K80network has been move to K39network so it shuts down before
> K60mountfs which mount the filesystem as ro.

Thought you would probably get this working once you sorted out the
shutdown sequence -- perseverence does pay off now and then.

> > Does the source include any init examples? I assume that is why mine
> > calls dhclient in ifup -- to start dhclient and to force a read of the
> > lease file and acquire a new lease if needed.
>
> Yes it does. It has one init script see above
>
> > Except for something not right/gone wrong I can't imagine why you are
> > having to do this. I can understand if you don't have an ifup script
> > that includes the proper calls to dhclient, etc. but that is about all
> > you should have to do.
> >
>
> I just followed the LFS and BLFS books and I didn't want to get too far
> out in left field with this first one. In my opinion the LFS links in
> the rcx.d directories aren't right and you have to move some of them
> around to get the daemons to shutdown logged. They shutdown sysklogd
> before Sendmail, Bind, Sshd and so forth. I don't know about you but I
> LIKE to see those daemons say that they properly shutdown when you
> shutdown the system....it gives me a warm and fuzzy. ;o).

Yes, I agree that those shut down messages/logs are nice -- even more
so when they spit out an error so I'm forewarned on next startup ;-)

> > BTW, your dhcp-3.0pl2.tar.gz is dated 01/15/03 while the newest is
> > dhcp-3.0.1.tar.gz (dated 07/16/04):
> >
> >
> Yes I am aware that. Upon further examination it is the dhcp-3.0.1.tar.gz
> that I installed. Oops It's been a long day ;O)

Your persistence forced me to download the source code and take a look
at it -- no time to compile or look at the included man pages. Also
reviewed the LFS docs to remind me just what scripts they did provide.

I'm not aware of a "simple" ifup script -- slack with their BSD style
init?

The problem with using something like RH scripts as a model is that
they include _every_ imaginable startup configuration so it makes it
harder to follow what's going on. Their version of ifup is indeed
where the dhclient is invoked/started and ifdown is where it is
killed. This part is reasonably clear but there are two areas that
get "complicated".

The first is the handling of aliases -- apparently they weren't
satisfied with the handling provided with ISC source. Shows up in
most every network script. But that may well be something you can
dispense with.

The second, and perhaps problematic, is the handling of resolve.conf.
I couldn't quite figure out entirely why the ISC code was "inadequate"
-- seems to do with some housekeeping that the ISC code doesn't
address re: peer dns. Most likely you can do without that also. Re:
ppp/slip connections and setting hostname -- I couldn't follow through
the trail and don't know if there may be a gotcha there.

In any case, if you have rpm available, you can find all their network
scripts in the initscripts package:
initscripts-7.14-1.i386.rpm << for RH9
http://ftp.redhat.com/pub/redhat/linux/9/en/os/i386/RedHat/RPMS/

Don't know if they will ever prove helpful, though. Makes you realize
that the bootup and shutdown scripts are one of the major additions
that any distro makes to the basic code. And now you have to provide
your own -- hang in there. I would like to say I know _someone_ who
actually carried out an LFS project :)

good luck,
prg
email above disabled

Relevant Pages

  • Re: 2 Times is a "charm"...HELP! :)
    ... These scripts are not ... then Help and Support. ... >> really needing to check with Dell. ... >> your shutdown issues. ...
    (microsoft.public.windowsxp.general)
  • Re: GSoC2007: cnst-sensors.2007-09-13.patch
    ... I don't see why this is needed -- it was not used by the scripts ... As far as I can tell, you're starting a daemon, which means that it should ... significance of the shutdown keyword is. ... scripts in /etc/rc.d include the shutdown keyword. ...
    (freebsd-current)
  • Re: Reg Crontab
    ... These two scripts call a servlet to startup & shutdown the application ... The other two scripts also are related to application which actually does ... If you wish to confirm the origin or content of this communication, ...
    (AIX-L)
  • Going from multiuser to single-user back to multiuser
    ... mode using shutdown -g0 su. ... A couple of the rc2 startup scripts failed to execute properly: ... dlpid: ... or not you go to single-user mode first. ...
    (comp.unix.sco.misc)
  • Re: DHCP leases
    ... That DHCP option will enable me to eliminate my "ipconfig/release" ... shutdown script, thanks for the idea. ... I only have 200 and no more IPs to lease out. ...
    (microsoft.public.windows.server.general)
Loading