- Devel - libvirt List Archives

[Libvir] new release of ruby bindings
by Vadim Zaliva 15 Apr '08

15 Apr '08

Hi! Since last official release of ruby bindings is causing nasty crash in error handling code, wouldn't it be good idea to issue new bugfix release. I am packaging my software which is using libvirt and in RPM I am putting a dependency, specifying minimal ruby-libvirt version. I could not set it to last official release since it is known to cause crashes. So the only option I have is to distribute custom RPM of libvirt ruby bindings based on mercurial snapshot. Sincerely, Vadim -- "La perfection est atteinte non quand il ne reste rien a ajouter, mais quand il ne reste rien a enlever." (Antoine de Saint-Exupery)

2 1

[Libvir] crash on domain shutdown (via ruby)
by Vadim Zaliva 14 Apr '08

14 Apr '08

I am observing a crash with libvirt ruby bindings. Please see stack trace below. I am using libvirt-0.4.2 and ruby-libvirt-0.0.6. I have upgraded to new versions of both today, so I am not sure which one is to blame. The problem happening when I try to do domain shutdown. I can reproduce the problem, so if somebody will be looking into that, I can aid debugging it. Sincerely, Vadim *** glibc detected *** ruby: free(): invalid pointer: 0xb7e5e054 *** ======= Backtrace: ========= /lib/i686/nosegneg/libc.so.6[0x5166a6] /lib/i686/nosegneg/libc.so.6(cfree+0x90)[0x519c10] /usr/lib/libvirt.so.0(virResetError+0x2e)[0x421f3de] /usr/lib/ruby/site_ruby/1.8/i386-linux/_libvirt.so[0x11ca3e] /usr/lib/ruby/site_ruby/1.8/i386-linux/_libvirt.so(libvirt_dom_shutdown +0x5e)[0x11f9fe] /usr/lib/libruby.so.1.8[0xb45db5] /usr/lib/libruby.so.1.8[0xb4d49b] /usr/lib/libruby.so.1.8[0xb4e09d] /usr/lib/libruby.so.1.8[0xb45dc8] /usr/lib/libruby.so.1.8[0xb4d49b] /usr/lib/libruby.so.1.8[0xb4e1b8] /usr/lib/libruby.so.1.8[0xb55e76] /usr/lib/libruby.so.1.8[0xb5695e] /usr/lib/libruby.so.1.8[0xb56c1c] /usr/lib/libruby.so.1.8[0xb4dd74] /usr/lib/libruby.so.1.8[0xb4e1b8] /usr/lib/libruby.so.1.8[0xb55f92] /usr/lib/libruby.so.1.8[0xb58a88] /usr/lib/libruby.so.1.8[0xb59658] /usr/lib/libruby.so.1.8[0xb459c7] /usr/lib/libruby.so.1.8[0xb4d49b] /usr/lib/libruby.so.1.8[0xb4e1b8] /usr/lib/libruby.so.1.8[0xb55e76] /usr/lib/libruby.so.1.8[0xb5433a] /usr/lib/libruby.so.1.8[0xb5695e] /usr/lib/libruby.so.1.8[0xb58a88] /usr/lib/libruby.so.1.8[0xb59658] /usr/lib/libruby.so.1.8[0xb459c7] /usr/lib/libruby.so.1.8[0xb4d49b] /usr/lib/libruby.so.1.8[0xb4e1b8] /usr/lib/libruby.so.1.8[0xb55e76] /usr/lib/libruby.so.1.8[0xb55bd0] /usr/lib/libruby.so.1.8[0xb58a88] /usr/lib/libruby.so.1.8(rb_yield+0x21)[0xb59eb1] /usr/lib/libruby.so.1.8(rb_ary_each+0x31)[0xb33031] /usr/lib/libruby.so.1.8[0xb45db5] /usr/lib/libruby.so.1.8[0xb4d49b] /usr/lib/libruby.so.1.8[0xb4e1b8] /usr/lib/libruby.so.1.8[0xb5655d] /usr/lib/libruby.so.1.8[0xb4dd74] /usr/lib/libruby.so.1.8[0xb4e1b8] /usr/lib/libruby.so.1.8[0xb55f92] /usr/lib/libruby.so.1.8[0xb54b8c] /usr/lib/libruby.so.1.8[0xb5695e] /usr/lib/libruby.so.1.8[0xb4dd74] /usr/lib/libruby.so.1.8[0xb4e1b8] /usr/lib/libruby.so.1.8[0xb55f92] /usr/lib/libruby.so.1.8[0xb551c0] /usr/lib/libruby.so.1.8[0xb567c0] /usr/lib/libruby.so.1.8[0xb4dd74] /usr/lib/libruby.so.1.8[0xb4e1b8] /usr/lib/libruby.so.1.8[0xb55f92] /usr/lib/libruby.so.1.8[0xb4dd74] /usr/lib/libruby.so.1.8[0xb4e1b8] /usr/lib/libruby.so.1.8[0xb55f92] /usr/lib/libruby.so.1.8[0xb5467a] /usr/lib/libruby.so.1.8[0xb4dd74] /usr/lib/libruby.so.1.8[0xb4e1b8] /usr/lib/libruby.so.1.8(rb_call_super+0xa2)[0xb4f152] /usr/lib/libruby.so.1.8[0xb54b37] /usr/lib/libruby.so.1.8[0xb4dd74] /usr/lib/libruby.so.1.8[0xb4e1b8] /usr/lib/libruby.so.1.8[0xb55e76] ======= Memory map: ======== 00110000-00111000 r-xp 00000000 08:01 6095946 /usr/lib/ruby/1.8/ i386-linux/fcntl.so 00111000-00112000 rw-p 00000000 08:01 6095946 /usr/lib/ruby/1.8/ i386-linux/fcntl.so 00112000-00114000 r-xp 00000000 08:01 6095942 /usr/lib/ruby/1.8/ i386-linux/digest.so 00114000-00115000 rw-p 00001000 08:01 6095942 /usr/lib/ruby/1.8/ i386-linux/digest.so 00116000-00117000 r-xp 00116000 00:00 0 [vdso] 00117000-00123000 r-xp 00000000 08:01 6193153 /usr/lib/ruby/ site_ruby/1.8/i386-linux/_libvirt.so 00123000-00124000 rw-p 0000c000 08:01 6193153 /usr/lib/ruby/ site_ruby/1.8/i386-linux/_libvirt.so 00124000-00250000 r-xp 00000000 08:01 5618582 /usr/lib/libxml2.so. 2.6.26 00250000-00256000 rw-p 0012b000 08:01 5618582 /usr/lib/libxml2.so. 2.6.26 00256000-0025f000 r-xp 00000000 08:01 6095962 /usr/lib/ruby/1.8/ i386-linux/zlib.so 0025f000-00260000 rw-p 00008000 08:01 6095962 /usr/lib/ruby/1.8/ i386-linux/zlib.so 00260000-00264000 r-xp 00000000 08:01 6193994 /usr/lib/ruby/1.8/ i386-linux/digest/sha2.so 00264000-00265000 rw-p 00003000 08:01 6193994 /usr/lib/ruby/1.8/ i386-linux/digest/sha2.so 00265000-0028a000 r-xp 00000000 08:01 5614351 /usr/lib/ libk5crypto.so.3.1 0028a000-0028b000 rw-p 00025000 08:01 5614351 /usr/lib/ libk5crypto.so.3.1 0028b000-00296000 r-xp 00000000 08:01 14915360 /lib/ libgcc_s-4.1.2-20070626.so.1 00296000-00297000 rw-p 0000a000 08:01 14915360 /lib/ libgcc_s-4.1.2-20070626.so.1 0029b000-002a6000 r-xp 00000000 08:01 6095957 /usr/lib/ruby/1.8/ i386-linux/socket.so 002a6000-002a7000 rw-p 0000a000 08:01 6095957 /usr/lib/ruby/1.8/ i386-linux/socket.so 002bb000-00332000 r-xp 00000000 08:01 5609971 /usr/lib/libgnutls.so. 13.0.6 00332000-00338000 rw-p 00076000 08:01 5609971 /usr/lib/libgnutls.so. 13.0.6 00338000-0038b000 r-xp 00000000 08:01 5609906 /usr/lib/libgcrypt.so. 11.2.2 0038b000-0038d000 rw-p 00053000 08:01 5609906 /usr/lib/libgcrypt.so. 11.2.2 0048d000-004a6000 r-xp 00000000 08:01 14909450 /lib/ld-2.5.so 004a6000-004a7000 r--p 00019000 08:01 14909450 /lib/ld-2.5.so 004a7000-004a8000 rw-p 0001a000 08:01 14909450 /lib/ld-2.5.so 004aa000-004ac000 r-xp 00000000 08:01 14915357 /lib/libcom_err.so.2.1 004ac000-004ad000 rw-p 00001000 08:01 14915357 /lib/libcom_err.so.2.1 004af000-005ec000 r-xp 00000000 08:01 14909452 /lib/i686/nosegneg/ libc-2.5.so 005ec000-005ee000 r--p 0013d000 08:01 14909452 /lib/i686/nosegneg/ libc-2.5.so 005ee000-005ef000 rw-p 0013f000 08:01 14909452 /lib/i686/nosegneg/ libc-2.5.so 005ef000-005f2000 rw-p 005ef000 00:00 0 005f4000-005f6000 r-xp 00000000 08:01 14909481 /lib/libdl-2.5.so 005f6000-005f7000 r--p 00001000 08:01 14909481 /lib/libdl-2.5.so 005f7000-005f8000 rw-p 00002000 08:01 14909481 /lib/libdl-2.5.so 005fa000-0060d000 r-xp 00000000 08:01 14909458 /lib/i686/nosegneg/ libpthread-2.5.so 0060d000-0060e000 r--p 00012000 08:01 14909458 /lib/i686/nosegneg/ libpthread-2.5.so 0060e000-0060f000 rw-p 00013000 08:01 14909458 /lib/i686/nosegneg/ libpthread-2.5.so 0060f000-00611000 rw-p 0060f000 00:00 0 00613000-00638000 r-xp 00000000 08:01 14909471 /lib/i686/nosegneg/ libm-2.5.so 00638000-00639000 r--p 00024000 08:01 14909471 /lib/i686/nosegneg/ libm-2.5.so 00639000-0063a000 rw-p 00025000 08:01 14909471 /lib/i686/nosegneg/ libm-2.5.so 0063c000-00651000 r-xp 00000000 08:01 14915356 /lib/libselinux.so.1 00651000-00653000 rw-p 00015000 08:01 14915356 /lib/libselinux.so.1 00655000-00690000 r-xp 00000000 08:01 14915355 /lib/libsepol.so.1 00690000-00691000 rw-p 0003a000 08:01 14915355 /lib/libsepol.so.1 00691000-0069b000 rw-p 00691000 00:00 0 0069d000-006af000 r-xp 00000000 08:01 5609961 /usr/lib/libz.so.1.2.3 006af000-006b0000 rw-p 00011000 08:01 5609961 /usr/lib/libz.so.1.2.3 006b2000-006b6000 r-xp 00000000 08:01 5614350 /usr/lib/ libxenstore.so.3.0.0 006b6000-006b7000 rw-p 00003000 08:01 5614350 /usr/lib/ libxenstore.so.3.0.0 006b7000-006ba000 rw-p 006b7000 00:00 0 006bd000-006d0000 r-xp 00000000 08:01 14909475 /lib/libnsl-2.5.so 006d0000-006d1000 r--p 00012000 08:01 14909475 /lib/libnsl-2.5.so 006d1000-006d2000 rw-p 00013000 08:01 14909475 /lib/libnsl-2.5.so 006d2000-006d4000 rw-p 006d2000 00:00 0 006d6000-006e5000 r-xp 00000000 08:01 14909651 /lib/libresolv-2.5.so 006e5000-006e6000 r--p 0000e000 08:01 14909651 /lib/libresolv-2.5.so 006e6000-006e7000 rw-p 0000f000 08:01 14909651 /lib/libresolv-2.5.so 006e7000-006e9000 rw-p 006e7000 00:00 0 006ec000-006f0000 r-xp 00000000 08:01 6095958 /usr/lib/ruby/1.8/ i386-linux/stringio.so 006f0000-006f1000 rw-p 00003000 08:01 6095958 /usr/lib/ruby/1.8/ i386-linux/stringio.so 006f9000-00711000 r-xp 00000000 08:01 5621763 /usr/lib/libsasl2.so. 2.0.22 00711000-00712000 rw-p 00017000 08:01 5621763 /usr/lib/libsasl2.so. 2.0.22 007e6000-00821000 r-xp 00000000 08:01 6095951 /usr/lib/ruby/1.8/ i386-linux/openssl.so 00821000-00823000 rw-p 0003a000 08:01 6095951 /usr/lib/ruby/1.8/ i386-linux/openssl.so 008c0000-008c5000 r-xp 00000000 08:01 14909479 /lib/libcrypt-2.5.so 008c5000-008c6000 r--p 00004000 08:01 14909479 /lib/libcrypt-2.5.so 008c6000-008c7000 rw-p 00005000 08:01 14909479 /lib/libcrypt-2.5.so 008c7000-008ee000 rw-p 008c7000 00:00 0 008f0000-0091d000 r-xp 00000000 08:01 5614349 /usr/lib/ libgssapi_krb5.so.2.2 0091d000-0091e000 rw-p 0002d000 08:01 5614349 /usr/lib/ libgssapi_krb5.so.2.2 00937000-0093b000 r-xp 00000000 08:01 6095959 /usr/lib/ruby/1.8/ i386-linux/strscan.so 0093b000-0093c000 rw-p 00003000 08:01 6095959 /usr/lib/ruby/1.8/ i386-linux/strscan.so 00948000-00950000 r-xp 00000000 08:01 5622056 /usr/lib/ libkrb5support.so.0.1 00950000-00951000 rw-p 00007000 08:01 5622056 /usr/lib/ libkrb5support.so.0.1 00985000-00987000 r-xp 00000000 08:01 14909636 /lib/libkeyutils-1.2.so 00987000-00988000 rw-p 00001000 08:01 14909636 /lib/libkeyutils-1.2.so 00b21000-00bfd000 r-xp 00000000 08:01 5623120 /usr/lib/libruby.so. 1.8.5 00bfd000-00c01000 rw-p 000db000 08:01 5623120 /usr/lib/libruby.so. 1.8.5 00c01000-00c10000 rw-p 00c01000 00:00 0 00c22000-00c3d000 r-xp 00000000 08:01 6095960 /usr/lib/ruby/1.8/ i386-linux/syck.so 00c3d000-00c3e000 rw-p 0001b000 08:01 6095960 /usr/lib/ruby/1.8/ i386-linux/syck.so 00c91000-00c94000 r-xp 00000000 08:01 5609879 /usr/lib/libgpg- error.so.0.3.0 00c94000-00c95000 rw-p 00002000 08:01 5609879 /usr/lib/libgpg- error.so.0.3.0 00cda000-00cdc000 r-xp 00000000 08:01 6095945 /usr/lib/ruby/1.8/ i386-linux/etc.so 00cdc000-00cdd000 rw-p 00001000 08:01 6095945 /usr/lib/ruby/1.8/ i386-linux/etc.so 00d2f000-00d31000 r-xp 00000000 08:01 6193294 /usr/lib/ruby/1.8/ i386-linux/digest/md5.so 00d31000-00d32000 rw-p 00001000 08:01 6193294 /usr/lib/ruby/1.8/ i386-linux/digest/md5.so 00def000-00df3000 r-xp 00000000 08:01 6193993 /usr/lib/ruby/1.8/ i386-linux/digest/sha1.so 00df3000-00df4000 rw-p 00003000 08:01 6193993 /usr/lib/ruby/1.8/ i386-linux/digest/sha1.so 041f2000-04275000 r-xp 00000000 08:01 5618887 /usr/lib/libvirt.so. 0.4.2 04275000-04277000 rw-p 00083000 08:01 5618887 /usr/lib/libvirt.so. 0.4.2 04277000-04279000 rw-p 04277000 00:00 0 048f5000-04a12000 r-xp 00000000 08:01 14909468 /lib/libcrypto.so. 0.9.8b 04a12000-04a25000 rw-p 0011c000 08:01 14909468 /lib/libcrypto.so. 0.9.8b 04a25000-04a28000 rw-p 04a25000 00:00 0 04a9a000-04b2a000 r-xp 00000000 08:01 5614339 /usr/lib/libkrb5.so.3.3 04b2a000-04b2d000 rw-p 0008f000 08:01 5614339 /usr/lib/libkrb5.so.3.3 04b2f000-04b70000 r-xp 00000000 08:01 14909496 /lib/libssl.so.0.9.8b 04b70000-04b74000 rw-p 00040000 08:01 14909496 /lib/libssl.so.0.9.8b 08048000-08049000 r-xp 00000000 08:01 5623121 /usr/bin/ruby 08049000-0804a000 rw-p 00000000 08:01 5623121 /usr/bin/ruby 08279000-0860e000 rw-p 08279000 00:00 0 b7000000-b7021000 rw-p b7000000 00:00 0 b7021000-b7100000 ---p b7021000 00:00 0 b7147000-b7348000 rw-p b7147000 00:00 0 b7348000-b7349000 ---p b7348000 00:00 0 b7349000-b7e66000 rw-p b7349000 00:00 0 b7e67000-b7f06000 rw-p b7e67000 00:00 0 b7f06000-b7f3b000 r--s 00000000 08:01 10750807 /var/db/nscd/hosts b7f3b000-b7fc6000 rw-p b7f3b000 00:00 0 b7fcc000-b7fd2000 rw-p b7fcc000 00:00 0 bf864000-bf8b6000 rw-p bf864000 00:00 0 [stack] Aborted -- "La perfection est atteinte non quand il ne reste rien a ajouter, mais quand il ne reste rien a enlever." (Antoine de Saint-Exupery)

4 10

[Libvir] new ruby error handling
by Vadim Zaliva 14 Apr '08

14 Apr '08

I have a dumb question about new error handling. What is the rationale for using 'libvirt_message' instead of 'message' in new Libvirt Ruby error classes? Here is an example of code I am writing: rescue SystemCallError process($!.message) ... rescue Libvirt::Error process($!.libvirt_message) ... instead of, shorter: rescue Libvirt::Error, SystemCallError process($!.message) ... In reality, my rescue classes are bit longer, so the code gets hairy. Wouldn't it be better to use standard 'message' attribute instead? Sincerely, Vadim -- "La perfection est atteinte non quand il ne reste rien a ajouter, mais quand il ne reste rien a enlever." (Antoine de Saint-Exupery)

3 4

[Libvir] Documentation for virConnectOpenAuth
by Richard W.M. Jones 13 Apr '08

13 Apr '08

Documentation for virConnectOpenAuth is a bit light at the moment. I found: http://libvirt.org/html/libvirt-libvirt.html#virConnectOpenAuth http://libvirt.org/auth.html This is the most serious omission from the documentation: http://libvirt.org/html/libvirt-libvirt.html#virConnectAuthCallbackPtr virConnectAuthPtrDefault is a default implementation of the callback that you should use for command-line tools. It's used in virsh.c. It's not documented at all, but the source for it (in libvirt.c) does give a little bit of guidance. Anyway, as long as there isn't some font of documentation for this call which I've missed, I'll have a go at writing some while I write the OCaml binding. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v

2 1

[Libvir] Relative paths in domain XML
by Richard W.M. Jones 13 Apr '08

13 Apr '08

What would be really useful is to allow paths (eg. to file-backed block devices) to be relative in a useful way. This would let you have the domain XML configuration file & the block device files sit next to each other to give a machine description: mydomain.hda.img mydomain.xml # refers to <source file="mydomain.hda.img"> This isn't possible at the moment as far as I can tell, which means you need to know which directory the files are located in, and you can't move them around. [As an aside, at present the QEMU driver makes no attempt to check that the source file is an absolute path, it just passes whatever it finds to the '-hdc' argument to qemu.] For the command: virsh define mydomain.xml One implementation would be to have virsh rewriting paths, but that requires special knowledge of the XML format in virsh so I don't think it's a workable idea. Another would be to allow virsh to supply a 'base URI' (basically, the current directory) to the virDomainDefineXML call. Any thoughts? Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top

2 1

[Libvir] API confusion...
by Spencer Parker 11 Apr '08

11 Apr '08

Since I am kind of an idiot and don't know what I am doing...I am having trouble with getting network stats to work in Python. I have everything correct...but I am just not sure exactly what it is looking for. I get this error: libvir: Xen error : invalid argument in xenHypervisorDomainInterfaceStats: invalid path, should be vif<domid>.<n>. I guess I just need some kind of example to work from on this. -- Spencer Parker _______________________________________________________ "if you can't go to heaven, may you at least die in Ireland." _______________________________________________________

2 3

[Libvir] ANNOUNCE: Ruby bindings for libvirt, version 0.0.6
by David Lutterkort 10 Apr '08

10 Apr '08

I'm pleased to announce version 0.0.6 of the Ruby bindings for libvirt. The most notable addition is support for the libvirt storage API. From the NEWS file: * Explicit free methods for various objects (based on a patch by Vadim Zaliva) * Make the FLAGS argument for various calls optional, and default it to 0. (Chris Lalancette) * More finegrained exceptions on errors, containing libvirt error message (Mohammed Morsi) * Bindings for the libvirt storage API (requires libvirt 0.4.1) * Suppress some bindings if the underlying libvirt doesn't support it * Bindings for virDomainSetMemory, virDomainPinVcpu, and virDomainSetVcpus (Vadim Zaliva) The main site for ruby-libvirt is http://libvirt.org/ruby API docs can be found at http://libvirt.org/ruby/api/index.html Please send all your patches (and comments/questions) to this list. David

1 0

[Libvir] XVDA
by Spencer Parker 10 Apr '08

10 Apr '08

I have on question...when I go to grab blockStats...why do I have use XVDA vs. HDA? Just wondering if there was something I was missing. I have all of my Xen Domu's set up to use HDA is there some compelling reason to change over? -- Spencer Parker _______________________________________________________ "if you can't go to heaven, may you at least die in Ireland." _______________________________________________________

2 1

[Libvir] [PATCH] Very minor patch to remove unused uid field in virsh structure
by Richard W.M. Jones 10 Apr '08

10 Apr '08

Since we removed the test for uid==0 in virsh, the uid field in the control structure is no longer needed or used. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v

2 1

[Libvir] [PATCH 4/4] HACKING: begin to describe contributor/coding guidelines
by Jim Meyering 10 Apr '08

10 Apr '08

This is the name many projects already use for their code-contribution guidelines, but if people here prefer something different, it's trivial to change. For now, it's not included in the tarball (and I think that's appropriate), but adding it there is fine, too. Of course, this is just one small part. Dan Berrange posted a preliminary list a few months ago, describing some aspects of existing practice, and those belong here, too. Jim ----------------------- HACKING: New file: begin to describe contributor/coding guidelines. diff --git a/HACKING b/HACKING new file mode 100644 index 0000000..a90addc --- /dev/null +++ b/HACKING @@ -0,0 +1,45 @@ +Libvirt contributor guidelines +============================== + + +Code indentation +================ +Libvirt's C source code generally adheres to some basic code-formatting +conventions. The existing code base is not totally consistent on this +front, but we do prefer that contributed code be formatted similarly. +In short, use spaces-not-TABs for indentation, use 4 spaces for each +indentation level, and other than that, follow the K&R style. + +If you use Emacs, add the following to one of one of your start-up files +(e.g., ~/.emacs), to help ensure that you get indentation right: + + ;;; When editing C sources in libvirt, use this style. + (defun libvirt-c-mode () + "C mode with adjusted defaults for use with libvirt." + (interactive) + (c-set-style "K&R") + (setq indent-tabs-mode nil) ; indent using spaces, not TABs + (setq c-indent-level 4) + (setq c-basic-offset 4)) + (add-hook 'c-mode-hook + '(lambda () (if (string-match "/libvirt" (buffer-file-name)) + (libvirt-c-mode)))) + +Code formatting (especially for new code) +========================================= +With new code, we can be even more strict. +Please apply the following function (using GNU indent) to any new code. +Note that this also gives you an idea of the type of spacing we prefer +around operators and keywords: + + indent-libvirt() + { + indent -bad -bap -bbb -bli4 -br -ce -brs -cs -i4 -l75 -lc75 \ + -sbi4 -psl -saf -sai -saw -sbi4 -ss -sc -cdw -cli4 -npcs -nbc \ + --no-tabs "$@" + } + +Note that sometimes you'll have to postprocess that output further, by +piping it through "expand -i", since some leading TABs can get through. +Usually they're in macro definitions or strings, and should be converted +anyhow. -- 1.5.5.24.g3cff

3 3