On Thu, Nov 11, 2010 at 10:33:57AM +0000, Daniel P. Berrange wrote: > On Thu, Nov 11, 2010 at 11:14:09AM +1100, Justin Clift wrote: > > Hi all, > > > > Had a thought the other night, about a possible approach to having a "per user" libvirt preferences file. > > > > How about, in the user's home directory, we have a single text file, say ".libvirt-prefs", structured something like this: > > > > [common] > > default_uri = qemu+ssh://somehost/system > > default_socket = /path/to/somewhere-socket > > default_session_type = system > > tls_client_cert = /path/to/somewhere.cert > > tls_client_key = /path/to/somewhere.key > > log_file=/path/to/logfile.log > > some_other_preference=value > > This is fine, except that default_session_type and default_socket > are already encoded as part of the URI. Oh actually, we need to be able to specify TLS paths in the URI as well, so if we add that ability to the URI, then we don't need the config params for tls either. So we really come down to a config file with the URI and a logfile. Is this any better than just setting LIBVIRT_DEFUALT_URI and LIBVIRT_LOG_OUTPUTS in $HOME/.bashrc, which *will* actually impact any application using libvirt.so without needing any code changes on those apps Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list