CODEWITHSUNDEEP
linuxbashshellinitstartupscript
rp346
rp346

Reputation: 7028

How do I write pid to file

I know this could be easy, but I am unable to figure out. We want to run two instances of luigi on one machine so need to modify init.d script to write PID to file rather than just touching empty file.

echo -n $"Starting luigid scheduler as $LUIGID_USER: "
( ( /usr/bin/sudo -u $LUIGID_USER $LUIGID_BIN >>/var/log/luigid/server.log 2>&1 ) &)
RETVAL=$?
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/luigid && echo_success || echo_failure
echo
return $RETVAL

At present its just touching the empty PID file. I want it to write PID into the file. Also while stopping I want to kill by PID stored in PID file

echo -n $"Stopping luigid scheduler: "
killproc luigid
RETVAL=$?
[ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/luigid && echo_success || echo_failure
echo

Any help please ?

Thanks

Upvotes: 3

Views: 16673

Answers (2)

masseyb
masseyb

Reputation: 4132

(man) shlock should do the trick for that I do believe :

shlock [-du] [-p PID] -f lockfile

...

shlock uses the link(2) system call to make the final target lock file, which
is an atomic operation (i.e. "dot locking", so named for this mechanisms 
original use for locking system mailboxes).  It puts the process ID ("PID") 
from the command line into the requested lock file.

Or depending on the situation (man) flock, for a great example check this out : http://codehackit.blogspot.fr/2013/04/locking-processes-with-flock.html

Upvotes: 0

arco444
arco444

Reputation: 22821

You can get the PID of the previous command with $!

Change the start script to:

echo -n "Starting luigid scheduler as $LUIGID_USER: "
/usr/bin/sudo -u $LUIGID_USER $LUIGID_BIN >>/var/log/luigid/server.log 2>&1 &
RETVAL=$?
PID=$!
[ $RETVAL -eq 0 ] && echo $PID > /var/lock/subsys/luigid && echo_success || echo_failure
echo
return $RETVAL

Note you need to remove the brackets from around the command as they start the program in a subshell. The subshell will not return the PID of the started program back to your shell, so you should call it directly from your shell.

Upvotes: 9

Related Questions