daemonize runs a command as a Unix daemon. As defined in W. Richard Stevens’ 1990 book, UNIX Network Programming (Addison-Wesley, 1990), a daemon is “a process that executes ‘in the background’ (i.e., without an associated terminal or login shell) either waiting for some event to occur, or waiting to perform some specified task on a periodic basis.” Upon startup, a typical daemon program will:
- Close all open file descriptors (especially standard input, standard output and standard error)
- Change its working directory to the root filesystem, to ensure that it doesn’t tie up another filesystem and prevent it from being unmounted
- Reset its umask value
- Run in the background (i.e., fork)
- Disassociate from its process group (usually a shell), to insulate itself from signals (such as HUP) sent to the process group
- Ignore all terminal I/O signals
- Disassociate from the control terminal (and take steps not to reacquire one)
- Handle any
Most programs that are designed to be run as daemons do that work for themselves. However, you’ll occasionally run across one that does not. When you must run a daemon program that does not properly make itself into a true Unix daemon, you can use daemonize to force it to run as a true daemon.
See the man page for full details.
If the host operating system provides the daemon(3) library routine, daemonize will use it. Otherwise, daemonize uses its own version of daemon(3). This choice is made at compile time. (BSD 4.4-derived operating systems tend to provide their own daemon(3) routine.)
FreeBSD 5.0 introduced a daemon(1) command that is similar to, but less functional, than daemonize.
daemonize is written in C. Given the number of Unix-like operating systems, and the number of releases of each, it is impractical for me to provide binaries of daemonize for every combination of Unix-like operating system and operating system release.
If you’re on a Mac, you can use homebrew to instsall daemonize, like so:
$ brew install daemonize
If you’re on any other Unix-like operating system, you must build daemonize from source code, as described below.
There are two ways to get the source code:
Download a release zip
You can download a release zip file, containing the source, from the releases page. Just unzip the file to unpack the source directory.
Clone the Git repository
You can also simply clone the git repository, using one of the following commands.
$ git clone git://github.com/bmc/daemonize.git $ git clone http://github.com/bmc/daemonize.git
Once you’ve unpacked the source, change your working directory to the daemonize directory. From there, building and installing the code is fairly typical:
$ sh configure $ make $ sudo make install
For a detailed report of the available
$ sh configure --help
I have personally compiled and tested daemonize on the following platforms:
- FreeBSD 4.x, 8.0-RELEASE, 8.1-RELEASE and 8.2-RELEASE
- Red Hat Enterprise Linux 4 / CentOS 4
- Solaris (SunOS 5.8, 5.10)
- Fedora Core 5
- Ubuntu 8 through 15
- Mac OS X 10.4 (Tiger) and 10.6 through 10.11.
The accompanying “configure” script was generated with GNU autoconf version 2.69. It should work, as is, for most Unix systems.
See the daemonize Change Log for a description of the changes in each version.
Brian Clapper, email@example.com
With the exception of the
install-sh script and the
this software is released under BSD license. See the license for details.
With the exception of the “install-sh” script and the “getopt.c” source, this software is copyright 2003-2015, Brian M. Clapper
I gladly accept patches from their original authors. Feel free to email patches to me or to fork the GitHub repository and send me a pull request. Along with any patch you send:
- Please state that the patch is your original work.
- Please indicate that you license the work to the daemonize project under a BSD License.