daemons.el - An Emacs UI for managing init system services

  •        6

This is an Emacs mode to give you a UI for managing init system daemons (services). I wrote this after getting tired of typing out sudo service my_thing reload all the time. It’s also nice to have a consistent UI over different init systems. N.B. This package was briefly known as services-mode.




Related Projects

docker-onion-nmap - Scan

  •    Shell

Use nmap to scan hidden "onion" services on the Tor network. Minimal image based on alpine, using proxychains to wrap nmap. Tor and dnsmasq are run as daemons via s6, and proxychains wraps nmap to use the Tor SOCKS proxy on port 9050. Tor is also configured via DNSPort to anonymously resolve DNS requests to port 9053. dnsmasq is configured to with this localhost:9053 as an authority DNS server. Proxychains is configured to proxy DNS through the local resolver, so all DNS requests will go through Tor and applications can resolve .onion addresses. When the container boots, it launches Tor and dnsmasq as daemons. The tor_wait script then waits for the Tor SOCKS proxy to be up before executing your command.


  •    C

LaunchMON is a software infrastructure that enables HPC run-time tools to co-locate tool daemons with a parallel job. Its API allows a tool to identify all the remote processes of a job and to scalably launch daemons into the relevant nodes.

Daemons IFace

  •    C

Daemons IFace is a library to help developers to write a daemon in minutes... what you need is just create a dispatcher for the service your daemon is for and linking with the library everything is started up for you at program run. (very configurable).

redis_failover - redis_failover is a ZooKeeper-based automatic master/slave failover solution for Ruby

  •    Ruby

redis_failover provides a full automatic master/slave failover solution for Ruby. Redis does not currently provide an automatic failover capability when configured for master/slave replication. When the master node dies, a new master must be manually brought online and assigned as the slave's new master. This manual switch-over is not desirable in high traffic sites where Redis is a critical part of the overall architecture. The existing standard Redis client for Ruby also only supports configuration for a single Redis server. When using master/slave replication, it is desirable to have all writes go to the master, and all reads go to one of the N configured slaves. This gem (built using ZK) attempts to address these failover scenarios. One or more Node Manager daemons run as background processes and monitor all of your configured master/slave nodes. When the daemon starts up, it automatically discovers the current master/slaves. Background watchers are setup for each of the redis nodes. As soon as a node is detected as being offline, it will be moved to an "unavailable" state. If the node that went offline was the master, then one of the slaves will be promoted as the new master. All existing slaves will be automatically reconfigured to point to the new master for replication. All nodes marked as unavailable will be periodically checked to see if they have been brought back online. If so, the newly available nodes will be configured as slaves and brought back into the list of available nodes. Note that detection of a node going down should be nearly instantaneous, since the mechanism used to keep tabs on a node is via a blocking Redis BLPOP call (no polling). This call fails nearly immediately when the node actually goes offline. To avoid false positives (i.e., intermittent flaky network interruption), the Node Manager will only mark a node as unavailable if it fails to communicate with it 3 times (this is configurable via --max-failures, see configuration options below). Note that you can (and should) deploy multiple Node Manager daemons since they each report periodic health reports/snapshots of the redis servers. A "node strategy" is used to determine if a node is actually unavailable. By default a majority strategy is used, but you can also configure "consensus" or "single" as well.

[incr tcl] Internet daemons

  •    Perl

tcl-idaemons is a collection of Internet daemons in the form of a tcl package. It is similar to (and based on) minihttpd and the ftpd from tcllib, but is designed in an OO fashion using [incr tcl]. It is hoped that the scope will grow to other servers

API-Hour - Write efficient network daemons (HTTP, SSH...) with ease.

  •    Python

API-Hour is a lightweight daemon framework, that lets you write powerful applications. It was created to answer the need for a simple, robust, and super-fast server-side environment to build very efficient Daemons with ease.

go-daemon - A library for writing system daemons in golang.

  •    Go

Library for writing system daemons in Go. Now supported only UNIX-based OS (Windows is not supported). But the library was tested only on Linux and OSX, so that if you have an ability to test the library on other platforms, give me feedback, please (#26).

simplehttp - a family of libraries and daemons for building scalable web infrastructure

  •    C

simplehttp is a family of libraries and daemons built upon libevent that make high performance HTTP servers simple and straightforward to write. to install any of the simplehttp components you will need to install libevent 1.4.13+ and the 'simplehttp' module first.

daemonize - daemonize is a library for writing system daemons in Python.

  •    Python

daemonize is a library for writing system daemons in Python. It is distributed under MIT license. Latest version can be downloaded from PyPI. Full documentation can be found at ReadTheDocs.

PHP-Daemon - Build production-ready Daemons using PHP 5

  •    PHP

Create solid, long-running PHP daemon processes by extending the Core_Daemon class. Use a built-in timer to run your application in second or sub-second frequencies, or build servers using libraries like Socket and LibEvent. Create conventional single-process applications or choose true parallel processing in PHP with persistent background workers. Note: For many reasons PHP is not an optimal language choice for creating servers or daemons. I created this library so if you must use PHP for these things, you can do it with ease and produce great results. But if you have the choice, Java, Python, Ruby, etc, are all better suited for this.

nanite - self assembling fabric of ruby daemons

  •    Ruby

Nanite is a new way of thinking about building cloud ready web applications. Having a scalable message queueing back-end with all the discovery and dynamic load based dispatch that Nanite has is a very scalable way to construct web application back-ends. A Nanite system has two types of components. There are nanite agents, these are the daemons where you implement your code functionality as actors. And then there are mappers.

systemd-manager - A systemd service manager written in Rust with the GTK-rs wrapper and direct integration with dbus

  •    Rust

This application is a systemd service manager written in the Rust programming language with GTK3 as the graphical user interface of choice. The units are filtered into three separate lists: services, sockets, and timers. As a unit is selected in the left pane, the right pane is updated with information pertaining to that unit, and the right headerbar is updated to reflect the status of the unit where you may disable/enable and start/stop the selected unit. Services are units that are activated immediately, sockets are units that are activated when they are needed, and timers are units that activate on a regular time interval. In addition to display units, the application also provides stats generated by systemd-analyze on the Systemd Analyze view.This is available in the AUR as a git package: systemd-manager-git.

Virus Server for MacOS X


A binary distribution of various open-source tools and daemons to provide an easily-installable mail service, webmail and sundry other common Internet services on MacOS X.

hotway daemon

  •    C

hotwayd/hotsmtpd are POP3/SMTP-HTTPMail gateway daemons. The HTTPMail protocol is used by the mail servers Hotmail, Lycos, Spray and MSN. The hotway suite you can receive and send mail via these services using any POP3/SMTP compliant mail reader.

dumb-init - A minimal init system for Linux containers

  •    Python

dumb-init is a simple process supervisor and init system designed to run as PID 1 inside minimal container environments (such as Docker). It is deployed as a small, statically-linked binary written in C.Lightweight containers have popularized the idea of running a single process or service without normal init systems like systemd or sysvinit. However, omitting an init system often leads to incorrect handling of processes and signals, and can result in problems such as containers which can't be gracefully stopped, or leaking containers which should have been destroyed.


  •    C

pinit is a sysvinit alternative. It's a different way of booting linux. Keywords are: xml configuration, fast and parallel booting of services, modular design, dependecy based booting of services. It's intented to be more robust and faster than sysvini

daemons - A toolkit to convert your script to a controllable daemon.

  •    Ruby

A toolkit to convert your script to a controllable daemon.


  •    Ruby

Daemon Kit aims to simplify creating Ruby daemons by providing a sound application skeleton (through a generator), task specific generators (jabber bot, etc) and robust environment management code.

Rapid Application Development Library

  •    C

radlib is a rapid application development library for unix multi-process applications. It uses SYS V IPC facilities and FIFOs to provide an RTOS-like, event-driven, distributed framework. Processes may be run as daemons or have a controlling terminal.


  •    C

Privbind is a small tool allowing secure running of unprivileged programs, but allowing them to bind to privileged (lt;1024) TCP/UDP ports. Privbind has a secure design, with no SUID executables and no daemons.