
* config file comments can only be on a line by themselves
* config file strings can't have nested double quotes

* must catch the case that the given file is not a flat file

* errors from the http server arn't being caught.  If I setup an
  anon http server, but neglect to install the 'put' script, i get
  a 404 "not found" error from the server, nor 500 "Internal Server 
  error", but fastback doesn' catch it.  I believe this info also
  comes back in the headers from http.  IMO libcurl should be
  catching these errors and reporting them (just as it does for 
  ftp (it does do this for ftp, right?)), but it doesn't.  Figure
  out how to capture the headers and body from the html response
  capture the errors, send the headers and body to the log.

  Additionally, the html that comes back from the server is dumped 
  to stdout which isn't pretty.

* Test that the RPMs work on RHEL5 (x86,x86_64) and Fedora(10,11,12) 
      (x86, x86_64)
* Cleanup Log file handleing
    * copy the log into std error on error?
    * look for the PASV error message, report proxy problem to user
             "425 Use PORT or PASV first."
    * setup ftp proxy test, break the proxy, see if error message is working
* Add some comments about the reciept and unload-reciept to the README 

* look for a config file in $HOME/.fastback before looking in 
       /etc/fastback.conf

* look at the options handleing code to see if I can marke the 
    debug-XX options so that they don't print in the help or
    are less prominant.

* so I have reimplemented something like the built in log file handler,
  but is the builtin log file writer available to be reused by me.
  say by looking at DEBUGFUNCTION before setting it?




