If you're updating, why wouldn't you just put the override files as the "stock" files and forget about the overrides altogether?
Cheers, Bernard > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Ben Hartshorne > Sent: Monday, January 09, 2006 18:10 > To: [email protected] > Subject: Re: [Sisuite-users] overrides and timing issues > > On Mon, Jan 09, 2006 at 04:08:48PM -0800, Bernard Li wrote: > > You won't be running apache during imaging, the server needs to be > > rebooted (into the SystemImager kernel) before imaging can occur. > > > > Updating is a different story though. > > I'm sorry, I mispoke. I meant updating, not imaging. You are quite > correct that apache will not be running during the initial image, but > the initial image is the least of my worries. In my environment, I > expect to be running an automated update nightly. As time goes on, it > becomes more likely that something dependant on one of these overrides > being there increases. > > Thoughts? > > -ben > > > -- > Ben Hartshorne > email: [EMAIL PROTECTED] > http://ben.hartshorne.net > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
