[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: httpd not running after reboot
- From: "Robert M. Riches Jr." <richesr1 inetarena com>
- To: axp-list redhat com
- Subject: Re: httpd not running after reboot
- Date: Thu, 14 Feb 2002 13:27:19 -0800
> From: Mark Arrasmith <arrasmith@math.twsu.edu>
> Date: Thu, 14 Feb 2002 14:56:51 -0600
>
> > From: "Robert M. Riches Jr." <richesr1@inetarena.com>
> >
> > > Maybe this is too obvious, but one kludgey workaround would be
> > > to put in a script to happen just before Apache tries to start,
> > > and have that script do a bunch of disk I/O.
> > >
>
> Works, but it adds 2 to 3 min's to the startup. I wonder what the real
> problem is.
Then, I would suggest doing just the minimum amount of disk I/O
to get Apache to start up.
Control of how much disk I/O is done could be accomplished by
piping the output of "find" to "head -40000" (or some other
number), provided this pipeline would cut off the "find" command
when the "head" command quit reading from stdin. In the worst
case, a short C program or Perl script could read from the disk
until some end-point criterion was met.
Static determination of the needed amount could be done by trying
different amounts. Binary search should find a close-to-optimal
solution in fairly short order.
It might be possible to do dynamic determination of the needed
amount by putting the "find" or other disk I/O generator in the
background, periodically checking for the presence of an "httpd"
process or some file that indicates Apache had started. That's
essentially what I do with the X server on my system.
Good luck.
Robert Riches
richesr1@inetarena.com
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[]