I have added in an rc.d-style script to start up a slon.  It's not
(yet) properly documented, but I have integrated it into the
regression tests, so it'll become well tested soon enough, now being a
dependancy for *all* runs of the tests.

Its use is as follows:

 - You either edit the first few lines to set SLON_BIN_PATH,
   SLON_CONF, and SLON_LOG, to indicate where to find these
   interesting values, or

 - Set those values in your environment.

   (I would somewhat prefer to use hardcoded values, but that would
   make regression tests much harder...)

Note that it *requires* use of "slon.conf" files to manage the
configuration, and further requires that you specify, in that file, a
place to stow the slon's PID file.

Then, you can run:

$ start_slon.sh start
to start the slon

$ start_slon.sh stop
to (surprise!) stop the slon

$ start_slon.sh status
to get info about it; it reports back the values of SLON_CONF,
SLON_BIN_PATH, and reports whether it found the slon running.

I'd appreciate if people running on non-Linux platforms could take a
quick peek at this from a portability perspective; I tried to make
sure this was portable, but ps often seems troublesome :-(.
-- 
select 'cbbrowne' || '@' || 'linuxfinances.info';
http://cbbrowne.com/info/lsf.html
Rules  of the  Evil Overlord  #145. "My  dungeon cell  decor  will not
feature exposed pipes.  While they add to the  gloomy atmosphere, they
are good  conductors of vibrations and  a lot of  prisoners know Morse
code." <http://www.eviloverlord.com/>