updated parser to accept all ascii input
fix in storage/posix to calculate to usec from nsec
reply references dictionary marked 'locked' in posix_readv - caused unpredictable double free's and heap corruption
to make sure that we handle the case when "for (i = 0; i < child_count; i++)" loop fails, we STACK_UNWIND with error instead of segfaulting.
mark data_t holding reference with locked attribute in posix_readv
Protocol changes to limit the maximum block size that client/server can recieve.
* Both client and server can be specified through spec file to limit the block size of data they recieve.
  - spec file option is 'limits.transaction-size <size>'
  - size of 0 (zero) specifies that there is no limit on the block size.
check for self-looping subvolumes
* BugFix: Bug-ID #21256 - Schedulers segfault, if scheduler config is wrong. Fixed.

* BugFix: Bug-ID #21259 - Applied the patch to show the correct value when block sizes of the subvolumes are different in unify. (statfs())

* Corrected 'min-free-disk 5GB' to 'min-free-disk 5%' in user-guide.*
glusterfs-server init.d script update from Matthias Albert
auth layer after rewrite.
* Makefile.am: added 'auth' to the subdirs list.

* schedulers/*/src/*.c: Added check in notify(), as there is a case of segfault, in case of failed initialization.

* xlators/storage/posix: removed the code which creates the export directory if not exists, but added a check for its presence there.

* xlators/cluster/unify: added code to handle different block sizes in case of statvfs() call.

Conflicts:
	xlators/cluster/unify/src/unify.c
Making the default version to start off with a file to be "2" instead of 1. This will fix a rare bug - when creating & writing to a file for the first time and killing the 1st child of afr. When the child is brought back the contents of the first child are taken to be the latest.
Conflicts:
	xlators/storage/posix/src/posix.c
Committing so that I don't again stupidly change by doing rm -rf ,,undo* :(

Conflicts:
	doc/user-guide/user-guide.texi
propagate CHILD_UP notification upwards in unify
* init script update by Matthias Albert
* added __DATE__ to --version output
* spec parser update to accept input of all ascii
* unify notify propagates child_up upwards
python check and update to rpm spec by Harshavardhana Ranganath
updated License, Description and Vendor in glusterfs.spec.in
auth layer rewrite to implement code review comments.
	bug description: file creation was failing with striping enabled.
	xlators configuration: stripe over unify
	cause: unify was propagating CHILD_UP event to stripe for _each_ of its _own children_ causing stripe recieving more CHILD_UP events than it should've recieved.
	Fix: make unify to propagate only one CHILD_UP event to its parent.
	* bug description: file creation was failing with striping enabled.
        * xlators configuration: stripe over unify
        * cause: unify was propagating CHILD_UP event to stripe for _each_ of its _own children_ causing stripe recieving more CHILD_UP events than it should've recieved.
        * fix: make unify to propagate only one CHILD_UP event to its parent.