================================================================================
Version      : glusterfs 2.0.2 built on Jun  9 2009 06:00:11
TLA Revision : 07019da2e16534d527215a91904298ede09bb798
Starting Time: 2009-06-15 05:44:22
Command line : /opt/glusterfs/2.0.2/sbin/glusterfs -l /tmp/client.log -f client.vol 
PID          : 27432
System name  : Linux
Nodename     : client01
Kernel Release : 2.6.18-92.el5
Hardware Identifier: x86_64

Given volfile:
+------------------------------------------------------------------------------+
..
..
 31: volume writebehind
 32:   type performance/write-behind
 33:   # option aggregate-size 1MB
 34:   # option window-size 1MB
 35:   option cache-size 128MB
 36:   option flush-behind on
 37:   subvolumes readahead
 38: end-volume
 39: 
 40: volume cache
 41:   type performance/io-cache
 42:   option cache-size 512MB
 43:   subvolumes writebehind
 44: end-volume
 45: 

+------------------------------------------------------------------------------+
[2009-06-15 05:44:22] W [io-cache.c:1255:init] cache: dangling volume. check volfile 
[2009-06-15 05:44:22] E [glusterfsd.c:555:glusterfs_graph_init] glusterfs: no valid translator loaded at the top or no mount point given. exiting
[2009-06-15 05:44:22] E [glusterfsd.c:1191:main] glusterfs: translator initialization failed.  exiting



"dangling volume" is misleading/confusing. So is "no valid translator loaded at the top".

Is it possible to supress the first message and print a simple "no mount point given" for the second?