archimondain
I would like to know if the function
Process.exit(pid, :kill)
Is synchronous : once the function has returned, are we sure that no more code from the process pid will be executed ? If not how could we kill a process in a synchronous way ?
Best
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Hi everyone.
My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
Hello folks!
So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
How Can I Optimise Compile Time Dependencies
I have been building an elixir application for about 2 years now. Many modules and files ha...
New
Other Trending Topics
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with.
But I don’t use it anymore.
Serverless was the promis...
New
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
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming











Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
lud
I am not sure that the function is synchronous, but to be sure, you could first set a monitor on the process with
Process.monitor, then kill it, then wait for the:DOWNmessage from the monitor.Qqwy
Because the Elixir documentation (as well as the Erlang documentation of
:erlang.exit/2, which this function delegates to) only mention “sends an exit signal”, I am fairly certain that the function is asynchronous.The approach mentioned by @lud works. However, this will not (always) prevent other code from running on
pidbefore it exits. It will only prevent code running on the process callingProcess.exitto wait with continuing beforepidhas exited.However, another question would be: what are you trying to do? It seems like a rather odd request. Maybe your actual problem can be resolved in a wholly different manner.
archimondain
Here is what I try to achieve : I want to run a process and be able to kill it if needed. When the process is either killed or terminates normally, there is a piece of code that I always want to run.
The issue I see with
@lud’s solution is the following : To monitor a process, you need a pid. So when you call themonitorfunction the process is normally already running. It may even be over by the time you call themonitorfunction, in which case you will never receive theDOWNmessage you expect (thisDOWNmessage would trigger the piece of code you always want to execute when a process finishes).Am I making sense ?
Qqwy
From the documentation of Process.monitor/1:
So you will receive the
:DOWNmessage in that case as well.archimondain
Well, then it seems to be a good way to implement what I want
lud
Also if you call
Process.monitoron a pid that is not alive, the down message will contain:noprocas the reason, so you will know your process was not alive.zkessin
if you use spawn_monitor/3 you will remove the race condition on starting the process