archimondain

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

Showing Posts 1 to 7

lud

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 :DOWN message from the monitor.

Qqwy

Qqwy

TypeCheck Core Team

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 pid before it exits. It will only prevent code running on the process calling Process.exit to wait with continuing before pid has 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

archimondain OP

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 the monitor function the process is normally already running. It may even be over by the time you call the monitor function, in which case you will never receive the DOWN message you expect (this DOWN message would trigger the piece of code you always want to execute when a process finishes).

Am I making sense ?

Qqwy

Qqwy

TypeCheck Core Team

From the documentation of Process.monitor/1:

If the process is already dead when calling Process.monitor/1 , a :DOWN message is delivered immediately.

So you will receive the :DOWN message in that case as well.

archimondain

archimondain OP

Well, then it seems to be a good way to implement what I want :slight_smile:

lud

lud

Also if you call Process.monitor on a pid that is not alive, the down message will contain :noproc as the reason, so you will know your process was not alive.

zkessin

zkessin

if you use spawn_monitor/3 you will remove the race condition on starting the process

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
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
nseaSeb
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
RemyXRenard
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
velrest
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
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
samoloth
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
FlyingNoodle
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 Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
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
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews