Running a script after a specific daemon service is started

ToniCipriani · 05-13-2017, 05:15 PM

I have a Raspberry Pi that I configured as my torrenting box, currently running openvpn as a service and deluged, both are started at boot time, with deluged starting after openvpn.

I have 2 scripts that I want run to configure the port forwarding for the connection:

- One script was provided by the VPN provider, which returns a JSON string with the port number. I modified this script to pass it through jq, and dumps the port number into a temp file in /tmp.
- Another script I have runs 2 commands for deluge-console, to update the listen_ports and disable random_ports parameters.

First script I can put it in up.sh in openvpn as they suggested, but I'm trying to figure out the right place to put the second one. Basically I want this to run after the deluged is started.

Thoughts?

BW-userx · 05-13-2017, 05:43 PM

how are you getting deluge to start at boot?
if within a init script then call it on the last line in that (deluge) script. you could put a loop in that second script that will keep checking to insure that deluge has started, then if true then start whatever you have starting in the second script. leave loop.

Code:

while (true)
do

[[ $(pgrep deluge | wc -l) == '1'  ]] && (
echo "deluge on"
break
)

done

results
deluge on

ToniCipriani · 05-13-2017, 09:07 PM

Quote:

Originally Posted by BW-userx

how are you getting deluge to start at boot?
if within a init script then call it on the last line in that (deluge) script. you could put a loop in that second script that will keep checking to insure that deluge has started, then if true then start whatever you have starting in the second script. leave loop.

Code:

while (true)
do

[[ $(pgrep deluge | wc -l) == '1'  ]] && (
echo "deluge on"
break
)

done

results
deluge on

It's part of init.d. Although I just found out somehow deluged is on S01deluged but openvpn is S02openvpn. Tried update-rc.d a few times and it's still on S01...

BW-userx · 05-14-2017, 02:43 PM

I am not familiar with PI but it is Linux.
Your using init.d which is a directory, yes?
it has scripts that will get ran on start up of system. so just created a different script using that loop within it. put it in init.d it should in theory just keep running until it gets a return=0 on deluge PID

all that loop is doing is keeping the if statement checking for is deluge PID until it gets a return=0
you can mod that to fit whatever name deluge uses as a daemon. to get your return=0 then try running whatever code you need to do whatever you need to do with deluge.

even try using a wildcard * to match it *deluge* so if it is S01deluged the 'deluge' is within it. then you'll get your return=0

try it first if not working post back results.

Question. You are using a separate script within init.d to start deluge yes:no?
if yes you still can place the name of that script (whatever you name it) at the bottom of the deluge script - this way deluge is started first then the other script is called to make changes afterwords.

It may need to wait before it attempts to make these changes. After your system has completely booted up and perhaps even logged into before any changes to deluge can be attempted to be made even. Again I am not familiar with PI. So whatever little differences their is I have no idea what they are.

This is where you come in to use your knowledge and apply it to this scenario.

ToniCipriani · 05-17-2017, 10:04 PM

Quote:

Originally Posted by BW-userx

I am not familiar with PI but it is Linux.
Your using init.d which is a directory, yes?
it has scripts that will get ran on start up of system. so just created a different script using that loop within it. put it in init.d it should in theory just keep running until it gets a return=0 on deluge PID

all that loop is doing is keeping the if statement checking for is deluge PID until it gets a return=0
you can mod that to fit whatever name deluge uses as a daemon. to get your return=0 then try running whatever code you need to do whatever you need to do with deluge.

even try using a wildcard * to match it *deluge* so if it is S01deluged the 'deluge' is within it. then you'll get your return=0

try it first if not working post back results.

Question. You are using a separate script within init.d to start deluge yes:no?
if yes you still can place the name of that script (whatever you name it) at the bottom of the deluge script - this way deluge is started first then the other script is called to make changes afterwords.

It may need to wait before it attempts to make these changes. After your system has completely booted up and perhaps even logged into before any changes to deluge can be attempted to be made even. Again I am not familiar with PI. So whatever little differences their is I have no idea what they are.

This is where you come in to use your knowledge and apply it to this scenario.

Should've been clearer, I'm actually running Raspbian Jessie on it.

I was under the impression that since it's S01deluged, S02openvpn, that means it'll run deluged first then openvpn? Higher the number, later the start?

pan64 · 05-18-2017, 02:35 AM

yes, S01 executed (started) before S02