summaryrefslogtreecommitdiffstats
path: root/po-docs/libguestfs-docs.pot
diff options
context:
space:
mode:
authorRichard W.M. Jones <rjones@redhat.com>2012-02-01 12:18:35 +0000
committerRichard W.M. Jones <rjones@redhat.com>2012-02-01 15:09:09 +0000
commit330fbea5b2d6bd7db84f7ea7afe87cf1bcd438e0 (patch)
tree5a1c1de5498303ace3de64f771ccba949f202df0 /po-docs/libguestfs-docs.pot
parent90d6386c13edcb479113889bbd3cedf83c2e6277 (diff)
downloadlibguestfs-330fbea5b2d6bd7db84f7ea7afe87cf1bcd438e0.tar.gz
libguestfs-330fbea5b2d6bd7db84f7ea7afe87cf1bcd438e0.tar.xz
libguestfs-330fbea5b2d6bd7db84f7ea7afe87cf1bcd438e0.zip
Clarify the error message when unavailable functions are called (RHBZ#679737).
Callers are supposed to use the availability API to check for functions that may not be available in particular builds of libguestfs. If they don't do this, currently they tend to get obscure error messages, eg: libguestfs: error: zerofree: /dev/vda1: zerofree: No such file or directory This commit changes the error message to explain what callers ought to be doing instead: libguestfs: error: zerofree: feature 'zerofree' is not available in this build of libguestfs. Read 'AVAILABILITY' in the guestfs(3) man page for how to check for the availability of features. This patch makes the stubs check for availability. The stub code changes to: static void zerofree_stub (XDR *xdr_in) { [...] /* The caller should have checked before calling this. */ if (! optgroup_zerofree_available ()) { reply_with_error ("feature '%s' is not available in this\n" "build of libguestfs. Read 'AVAILABILITY' in the guestfs(3) man page for\n" "how to check for the availability of features.", "zerofree"); goto done; } [...]
Diffstat (limited to 'po-docs/libguestfs-docs.pot')
0 files changed, 0 insertions, 0 deletions