RHEL: syntax errors with bash script
Clash Royale CLAN TAG#URR8PPP
up vote
-1
down vote
favorite
I was tasked to do a bash script that can audit logins in mysql.
If you activate the general_log
option in /etc/my.cnf
, you can register all the activity that mysql does and it get write (in my case) in /var/lib/mysql/localhost.log
.
If i cat
it, i get this line:
2018-11-18T12:39:46.622298Z 5 Connect Access denied for user 'root'@'localhost' (using password: YES)
So, with that in mind, I made this grep syntax (change the variables to actual numbers and it works!):
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -v denied
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep denied
I also made a grep instruction that counts how many of these logins are made.
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -cv denied
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -c denied
They all work and, AFAIK they are technically correct (spellchecked!).
But I need to bake them into a script so I can take variables from the user and put them into a proper script, but I can't make them work so far: I'm getting the error you can see below when bash
tries to read the first variable.
The code so far:
#!/bin/bash
echo "Year input: "
read -r year
if [[ $year -gt 2020 ]];
then
echo "Incorrect year input."
exit 1
else
echo "Month input: "
read -r month
if [[ $month -gt 12 ]];
then
echo "Incorrect month input."
exit 1
else
echo "Day input: "
read -r day
if [[ $day -gt 31 ]];
then
echo "Incorrect day input."
exit 1
else
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -v denied
logbien=$(grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -cv denied)
echo "Correct logins: "echo "$logbien" | wc -1 " times."
echo ''
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep denied
logmal=$(grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -c denied)
echo "Incorrect logins: "echo "$logmal" | wc -1 " times."
fi
fi
fi
exit 0
The error I get (original: image 1 below):
[root@localhost ~]# sh /medla/sf_compartida/two.sh
Year input:
2018
': not a valid identifiersh: line 3: read: `year
/media/sf_compartida/two.s: line 34: syntax error: unexpected end of file
[root@localhost ~]#
Edit
New code:
#!/bin/bash
read -r -p "Enter the date (YYYY-mm-dd): " date
if ! date=$(date -d "$date" "+%Y-%m-%d")
then
echo "Error: invalid date" >&2
exit 1
fi
year=$date%%-*
if [[ $year -gt 2020 ]]
then
echo "invalid year" >&2
exit 1
else
grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep -v denied
logbien=$(grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep -cv denied)
echo "Correct logins: "echo "$logbien" | wc -1" times."
echo ''
grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep denied
logmal=$(grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep -c denied)
echo "Incorrect logins: "echo "$logmal" | wc -1" times."
fi
The error I get (original: image 2 below):
[root@localhost ~]# sh /media/sf_compartida/two2.sh
Enter the date (YYYY-mm-dd): 2018-11-20
': not a valid identifier.sh: line 2: read: `date
/media/sf compartida/two2.sh: line 9: syntax error in conditional expression
'media/sf_compartida/two2.sh: line 9: syntax error near `]]
'media/sf_compartida/two2.sh: line 9: `if [[ $year -gt 2020 ]]
[root@localhost ~]#
Error 1 - image:
Error 2 - image:
linux bash scripting login mysql
|
show 11 more comments
up vote
-1
down vote
favorite
I was tasked to do a bash script that can audit logins in mysql.
If you activate the general_log
option in /etc/my.cnf
, you can register all the activity that mysql does and it get write (in my case) in /var/lib/mysql/localhost.log
.
If i cat
it, i get this line:
2018-11-18T12:39:46.622298Z 5 Connect Access denied for user 'root'@'localhost' (using password: YES)
So, with that in mind, I made this grep syntax (change the variables to actual numbers and it works!):
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -v denied
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep denied
I also made a grep instruction that counts how many of these logins are made.
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -cv denied
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -c denied
They all work and, AFAIK they are technically correct (spellchecked!).
But I need to bake them into a script so I can take variables from the user and put them into a proper script, but I can't make them work so far: I'm getting the error you can see below when bash
tries to read the first variable.
The code so far:
#!/bin/bash
echo "Year input: "
read -r year
if [[ $year -gt 2020 ]];
then
echo "Incorrect year input."
exit 1
else
echo "Month input: "
read -r month
if [[ $month -gt 12 ]];
then
echo "Incorrect month input."
exit 1
else
echo "Day input: "
read -r day
if [[ $day -gt 31 ]];
then
echo "Incorrect day input."
exit 1
else
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -v denied
logbien=$(grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -cv denied)
echo "Correct logins: "echo "$logbien" | wc -1 " times."
echo ''
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep denied
logmal=$(grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -c denied)
echo "Incorrect logins: "echo "$logmal" | wc -1 " times."
fi
fi
fi
exit 0
The error I get (original: image 1 below):
[root@localhost ~]# sh /medla/sf_compartida/two.sh
Year input:
2018
': not a valid identifiersh: line 3: read: `year
/media/sf_compartida/two.s: line 34: syntax error: unexpected end of file
[root@localhost ~]#
Edit
New code:
#!/bin/bash
read -r -p "Enter the date (YYYY-mm-dd): " date
if ! date=$(date -d "$date" "+%Y-%m-%d")
then
echo "Error: invalid date" >&2
exit 1
fi
year=$date%%-*
if [[ $year -gt 2020 ]]
then
echo "invalid year" >&2
exit 1
else
grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep -v denied
logbien=$(grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep -cv denied)
echo "Correct logins: "echo "$logbien" | wc -1" times."
echo ''
grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep denied
logmal=$(grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep -c denied)
echo "Incorrect logins: "echo "$logmal" | wc -1" times."
fi
The error I get (original: image 2 below):
[root@localhost ~]# sh /media/sf_compartida/two2.sh
Enter the date (YYYY-mm-dd): 2018-11-20
': not a valid identifier.sh: line 2: read: `date
/media/sf compartida/two2.sh: line 9: syntax error in conditional expression
'media/sf_compartida/two2.sh: line 9: syntax error near `]]
'media/sf_compartida/two2.sh: line 9: `if [[ $year -gt 2020 ]]
[root@localhost ~]#
Error 1 - image:
Error 2 - image:
linux bash scripting login mysql
3
shellcheck.net is a good resource for syntax checking shell scripts. You don't have any glaring errors here: you could improve your quoting and command substitution (as pointed out by shellcheck.net). The main problem with the output is thatlogbien
andlogmal
contain the grep output which is newline-separated lines. If you want the number of good logins, you need to count those lines:n_bien=$(echo "$logbien" | wc -l)
– glenn jackman
Nov 25 at 13:58
You may also want to run your script as(export LC_MESSAGES=C; ./your_script)
to report the actual error messages in English.
– fra-san
Nov 25 at 14:06
I hope you don't have a user called "denied" :-)
– Kusalananda
Nov 25 at 14:15
1
The: not an identifier
lines are the key. You have a carriage return character at the end of one or more of yourread
lines. Get rid of them in an editor. They might be displayed as^M
.
– Mark Plotnick
Nov 25 at 21:11
1
Looks like you definitely have CR (r) in there. Remove that semicolon, then rundos2unix < two.sh > twofixed.sh
and see if that new script still has those problems.
– Mark Plotnick
Nov 25 at 23:46
|
show 11 more comments
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I was tasked to do a bash script that can audit logins in mysql.
If you activate the general_log
option in /etc/my.cnf
, you can register all the activity that mysql does and it get write (in my case) in /var/lib/mysql/localhost.log
.
If i cat
it, i get this line:
2018-11-18T12:39:46.622298Z 5 Connect Access denied for user 'root'@'localhost' (using password: YES)
So, with that in mind, I made this grep syntax (change the variables to actual numbers and it works!):
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -v denied
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep denied
I also made a grep instruction that counts how many of these logins are made.
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -cv denied
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -c denied
They all work and, AFAIK they are technically correct (spellchecked!).
But I need to bake them into a script so I can take variables from the user and put them into a proper script, but I can't make them work so far: I'm getting the error you can see below when bash
tries to read the first variable.
The code so far:
#!/bin/bash
echo "Year input: "
read -r year
if [[ $year -gt 2020 ]];
then
echo "Incorrect year input."
exit 1
else
echo "Month input: "
read -r month
if [[ $month -gt 12 ]];
then
echo "Incorrect month input."
exit 1
else
echo "Day input: "
read -r day
if [[ $day -gt 31 ]];
then
echo "Incorrect day input."
exit 1
else
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -v denied
logbien=$(grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -cv denied)
echo "Correct logins: "echo "$logbien" | wc -1 " times."
echo ''
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep denied
logmal=$(grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -c denied)
echo "Incorrect logins: "echo "$logmal" | wc -1 " times."
fi
fi
fi
exit 0
The error I get (original: image 1 below):
[root@localhost ~]# sh /medla/sf_compartida/two.sh
Year input:
2018
': not a valid identifiersh: line 3: read: `year
/media/sf_compartida/two.s: line 34: syntax error: unexpected end of file
[root@localhost ~]#
Edit
New code:
#!/bin/bash
read -r -p "Enter the date (YYYY-mm-dd): " date
if ! date=$(date -d "$date" "+%Y-%m-%d")
then
echo "Error: invalid date" >&2
exit 1
fi
year=$date%%-*
if [[ $year -gt 2020 ]]
then
echo "invalid year" >&2
exit 1
else
grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep -v denied
logbien=$(grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep -cv denied)
echo "Correct logins: "echo "$logbien" | wc -1" times."
echo ''
grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep denied
logmal=$(grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep -c denied)
echo "Incorrect logins: "echo "$logmal" | wc -1" times."
fi
The error I get (original: image 2 below):
[root@localhost ~]# sh /media/sf_compartida/two2.sh
Enter the date (YYYY-mm-dd): 2018-11-20
': not a valid identifier.sh: line 2: read: `date
/media/sf compartida/two2.sh: line 9: syntax error in conditional expression
'media/sf_compartida/two2.sh: line 9: syntax error near `]]
'media/sf_compartida/two2.sh: line 9: `if [[ $year -gt 2020 ]]
[root@localhost ~]#
Error 1 - image:
Error 2 - image:
linux bash scripting login mysql
I was tasked to do a bash script that can audit logins in mysql.
If you activate the general_log
option in /etc/my.cnf
, you can register all the activity that mysql does and it get write (in my case) in /var/lib/mysql/localhost.log
.
If i cat
it, i get this line:
2018-11-18T12:39:46.622298Z 5 Connect Access denied for user 'root'@'localhost' (using password: YES)
So, with that in mind, I made this grep syntax (change the variables to actual numbers and it works!):
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -v denied
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep denied
I also made a grep instruction that counts how many of these logins are made.
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -cv denied
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -c denied
They all work and, AFAIK they are technically correct (spellchecked!).
But I need to bake them into a script so I can take variables from the user and put them into a proper script, but I can't make them work so far: I'm getting the error you can see below when bash
tries to read the first variable.
The code so far:
#!/bin/bash
echo "Year input: "
read -r year
if [[ $year -gt 2020 ]];
then
echo "Incorrect year input."
exit 1
else
echo "Month input: "
read -r month
if [[ $month -gt 12 ]];
then
echo "Incorrect month input."
exit 1
else
echo "Day input: "
read -r day
if [[ $day -gt 31 ]];
then
echo "Incorrect day input."
exit 1
else
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -v denied
logbien=$(grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -cv denied)
echo "Correct logins: "echo "$logbien" | wc -1 " times."
echo ''
grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep denied
logmal=$(grep "$year"-"$month"-"$day" /var/lib/mysql/localhost.log | grep Connect | grep -c denied)
echo "Incorrect logins: "echo "$logmal" | wc -1 " times."
fi
fi
fi
exit 0
The error I get (original: image 1 below):
[root@localhost ~]# sh /medla/sf_compartida/two.sh
Year input:
2018
': not a valid identifiersh: line 3: read: `year
/media/sf_compartida/two.s: line 34: syntax error: unexpected end of file
[root@localhost ~]#
Edit
New code:
#!/bin/bash
read -r -p "Enter the date (YYYY-mm-dd): " date
if ! date=$(date -d "$date" "+%Y-%m-%d")
then
echo "Error: invalid date" >&2
exit 1
fi
year=$date%%-*
if [[ $year -gt 2020 ]]
then
echo "invalid year" >&2
exit 1
else
grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep -v denied
logbien=$(grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep -cv denied)
echo "Correct logins: "echo "$logbien" | wc -1" times."
echo ''
grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep denied
logmal=$(grep "$date" /var/lib/mysql/localhost.log | grep Connect | grep -c denied)
echo "Incorrect logins: "echo "$logmal" | wc -1" times."
fi
The error I get (original: image 2 below):
[root@localhost ~]# sh /media/sf_compartida/two2.sh
Enter the date (YYYY-mm-dd): 2018-11-20
': not a valid identifier.sh: line 2: read: `date
/media/sf compartida/two2.sh: line 9: syntax error in conditional expression
'media/sf_compartida/two2.sh: line 9: syntax error near `]]
'media/sf_compartida/two2.sh: line 9: `if [[ $year -gt 2020 ]]
[root@localhost ~]#
Error 1 - image:
Error 2 - image:
linux bash scripting login mysql
linux bash scripting login mysql
edited Nov 26 at 15:12
fra-san
1,026214
1,026214
asked Nov 25 at 13:45
jfalava
13
13
3
shellcheck.net is a good resource for syntax checking shell scripts. You don't have any glaring errors here: you could improve your quoting and command substitution (as pointed out by shellcheck.net). The main problem with the output is thatlogbien
andlogmal
contain the grep output which is newline-separated lines. If you want the number of good logins, you need to count those lines:n_bien=$(echo "$logbien" | wc -l)
– glenn jackman
Nov 25 at 13:58
You may also want to run your script as(export LC_MESSAGES=C; ./your_script)
to report the actual error messages in English.
– fra-san
Nov 25 at 14:06
I hope you don't have a user called "denied" :-)
– Kusalananda
Nov 25 at 14:15
1
The: not an identifier
lines are the key. You have a carriage return character at the end of one or more of yourread
lines. Get rid of them in an editor. They might be displayed as^M
.
– Mark Plotnick
Nov 25 at 21:11
1
Looks like you definitely have CR (r) in there. Remove that semicolon, then rundos2unix < two.sh > twofixed.sh
and see if that new script still has those problems.
– Mark Plotnick
Nov 25 at 23:46
|
show 11 more comments
3
shellcheck.net is a good resource for syntax checking shell scripts. You don't have any glaring errors here: you could improve your quoting and command substitution (as pointed out by shellcheck.net). The main problem with the output is thatlogbien
andlogmal
contain the grep output which is newline-separated lines. If you want the number of good logins, you need to count those lines:n_bien=$(echo "$logbien" | wc -l)
– glenn jackman
Nov 25 at 13:58
You may also want to run your script as(export LC_MESSAGES=C; ./your_script)
to report the actual error messages in English.
– fra-san
Nov 25 at 14:06
I hope you don't have a user called "denied" :-)
– Kusalananda
Nov 25 at 14:15
1
The: not an identifier
lines are the key. You have a carriage return character at the end of one or more of yourread
lines. Get rid of them in an editor. They might be displayed as^M
.
– Mark Plotnick
Nov 25 at 21:11
1
Looks like you definitely have CR (r) in there. Remove that semicolon, then rundos2unix < two.sh > twofixed.sh
and see if that new script still has those problems.
– Mark Plotnick
Nov 25 at 23:46
3
3
shellcheck.net is a good resource for syntax checking shell scripts. You don't have any glaring errors here: you could improve your quoting and command substitution (as pointed out by shellcheck.net). The main problem with the output is that
logbien
and logmal
contain the grep output which is newline-separated lines. If you want the number of good logins, you need to count those lines: n_bien=$(echo "$logbien" | wc -l)
– glenn jackman
Nov 25 at 13:58
shellcheck.net is a good resource for syntax checking shell scripts. You don't have any glaring errors here: you could improve your quoting and command substitution (as pointed out by shellcheck.net). The main problem with the output is that
logbien
and logmal
contain the grep output which is newline-separated lines. If you want the number of good logins, you need to count those lines: n_bien=$(echo "$logbien" | wc -l)
– glenn jackman
Nov 25 at 13:58
You may also want to run your script as
(export LC_MESSAGES=C; ./your_script)
to report the actual error messages in English.– fra-san
Nov 25 at 14:06
You may also want to run your script as
(export LC_MESSAGES=C; ./your_script)
to report the actual error messages in English.– fra-san
Nov 25 at 14:06
I hope you don't have a user called "denied" :-)
– Kusalananda
Nov 25 at 14:15
I hope you don't have a user called "denied" :-)
– Kusalananda
Nov 25 at 14:15
1
1
The
: not an identifier
lines are the key. You have a carriage return character at the end of one or more of your read
lines. Get rid of them in an editor. They might be displayed as ^M
.– Mark Plotnick
Nov 25 at 21:11
The
: not an identifier
lines are the key. You have a carriage return character at the end of one or more of your read
lines. Get rid of them in an editor. They might be displayed as ^M
.– Mark Plotnick
Nov 25 at 21:11
1
1
Looks like you definitely have CR (r) in there. Remove that semicolon, then run
dos2unix < two.sh > twofixed.sh
and see if that new script still has those problems.– Mark Plotnick
Nov 25 at 23:46
Looks like you definitely have CR (r) in there. Remove that semicolon, then run
dos2unix < two.sh > twofixed.sh
and see if that new script still has those problems.– Mark Plotnick
Nov 25 at 23:46
|
show 11 more comments
1 Answer
1
active
oldest
votes
up vote
1
down vote
This is not an answer, but a bit of code review: I would offer this to improve your date entry: get the user to enter the date at once, and use the date
command to validate and normalize the user's input.
read -r -p "Enter the date (YYYY-mm-dd): " date
if ! date=$(date -d "$date" "+%Y-%m-%d"); then
echo "Error: invalid date" >&2
exit 1
fi
year=$date%%-*
if [[ $year -gt 2020 ]]; then echo "invalid year" >&2; exit 1; fi
# then: grep "$date" logfile ...
i appreciate that revision! it looks much more cleaner than my initial solution, no doubt. But i still get a lot of error messages. I used the shellcheck and it found no errors whatsoever. I'll add the new code in the post. Thanks!
– jfalava
Nov 25 at 16:47
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
This is not an answer, but a bit of code review: I would offer this to improve your date entry: get the user to enter the date at once, and use the date
command to validate and normalize the user's input.
read -r -p "Enter the date (YYYY-mm-dd): " date
if ! date=$(date -d "$date" "+%Y-%m-%d"); then
echo "Error: invalid date" >&2
exit 1
fi
year=$date%%-*
if [[ $year -gt 2020 ]]; then echo "invalid year" >&2; exit 1; fi
# then: grep "$date" logfile ...
i appreciate that revision! it looks much more cleaner than my initial solution, no doubt. But i still get a lot of error messages. I used the shellcheck and it found no errors whatsoever. I'll add the new code in the post. Thanks!
– jfalava
Nov 25 at 16:47
add a comment |
up vote
1
down vote
This is not an answer, but a bit of code review: I would offer this to improve your date entry: get the user to enter the date at once, and use the date
command to validate and normalize the user's input.
read -r -p "Enter the date (YYYY-mm-dd): " date
if ! date=$(date -d "$date" "+%Y-%m-%d"); then
echo "Error: invalid date" >&2
exit 1
fi
year=$date%%-*
if [[ $year -gt 2020 ]]; then echo "invalid year" >&2; exit 1; fi
# then: grep "$date" logfile ...
i appreciate that revision! it looks much more cleaner than my initial solution, no doubt. But i still get a lot of error messages. I used the shellcheck and it found no errors whatsoever. I'll add the new code in the post. Thanks!
– jfalava
Nov 25 at 16:47
add a comment |
up vote
1
down vote
up vote
1
down vote
This is not an answer, but a bit of code review: I would offer this to improve your date entry: get the user to enter the date at once, and use the date
command to validate and normalize the user's input.
read -r -p "Enter the date (YYYY-mm-dd): " date
if ! date=$(date -d "$date" "+%Y-%m-%d"); then
echo "Error: invalid date" >&2
exit 1
fi
year=$date%%-*
if [[ $year -gt 2020 ]]; then echo "invalid year" >&2; exit 1; fi
# then: grep "$date" logfile ...
This is not an answer, but a bit of code review: I would offer this to improve your date entry: get the user to enter the date at once, and use the date
command to validate and normalize the user's input.
read -r -p "Enter the date (YYYY-mm-dd): " date
if ! date=$(date -d "$date" "+%Y-%m-%d"); then
echo "Error: invalid date" >&2
exit 1
fi
year=$date%%-*
if [[ $year -gt 2020 ]]; then echo "invalid year" >&2; exit 1; fi
# then: grep "$date" logfile ...
answered Nov 25 at 14:04
community wiki
glenn jackman
i appreciate that revision! it looks much more cleaner than my initial solution, no doubt. But i still get a lot of error messages. I used the shellcheck and it found no errors whatsoever. I'll add the new code in the post. Thanks!
– jfalava
Nov 25 at 16:47
add a comment |
i appreciate that revision! it looks much more cleaner than my initial solution, no doubt. But i still get a lot of error messages. I used the shellcheck and it found no errors whatsoever. I'll add the new code in the post. Thanks!
– jfalava
Nov 25 at 16:47
i appreciate that revision! it looks much more cleaner than my initial solution, no doubt. But i still get a lot of error messages. I used the shellcheck and it found no errors whatsoever. I'll add the new code in the post. Thanks!
– jfalava
Nov 25 at 16:47
i appreciate that revision! it looks much more cleaner than my initial solution, no doubt. But i still get a lot of error messages. I used the shellcheck and it found no errors whatsoever. I'll add the new code in the post. Thanks!
– jfalava
Nov 25 at 16:47
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2funix.stackexchange.com%2fquestions%2f484040%2frhel-syntax-errors-with-bash-script%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
3
shellcheck.net is a good resource for syntax checking shell scripts. You don't have any glaring errors here: you could improve your quoting and command substitution (as pointed out by shellcheck.net). The main problem with the output is that
logbien
andlogmal
contain the grep output which is newline-separated lines. If you want the number of good logins, you need to count those lines:n_bien=$(echo "$logbien" | wc -l)
– glenn jackman
Nov 25 at 13:58
You may also want to run your script as
(export LC_MESSAGES=C; ./your_script)
to report the actual error messages in English.– fra-san
Nov 25 at 14:06
I hope you don't have a user called "denied" :-)
– Kusalananda
Nov 25 at 14:15
1
The
: not an identifier
lines are the key. You have a carriage return character at the end of one or more of yourread
lines. Get rid of them in an editor. They might be displayed as^M
.– Mark Plotnick
Nov 25 at 21:11
1
Looks like you definitely have CR (r) in there. Remove that semicolon, then run
dos2unix < two.sh > twofixed.sh
and see if that new script still has those problems.– Mark Plotnick
Nov 25 at 23:46