[ENBD] 2.4.23 released

[Peter T. Breuer]

I had lots of problems with my main server over the last few days which
prevented me putting out nbd 2.4.23.  The server broke a motherboard
while I was in the states a few weeks back, and we put the disk in
another machine as a patch up.  I returned the disk to its normal home
last weekend and it took me till now to locate the problem.  Since the
weekend the server has been up and down like a yo yo ..  I don't know
how many files I took back out of lost+found!

So I'm not quite sure if the tarball I put out is coherent. I believe it
is. 

   ftp://oboe.it.uc3m.es/pub/Programs/nbd-2.4.23.tgz

This release notably fixes a problem in which no connect could ever be
obtained if the client was launched before the server.  It was an
off-by-one bug, but it took a lot of finding.  I was at the point of
asking for help from the list in locating the exact version where the
bug first appeared.  But I got a good diagnostic that helped.

The release also contains the /etc/init.d/nbd script and /etc/nbd.conf
configuration file that we are currently using here to launch nbd at
machine boot.  It should be linked as about S24 in rcS.d (after lvm
and before raid for us).  Please go ahead and refine these scripts.
They put pid files in /var/run/nbd-{client|server}-X.pid and you can
run, for example,
  
  /etc/init.d/nbd start server 0

to start the server identified as X=0 in the conffile. If you say less
in a nbd start line (i.e. restrict less), more stuff will get launched.

The server script also ought to do a trick with inetd that talks the
client end into sending a SIGPWR to a client daemon when the server end
is rebooted.  That way the client will know to restart the negotiations
from scratch with a new server. I believe I commented out out
arrangement from the release script.

Ideas please .. or code. Our machines are connecting automatically on
boot with with these scripts.

Peter