Software Alternatives, Accelerators & Startups

runit

runit is a cross-platform Unix init scheme with service supervision, a replacement for sysvinit...

runit

runit Reviews and Details

This page is designed to help you find out whether runit is good and if it is the right choice for you.

Screenshots and images

  • runit Landing page
    Landing page //
    2019-03-14

Features & Specs

  1. Simplicity

    runit is known for its straightforward and simple design, making it easy to install, configure, and use.

  2. Fast Boot Times

    Due to its lightweight nature, runit can significantly speed up system boot times compared to more complex init systems.

  3. Service Supervision

    runit provides excellent service supervision capabilities, ensuring reliable and automatic restarting of services in case of failure.

  4. Compatibility

    runit is compatible with UNIX-like operating systems and can serve as a drop-in replacement for other init systems.

  5. Modular Design

    runit follows a modular approach, separating the init and supervision stages, which provides flexibility and robustness in managing services.

Badges

Promote runit. You can add any of these badges on your website.

SaaSHub badge
Show embed code

Videos

Void Linux: Runit Service Management Basics & Custom Services

Artix LXQt with Runit - Installation and First Look

Look @ antiX 19.2 Runit Edition - What Happened To My Runit?

Social recommendations and mentions

We have tracked the following product recommendations or mentions on various public social media platforms and blogs. They can help you see what people think about runit and what they use it for.
  • Nitro: A tiny but flexible init system and process supervisor
    If all you need is init (and not a process supervisor), docker comes with one called 'tini' built in. All you have to do is supply `--init` to the `docker run` command. As far as a different process supervisor, I'm not sure. I've used supervisord and agree it's kind of awkward. I have heard of these but don't know much about them: https://smarden.org/runit/ https://github.com/nicolas-van/multirun... - Source: Hacker News / 11 months ago
  • OS/2
    We've all done it. (-: For some while I read people saying that, despite the existence of Paul Jarc showing how svscan as process 1 would actually work and Gerrit Pape leading the way with runit-init and demonstrating the basic idea, one could not do full system management with daemontools and wholly eliminate van Smoorenberg init and rc. * https://code.dogmap.org/svscan-1/ * https://smarden.org/runit/ It was one... - Source: Hacker News / 11 months ago
  • Way too many ways to wait on a child process with a timeout
    Not so much about timeouts, but related in that it is based around managing children processes: The lineage of tools descending from daemontools for service management is worth exploring: daemontools: http://cr.yp.to/daemontools.html runit: https://smarden.org/runit/ s6: https://skarnet.org/software/s6/ dinit: https://davmac.org/projects/dinit/. - Source: Hacker News / over 1 year ago
  • S6 โ€“ skarnet's small supervision suite
    I personally am a fan of runit https://smarden.org/runit/ But s6 is excellent as well. - Source: Hacker News / almost 2 years ago
  • OpenRC is a dependency-based init system for Unix-like systems
    How does it compare to Runit[[0] used by Void Linux? [0]http://smarden.org/runit/. - Source: Hacker News / about 3 years ago
  • SystemD vs Runit. Just a suggestion, not fight.
    Still, I can try to give you a rundown of Runit. Essentially, it's an init system that uses init scripts, but it has a bit more structure to improve on the shortcomings of sysvinit. Much like systemd, it also does service management, although in a much less involved way. Like with sysvinit, the task of logging is left to a separate process, though it has its own logging daemon, if you wish to use it (as logging... Source: over 3 years ago
  • What manages systemd?
    PID 1 is special. It's the init. Instead of System V init, you can use OpenRC, runit, systemd, s6, or others. Source: over 4 years ago
  • How do I use rc.d? and service management in general for KISS
    Of course the original creator's document is great too: runit - a UNIX init scheme with service supervision. Source: about 5 years ago
  • How do I use rc.d? and service management in general for KISS
    I learned about it here. http://smarden.org/runit/ It is not long read. Source: about 5 years ago
  • Why?
    Then there's the init and service supervision system which is simple and great. I've used systemd professionally for years now and there are still things I don't understand about it. Void uses runit which I'd only used on some embedded systems before but knew from that experience was dead simple and relaiable with no nonsense. It's the reason I decided to try Void in the first place. Source: about 5 years ago
  • [Software Development][Linux] The bitter fight over how Linux should run
    Because the only requirement imposed by the Linux kernel on the init process is that it has to exist, there are many different ways to implement it. One of the usual roles filled by the init system is to launch and monitor background processes (called daemons). In the beginning, there was the Research Unix init system that simply ran a single script that started up all the other processes, then in came System V... Source: over 5 years ago

Summary of the public mentions of runit

Public Opinion on Runit: A Versatile Unix Init System

Runit, accessible at smarden.org, is a Unix initialization system renowned for its simplicity, reliability, and straightforward approach to service management. While it coexists with powerful competitors like Systemd, Sysvinit, and s6, Runit carves out its place by focusing on minimalist design principles, often appealing to users seeking efficient yet uncomplicated solutions for process supervision.

Key Strengths

Runitโ€™s primary advantage lies in its lightweight, uncomplicated structure. Its design philosophy emphasizes the separation of concerns, allowing logging and service management to operate independently. This modular nature provides users with the flexibility to use Runit's logging daemon or alternatively, integrate other logging processes suited to their needs.

Many users appreciate how Runit adheres to the Unix principle of "doing one thing well." Its three-stage boot process and simplicity in design circumvent the complexities often associated with larger, feature-rich systems like Systemd. This makes it an attractive option for environments where resource efficiency and ease of understanding are prioritized, such as in embedded systems or resource-constrained servers.

Comparison to Competitors

In contrast to Systemd, which is feature-rich and deeply embedded within operating systems like many modern Linux distributions, Runit stands out for being less invasive. Systemdโ€™s intricate architecture, while powerful, often results in a steeper learning curve and operational overhead, which some users find cumbersome. Conversely, Runit is appreciated for its clarity and user-friendliness, offering a straightforward solution without the multiple layers of abstraction present in Systemd.

Though Runit is similar to Sysvinit in its basic function as an init system, Runit provides improved service management and supervision, addressing deficiencies in Sysvinit by avoiding startup scripts' complexity and providing a more structured service management approach. Runitโ€™s modular approach appeals to users who prefer Unix-like simplicity over the comprehensive service management of Systemd or the structured dependency management of OpenRC.

Among users, there is a noted appreciation for its predictability and reliability. As testified by Void Linux users, Runitโ€™s integration into distributions like Void demonstrates its effectiveness in modern Unix environments, offering a robust alternative to proprietary or complex open-source solutions.

Community Sentiment

The community feedback exhibits a general fondness for Runit. It is commonly praised for being "dead simple" and "no-nonsense," traits that are highlighted by experienced users when considering alternatives to Systemd's complexity. For some, Runit represents a steady, less intrusive companion in managing processes across various environments, which is especially valued by those who have experienced the intricacies and sometimes opaque nature of systems like Systemd.

In summary, Runit is seen as an approachable, efficient system for users seeking performance without frills, making it a well-regarded tool in environments where simplicity is paramount. Its place alongside other Unix init systems is cemented by its dependable operation and ability to coalesce with modern operating systems, allowing users to engage with process supervision on their own terms.

Do you know an article comparing runit to other products?
Suggest a link to a post with product alternatives.

Suggest an article

runit discussion

Log in or Post with

Is runit good? This is an informative page that will help you find out. Moreover, you can review and discuss runit here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.