Here is what I have, that works for me. It also has a sysv init script. Repo is at GitHub, and I also have a brief blog post with links to other possible solutions I found. There can only be one daemon process running: that is managed by the PID lock file, like most other … Read more
Forever’s documentation explains each briefly: –minUptime Minimum uptime (millis) for a script to not be considered “spinning” –spinSleepTime Time to wait (millis) between launches of a spinning script. A “spinning” application is one that keeps failing/crashing shortly after a restart. –minUptime sets the minimum amount of time that an application is expected to run. If … Read more
On my system the file is at %userprofile%\.docker\daemon.json.
Windows service by itself is a console application which conforms to the interface rules and protocols of the Windows Service Control Manager. You can achieve the same on both platforms using .net core console application as a host.It will require to do some extra configuration to make it behave more like a real service / … Read more
I’ll open by stating that this is one way to manage a long running process (LRP) — not de facto by any stretch. In my experience, the best possible product comes from concentrating on the specific problem you’re dealing with, while delegating supporting tech to other libraries. In this case, I’m referring to the act … Read more
While jkp’s solution works, the newer way of doing things (and the way the documentation recommends) is to use the subprocess module. For simple commands its equivalent, but it offers more options if you want to do something complicated. Example for your case: import subprocess subprocess.Popen([“rm”,”-r”,”some.file”]) This will run rm -r some.file in the background. … Read more
From your mention of Upstart I will assume that this question is for a service being run on an Ubuntu server. On an Ubuntu server an upstart job is really the simplest and most convenient option for creating an always on service that starts up at the right time and can be stopped or reloaded … Read more
.NET Core has considerably evolved since @Stefano’s answer a year ago. In .NET Core 2.0, you can now use the well-known AppDomain.CurrentDomain.ProcessExit event instead of AssemblyLoadContext.Default.Unloading. It works fine for console applications on Linux, also in Docker.
There isn’t one right answer to this problem, but here’s how I’d approach it: Both the daemon and viewer application uses the same core data store to save and retrieve data. Because sharing a Core Data store between processes isn’t supported (as far as I know), I’d have the daemon expose an XPC Service. Instead … Read more
From http://www.steve.org.uk/Reference/Unix/faq_2.html#SEC16 Here are the steps to become a daemon: fork() so the parent can exit, this returns control to the command line or shell invoking your program. This step is required so that the new process is guaranteed not to be a process group leader. The next step, setsid(), fails if you’re a process … Read more