I do not know what your script does, and that determines the best approach to solve the problem. In the only case with which I have experience, I run a perl script as a stand-alone linux process using the normal perl interpreter. This script then connects to FreeSWITCH via ESL (the Event Socket Library) and listens for certain FreeSWITCH events, then reacts to them. This removes the script from the telephony processing loop in the dialplan and eliminates any possible blocking of telephony processing in the dialplan (which seems to be a common problem with many script implementations when called from the dialplan). This method requires compiling the ESL.pm module which is part of the FS source; this module provides the connection from perl to FS. Install it using these instructions: https://freeswitch.org/confluence/display/FREESWITCH/Event+Socket+Library#Ev... There are perl examples on this wiki page: https://freeswitch.org/confluence/display/FREESWITCH/Perl+ESL That’s not much, but I hope it helps. --- John Boteler BnC Group U.S.A. From: FreeSWITCH-users <freeswitch-users-bounces@lists.freeswitch.org> On Behalf Of Frederic Jean Sent: Thursday, 8 October, 2020 10:38 To: freeswitch-users@lists.freeswitch.org Subject: [Freeswitch-users] Defunct processes from starting a script Dear community, Newbie here; I am currently experiencing aleatory defunct processes by starting a Perl script this way: <action application="set" data= "ivr_path=/usr/local/freeswitch/scripts/myscript.pl"/> <action application="socket" data="127.0.0.1:9080 sync full"/> Are there any better ways to have it executed and avoid these? Regards Fred