We have several network services hosted on a FreeBSD system, and want it
to come up quickly, so that these services (dhcp, nameservice, nis, tftp
etc) are available when systems are restarting after a prolonged power
failure.
That is, several times a year we have multi-hour power failures
checking the existence of non-existant hardware and would not be appreciable
reduced with a faster CPU or disk. Are there kernel options that we could use
build custom kernel.
___
freebsd-questions@freebsd.org mailing list
In response to Daniel Feenberg [EMAIL PROTECTED]:
We have several network services hosted on a FreeBSD system, and want it
to come up quickly, so that these services (dhcp, nameservice, nis, tftp
etc) are available when systems are restarting after a prolonged power
failure.
That is,
In the last episode (Mar 05), Daniel Feenberg said:
We have several network services hosted on a FreeBSD system, and want
it to come up quickly, so that these services (dhcp, nameservice,
nis, tftp etc) are available when systems are restarting after a
prolonged power failure.
That is,
On Wednesday 05 March 2008 21:06:39 Daniel Feenberg wrote:
About the only thing I can find is to reduce the 10 second boot screen
delay - but we need to cut more than 30 seconds.
The server is statically configured but the clients obtain network
configuration from dhcp and pxeboot with nfs
On Wed, Mar 05, 2008 at 03:06:39PM -0500, Daniel Feenberg wrote:
snip
So, is there advice anywhere about speeding up the boot process? It appears
that most of the 1 minute 45 seconds to boot our system is wait time for
checking the existence of non-existant hardware and would not be
On Wed, 5 Mar 2008, Bill Moran wrote:
In response to Daniel Feenberg [EMAIL PROTECTED]:
We have several network services hosted on a FreeBSD system, and want it
to come up quickly, so that these services (dhcp, nameservice, nis, tftp
etc) are available when systems are restarting after a
I second the statement about BIOS checks taking a long
time. After working with many FreeBSD boxes, mostly Dells and a
few IBM servers, they can take forever (2 to 3 minutes) which
seems like forever when one is trying to get back on line quickly.
If one is using a serial console,
Martin McCormick skrev:
I second the statement about BIOS checks taking a long
time. After working with many FreeBSD boxes, mostly Dells and a
few IBM servers, they can take forever (2 to 3 minutes) which
seems like forever when one is trying to get back on line quickly.
If one
In response to Daniel Feenberg [EMAIL PROTECTED]:
On Wed, 5 Mar 2008, Bill Moran wrote:
In response to Daniel Feenberg [EMAIL PROTECTED]:
We have several network services hosted on a FreeBSD system, and want it
to come up quickly, so that these services (dhcp, nameservice, nis, tftp
Bill Moran wrote:
So, is there advice anywhere about speeding up the boot process? It
appears that most of the 1 minute 45 seconds to boot our system is wait
time for checking the existence of non-existant hardware and would not be
appreciable reduced with a faster CPU or disk. Are there kernel
On Wed, 5 Mar 2008, Kevin Kinsey wrote:
Bill Moran wrote:
So, is there advice anywhere about speeding up the boot process? It
appears that most of the 1 minute 45 seconds to boot our system is wait
time for checking the existence of non-existant hardware and would not
be
appreciable
In the last episode (Mar 05), Daniel Feenberg said:
As for the suggestion that we delay the clients, we plan to enable
memory testing in the BIOS of the clients to delay the first request
for dhcp services. Any delays placed later in the boot sequence won't
help with the problem.
Another
13 matches
Mail list logo
