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’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
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
- #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











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