On Mon, 29 Dec 2008, David Miller wrote:
Long ago when I was an AIX admin we had a script we ran every 6 months
or so and it created what we called the System Book. It had every
possible configuration option. While acknowledging that on a whole it
was overkill documentation, if we ever had to
Thanks Barry. Yeah that looks pretty close to what I'm looking for.
Funny how that slipped by me. Putting combinations of system audit
report config etc don't make for useful google results. And here I
should have tried apropos.
On Mon, Dec 29, 2008 at 8:09 PM, Barry Brimer li...@brimer.org
On Tue, Dec 30, 2008 at 7:32 AM, Dag Wieers d...@centos.org wrote:
On Mon, 29 Dec 2008, David Miller wrote:
Long ago when I was an AIX admin we had a script we ran every 6 months
or so and it created what we called the System Book. It had every
possible configuration option. While
David Miller wrote:
I wrote dconf in memory of the sysbook project. The aim here was not to
create indexed, human-readable documentation, but rather a file that
contains all hardware, software and latent configuration. That allows you
to backup a system's configuration, diff 2 configurations
Long ago when I was an AIX admin we had a script we ran every 6 months
or so and it created what we called the System Book. It had every
possible configuration option. While acknowledging that on a whole it
was overkill documentation, if we ever had to rebuild the systems we
knew *exactly* how the
On Mon, 29 Dec 2008, David Miller wrote:
Long ago when I was an AIX admin we had a script we ran every 6 months
or so and it created what we called the System Book. It had every
possible configuration option. While acknowledging that on a whole it
was overkill documentation, if we ever had to
On Mon, 29 Dec 2008, Barry Brimer wrote:
man sosreport
man sysreport
___
I second the recommendation. sos/sysreport will collect all kinds of
stuff, generate a static html page for it, then tar it all up. Trivial
to wrap a shell script around it
7 matches
Mail list logo
