On 5/21/2010 7:47 PM, Dr Lou wrote:
some recent testing on a 'sandbox' machine has raised an interesting
question... One of our techs, in fiddling with this machine, seems to have
deleted some key files; at least part of the /etc directory as well as - at
least - some of the devices directory...
1. Keep the root password in the global (default) zone to yourself or an
experienced Unix Admin.
2. Create a zone or zones for the tech to play in. They can have root
for their zone and if they mess up the zone it does not hurt the global
master zone. Easy to delete and add the zone again. You can also use
zones to test tings before putting them on production server zones.
Two reasonable commands to use "zoneadm" and "zonecfg".
Probably easy enough to fix, if it were a critical machine, with a
'fine-tooth-comb' approach.
But, as an academic question: What facility does openSolaris have for repair in
such a situation?
Is there, effectively, a 'repair existing installation' function as an option
to installation?
Is there a way to mass query the package database and contents, and somehow
determine what's missing?
The "pkg" command has all the options
What strategies would the experts recommend in such a case to maximize uptime?
Control access to the Global zone root.
I know, a far-reaching question, but thought it might be worth posting here.
Have never run into this, but it may be a reasonable question for a real
environment at some point.
(I know, don't give the new guy full root access; I know, I know!) Lou
_______________________________________________
opensolaris-help mailing list
opensolaris-help@opensolaris.org
