Thought I would just send an update on this. Thanks for the all the
suggestions.
To get around our particular issue I just added some retry logic to the
/etc/init.d/ script. When it runs it if finds that the operation has failed
it pauses for a second and will try again. It will try up to three
On Tue, Dec 13, 2011 at 09:44:23AM -0600, Derek McEachern wrote:
Thought I would just send an update on this. Thanks for the all the
suggestions.
To get around our particular issue I just added some retry logic to the
/etc/init.d/ script. When it runs it if finds that the operation has failed
In message 4ee8183b.2050...@ianshome.com, Ian Collins writes:
The zone originally came from a Solaris 10 update 9 system. How do I go
about patching it?
Can you v2v the zone back to an S10 system and then apply the latest
patches there?
John
groenv...@acm.org
On 12/14/11 04:48 PM, John D Groenveld wrote:
In message4ee8183b.2050...@ianshome.com, Ian Collins writes:
The zone originally came from a Solaris 10 update 9 system. How do I go
about patching it?
Can you v2v the zone back to an S10 system and then apply the latest
patches there?
I was
On Wed 14 Dec 2011 at 05:02PM, Ian Collins wrote:
On 12/14/11 04:54 PM, Ian Collins wrote:
On 12/14/11 04:48 PM, John D Groenveld wrote:
In message4ee8183b.2050...@ianshome.com, Ian Collins writes:
The zone originally came from a Solaris 10 update 9 system. How do I go
about patching it?
Can
On 12/14/11 05:06 PM, Mike Gerdts wrote:
On Wed 14 Dec 2011 at 05:02PM, Ian Collins wrote:
On 12/14/11 04:54 PM, Ian Collins wrote:
On 12/14/11 04:48 PM, John D Groenveld wrote:
In message4ee8183b.2050...@ianshome.com, Ian Collins writes:
The zone originally came from a Solaris 10 update 9
