Dr Lou wrote, On 05/22/10 04:03:
LW,
Thanks for your reply - but my question wasn't on [i]prophylaxis...[/i]
The point was to generate a little 'creative destruction', then to test what
resources openSolaris has for [i]treatment.[/i]
So now, if this [i][/i]were, really,[b][/b] a damaged production environment,
what steps would one take? Please be explicit. As a support firm, let's say
you're faced with a client who's destroyed his environment.
If this was a production environment I would ABSOLUTELY have an
Alternative Boot Environment (ABE) in place at all times. This option
had been available since Solaris 9 and is a real life/stress saver for
any serious UNIX administration. The ABE is a snapshot so the person
playing with the system to add updates or new packages needs to remember
to rebuild the ABE before playing so that they have the current running
environment to recover to if needed.
I have several ABE of different versions of OpenSolaris but I have an
ABE of the running one as a CYA and this is just for my desktop. Look
at "man beadm" for OpenSolaris.
r...@mxxx:~# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
134a - - 20.95M static 2010-04-29 13:31
134a-1 NR / 22.21G static 2010-05-21 09:26
134a-1-ABE - - 106.0K static 2010-05-24 08:10
opensolaris-sru8 - - 32.64M static 2010-01-29 13:42
opensolaris-sru9 - - 139.97M static 2010-03-04 09:50
The pkg command does have all the options needed as "man pkg" shows but
it assumes the affected server has access to a IPS repository.
Check to see if your IPS repository is set but only you can know if it
is a valid one
pkg publisher
Check your packages and fix them if needed.
pkg verify or pkg verify -q
pkg fix pkg_fmri_pattern
What steps would you take toward remediation? With what algorithm would you
diagnose it?
The "pkg" command has all the options
We're very familiar with the pkg command, but what variant/syntax gives you
'What part of my environment needs fixing?'
Saying: 'Find another patient!' isn't an option, really!)
Many Thanks. Yours in Thought Experimentation, Lou
_______________________________________________
opensolaris-help mailing list
opensolaris-help@opensolaris.org
