Mike Gerdts wrote:
> On Mon, Mar 10, 2008 at 2:00 PM, Ethan Quach <ethan.quach at sun.com> wrote:
>>  Proposal
>>  --------
>>  A proposal we have for solving this in Snap Upgrade, is to create
>>  a /var/shared directory which will be its own dataset shared across
>>  all Snap Upgrade BEs.  We will move the directories that we want
>>  "synced" under /var/shared and create symlinks from their original
>>  locations.  The directories that we are proposing to do this with are:
> 
> I (still) think this is a very good idea.  Thanks for listening!
> 
>>  /var/adm
>>  /var/log
>>  /var/mail
>>  /var/spool
> 
> There may be others worth discussing.  For details see
> http://mail.opensolaris.org/pipermail/caiman-discuss/2007-August/000737.html.

I came to the above list by looking at what should be required
to be shared across BEs vs. what could just be optional.  What we need
to be careful in considering is not only the format, but also the
existence of what were sharing across BEs and software version updates.

 From looking again at what's listed in that thread, perhaps a few
more that could be considered for sharing are:

audit cron idmap inet news preserve saf

> 
> 
>>  Restrictions/Issues
>>  -------------------
>>  The list of items being synced will no longer be a publicly
>>  modifiable interface.  Users will no longer be able to add
>>  arbitrary files or dirs that they want synced.
> 
> Does it need to be an either/or?
> 
> Perhaps keeping the lu style synclist with a DATASET entry would be
> best.  Merging your list above with the example at
> http://docs.sun.com/app/docs/doc/820-0178/6nbufm85f?a=view:
> 
> /var/share                   DATASET
> /etc/passwd                  OVERWRITE
> /etc/shadow                  OVERWRITE
> /etc/opasswd                 OVERWRITE
> /etc/oshadow                 OVERWRITE
> /etc/group                   OVERWRITE
> /etc/pwhist                  OVERWRITE
> /etc/default/passwd          OVERWRITE
> /etc/dfs                     OVERWRITE

Maintaining this synclist means supporting some form of shutdown/startup
processing, which is what we're trying to avoid.  The idea is to
intentionally take this away, and stop facilitating the ability to
specify arbitrary system files and directories to sync.  What type of
things do you see an admin wanting to add?

These /etc/* files from the lu synclist are things we're proposing to
drop from being sync'ed.



Reply via email to