5 Commits

Author	SHA1	Message	Date
Eric Blake	2795813c69	run: use portable shell ... Nothing in run required bash, except for the shebang. On systems where /bin/bash doesn't exist (I hit it on FreeBSD), using /bin/sh instead fixes a 'make check' failure: gmake[3]: Entering directory `/usr/home/dummy/libvirt/python' GEN check-local /usr/local/bin/bash: ../run: /bin/bash: bad interpreter: No such file or directory * run.in: Use /bin/sh, not bash.	2013-02-22 17:16:12 -07:00
Daniel P. Berrange	eb8268a4f6	Add a virtlockd client as a lock driver impl ... This adds a 'lockd' lock driver which is just a client which talks to the lockd daemon to perform all locking. This will be the default lock driver for any hypervisor which needs one. * src/Makefile.am: Add lockd.so plugin * src/locking/lock_driver_lockd.c: Lockd driver impl Signed-off-by: Daniel P. Berrange <berrange@redhat.com>	2012-12-13 15:26:57 +00:00
Martin Kletzander	9ac287f826	syntax-check: fix run.in ... Two more problems in "run.in" made the syntax-check fail.	2012-09-18 13:59:53 +02:00
Guido Günther	956ce7b472	Adhere to copyright_address check ... to fix "make syntax-check" Found by http://honk.sigxcpu.org:8001/job/libvirt-syntax-check/	2012-09-18 13:55:40 +02:00
Richard W.M. Jones	5090c576e3	Add a ./run script for running programs from the local directory. ... With this script you can run libvirt programs without needing to install them first. You just have to do for example: ./run ./tools/virsh [args ...] If you are already in the tools/ subdirectory, then the following command will also work: ../run ./virsh [...] You can also run the C programs under valgrind like this: ./run valgrind [valgrind opts...] ./program or under gdb: ./run gdb --args ./program This also works with sudo (eg. if you need root access for libvirt): sudo ./run ./tools/virsh list --all Derived from libguestfs and simplified. The ./run script in libguestfs is much more sophisticated: https://github.com/libguestfs/libguestfs/blob/master/run.in	2012-09-18 10:59:16 +01:00