Semaphore thinks lock file already exists












0















I'm using link to create a semaphore - the idea is to lock out of writing to a db.



Here I have a script to create a table in a database:



#!/bin/bash


if [ "$#" -lt 3 ]; then
echo "Not enough parameters"
exit 1
elif [ "$#" -gt 3 ]; then
echo "Too many parameters"
exit 1
fi


if [ ! -d "$1" ]; then
echo "That database doesn't exist!"
exit 1
fi

./P.sh $1
if [ -f "$1/$2.txt" ]; then
echo "That table already exists!"
./V.sh $1
exit 1
else
touch "$1/$2.txt"
fi
./V.sh $1

echo "$3" > "$1/$2.txt"

echo "Ok, table created"

exit 0


Here's my P file:



#!/bin/bash

if [ -z "$1" ]; then
echo "Usage $0 mutex-name"
exit 1
elif [ ! -e "$1" ]; then
echo "Target for the lock must exist"
exit 2
else
while ! ln "$1" "$1.lock"; do
sleep 1
done
exit 0
fi


and my V:



#! /bin/bash
if [ -z "$1" ]; then
echo "Usage $1 mutex-name"
exit 1
else
rm "$1.lock"
exit 0
fi


let's say I create a table by running ./create_table people footballers age,height



This should create a file footballers.lock (created by P) and then once the writing has happened the V should remove it. But for some reason the P thinks that the .lock file already exists, and it definitely doesn't.



Can anyone spot what's going wrong?










share|improve this question



























    0















    I'm using link to create a semaphore - the idea is to lock out of writing to a db.



    Here I have a script to create a table in a database:



    #!/bin/bash


    if [ "$#" -lt 3 ]; then
    echo "Not enough parameters"
    exit 1
    elif [ "$#" -gt 3 ]; then
    echo "Too many parameters"
    exit 1
    fi


    if [ ! -d "$1" ]; then
    echo "That database doesn't exist!"
    exit 1
    fi

    ./P.sh $1
    if [ -f "$1/$2.txt" ]; then
    echo "That table already exists!"
    ./V.sh $1
    exit 1
    else
    touch "$1/$2.txt"
    fi
    ./V.sh $1

    echo "$3" > "$1/$2.txt"

    echo "Ok, table created"

    exit 0


    Here's my P file:



    #!/bin/bash

    if [ -z "$1" ]; then
    echo "Usage $0 mutex-name"
    exit 1
    elif [ ! -e "$1" ]; then
    echo "Target for the lock must exist"
    exit 2
    else
    while ! ln "$1" "$1.lock"; do
    sleep 1
    done
    exit 0
    fi


    and my V:



    #! /bin/bash
    if [ -z "$1" ]; then
    echo "Usage $1 mutex-name"
    exit 1
    else
    rm "$1.lock"
    exit 0
    fi


    let's say I create a table by running ./create_table people footballers age,height



    This should create a file footballers.lock (created by P) and then once the writing has happened the V should remove it. But for some reason the P thinks that the .lock file already exists, and it definitely doesn't.



    Can anyone spot what's going wrong?










    share|improve this question

























      0












      0








      0








      I'm using link to create a semaphore - the idea is to lock out of writing to a db.



      Here I have a script to create a table in a database:



      #!/bin/bash


      if [ "$#" -lt 3 ]; then
      echo "Not enough parameters"
      exit 1
      elif [ "$#" -gt 3 ]; then
      echo "Too many parameters"
      exit 1
      fi


      if [ ! -d "$1" ]; then
      echo "That database doesn't exist!"
      exit 1
      fi

      ./P.sh $1
      if [ -f "$1/$2.txt" ]; then
      echo "That table already exists!"
      ./V.sh $1
      exit 1
      else
      touch "$1/$2.txt"
      fi
      ./V.sh $1

      echo "$3" > "$1/$2.txt"

      echo "Ok, table created"

      exit 0


      Here's my P file:



      #!/bin/bash

      if [ -z "$1" ]; then
      echo "Usage $0 mutex-name"
      exit 1
      elif [ ! -e "$1" ]; then
      echo "Target for the lock must exist"
      exit 2
      else
      while ! ln "$1" "$1.lock"; do
      sleep 1
      done
      exit 0
      fi


      and my V:



      #! /bin/bash
      if [ -z "$1" ]; then
      echo "Usage $1 mutex-name"
      exit 1
      else
      rm "$1.lock"
      exit 0
      fi


      let's say I create a table by running ./create_table people footballers age,height



      This should create a file footballers.lock (created by P) and then once the writing has happened the V should remove it. But for some reason the P thinks that the .lock file already exists, and it definitely doesn't.



      Can anyone spot what's going wrong?










      share|improve this question














      I'm using link to create a semaphore - the idea is to lock out of writing to a db.



      Here I have a script to create a table in a database:



      #!/bin/bash


      if [ "$#" -lt 3 ]; then
      echo "Not enough parameters"
      exit 1
      elif [ "$#" -gt 3 ]; then
      echo "Too many parameters"
      exit 1
      fi


      if [ ! -d "$1" ]; then
      echo "That database doesn't exist!"
      exit 1
      fi

      ./P.sh $1
      if [ -f "$1/$2.txt" ]; then
      echo "That table already exists!"
      ./V.sh $1
      exit 1
      else
      touch "$1/$2.txt"
      fi
      ./V.sh $1

      echo "$3" > "$1/$2.txt"

      echo "Ok, table created"

      exit 0


      Here's my P file:



      #!/bin/bash

      if [ -z "$1" ]; then
      echo "Usage $0 mutex-name"
      exit 1
      elif [ ! -e "$1" ]; then
      echo "Target for the lock must exist"
      exit 2
      else
      while ! ln "$1" "$1.lock"; do
      sleep 1
      done
      exit 0
      fi


      and my V:



      #! /bin/bash
      if [ -z "$1" ]; then
      echo "Usage $1 mutex-name"
      exit 1
      else
      rm "$1.lock"
      exit 0
      fi


      let's say I create a table by running ./create_table people footballers age,height



      This should create a file footballers.lock (created by P) and then once the writing has happened the V should remove it. But for some reason the P thinks that the .lock file already exists, and it definitely doesn't.



      Can anyone spot what's going wrong?







      bash semaphore ln






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 22 '18 at 15:47









      Raph117Raph117

      176111




      176111
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Found it - you can't use ln on directories...






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53434421%2fsemaphore-thinks-lock-file-already-exists%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Found it - you can't use ln on directories...






            share|improve this answer




























              0














              Found it - you can't use ln on directories...






              share|improve this answer


























                0












                0








                0







                Found it - you can't use ln on directories...






                share|improve this answer













                Found it - you can't use ln on directories...







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 22 '18 at 16:01









                Raph117Raph117

                176111




                176111






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53434421%2fsemaphore-thinks-lock-file-already-exists%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Ottavio Pratesi

                    Tricia Helfer

                    15 giugno