Script with more than one flag2019 Community Moderator ElectionHow to cd into more than one directory?More shell scripts than one in one text file?Sort command on more than one fieldLog output from more than one scriptHow do I exec more than one command?Call one shell script with anotherOrganizing one script with anotherSorting more than one columnLinux -more than one root accountUsing 'read' for more than one variable

Mixing PEX brands

What does "Scientists rise up against statistical significance" mean? (Comment in Nature)

Is there a way to get `mathscr' with lower case letters in pdfLaTeX?

Why does AES have exactly 10 rounds for a 128-bit key, 12 for 192 bits and 14 for a 256-bit key size?

Quoting Keynes in a lecture

Redundant comparison & "if" before assignment

Why did the EU agree to delay the Brexit deadline?

Can disgust be a key component of horror?

Why would a new[] expression ever invoke a destructor?

Terse Method to Swap Lowest for Highest?

Can I still be respawned if I die by falling off the map?

Why "had" in "[something] we would have made had we used [something]"?

Calculating total slots

Why is this estimator biased?

Why is the "ls" command showing permissions of files in a FAT32 partition?

Calculate sum of polynomial roots

Why does a simple loop result in ASYNC_NETWORK_IO waits?

How can I write humor as character trait?

Why is it that I can sometimes guess the next note?

Does the UK parliament need to pass secondary legislation to accept the Article 50 extension

What are some good ways to treat frozen vegetables such that they behave like fresh vegetables when stir frying them?

Is there an injective, monotonically increasing, strictly concave function from the reals, to the reals?

How could a planet have erratic days?

Can a College of Swords bard use a Blade Flourish option on an opportunity attack provoked by their own Dissonant Whispers spell?



Script with more than one flag



2019 Community Moderator ElectionHow to cd into more than one directory?More shell scripts than one in one text file?Sort command on more than one fieldLog output from more than one scriptHow do I exec more than one command?Call one shell script with anotherOrganizing one script with anotherSorting more than one columnLinux -more than one root accountUsing 'read' for more than one variable










1















I am trying to create a script that lowercases/uppercases files or directories.



 modify [-r] [-l|-u] <dir/file names...>


I am currently using getopts to check for flags. However, I can't run my command like that modify -rl to lowercase recursively my dir / files.



(edit) The code:



#!/bin/bash

FLAGS=""
if [ $# -eq 0 ]
then
echo -e "No arguments supplied. nPlease supply an argument.For more information use -h."
else
while getopts "rluh" opt
do
case $opt in
r)
FLAGS+=r
;;
l)
FLAGS+=l
;;
u)
FLAGS+=u
;;
h)
FLAGS+=h
;;
*)
echo "Unrecognized argument. Please enter -h for information"
esac
done

fi
if [[ "$FLAGS" == "l" && "$2" -eq 0 ]]
then
echo "file to modify $2"
elif [[ "$FLAGS" == "h" && "$2" -eq 0 ]]
then
echo "Some info"
fi


exit 0









share|improve this question









New contributor




ClemHlrdt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • Is this a question about how to handle the command line options using getopts or about how to implement lowercasing of filenames? In either case, you have not shown any actual code.

    – Kusalananda
    yesterday











  • Sorry for that. It is actually a question about how to handle options using getopts.

    – ClemHlrdt
    yesterday















1















I am trying to create a script that lowercases/uppercases files or directories.



 modify [-r] [-l|-u] <dir/file names...>


I am currently using getopts to check for flags. However, I can't run my command like that modify -rl to lowercase recursively my dir / files.



(edit) The code:



#!/bin/bash

FLAGS=""
if [ $# -eq 0 ]
then
echo -e "No arguments supplied. nPlease supply an argument.For more information use -h."
else
while getopts "rluh" opt
do
case $opt in
r)
FLAGS+=r
;;
l)
FLAGS+=l
;;
u)
FLAGS+=u
;;
h)
FLAGS+=h
;;
*)
echo "Unrecognized argument. Please enter -h for information"
esac
done

fi
if [[ "$FLAGS" == "l" && "$2" -eq 0 ]]
then
echo "file to modify $2"
elif [[ "$FLAGS" == "h" && "$2" -eq 0 ]]
then
echo "Some info"
fi


exit 0









share|improve this question









New contributor




ClemHlrdt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • Is this a question about how to handle the command line options using getopts or about how to implement lowercasing of filenames? In either case, you have not shown any actual code.

    – Kusalananda
    yesterday











  • Sorry for that. It is actually a question about how to handle options using getopts.

    – ClemHlrdt
    yesterday













1












1








1








I am trying to create a script that lowercases/uppercases files or directories.



 modify [-r] [-l|-u] <dir/file names...>


I am currently using getopts to check for flags. However, I can't run my command like that modify -rl to lowercase recursively my dir / files.



(edit) The code:



#!/bin/bash

FLAGS=""
if [ $# -eq 0 ]
then
echo -e "No arguments supplied. nPlease supply an argument.For more information use -h."
else
while getopts "rluh" opt
do
case $opt in
r)
FLAGS+=r
;;
l)
FLAGS+=l
;;
u)
FLAGS+=u
;;
h)
FLAGS+=h
;;
*)
echo "Unrecognized argument. Please enter -h for information"
esac
done

fi
if [[ "$FLAGS" == "l" && "$2" -eq 0 ]]
then
echo "file to modify $2"
elif [[ "$FLAGS" == "h" && "$2" -eq 0 ]]
then
echo "Some info"
fi


exit 0









share|improve this question









New contributor




ClemHlrdt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I am trying to create a script that lowercases/uppercases files or directories.



 modify [-r] [-l|-u] <dir/file names...>


I am currently using getopts to check for flags. However, I can't run my command like that modify -rl to lowercase recursively my dir / files.



(edit) The code:



#!/bin/bash

FLAGS=""
if [ $# -eq 0 ]
then
echo -e "No arguments supplied. nPlease supply an argument.For more information use -h."
else
while getopts "rluh" opt
do
case $opt in
r)
FLAGS+=r
;;
l)
FLAGS+=l
;;
u)
FLAGS+=u
;;
h)
FLAGS+=h
;;
*)
echo "Unrecognized argument. Please enter -h for information"
esac
done

fi
if [[ "$FLAGS" == "l" && "$2" -eq 0 ]]
then
echo "file to modify $2"
elif [[ "$FLAGS" == "h" && "$2" -eq 0 ]]
then
echo "Some info"
fi


exit 0






linux bash shell-script arguments






share|improve this question









New contributor




ClemHlrdt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




ClemHlrdt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited yesterday









Rui F Ribeiro

41.6k1483141




41.6k1483141






New contributor




ClemHlrdt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked yesterday









ClemHlrdtClemHlrdt

113




113




New contributor




ClemHlrdt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





ClemHlrdt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






ClemHlrdt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • Is this a question about how to handle the command line options using getopts or about how to implement lowercasing of filenames? In either case, you have not shown any actual code.

    – Kusalananda
    yesterday











  • Sorry for that. It is actually a question about how to handle options using getopts.

    – ClemHlrdt
    yesterday

















  • Is this a question about how to handle the command line options using getopts or about how to implement lowercasing of filenames? In either case, you have not shown any actual code.

    – Kusalananda
    yesterday











  • Sorry for that. It is actually a question about how to handle options using getopts.

    – ClemHlrdt
    yesterday
















Is this a question about how to handle the command line options using getopts or about how to implement lowercasing of filenames? In either case, you have not shown any actual code.

– Kusalananda
yesterday





Is this a question about how to handle the command line options using getopts or about how to implement lowercasing of filenames? In either case, you have not shown any actual code.

– Kusalananda
yesterday













Sorry for that. It is actually a question about how to handle options using getopts.

– ClemHlrdt
yesterday





Sorry for that. It is actually a question about how to handle options using getopts.

– ClemHlrdt
yesterday










3 Answers
3






active

oldest

votes


















2














It's easier if you set individual flags for each option that is activated, so that you don't have yet another string to parse just to check whether an option was used.



For example:



#!/bin/bash

self=$0

show_help ()
cat <<END_HELP
Usage: $self [-r] [-l

recurse=0 # don't recurse by default
lowercase=1 # lowercase by default

while getopts rluh opt; do
case $opt in
r) recurse=1 ;;
l) lowercase=1 ;;
u) lowercase=0 ;;
h) show_help
exit ;;
*) echo 'Error in parsing options' >&2
exit 1
esac
done

shift "$(( OPTIND - 1 ))"

for pathname do
if [ -d "$pathname" ] && [ "$recurse" -eq 1 ]; then
# recurse here
fi
if [ "$lowercase" -eq 1 ]; then
# turn into lowercase
else
# turn into uppercase
fi
done


Note that the code after the shift is just example code. I would suggest that you instead of a loop considered using find for doing recursion (possibly in all cases, even if the recursion flag isn't set).



The shift, by the way, gets rid of all the parsed options from "$@" so that only pathname operands are left in the list of positional parameters. This is what the loop afterwards iterates over.



The code, as written above uses sensible defaults (these should be mentioned in the help text). This means that it's perfectly ok to run the script without any options. As a side note, running the tool with no arguments whatsoever should probably not result in an error. There's no work to do, so no work should be done.






share|improve this answer

























  • Or use false/true instead of 0/1 and use "$recurse" instead of [ "$recurse" -eq 1 ]

    – Stéphane Chazelas
    yesterday


















2














You're concatenating the flag letters to a single string, so with myscript -l -r, you get FLAGS=lr, which isn't equal to either l or r.



You could use pattern matching instead of equality testing to deal with that:



if [[ $FLAGS = *r* ]]; then
echo "flag -r was given"


or add distinct variables for each flag:



r_flag=
l_flag=
while getopts "rluh" opt; do
case $opt in
r) r_flag=1;;
...
if [[ $r_flag ]]; then
echo "flag -r was given"


In any case, you're very likely to want to shift $(( OPTIND - 1 )) after the while getopts loop, so that the options handled by getopts are removed from the positional parameters, and what's left in $1, $2... are the script arguments given after the options.






share|improve this answer






























    0














    Something like FLAGS+=r will append r to FLAGS. For modify -r -l FLAGS therefore will be rl. You should use one variable per option (FLAG_r).



    The comparision "$2" -eq 0 will only work if the script gets two directory names, with the second one being 0.
    A better comparision would be "$2" = "".






    share|improve this answer








    New contributor




    Uwe Ohse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.



















      Your Answer








      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "106"
      ;
      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: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      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
      );



      );






      ClemHlrdt is a new contributor. Be nice, and check out our Code of Conduct.









      draft saved

      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f507763%2fscript-with-more-than-one-flag%23new-answer', 'question_page');

      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      2














      It's easier if you set individual flags for each option that is activated, so that you don't have yet another string to parse just to check whether an option was used.



      For example:



      #!/bin/bash

      self=$0

      show_help ()
      cat <<END_HELP
      Usage: $self [-r] [-l

      recurse=0 # don't recurse by default
      lowercase=1 # lowercase by default

      while getopts rluh opt; do
      case $opt in
      r) recurse=1 ;;
      l) lowercase=1 ;;
      u) lowercase=0 ;;
      h) show_help
      exit ;;
      *) echo 'Error in parsing options' >&2
      exit 1
      esac
      done

      shift "$(( OPTIND - 1 ))"

      for pathname do
      if [ -d "$pathname" ] && [ "$recurse" -eq 1 ]; then
      # recurse here
      fi
      if [ "$lowercase" -eq 1 ]; then
      # turn into lowercase
      else
      # turn into uppercase
      fi
      done


      Note that the code after the shift is just example code. I would suggest that you instead of a loop considered using find for doing recursion (possibly in all cases, even if the recursion flag isn't set).



      The shift, by the way, gets rid of all the parsed options from "$@" so that only pathname operands are left in the list of positional parameters. This is what the loop afterwards iterates over.



      The code, as written above uses sensible defaults (these should be mentioned in the help text). This means that it's perfectly ok to run the script without any options. As a side note, running the tool with no arguments whatsoever should probably not result in an error. There's no work to do, so no work should be done.






      share|improve this answer

























      • Or use false/true instead of 0/1 and use "$recurse" instead of [ "$recurse" -eq 1 ]

        – Stéphane Chazelas
        yesterday















      2














      It's easier if you set individual flags for each option that is activated, so that you don't have yet another string to parse just to check whether an option was used.



      For example:



      #!/bin/bash

      self=$0

      show_help ()
      cat <<END_HELP
      Usage: $self [-r] [-l

      recurse=0 # don't recurse by default
      lowercase=1 # lowercase by default

      while getopts rluh opt; do
      case $opt in
      r) recurse=1 ;;
      l) lowercase=1 ;;
      u) lowercase=0 ;;
      h) show_help
      exit ;;
      *) echo 'Error in parsing options' >&2
      exit 1
      esac
      done

      shift "$(( OPTIND - 1 ))"

      for pathname do
      if [ -d "$pathname" ] && [ "$recurse" -eq 1 ]; then
      # recurse here
      fi
      if [ "$lowercase" -eq 1 ]; then
      # turn into lowercase
      else
      # turn into uppercase
      fi
      done


      Note that the code after the shift is just example code. I would suggest that you instead of a loop considered using find for doing recursion (possibly in all cases, even if the recursion flag isn't set).



      The shift, by the way, gets rid of all the parsed options from "$@" so that only pathname operands are left in the list of positional parameters. This is what the loop afterwards iterates over.



      The code, as written above uses sensible defaults (these should be mentioned in the help text). This means that it's perfectly ok to run the script without any options. As a side note, running the tool with no arguments whatsoever should probably not result in an error. There's no work to do, so no work should be done.






      share|improve this answer

























      • Or use false/true instead of 0/1 and use "$recurse" instead of [ "$recurse" -eq 1 ]

        – Stéphane Chazelas
        yesterday













      2












      2








      2







      It's easier if you set individual flags for each option that is activated, so that you don't have yet another string to parse just to check whether an option was used.



      For example:



      #!/bin/bash

      self=$0

      show_help ()
      cat <<END_HELP
      Usage: $self [-r] [-l

      recurse=0 # don't recurse by default
      lowercase=1 # lowercase by default

      while getopts rluh opt; do
      case $opt in
      r) recurse=1 ;;
      l) lowercase=1 ;;
      u) lowercase=0 ;;
      h) show_help
      exit ;;
      *) echo 'Error in parsing options' >&2
      exit 1
      esac
      done

      shift "$(( OPTIND - 1 ))"

      for pathname do
      if [ -d "$pathname" ] && [ "$recurse" -eq 1 ]; then
      # recurse here
      fi
      if [ "$lowercase" -eq 1 ]; then
      # turn into lowercase
      else
      # turn into uppercase
      fi
      done


      Note that the code after the shift is just example code. I would suggest that you instead of a loop considered using find for doing recursion (possibly in all cases, even if the recursion flag isn't set).



      The shift, by the way, gets rid of all the parsed options from "$@" so that only pathname operands are left in the list of positional parameters. This is what the loop afterwards iterates over.



      The code, as written above uses sensible defaults (these should be mentioned in the help text). This means that it's perfectly ok to run the script without any options. As a side note, running the tool with no arguments whatsoever should probably not result in an error. There's no work to do, so no work should be done.






      share|improve this answer















      It's easier if you set individual flags for each option that is activated, so that you don't have yet another string to parse just to check whether an option was used.



      For example:



      #!/bin/bash

      self=$0

      show_help ()
      cat <<END_HELP
      Usage: $self [-r] [-l

      recurse=0 # don't recurse by default
      lowercase=1 # lowercase by default

      while getopts rluh opt; do
      case $opt in
      r) recurse=1 ;;
      l) lowercase=1 ;;
      u) lowercase=0 ;;
      h) show_help
      exit ;;
      *) echo 'Error in parsing options' >&2
      exit 1
      esac
      done

      shift "$(( OPTIND - 1 ))"

      for pathname do
      if [ -d "$pathname" ] && [ "$recurse" -eq 1 ]; then
      # recurse here
      fi
      if [ "$lowercase" -eq 1 ]; then
      # turn into lowercase
      else
      # turn into uppercase
      fi
      done


      Note that the code after the shift is just example code. I would suggest that you instead of a loop considered using find for doing recursion (possibly in all cases, even if the recursion flag isn't set).



      The shift, by the way, gets rid of all the parsed options from "$@" so that only pathname operands are left in the list of positional parameters. This is what the loop afterwards iterates over.



      The code, as written above uses sensible defaults (these should be mentioned in the help text). This means that it's perfectly ok to run the script without any options. As a side note, running the tool with no arguments whatsoever should probably not result in an error. There's no work to do, so no work should be done.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited yesterday

























      answered yesterday









      KusalanandaKusalananda

      137k17258426




      137k17258426












      • Or use false/true instead of 0/1 and use "$recurse" instead of [ "$recurse" -eq 1 ]

        – Stéphane Chazelas
        yesterday

















      • Or use false/true instead of 0/1 and use "$recurse" instead of [ "$recurse" -eq 1 ]

        – Stéphane Chazelas
        yesterday
















      Or use false/true instead of 0/1 and use "$recurse" instead of [ "$recurse" -eq 1 ]

      – Stéphane Chazelas
      yesterday





      Or use false/true instead of 0/1 and use "$recurse" instead of [ "$recurse" -eq 1 ]

      – Stéphane Chazelas
      yesterday













      2














      You're concatenating the flag letters to a single string, so with myscript -l -r, you get FLAGS=lr, which isn't equal to either l or r.



      You could use pattern matching instead of equality testing to deal with that:



      if [[ $FLAGS = *r* ]]; then
      echo "flag -r was given"


      or add distinct variables for each flag:



      r_flag=
      l_flag=
      while getopts "rluh" opt; do
      case $opt in
      r) r_flag=1;;
      ...
      if [[ $r_flag ]]; then
      echo "flag -r was given"


      In any case, you're very likely to want to shift $(( OPTIND - 1 )) after the while getopts loop, so that the options handled by getopts are removed from the positional parameters, and what's left in $1, $2... are the script arguments given after the options.






      share|improve this answer



























        2














        You're concatenating the flag letters to a single string, so with myscript -l -r, you get FLAGS=lr, which isn't equal to either l or r.



        You could use pattern matching instead of equality testing to deal with that:



        if [[ $FLAGS = *r* ]]; then
        echo "flag -r was given"


        or add distinct variables for each flag:



        r_flag=
        l_flag=
        while getopts "rluh" opt; do
        case $opt in
        r) r_flag=1;;
        ...
        if [[ $r_flag ]]; then
        echo "flag -r was given"


        In any case, you're very likely to want to shift $(( OPTIND - 1 )) after the while getopts loop, so that the options handled by getopts are removed from the positional parameters, and what's left in $1, $2... are the script arguments given after the options.






        share|improve this answer

























          2












          2








          2







          You're concatenating the flag letters to a single string, so with myscript -l -r, you get FLAGS=lr, which isn't equal to either l or r.



          You could use pattern matching instead of equality testing to deal with that:



          if [[ $FLAGS = *r* ]]; then
          echo "flag -r was given"


          or add distinct variables for each flag:



          r_flag=
          l_flag=
          while getopts "rluh" opt; do
          case $opt in
          r) r_flag=1;;
          ...
          if [[ $r_flag ]]; then
          echo "flag -r was given"


          In any case, you're very likely to want to shift $(( OPTIND - 1 )) after the while getopts loop, so that the options handled by getopts are removed from the positional parameters, and what's left in $1, $2... are the script arguments given after the options.






          share|improve this answer













          You're concatenating the flag letters to a single string, so with myscript -l -r, you get FLAGS=lr, which isn't equal to either l or r.



          You could use pattern matching instead of equality testing to deal with that:



          if [[ $FLAGS = *r* ]]; then
          echo "flag -r was given"


          or add distinct variables for each flag:



          r_flag=
          l_flag=
          while getopts "rluh" opt; do
          case $opt in
          r) r_flag=1;;
          ...
          if [[ $r_flag ]]; then
          echo "flag -r was given"


          In any case, you're very likely to want to shift $(( OPTIND - 1 )) after the while getopts loop, so that the options handled by getopts are removed from the positional parameters, and what's left in $1, $2... are the script arguments given after the options.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered yesterday









          ilkkachuilkkachu

          62.4k10103179




          62.4k10103179





















              0














              Something like FLAGS+=r will append r to FLAGS. For modify -r -l FLAGS therefore will be rl. You should use one variable per option (FLAG_r).



              The comparision "$2" -eq 0 will only work if the script gets two directory names, with the second one being 0.
              A better comparision would be "$2" = "".






              share|improve this answer








              New contributor




              Uwe Ohse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.
























                0














                Something like FLAGS+=r will append r to FLAGS. For modify -r -l FLAGS therefore will be rl. You should use one variable per option (FLAG_r).



                The comparision "$2" -eq 0 will only work if the script gets two directory names, with the second one being 0.
                A better comparision would be "$2" = "".






                share|improve this answer








                New contributor




                Uwe Ohse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






















                  0












                  0








                  0







                  Something like FLAGS+=r will append r to FLAGS. For modify -r -l FLAGS therefore will be rl. You should use one variable per option (FLAG_r).



                  The comparision "$2" -eq 0 will only work if the script gets two directory names, with the second one being 0.
                  A better comparision would be "$2" = "".






                  share|improve this answer








                  New contributor




                  Uwe Ohse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.










                  Something like FLAGS+=r will append r to FLAGS. For modify -r -l FLAGS therefore will be rl. You should use one variable per option (FLAG_r).



                  The comparision "$2" -eq 0 will only work if the script gets two directory names, with the second one being 0.
                  A better comparision would be "$2" = "".







                  share|improve this answer








                  New contributor




                  Uwe Ohse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  share|improve this answer



                  share|improve this answer






                  New contributor




                  Uwe Ohse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered yesterday









                  Uwe OhseUwe Ohse

                  1013




                  1013




                  New contributor




                  Uwe Ohse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  Uwe Ohse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  Uwe Ohse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.




















                      ClemHlrdt is a new contributor. Be nice, and check out our Code of Conduct.









                      draft saved

                      draft discarded


















                      ClemHlrdt is a new contributor. Be nice, and check out our Code of Conduct.












                      ClemHlrdt is a new contributor. Be nice, and check out our Code of Conduct.











                      ClemHlrdt is a new contributor. Be nice, and check out our Code of Conduct.














                      Thanks for contributing an answer to Unix & Linux Stack Exchange!


                      • 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%2funix.stackexchange.com%2fquestions%2f507763%2fscript-with-more-than-one-flag%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

                      getting Checkpoint VPN SSL Network Extender working in the command lineHow to connect to CheckPoint VPN on Ubuntu 18.04LTS?Will the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayVPN SSL Network Extender in FirefoxLinux Checkpoint SNX tool configuration issuesCheck Point - Connect under Linux - snx + OTPSNX VPN Ububuntu 18.XXUsing Checkpoint VPN SSL Network Extender CLI with certificateVPN with network manager (nm-applet) is not workingWill the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayImport VPN config files to NetworkManager from command lineTrouble connecting to VPN using network-manager, while command line worksStart a VPN connection with PPTP protocol on command linestarting a docker service daemon breaks the vpn networkCan't connect to vpn with Network-managerVPN SSL Network Extender in FirefoxUsing Checkpoint VPN SSL Network Extender CLI with certificate

                      Cannot Extend partition with GParted The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsCan't increase partition size with GParted?GParted doesn't recognize the unallocated space after my current partitionWhat is the best way to add unallocated space located before to Ubuntu 12.04 partition with GParted live?I can't figure out how to extend my Arch home partition into free spaceGparted Linux Mint 18.1 issueTrying to extend but swap partition is showing as Unknown in Gparted, shows proper from fdiskRearrange partitions in gparted to extend a partitionUnable to extend partition even though unallocated space is next to it using GPartedAllocate free space to root partitiongparted: how to merge unallocated space with a partition

                      Marilyn Monroe Ny fiainany manokana | Jereo koa | Meny fitetezanafanitarana azy.