🚀 go-pugleaf

In article <1b2cmmINNhof@agate.berkeley.edu> izumi@pinoko.berkeley.edu writes:
>This is a huge drawback of the NetInfo, that it allows communication
>with the active copies of the database.  There has to be a way to
>allow editing of inactive copies of the netinfo databases, i.e., those
>I make by doing:
>cp -rp /etc/netinfo /etc/netinfo.backup

What about making your backup something like backup.nidb in /etc/netinfo,
then killing and restarting nibindd (I doubt firing up a netinfod backup will
work since nibindd most likely won't know it's there) or rebooting, and using
niutil -t local/backup -read or whatnot?  3.0's NetInfoManager even has an
Open by Tag feature so you can use that.

The database'll be there but no one will try to bind to it 'cause no one
knows it's there.

There are only two things I'm not sure of about this -- I'm not 100% sure it
won't cause some problems in binding depending on the master property in it.
Well, actually, that's it.  I've done it by, um, accident once and it didn't
seem to have an adverse affect on the rest of the network's operation.

>Izumi Ohzawa
------
Mike Matthews, matthews@oberon.umd.edu (NeXTmail accepted)
------
The truth is that Christian theology, like every other theology, is not only
opposed to the scientific spirit; it is also opposed to all other attempts
at rational thinking.  Not by accident does Genesis 3 make the father of
knowledge a serpent -- slimy, sneaking and abominable.  Since the earliest
days the church as an organization has thrown itself violently against every
effort to liberate the body and mind of man.  It has been, at all times and
everywhere, the habitual and incorrigible defender of bad governments, bad
laws, bad social theories, bad institutions.  It was, for centuries, an
apologist for slavery, as it was the apologist for the divine right of kings.
- H. L. Mencken

In article <1b1vosINN811@network.ucsd.edu>  alevine@ucsd.edu writes:
>Hello!  Hey, does anyone know a way of accessing information in a backup
>netinfo database, either through NetInfoManager or nidump?
 
About the only thing that comes to my simple mind is to backup the
current /etc/netinfo directory and maybe /etc/hostconfig on a
machine that can be off your net for a while, replace these with the
files you want to examine, bring up the machine with the old netinfo
database, do appropriate nidumps, do an nilist or niprint to catch
anything what the nidumps miss.  I've taken to doing nidumps and
and nilist whenever I want to preserve a NetInfo database, as these
allow easy recovery of specific little items, like a user's password
or a printcap entry.