Softpanorama

Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
May the source be with you, but remember the KISS principle ;-)
Bigger doesn't imply better. Bigger often is a sign of obesity, of lost control, of overcomplexity, of cancerous cells

dconf

News

Baseliners

Recommended Books Recommended Links  Installation Checklist Reference

supportconfig

confstore
(perl)
SCC
(perl)
dconf
(Python)

Humor

Etc

Name: dconf
Summary: Collect a system's hardware and software configuration
Authority: dag
Upstream: Dag Wieers
Implementation:
Epoch: (none)
License: GPL
Group: System Environment/Base
URL: http://dag.wieers.com/home-made/dconf/

dconf - create a system's hardware and software configuration snapshot

dconf [-q] [-v] [-c config] [-o output]

Dconf is a tool to collect a system's hardware and software configuration. It allows to take your system configuration with you on the road, compare identical systems (like nodes in a cluster) to troubleshoot HW or SW problems.

Dconf is also useful in projects where you have to manage changes as a team. Dconf can run periodically and send out system changes to a list of email addresses so that they can be revised and discussed in group.

You can customize your dconf configuration for specific needs, like making a profile of your laptop's hardware or copy specific software configuration files to send out or compare with other systems.

As a sysadmin, you won't become too paranoid if less experienced people have root-access. As a consultant, you won't feel isolated if you don't have remote access to your systems. As a support engineer, you won't become frustrated if a customer has fiddled around with some important config file and you have to find which. As a performance tuner, you can capture the state of the system configuration in between performance tests/benchmarks.

OPTIONS

-c, --config file
specify alternative configfile
-o, --output file
write output to given file
-q, --quiet
minimal output
-v, --verbose
increase verbosity
-vv, -vvv
increase verbosity more

ARGUMENTS

Man:
Ah. I'd like to have an argument, please.
Receptionist:
Certainly sir. Have you been here before?
Man:
No, I haven't, this is my first time.
Receptionist:
I see. Well, do you want to have just one argument, or were you thinking of taking a course?
Man:
Well, what is the cost?
Receptionist:
Well, It's one pound for a five minute argument, but only eight pounds for a course of ten.
Man:
Well, I think it would be best if I perhaps started off with just the one and then see how it goes.
For more arguments, see:
http://orangecow.org/pythonet/sketches/argument.htm

USAGE

To create a snapshot of the current system:
 
dconf
To check the latest changes against the previous snapshot:
 
zdiff -u /var/log/dconf/dconf-$HOSTNAME-previous.log.gz /var/log/dconf/dconf-$HOSTNAME-latest.log.gz
You can add files and commands to /etc/dconf-custom.conf and include that from your /etc/dconf.conf, however I would appreciate if you send me any changes you make so that they can be include in the next version.

Dconf was design so that an excessive list of configuration files or commands would not harm the execution of the program or the content of the snapshot file.

Please send changes to: Dag Wieers dag@wieers.com

See the TODO file for known bugs and future plans.

FILES

/etc/dconf.conf
the main Dconf configuration file (replaced on update)
/etc/dconf-custom.conf
the customized configuration file (customize this one)
/var/log/dconf/
the location of the snapshot files

SEE ALSO

snap(8)

AUTHOR

Written by Dag Wieers dag@wieers.com

Homepage at http://dag.wieers.com/home-made/dconf/

DAG Dconf System config collector


Top Visited
Switchboard
Latest
Past week
Past month

NEWS CONTENTS

Old News ;-)

Linux command to gather hardware and software snapshot for ...

When you work in tech support department and deal with inexperienced [ read as green ] clients debugging problems turns into nightmare.

Luckily, some nifty tools can create a system's hardware and software configuration snapshot. This kind of information is valuable asset while troubleshooting problems.

Dconf (System config collector) is one of such tool. It allows to take your system configuration with you on the road, compare identical systems (like nodes in a cluster) to troubleshoot HW or SW problems, indeed a lifesaver.

Dconf is also useful in projects where you have to manage changes as a team. Dconf can run periodically and send out system changes to a list of email addresses so that they can be revised and discussed in group.

You can customize your dconf configuration for specific needs, like making a profile of your web server's hardware or copy specific software configuration files to send out or compare with other systems.

As a sysadmin, you will not become too paranoid if less experienced people have root-access. As a consultant, you will not feel isolated if you do not have remote access to your systems. As a support engineer, you will not become frustrated if a customer has fiddled around with some important config file and you have to find which. As a performance tuner, you can capture the state of the system configuration in between performance tests/benchmarks.

Install dconf
If you are using Debian Linux then type command:

# apt-get install dconf

You can download Dconf for RedHat or Suse Linux here

Once installed you can simply create a snapshot using dconf command:

# dconf

It will write snapshot in /var/log/dconf/ directory.

See also:

If you get stuck on something or have a question, post your question to our excellent Linux tech support forum. You can subscribe to our free e-mail newsletter or RSS feed or Leave a reply/comment .

Scott Wheeler wheeler at kde.org
Sun Apr 10 07:41:18 EEST 2005
On Wednesday 06 April 2005 23:36, Chris Lee wrote:
> Ah, and that's the fun part. See, it turns out, this is a solution in
> search of a problem.

Actually -- while I'm not going to get into the specifics of GConf vs. 
KConfig, it's most definitely a problem -- and in fact a problem that's more 
important than whether GConf or KConfig is cooler.

Here's the basic problem:

Configuring a Linux box is hard.

It's hard because it's damn near impossible to write a tool that can configure 
most of the stuff on it because everything is using its own configuration 
formats.  Let's just assume for the sake of argument that YaST is the best 
one out there for doing this -- it's still a huge hack that's incredibly 
difficult to maintain because of the huge domain of encapsulated information.

There are places that Linux on the desktop won't be able to go until we can 
get the number of configuration formats down to a very small number.  And 
really I don't mean just on the desktop, but I don't think we're going to 
have a sane case to pitch to other tool developers until we can get this 
sorted out just between a couple of desktop projects.

This is one of the Big Problems (tm).  We've got some smart people on this 
list and it's certainly not beyond them to solve problems when them come up 
if they start working on something like this.  At some point we'll just have 
to get everyone in a room with enough beer, pizza and stimulants and knock 
this out once and for all.  Until then iterative approaches, even if they're 
not likely to a lot of buy in certainly don't hurt.  I think your point about 
the naming is rather appropriate, but with a slightly different 
interpretation -- if some iteration of the above won't work for KDE it's not 
we're going to be tricked into using it, so why fuss about the name?

Sorry, normally I ignore the N-th iteration of this thread on here (apply the 
standard excuse of "this is important, but I'm way too overcommitted 
already"), but I just felt like you were quite off here Chris.  ;-)

Cheers,

-Scott
-- 
The fact that an opinion has been widely held is no evidence whatever that it 
is not utterly absurd. 
--Bertrand Russell



Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least


Copyright © 1996-2018 by Dr. Nikolai Bezroukov. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) in the author free time and without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

 

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info

Disclaimer:

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: September 12, 2017