Provided by: nanoweb_2.2.9-0ubuntu1_all bug


       nanoweb.php - Nanoweb HyperText Transfer Protocol server


       nanoweb.php [ /path/to/nanoweb.conf ] [ -h ] [ -v ]

       nanoweb.php   [   -c   /etc/nanoweb/nanoweb.conf   ]   [   -o  'directive=value'  ]  [  -a
       'directive=value' ]


       Nanoweb is a very flexible HyperText Transfer  Protocol  (HTTP)  server,  which  is  fully
       implemented  in  the  php(1)  scripting language and comes along with a bunch of extension

       Instead of invoking nanoweb.php directly you should consider utilizing nanoctl(8)  to  get
       it  run  as  standalone  server, alternatively you could just add an entry to the internet
       superserver inetd(8) configuration file to  have  it  automatically  started  on  incoming


       -c nanoweb.conf, --config=nanoweb.conf
              This  tells  nanoweb which configuration file to use; if the -c is omitted the full
              path name of the main configuration  file  must  be  the  very  first  argument  to

       -o directive='value', --set-option='dir=val'
              This command line option can be used to override configuration settings from one of
              the configuration files.

              Quotes or those ticks are neccessary, when your  shell  could  otherwise  interpret
              some  characters  of  the value as meta symbols (values containing spaces should at
              least be enclosed in ticks or double quotes).

       -a 'directive=value', --add-option=dir='val'
              Use this to add a configuration setting where many may be given for a directive.

       -d, --start-daemon
              Runs Nanoweb in daemon  mode  (as  background  server  process),  this  is  in  the
              "standard" mode (as opposite to inetd mode).

       -q, --quiet
              Supresses any messages that may be written to standard output.

       -h, --help
              Prints out the help screen with all available command line options.

       -v, --version
              Shows version information.


       Nanoweb listens to environmental variables only when run in inetd mode, as it needs to get
       the IP address and port of the requesting host via the helper util getpeername(1) from the
       tcputils  package  in this case; but this is handled transparently by in.nanoweb(8) (every
       daemon capable of being run from inetd utilizes such a wrapper).

              address of the requesting host

              the TCP port address


       Usually, none ;)




       nanoctl(8) nanoweb.conf(5) inetd(8) in.nanoweb(8) getpeername(1) php(1)