Subject: Re: timeout for rc-scripts?
To: Hubert Feyrer <firstname.lastname@example.org>
From: Jason Thorpe <email@example.com>
Date: 06/03/2004 11:00:37
Content-Type: text/plain; charset=US-ASCII; format=flowed
On Jun 3, 2004, at 2:59 AM, Hubert Feyrer wrote:
> Today, I had a machine hang during startup because ypbind wasn't able
> connect to the NIS server. I wonder if it would be possible to
> some timeout after which a start-script would either be aborted, or be
> moved into background, and not just hang the boot process (at the
> administrator's decision)?
In the example you use, doing so would be completely inappropriate.
Consider the case of your amd maps coming from NIS. If you punt on
ypbind and let it try in the background, then amd will start up with no
maps. Blocking on ypbind is completely appropriate.
If this is to be done at all, it should be done by the service that the
script starts up, and ONLY if doing so is "safe" (i.e. does not lead to
incorrect operation later).
-- Jason R. Thorpe <firstname.lastname@example.org>
content-type: application/pgp-signature; x-mac-type=70674453;
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
-----END PGP SIGNATURE-----