Shell script can be run only with sh commandHow Can I Run an Shell Script With .desktop Config File?Automated Shell script to run fdisk command with user inputcustomized shell script can not be runUnable to Run Shell Script on UbuntuUbuntu Unity 16.10 'sudo: no tty present and no askpass program specified'Can I run shell script together with application?Executable shell script doesn't runShell script for network manager not completingcurl command not executing via shell script in bashHow can I run gsettings from a GNOME Shell Extension?
Why are 150k or 200k jobs considered good when there are 300k+ births a month?
What are these boxed doors outside store fronts in New York?
How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?
Why is "Reports" in sentence down without "The"
Should I join office cleaning event for free?
GPS Rollover on Android Smartphones
How do we improve the relationship with a client software team that performs poorly and is becoming less collaborative?
Awk syntax, strange variable?
Underlining section titles
The magic money tree problem
XeLaTeX and pdfLaTeX ignore hyphenation
What is the command to reset a PC without deleting any files
I probably found a bug with the sudo apt install function
Why can't I see bouncing of a switch on an oscilloscope?
Theorems that impeded progress
How can I fix this gap between bookcases I made?
Do Phineas and Ferb ever actually get busted in real time?
Do airline pilots ever risk not hearing communication directed to them specifically, from traffic controllers?
How to report a triplet of septets in NMR tabulation?
A newer friend of my brother's gave him a load of baseball cards that are supposedly extremely valuable. Is this a scam?
How is it possible for user to changed after storage was encrypted? (on OS X, Android)
How old can references or sources in a thesis be?
DOS, create pipe for stdin/stdout of command.com(or 4dos.com) in C or Batch?
Can I interfere when another PC is about to be attacked?
Shell script can be run only with sh command
How Can I Run an Shell Script With .desktop Config File?Automated Shell script to run fdisk command with user inputcustomized shell script can not be runUnable to Run Shell Script on UbuntuUbuntu Unity 16.10 'sudo: no tty present and no askpass program specified'Can I run shell script together with application?Executable shell script doesn't runShell script for network manager not completingcurl command not executing via shell script in bashHow can I run gsettings from a GNOME Shell Extension?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I have a small sh script that I use to backup to a remote server. It worked on Ubuntu 16.04 for years, but now on 18.04 it fails. At first I thought it was a problem with anacron, but now I think it is a problem with the script itself or with dash. Here is what is happening:
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$ sudo chmod +x rsync-doc-script
[sudo] Mot de passe de stefan :
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$ ./rsync-doc-script
/bin/sh: 0: Can't open *
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$ sh rsync-doc-script
opening connection using: ssh -i /home/stefan/.ssh/id_rsa -l totem MouseHouse rsync --server -vvlogDtprze.iLsfxC . /totembackup/totemdoc (11 args)
ssh: connect to host mousehouse port 22: Connection refused
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(235) [sender=3.1.2]
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$
The error can't open * is preventing the script from running correctly when run by run-parts. Why is this error occurring?
It is not relevant that in the last line, when the script ran, it couldn't establish connection. The server is turned off now.
Here is the script:
#!/bin/sh *
rsync -azvv -e "ssh -i /home/stefan/.ssh/id_rsa" /home/stefan/Documents/ totem@MouseHouse:/totembackup/totemdoc
bash scripts sh
asked 1 hour ago
Stefan DawydiakStefan Dawydiak
1235
add a comment |
I have a small sh script that I use to backup to a remote server. It worked on Ubuntu 16.04 for years, but now on 18.04 it fails. At first I thought it was a problem with anacron, but now I think it is a problem with the script itself or with dash. Here is what is happening:
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$ sudo chmod +x rsync-doc-script
[sudo] Mot de passe de stefan :
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$ ./rsync-doc-script
/bin/sh: 0: Can't open *
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$ sh rsync-doc-script
opening connection using: ssh -i /home/stefan/.ssh/id_rsa -l totem MouseHouse rsync --server -vvlogDtprze.iLsfxC . /totembackup/totemdoc (11 args)
ssh: connect to host mousehouse port 22: Connection refused
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(235) [sender=3.1.2]
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$
The error can't open * is preventing the script from running correctly when run by run-parts. Why is this error occurring?
It is not relevant that in the last line, when the script ran, it couldn't establish connection. The server is turned off now.
Here is the script:
#!/bin/sh *
rsync -azvv -e "ssh -i /home/stefan/.ssh/id_rsa" /home/stefan/Documents/ totem@MouseHouse:/totembackup/totemdoc
bash scripts sh
asked 1 hour ago
Stefan DawydiakStefan Dawydiak
1235
add a comment |
I have a small sh script that I use to backup to a remote server. It worked on Ubuntu 16.04 for years, but now on 18.04 it fails. At first I thought it was a problem with anacron, but now I think it is a problem with the script itself or with dash. Here is what is happening:
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$ sudo chmod +x rsync-doc-script
[sudo] Mot de passe de stefan :
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$ ./rsync-doc-script
/bin/sh: 0: Can't open *
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$ sh rsync-doc-script
opening connection using: ssh -i /home/stefan/.ssh/id_rsa -l totem MouseHouse rsync --server -vvlogDtprze.iLsfxC . /totembackup/totemdoc (11 args)
ssh: connect to host mousehouse port 22: Connection refused
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(235) [sender=3.1.2]
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$
The error can't open * is preventing the script from running correctly when run by run-parts. Why is this error occurring?
It is not relevant that in the last line, when the script ran, it couldn't establish connection. The server is turned off now.
Here is the script:
#!/bin/sh *
rsync -azvv -e "ssh -i /home/stefan/.ssh/id_rsa" /home/stefan/Documents/ totem@MouseHouse:/totembackup/totemdoc
bash scripts sh
asked 1 hour ago
Stefan DawydiakStefan Dawydiak
1235
I have a small sh script that I use to backup to a remote server. It worked on Ubuntu 16.04 for years, but now on 18.04 it fails. At first I thought it was a problem with anacron, but now I think it is a problem with the script itself or with dash. Here is what is happening:
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$ sudo chmod +x rsync-doc-script
[sudo] Mot de passe de stefan :
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$ ./rsync-doc-script
/bin/sh: 0: Can't open *
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$ sh rsync-doc-script
opening connection using: ssh -i /home/stefan/.ssh/id_rsa -l totem MouseHouse rsync --server -vvlogDtprze.iLsfxC . /totembackup/totemdoc (11 args)
ssh: connect to host mousehouse port 22: Connection refused
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(235) [sender=3.1.2]
stefan@stefan-Aspire-F5-573T:/etc/cron.daily$
The error can't open * is preventing the script from running correctly when run by run-parts. Why is this error occurring?
It is not relevant that in the last line, when the script ran, it couldn't establish connection. The server is turned off now.
Here is the script:
#!/bin/sh *
rsync -azvv -e "ssh -i /home/stefan/.ssh/id_rsa" /home/stefan/Documents/ totem@MouseHouse:/totembackup/totemdoc
bash scripts sh
bash scripts sh
asked 1 hour ago
Stefan DawydiakStefan Dawydiak
1235
asked 1 hour ago
Stefan DawydiakStefan Dawydiak
1235
asked 1 hour ago
Stefan DawydiakStefan Dawydiak
1235
asked 1 hour ago
Stefan DawydiakStefan Dawydiak
1235
asked 1 hour ago
Stefan DawydiakStefan Dawydiak
1235
1235
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I'd switch from using #!/bin/sh as your shebang to #!/bin/bash since you're expecting Bash features vs. /bin/sh or /bin/dash.
Also I can't tell for sure but it looks like you have a typo on the first line where there's a stray * over to the right.
#!/bin/sh *
^^^ Scroll over to the right to see it.
Example
$ cat script.bash
#!/bin/sh *
echo hi
Run directly:
$ ./script.bash
/bin/sh: *: No such file or directory
Run via sh:
$ sh script.bash
hi
answered 1 hour ago
slmslm
1,87111824
2
Exactly, this asterisk is producing a syntax error when the shebang line is used, thus preventing the script from being run. OP’s script is not using anybashfeatures though, there’s no need to make it#!/bin/bash. A shebang line#!/bin/bash *throws an error as well.
– dessert
1 hour ago
1
@dessert - I state that as a general practice, if you expect features from X, use X.
– slm
1 hour ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1131967%2fshell-script-can-be-run-only-with-sh-command%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
I'd switch from using #!/bin/sh as your shebang to #!/bin/bash since you're expecting Bash features vs. /bin/sh or /bin/dash.
Also I can't tell for sure but it looks like you have a typo on the first line where there's a stray * over to the right.
#!/bin/sh *
^^^ Scroll over to the right to see it.
Example
$ cat script.bash
#!/bin/sh *
echo hi
Run directly:
$ ./script.bash
/bin/sh: *: No such file or directory
Run via sh:
$ sh script.bash
hi
answered 1 hour ago
slmslm
1,87111824
2
Exactly, this asterisk is producing a syntax error when the shebang line is used, thus preventing the script from being run. OP’s script is not using anybashfeatures though, there’s no need to make it#!/bin/bash. A shebang line#!/bin/bash *throws an error as well.
– dessert
1 hour ago
1
@dessert - I state that as a general practice, if you expect features from X, use X.
– slm
1 hour ago
add a comment |
I'd switch from using #!/bin/sh as your shebang to #!/bin/bash since you're expecting Bash features vs. /bin/sh or /bin/dash.
Also I can't tell for sure but it looks like you have a typo on the first line where there's a stray * over to the right.
#!/bin/sh *
^^^ Scroll over to the right to see it.
Example
$ cat script.bash
#!/bin/sh *
echo hi
Run directly:
$ ./script.bash
/bin/sh: *: No such file or directory
Run via sh:
$ sh script.bash
hi
answered 1 hour ago
slmslm
1,87111824
2
Exactly, this asterisk is producing a syntax error when the shebang line is used, thus preventing the script from being run. OP’s script is not using anybashfeatures though, there’s no need to make it#!/bin/bash. A shebang line#!/bin/bash *throws an error as well.
– dessert
1 hour ago
1
@dessert - I state that as a general practice, if you expect features from X, use X.
– slm
1 hour ago
add a comment |
I'd switch from using #!/bin/sh as your shebang to #!/bin/bash since you're expecting Bash features vs. /bin/sh or /bin/dash.
Also I can't tell for sure but it looks like you have a typo on the first line where there's a stray * over to the right.
#!/bin/sh *
^^^ Scroll over to the right to see it.
Example
$ cat script.bash
#!/bin/sh *
echo hi
Run directly:
$ ./script.bash
/bin/sh: *: No such file or directory
Run via sh:
$ sh script.bash
hi
answered 1 hour ago
slmslm
1,87111824
I'd switch from using #!/bin/sh as your shebang to #!/bin/bash since you're expecting Bash features vs. /bin/sh or /bin/dash.
Also I can't tell for sure but it looks like you have a typo on the first line where there's a stray * over to the right.
#!/bin/sh *
^^^ Scroll over to the right to see it.
Example
$ cat script.bash
#!/bin/sh *
echo hi
Run directly:
$ ./script.bash
/bin/sh: *: No such file or directory
Run via sh:
$ sh script.bash
hi
answered 1 hour ago
slmslm
1,87111824
edited 1 hour ago
answered 1 hour ago
slmslm
1,87111824
answered 1 hour ago
slmslm
1,87111824
answered 1 hour ago
slmslm
1,87111824
1,87111824
2
Exactly, this asterisk is producing a syntax error when the shebang line is used, thus preventing the script from being run. OP’s script is not using anybashfeatures though, there’s no need to make it#!/bin/bash. A shebang line#!/bin/bash *throws an error as well.
– dessert
1 hour ago
1
@dessert - I state that as a general practice, if you expect features from X, use X.
– slm
1 hour ago
add a comment |
2
Exactly, this asterisk is producing a syntax error when the shebang line is used, thus preventing the script from being run. OP’s script is not using anybashfeatures though, there’s no need to make it#!/bin/bash. A shebang line#!/bin/bash *throws an error as well.
– dessert
1 hour ago
1
@dessert - I state that as a general practice, if you expect features from X, use X.
– slm
1 hour ago
2
2
Exactly, this asterisk is producing a syntax error when the shebang line is used, thus preventing the script from being run. OP’s script is not using any
bash features though, there’s no need to make it #!/bin/bash. A shebang line #!/bin/bash * throws an error as well.– dessert
1 hour ago
Exactly, this asterisk is producing a syntax error when the shebang line is used, thus preventing the script from being run. OP’s script is not using any
bash features though, there’s no need to make it #!/bin/bash. A shebang line #!/bin/bash * throws an error as well.– dessert
1 hour ago
1
1
@dessert - I state that as a general practice, if you expect features from X, use X.
– slm
1 hour ago
@dessert - I state that as a general practice, if you expect features from X, use X.
– slm
1 hour ago
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1131967%2fshell-script-can-be-run-only-with-sh-command%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
