cjbottaro
I want my Elixir app to managed a Unix process…
defmodule MyApp.RedisServer do
use Task, restart: :permanent
def start_link([]) do
Task.start_link(__MODULE__, :run, [])
end
@args ~w(--unixsocket redis.sock --port 0)
@options [stderr_to_stdout: true, into: IO.stream(:stdio, :line)]
def run do
System.cmd("redis-server", @args, @options)
end
end
Then I shove that task into my app’s supervision tree. The problem is that if I ctrl-c ctrl-c the Elixir app, then the redis-server Unix process is still running.
How to stop the unix process started by System.cmd when the Elixir app stops?
Thanks for the help!
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
derek-zhou
trap exit and when you see a :EXIT message kill the process.
I am not sure what you want to achieve, running a long running external process through System.cmd does not seem right. You can use a port at least, or something even fancier.
cjbottaro
I just want a Unix process started up when the Elixir app starts up and killed when the Elixir app terminates. The Unix process isn’t a daemon; it runs in the foreground.
Further, if the Unix process dies while the Elixir app is running, I want it restarted; hence the supervised Task.
Thanks!
derek-zhou
It is not as simple as it look. To kill a external process, you have to maximize the chance it naturally quits, so your data is not corrupted. Also you may want to capture its output as log, and if it crash, you want to have some progressive push back in restart, or you can end up with very ugly situation.
This is why people use external daemon watchers. General speaking your application should tolerate dependency service being off-line and reconnect when it is back up. Trying to do more than that is usually not the best idea.
lud
The
Portdocumentation addresses this problem.Nicd
In my build utility package I wrote a wrapper Elixir script to kill a child process when the parent’s STDIN closes: lib/apprunner.exs · master · Mikko Ahlroth / mbu · GitLab