Go to main content

man pages section 1M: System Administration Commands

Exit Print View

Updated: July 2017

lighttpd (1m)


lighttpd - a fast, secure and flexible webserver




System Administration Commands                                    lighttpd(1M)

       lighttpd - a fast, secure and flexible webserver


       The  Lighttpd  Web  Server  consists  of  a  server daemon,  a watchdog
       process, loadable server modules, configuration  files  and  documenta-

       The following paths specify the installation locations for Lighttpd:

       Note :

           o      The  string  [version]  should be expanded to "MAJOR.MINOR".
                  For example, /usr/lighttpd/1.4/*.


           Contains lighttpd configuration files. A  new  install  contains  a
           single, default configuration file lighttpd.conf.


           Contains  additional server configuration files. These files gener-
           ally require some customisation and are therefore not automatically
           loaded by the main configuration file.


           Contains  the  lighttpd  executable and the lighttpd-angel watchdog


           Contains man pages for the server and utility programs.

           Add this directory to your MANPATH to read the Lighttpd man  pages.
           See Notes.


           Contains  the  Lighttpd  loadable  modules.  These can be loaded by
           using directives in the configuration file.


           The default location for content as specified by  the  server.docu-
           ment-root directive in the Lightpd configuration file.


           This is the default location for the Lighttpd log files.

           The  formats,  names,  and locations of the files in this directory
           can  be  altered  by  various  configuration  directives   in   the
           lighttpd.conf file.

       The  lighttpd14  package  for Solaris (web/server/lighttpd-14) includes
       all of the files necessary to register Lighttpd with the  Service  Man-
       agement Facility described in SMF(5). The following procedure describes
       the steps to automate service management for lighttpd.

       Note :

           o      The the full name  of  the  lighttpd  service  is  svc:/net-
                  work/http:lighttpd14  This  can be abbreviated to lighttpd14
                  which is the instance name of the service.

           1.     To enable the lighttpd14 service.

                    example% svcadm enable lighttpd14

                  The state of the service instance changes to online, and the
                  lighttpd14 service instance is now available:

                    example% svcs lighttpd14
                    STATE          STIME    FMRI
                    online         11:22:17 svc:/network/http:lighttpd14

           2.     To disable the lighttpd14 service instance,

                    example% svcadm disable lighttpd14

                  The  state  of the service instance changes to disabled, and
                  the lighttpd service instance is no longer available:

                    example% svcs lighttpd14
                    STATE          STIME    FMRI
                    disabled       11:35:15 svc:/network/http:lighttpd14

       You can use RBAC(5) to authorize otherwise non-privileged users to man-
       age  the  lighttpd14 service.  To allow a user to manage the lighttpd14
       service states, add a line to /etc/user_attr of the form:

         <username>::::type=role;profiles=Lighttpd 14 Administration,All

       Where <username> is the name of the user being granted  the  authorisa-
       tion.  If  the  user  already  has  an entry in /etc/user_attr, add the
       "Lighttpd 14 Administration" profile to his or her entry.

       Version 1.4.23 of the Lighttpd web server sees the refactoring  of  the
       spawn-fcgi utility into a separate source distribution and as a result,
       spawn-fcgi  has  been  spun  out  into   a   separate   package   named
       web/fastcgi/spawn-fcgi.      The      Lighttpd     packages     install
       web/fastcgi/spawn-fcgi as a dependency and provide symbolic links  from
       the  original locations of the spawn-fcgi executable and manpage to the
       locations delivered by the spawn-fcgi package, i.e.:

         /usr/lighttpd/1.4/bin/spawn-fcgi -> /usr/bin/spawn-fcgi

                             -> /usr/share/man/man1/spawn-fcgi.1

       These symbolic links may be removed in a future update of the  Lighttpd

       At  this time, use of multiple Lighttpd worker processes is discouraged
       and is not supported by the Lighttpd community. From version 1.4.23 the
       supplied configuration file has the following line removed:

         server.max-worker = 4

       The result of this change is that by default, Lighttpd will be run with
       a single worker process

       See attributes(5) for descriptions of the following attributes:

       |Availability   | web/server/lighttpd-14 |
       |Stability      | Uncommitted            |
       attributes(5), lighttpd(8), spawn-fcgi(8), lighttpd-angel(8)


       In addition to the documentation and man pages included  with  Solaris,
       more information is available at http://www.lighttpd.net.

       The  Lighttpd  man  pages are provided with the programming modules. To
       view the manual pages for the Lighttpd modules with  the  man  command,
       add  /usr/lighttpd/[version]/man  to  the MANPATH environment variable.
       See man(1) for more information. Running  catman(1M)  on  the  Lighttpd
       manual pages is not supported.

       This     software     was    built    from    source    available    at
       https://java.net/projects/solaris-userland.   The  original   community
       source     was     downloaded    from     http://www.lighttpd.net/down-

       Further information about this software can be found on the open source
       community website at http://www.lighttpd.net/.

SunOS 5.11                       October 2009                     lighttpd(1M)