Jordan Brown (Sun) wrote: Hi,
We had a similar situation with a rc script to install additional software. Depending on the number of software packages to install this could take a very long time -- much longer than the timeout value for rc scripts. To get around the timeout issue we use a wrapper script that starts the installation script in the background and returns imediately. Using this approach we do not have to change the timeout value and we don't have to care about it in the future (if, for example, the installation takes again more time because of additional software to install). regards Bernd > I recently saw: > > Nov 15 18:15:55/3: svc:/milestone/single-user:default: Method or service > exit timed out. Killing contract 30. > > Our product doesn't have any services that run during single-user > startup, but we do have a legacy rcS.d script that could well run for an > hour or more (installing patches). Is there a timeout imposed on legacy > rcS.d scripts? > _______________________________________________ > smf-discuss mailing list > smf-discuss at opensolaris.org > > -- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html M s temprano que tarde el mundo cambiar . Fidel Castro
