How to pass parameter (= path with * ) to bash scriptPiping a script with “read” to bashbash: Source: command not foundBash script arguments not being passed to function?Bash Script if condition is always trueFolder exclusion formatting issueHow to escape a character in a heredoc bash scriptWhich shell interpreter runs a script with no hashbang… but run as sudo?To pass parameter to bash script fileHow do I get CRON to run a script that works in my regular shell, but not in CRON?Portable way to run command without PATH from bash script

Can criminal fraud exist without damages?

Are there any comparative studies done between Ashtavakra Gita and Buddhim?

Products and sum of cubes in Fibonacci

Confused about a passage in Harry Potter y la piedra filosofal

What is the opposite of 'gravitas'?

Why Were Madagascar and New Zealand Discovered So Late?

Increase performance creating Mandelbrot set in python

Can I Retrieve Email Addresses from BCC?

Was the picture area of a CRT a parallelogram (instead of a true rectangle)?

Efficiently merge handle parallel feature branches in SFDX

Valid Badminton Score?

Mapping a list into a phase plot

What defines a dissertation?

Is exact Kanji stroke length important?

apt-get update is failing in debian

Why did Kant, Hegel, and Adorno leave some words and phrases in the Greek alphabet?

Can somebody explain Brexit in a few child-proof sentences?

Trouble understanding overseas colleagues

Student evaluations of teaching assistants

How do I rename a LINUX host without needing to reboot for the rename to take effect?

Is expanding the research of a group into machine learning as a PhD student risky?

Why "be dealt cards" rather than "be dealing cards"?

Bash method for viewing beginning and end of file

How can I replace every global instance of "x[2]" with "x_2"



How to pass parameter (= path with * ) to bash script


Piping a script with “read” to bashbash: Source: command not foundBash script arguments not being passed to function?Bash Script if condition is always trueFolder exclusion formatting issueHow to escape a character in a heredoc bash scriptWhich shell interpreter runs a script with no hashbang… but run as sudo?To pass parameter to bash script fileHow do I get CRON to run a script that works in my regular shell, but not in CRON?Portable way to run command without PATH from bash script













0















can anyone here tell me why the * is not passed to the bash shell script?



My script named as top40 is



 #!/bin/bash
sudo du -shx $1 | sort -rh | head -n 40


when I try to run it as top40 /var/* the * is ignored. It is like top40 /var but I want to see the top 40`s size of the directories.



when I do it whithout script and type it on the prompt, it works fine.



I really can not find the reason for this.
Thanks for opening my eyes. I use Ubuntu 18.04 LTS










share|improve this question









New contributor




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




















  • Wildcards are expanded before your script is called. (You'll find that $2, $3 etc are defined.)

    – Ulrich Schwarz
    yesterday






  • 1





    Change $1 to "$@".

    – jordanm
    yesterday











  • @jordanm thanks a lot!

    – Walter Schrabmair
    yesterday















0















can anyone here tell me why the * is not passed to the bash shell script?



My script named as top40 is



 #!/bin/bash
sudo du -shx $1 | sort -rh | head -n 40


when I try to run it as top40 /var/* the * is ignored. It is like top40 /var but I want to see the top 40`s size of the directories.



when I do it whithout script and type it on the prompt, it works fine.



I really can not find the reason for this.
Thanks for opening my eyes. I use Ubuntu 18.04 LTS










share|improve this question









New contributor




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




















  • Wildcards are expanded before your script is called. (You'll find that $2, $3 etc are defined.)

    – Ulrich Schwarz
    yesterday






  • 1





    Change $1 to "$@".

    – jordanm
    yesterday











  • @jordanm thanks a lot!

    – Walter Schrabmair
    yesterday













0












0








0








can anyone here tell me why the * is not passed to the bash shell script?



My script named as top40 is



 #!/bin/bash
sudo du -shx $1 | sort -rh | head -n 40


when I try to run it as top40 /var/* the * is ignored. It is like top40 /var but I want to see the top 40`s size of the directories.



when I do it whithout script and type it on the prompt, it works fine.



I really can not find the reason for this.
Thanks for opening my eyes. I use Ubuntu 18.04 LTS










share|improve this question









New contributor




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












can anyone here tell me why the * is not passed to the bash shell script?



My script named as top40 is



 #!/bin/bash
sudo du -shx $1 | sort -rh | head -n 40


when I try to run it as top40 /var/* the * is ignored. It is like top40 /var but I want to see the top 40`s size of the directories.



when I do it whithout script and type it on the prompt, it works fine.



I really can not find the reason for this.
Thanks for opening my eyes. I use Ubuntu 18.04 LTS







bash ubuntu






share|improve this question









New contributor




Walter Schrabmair 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




Walter Schrabmair 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







Walter Schrabmair













New contributor




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









asked yesterday









Walter SchrabmairWalter Schrabmair

1033




1033




New contributor




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





New contributor





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






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












  • Wildcards are expanded before your script is called. (You'll find that $2, $3 etc are defined.)

    – Ulrich Schwarz
    yesterday






  • 1





    Change $1 to "$@".

    – jordanm
    yesterday











  • @jordanm thanks a lot!

    – Walter Schrabmair
    yesterday

















  • Wildcards are expanded before your script is called. (You'll find that $2, $3 etc are defined.)

    – Ulrich Schwarz
    yesterday






  • 1





    Change $1 to "$@".

    – jordanm
    yesterday











  • @jordanm thanks a lot!

    – Walter Schrabmair
    yesterday
















Wildcards are expanded before your script is called. (You'll find that $2, $3 etc are defined.)

– Ulrich Schwarz
yesterday





Wildcards are expanded before your script is called. (You'll find that $2, $3 etc are defined.)

– Ulrich Schwarz
yesterday




1




1





Change $1 to "$@".

– jordanm
yesterday





Change $1 to "$@".

– jordanm
yesterday













@jordanm thanks a lot!

– Walter Schrabmair
yesterday





@jordanm thanks a lot!

– Walter Schrabmair
yesterday










1 Answer
1






active

oldest

votes


















1














This is basic shell expansion. Because the calling shell recognizes the * as a wildcard character, it's actually interpreting that for you, and passing a list of all the items in /var/ to your script.



If you escape the wildcard, or quote the wildcard to prevent it from being expanded in the calling shell, it will pass to your script the way you expect it to.



Here are two examples that will probably do what you want if my understanding of your intent is correct.




  • /path/to/script.sh '/var/run/*'

    • this example prevents shell interpretation by putting the asterisk in a single quoted string, which bypasses expansion and gets passed as-is to the script.



  • /path/to/script.sh /var/run/*

    • this example just escapes the single asterisk character from shell expansion.


Both of these examples result in the string /var/run/* being passed AS-IS, to your script where they become $1.






share|improve this answer


















  • 1





    Thank you - I learnt a lot with your answer.

    – Walter Schrabmair
    yesterday










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
);



);






Walter Schrabmair 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%2f508512%2fhow-to-pass-parameter-path-with-to-bash-script%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









1














This is basic shell expansion. Because the calling shell recognizes the * as a wildcard character, it's actually interpreting that for you, and passing a list of all the items in /var/ to your script.



If you escape the wildcard, or quote the wildcard to prevent it from being expanded in the calling shell, it will pass to your script the way you expect it to.



Here are two examples that will probably do what you want if my understanding of your intent is correct.




  • /path/to/script.sh '/var/run/*'

    • this example prevents shell interpretation by putting the asterisk in a single quoted string, which bypasses expansion and gets passed as-is to the script.



  • /path/to/script.sh /var/run/*

    • this example just escapes the single asterisk character from shell expansion.


Both of these examples result in the string /var/run/* being passed AS-IS, to your script where they become $1.






share|improve this answer


















  • 1





    Thank you - I learnt a lot with your answer.

    – Walter Schrabmair
    yesterday















1














This is basic shell expansion. Because the calling shell recognizes the * as a wildcard character, it's actually interpreting that for you, and passing a list of all the items in /var/ to your script.



If you escape the wildcard, or quote the wildcard to prevent it from being expanded in the calling shell, it will pass to your script the way you expect it to.



Here are two examples that will probably do what you want if my understanding of your intent is correct.




  • /path/to/script.sh '/var/run/*'

    • this example prevents shell interpretation by putting the asterisk in a single quoted string, which bypasses expansion and gets passed as-is to the script.



  • /path/to/script.sh /var/run/*

    • this example just escapes the single asterisk character from shell expansion.


Both of these examples result in the string /var/run/* being passed AS-IS, to your script where they become $1.






share|improve this answer


















  • 1





    Thank you - I learnt a lot with your answer.

    – Walter Schrabmair
    yesterday













1












1








1







This is basic shell expansion. Because the calling shell recognizes the * as a wildcard character, it's actually interpreting that for you, and passing a list of all the items in /var/ to your script.



If you escape the wildcard, or quote the wildcard to prevent it from being expanded in the calling shell, it will pass to your script the way you expect it to.



Here are two examples that will probably do what you want if my understanding of your intent is correct.




  • /path/to/script.sh '/var/run/*'

    • this example prevents shell interpretation by putting the asterisk in a single quoted string, which bypasses expansion and gets passed as-is to the script.



  • /path/to/script.sh /var/run/*

    • this example just escapes the single asterisk character from shell expansion.


Both of these examples result in the string /var/run/* being passed AS-IS, to your script where they become $1.






share|improve this answer













This is basic shell expansion. Because the calling shell recognizes the * as a wildcard character, it's actually interpreting that for you, and passing a list of all the items in /var/ to your script.



If you escape the wildcard, or quote the wildcard to prevent it from being expanded in the calling shell, it will pass to your script the way you expect it to.



Here are two examples that will probably do what you want if my understanding of your intent is correct.




  • /path/to/script.sh '/var/run/*'

    • this example prevents shell interpretation by putting the asterisk in a single quoted string, which bypasses expansion and gets passed as-is to the script.



  • /path/to/script.sh /var/run/*

    • this example just escapes the single asterisk character from shell expansion.


Both of these examples result in the string /var/run/* being passed AS-IS, to your script where they become $1.







share|improve this answer












share|improve this answer



share|improve this answer










answered yesterday









Tim KennedyTim Kennedy

14.7k23152




14.7k23152







  • 1





    Thank you - I learnt a lot with your answer.

    – Walter Schrabmair
    yesterday












  • 1





    Thank you - I learnt a lot with your answer.

    – Walter Schrabmair
    yesterday







1




1





Thank you - I learnt a lot with your answer.

– Walter Schrabmair
yesterday





Thank you - I learnt a lot with your answer.

– Walter Schrabmair
yesterday










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









draft saved

draft discarded


















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












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











Walter Schrabmair 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%2f508512%2fhow-to-pass-parameter-path-with-to-bash-script%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







-bash, ubuntu

Popular posts from this blog

Frič See also Navigation menuinternal link

Identify plant with long narrow paired leaves and reddish stems Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is this plant with long sharp leaves? Is it a weed?What is this 3ft high, stalky plant, with mid sized narrow leaves?What is this young shrub with opposite ovate, crenate leaves and reddish stems?What is this plant with large broad serrated leaves?Identify this upright branching weed with long leaves and reddish stemsPlease help me identify this bulbous plant with long, broad leaves and white flowersWhat is this small annual with narrow gray/green leaves and rust colored daisy-type flowers?What is this chilli plant?Does anyone know what type of chilli plant this is?Help identify this plant

fontconfig warning: “/etc/fonts/fonts.conf”, line 100: unknown “element blank” The 2019 Stack Overflow Developer Survey Results Are In“tar: unrecognized option --warning” during 'apt-get install'How to fix Fontconfig errorHow do I figure out which font file is chosen for a system generic font alias?Why are some apt-get-installed fonts being ignored by fc-list, xfontsel, etc?Reload settings in /etc/fonts/conf.dTaking 30 seconds longer to boot after upgrade from jessie to stretchHow to match multiple font names with a single <match> element?Adding a custom font to fontconfigRemoving fonts from fontconfig <match> resultsBroken fonts after upgrading Firefox ESR to latest Firefox