pipe commands inside find -exec?
Let's suppose I want to find all .txt files and search for some string. I would do:
find ./ -type f -name "*.txt" -exec egrep -iH 'something' '{}' ;
What if I want to do a more complex filtering, like this:
egrep something file.txt | egrep somethingelse | egrep other
Inside find -exec? (or similar)
Please keep in mind that I'm searching for a solution that I could easily type when I need it. I know that this could be done with a few lines using a shell script, but that isn't what I'm looking for.
shell find pipe
edited Mar 18 at 16:43
terdon♦
133k32266446
asked Mar 18 at 16:38
1nt3rn3t1nt3rn3t
232
add a comment |
Let's suppose I want to find all .txt files and search for some string. I would do:
find ./ -type f -name "*.txt" -exec egrep -iH 'something' '{}' ;
What if I want to do a more complex filtering, like this:
egrep something file.txt | egrep somethingelse | egrep other
Inside find -exec? (or similar)
Please keep in mind that I'm searching for a solution that I could easily type when I need it. I know that this could be done with a few lines using a shell script, but that isn't what I'm looking for.
shell find pipe
edited Mar 18 at 16:43
terdon♦
133k32266446
asked Mar 18 at 16:38
1nt3rn3t1nt3rn3t
232
add a comment |
Let's suppose I want to find all .txt files and search for some string. I would do:
find ./ -type f -name "*.txt" -exec egrep -iH 'something' '{}' ;
What if I want to do a more complex filtering, like this:
egrep something file.txt | egrep somethingelse | egrep other
Inside find -exec? (or similar)
Please keep in mind that I'm searching for a solution that I could easily type when I need it. I know that this could be done with a few lines using a shell script, but that isn't what I'm looking for.
shell find pipe
edited Mar 18 at 16:43
terdon♦
133k32266446
asked Mar 18 at 16:38
1nt3rn3t1nt3rn3t
232
Let's suppose I want to find all .txt files and search for some string. I would do:
find ./ -type f -name "*.txt" -exec egrep -iH 'something' '{}' ;
What if I want to do a more complex filtering, like this:
egrep something file.txt | egrep somethingelse | egrep other
Inside find -exec? (or similar)
Please keep in mind that I'm searching for a solution that I could easily type when I need it. I know that this could be done with a few lines using a shell script, but that isn't what I'm looking for.
shell find pipe
shell find pipe
edited Mar 18 at 16:43
terdon♦
133k32266446
asked Mar 18 at 16:38
1nt3rn3t1nt3rn3t
232
edited Mar 18 at 16:43
terdon♦
133k32266446
asked Mar 18 at 16:38
1nt3rn3t1nt3rn3t
232
edited Mar 18 at 16:43
terdon♦
133k32266446
edited Mar 18 at 16:43
terdon♦
133k32266446
edited Mar 18 at 16:43
terdon♦
133k32266446
133k32266446
asked Mar 18 at 16:38
1nt3rn3t1nt3rn3t
232
asked Mar 18 at 16:38
1nt3rn3t1nt3rn3t
232
asked Mar 18 at 16:38
1nt3rn3t1nt3rn3t
232
232
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
If you must do it from within find, you need to call a shell:
find ./ -type f -name "*.txt" -exec sh -c 'grep -EiH something "$1" | grep -E somethingelse | grep -E other' sh {} ;
Other alternatives include using xargs instead:
find ./ -type f -name "*.txt" |
xargs -I{} grep -EiH something {} |
grep -EiH somethingelse |
grep -EiH other
Or, much safer for arbitrary filenames (assuming your find supports -print0):
find ./ -type f -name "*.txt" -print0 |
xargs -0 grep -EiH something {} |
grep -Ei somethingelse |
grep -Ei other
Or, you could just use a shell loop instead:
find ./ -type f -name "*.txt" -print0 |
while IFS= read -d '' file; do
grep -Ei something "$file" |
grep -Ei somethingelse |
grep -Ei other
done
edited Mar 18 at 17:20
Kusalananda♦
138k17258426
answered Mar 18 at 16:51
terdon♦terdon
133k32266446
The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.
– 1nt3rn3t
Mar 18 at 16:57
1
... andxargscould also be used asxargs -I {} sh -c '...' sh {}, if one wanted to (it makes it possible to run parallel jobs with-Pif one wanted to).
– Kusalananda♦
Mar 18 at 17:23
add a comment |
Edit: This answer is not preferred, but is left here for comparison and illustration of potentially dangerous pitfalls in bash scripting.
You can put bash (or another shell) as your -exec command:
find -type -f -name "*.txt" -exec bash -c 'egrep -iH something "{}" | egrep somethingelse | egrep other' ;
One of the downsides of doing it this way is that it creates more potential for nested quoting issues as your commands get more complex. If you want to avoid that, you can break it out into a for-loop:
for i in $(find -type -f -name "*.txt"); do
if egrep -iH something "$i" | egrep somethingelse | egrep other; then
echo "Found something: $i"
fi
done
answered Mar 18 at 16:55
trobinsontrobinson
443
1
The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.
– 1nt3rn3t
Mar 18 at 16:59
1
Thatforloop is a very bad idea.Also known as bash pitfall #1.
– terdon♦
Mar 18 at 17:04
1
This"{}"in your first command may even lead to code injection. Imagine you got files from me and there's a file literally named" & rm -rf ~ & : ".txt. Luckily for you-type -fis invalid, it just saved your home directory. Fix the typo and try again. :) terdon did it right:find … -exec sh -c '… "$1" …' foo {} ;.
– Kamil Maciorowski
Mar 18 at 17:55
Thanks for the information! Yeah, the-type -fis a typo I make constantly when usingfind, and I didn't notice it in my answer. Whoops. terdon's answer is better, but I'll leave this for comparative purposes.
– trobinson
Mar 18 at 20:20
@terdon: tx for referencing the mywiki.wooledge.org page. It's nice to have a bunch of GPs neatly summarized in one place.
– Cbhihe
Mar 19 at 8:03
|
show 1 more comment
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
});
}
});
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%2f507023%2fpipe-commands-inside-find-exec%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you must do it from within find, you need to call a shell:
find ./ -type f -name "*.txt" -exec sh -c 'grep -EiH something "$1" | grep -E somethingelse | grep -E other' sh {} ;
Other alternatives include using xargs instead:
find ./ -type f -name "*.txt" |
xargs -I{} grep -EiH something {} |
grep -EiH somethingelse |
grep -EiH other
Or, much safer for arbitrary filenames (assuming your find supports -print0):
find ./ -type f -name "*.txt" -print0 |
xargs -0 grep -EiH something {} |
grep -Ei somethingelse |
grep -Ei other
Or, you could just use a shell loop instead:
find ./ -type f -name "*.txt" -print0 |
while IFS= read -d '' file; do
grep -Ei something "$file" |
grep -Ei somethingelse |
grep -Ei other
done
edited Mar 18 at 17:20
Kusalananda♦
138k17258426
answered Mar 18 at 16:51
terdon♦terdon
133k32266446
The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.
– 1nt3rn3t
Mar 18 at 16:57
1
... andxargscould also be used asxargs -I {} sh -c '...' sh {}, if one wanted to (it makes it possible to run parallel jobs with-Pif one wanted to).
– Kusalananda♦
Mar 18 at 17:23
add a comment |
If you must do it from within find, you need to call a shell:
find ./ -type f -name "*.txt" -exec sh -c 'grep -EiH something "$1" | grep -E somethingelse | grep -E other' sh {} ;
Other alternatives include using xargs instead:
find ./ -type f -name "*.txt" |
xargs -I{} grep -EiH something {} |
grep -EiH somethingelse |
grep -EiH other
Or, much safer for arbitrary filenames (assuming your find supports -print0):
find ./ -type f -name "*.txt" -print0 |
xargs -0 grep -EiH something {} |
grep -Ei somethingelse |
grep -Ei other
Or, you could just use a shell loop instead:
find ./ -type f -name "*.txt" -print0 |
while IFS= read -d '' file; do
grep -Ei something "$file" |
grep -Ei somethingelse |
grep -Ei other
done
edited Mar 18 at 17:20
Kusalananda♦
138k17258426
answered Mar 18 at 16:51
terdon♦terdon
133k32266446
The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.
– 1nt3rn3t
Mar 18 at 16:57
1
... andxargscould also be used asxargs -I {} sh -c '...' sh {}, if one wanted to (it makes it possible to run parallel jobs with-Pif one wanted to).
– Kusalananda♦
Mar 18 at 17:23
add a comment |
If you must do it from within find, you need to call a shell:
find ./ -type f -name "*.txt" -exec sh -c 'grep -EiH something "$1" | grep -E somethingelse | grep -E other' sh {} ;
Other alternatives include using xargs instead:
find ./ -type f -name "*.txt" |
xargs -I{} grep -EiH something {} |
grep -EiH somethingelse |
grep -EiH other
Or, much safer for arbitrary filenames (assuming your find supports -print0):
find ./ -type f -name "*.txt" -print0 |
xargs -0 grep -EiH something {} |
grep -Ei somethingelse |
grep -Ei other
Or, you could just use a shell loop instead:
find ./ -type f -name "*.txt" -print0 |
while IFS= read -d '' file; do
grep -Ei something "$file" |
grep -Ei somethingelse |
grep -Ei other
done
edited Mar 18 at 17:20
Kusalananda♦
138k17258426
answered Mar 18 at 16:51
terdon♦terdon
133k32266446
If you must do it from within find, you need to call a shell:
find ./ -type f -name "*.txt" -exec sh -c 'grep -EiH something "$1" | grep -E somethingelse | grep -E other' sh {} ;
Other alternatives include using xargs instead:
find ./ -type f -name "*.txt" |
xargs -I{} grep -EiH something {} |
grep -EiH somethingelse |
grep -EiH other
Or, much safer for arbitrary filenames (assuming your find supports -print0):
find ./ -type f -name "*.txt" -print0 |
xargs -0 grep -EiH something {} |
grep -Ei somethingelse |
grep -Ei other
Or, you could just use a shell loop instead:
find ./ -type f -name "*.txt" -print0 |
while IFS= read -d '' file; do
grep -Ei something "$file" |
grep -Ei somethingelse |
grep -Ei other
done
edited Mar 18 at 17:20
Kusalananda♦
138k17258426
answered Mar 18 at 16:51
terdon♦terdon
133k32266446
edited Mar 18 at 17:20
Kusalananda♦
138k17258426
edited Mar 18 at 17:20
Kusalananda♦
138k17258426
edited Mar 18 at 17:20
Kusalananda♦
138k17258426
138k17258426
answered Mar 18 at 16:51
terdon♦terdon
133k32266446
answered Mar 18 at 16:51
terdon♦terdon
133k32266446
answered Mar 18 at 16:51
terdon♦terdon
133k32266446
133k32266446
The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.
– 1nt3rn3t
Mar 18 at 16:57
1
... andxargscould also be used asxargs -I {} sh -c '...' sh {}, if one wanted to (it makes it possible to run parallel jobs with-Pif one wanted to).
– Kusalananda♦
Mar 18 at 17:23
add a comment |
The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.
– 1nt3rn3t
Mar 18 at 16:57
1
... andxargscould also be used asxargs -I {} sh -c '...' sh {}, if one wanted to (it makes it possible to run parallel jobs with-Pif one wanted to).
– Kusalananda♦
Mar 18 at 17:23
The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.
– 1nt3rn3t
Mar 18 at 16:57
The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.
– 1nt3rn3t
Mar 18 at 16:57
1
1
... and
xargs could also be used as xargs -I {} sh -c '...' sh {}, if one wanted to (it makes it possible to run parallel jobs with -P if one wanted to).– Kusalananda♦
Mar 18 at 17:23
... and
xargs could also be used as xargs -I {} sh -c '...' sh {}, if one wanted to (it makes it possible to run parallel jobs with -P if one wanted to).– Kusalananda♦
Mar 18 at 17:23
add a comment |
Edit: This answer is not preferred, but is left here for comparison and illustration of potentially dangerous pitfalls in bash scripting.
You can put bash (or another shell) as your -exec command:
find -type -f -name "*.txt" -exec bash -c 'egrep -iH something "{}" | egrep somethingelse | egrep other' ;
One of the downsides of doing it this way is that it creates more potential for nested quoting issues as your commands get more complex. If you want to avoid that, you can break it out into a for-loop:
for i in $(find -type -f -name "*.txt"); do
if egrep -iH something "$i" | egrep somethingelse | egrep other; then
echo "Found something: $i"
fi
done
answered Mar 18 at 16:55
trobinsontrobinson
443
1
The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.
– 1nt3rn3t
Mar 18 at 16:59
1
Thatforloop is a very bad idea.Also known as bash pitfall #1.
– terdon♦
Mar 18 at 17:04
1
This"{}"in your first command may even lead to code injection. Imagine you got files from me and there's a file literally named" & rm -rf ~ & : ".txt. Luckily for you-type -fis invalid, it just saved your home directory. Fix the typo and try again. :) terdon did it right:find … -exec sh -c '… "$1" …' foo {} ;.
– Kamil Maciorowski
Mar 18 at 17:55
Thanks for the information! Yeah, the-type -fis a typo I make constantly when usingfind, and I didn't notice it in my answer. Whoops. terdon's answer is better, but I'll leave this for comparative purposes.
– trobinson
Mar 18 at 20:20
@terdon: tx for referencing the mywiki.wooledge.org page. It's nice to have a bunch of GPs neatly summarized in one place.
– Cbhihe
Mar 19 at 8:03
|
show 1 more comment
Edit: This answer is not preferred, but is left here for comparison and illustration of potentially dangerous pitfalls in bash scripting.
You can put bash (or another shell) as your -exec command:
find -type -f -name "*.txt" -exec bash -c 'egrep -iH something "{}" | egrep somethingelse | egrep other' ;
One of the downsides of doing it this way is that it creates more potential for nested quoting issues as your commands get more complex. If you want to avoid that, you can break it out into a for-loop:
for i in $(find -type -f -name "*.txt"); do
if egrep -iH something "$i" | egrep somethingelse | egrep other; then
echo "Found something: $i"
fi
done
answered Mar 18 at 16:55
trobinsontrobinson
443
1
The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.
– 1nt3rn3t
Mar 18 at 16:59
1
Thatforloop is a very bad idea.Also known as bash pitfall #1.
– terdon♦
Mar 18 at 17:04
1
This"{}"in your first command may even lead to code injection. Imagine you got files from me and there's a file literally named" & rm -rf ~ & : ".txt. Luckily for you-type -fis invalid, it just saved your home directory. Fix the typo and try again. :) terdon did it right:find … -exec sh -c '… "$1" …' foo {} ;.
– Kamil Maciorowski
Mar 18 at 17:55
Thanks for the information! Yeah, the-type -fis a typo I make constantly when usingfind, and I didn't notice it in my answer. Whoops. terdon's answer is better, but I'll leave this for comparative purposes.
– trobinson
Mar 18 at 20:20
@terdon: tx for referencing the mywiki.wooledge.org page. It's nice to have a bunch of GPs neatly summarized in one place.
– Cbhihe
Mar 19 at 8:03
|
show 1 more comment
Edit: This answer is not preferred, but is left here for comparison and illustration of potentially dangerous pitfalls in bash scripting.
You can put bash (or another shell) as your -exec command:
find -type -f -name "*.txt" -exec bash -c 'egrep -iH something "{}" | egrep somethingelse | egrep other' ;
One of the downsides of doing it this way is that it creates more potential for nested quoting issues as your commands get more complex. If you want to avoid that, you can break it out into a for-loop:
for i in $(find -type -f -name "*.txt"); do
if egrep -iH something "$i" | egrep somethingelse | egrep other; then
echo "Found something: $i"
fi
done
answered Mar 18 at 16:55
trobinsontrobinson
443
Edit: This answer is not preferred, but is left here for comparison and illustration of potentially dangerous pitfalls in bash scripting.
You can put bash (or another shell) as your -exec command:
find -type -f -name "*.txt" -exec bash -c 'egrep -iH something "{}" | egrep somethingelse | egrep other' ;
One of the downsides of doing it this way is that it creates more potential for nested quoting issues as your commands get more complex. If you want to avoid that, you can break it out into a for-loop:
for i in $(find -type -f -name "*.txt"); do
if egrep -iH something "$i" | egrep somethingelse | egrep other; then
echo "Found something: $i"
fi
done
answered Mar 18 at 16:55
trobinsontrobinson
443
edited Mar 20 at 6:43
answered Mar 18 at 16:55
trobinsontrobinson
443
answered Mar 18 at 16:55
trobinsontrobinson
443
answered Mar 18 at 16:55
trobinsontrobinson
443
443
1
The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.
– 1nt3rn3t
Mar 18 at 16:59
1
Thatforloop is a very bad idea.Also known as bash pitfall #1.
– terdon♦
Mar 18 at 17:04
1
This"{}"in your first command may even lead to code injection. Imagine you got files from me and there's a file literally named" & rm -rf ~ & : ".txt. Luckily for you-type -fis invalid, it just saved your home directory. Fix the typo and try again. :) terdon did it right:find … -exec sh -c '… "$1" …' foo {} ;.
– Kamil Maciorowski
Mar 18 at 17:55
Thanks for the information! Yeah, the-type -fis a typo I make constantly when usingfind, and I didn't notice it in my answer. Whoops. terdon's answer is better, but I'll leave this for comparative purposes.
– trobinson
Mar 18 at 20:20
@terdon: tx for referencing the mywiki.wooledge.org page. It's nice to have a bunch of GPs neatly summarized in one place.
– Cbhihe
Mar 19 at 8:03
|
show 1 more comment
1
The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.
– 1nt3rn3t
Mar 18 at 16:59
1
Thatforloop is a very bad idea.Also known as bash pitfall #1.
– terdon♦
Mar 18 at 17:04
1
This"{}"in your first command may even lead to code injection. Imagine you got files from me and there's a file literally named" & rm -rf ~ & : ".txt. Luckily for you-type -fis invalid, it just saved your home directory. Fix the typo and try again. :) terdon did it right:find … -exec sh -c '… "$1" …' foo {} ;.
– Kamil Maciorowski
Mar 18 at 17:55
Thanks for the information! Yeah, the-type -fis a typo I make constantly when usingfind, and I didn't notice it in my answer. Whoops. terdon's answer is better, but I'll leave this for comparative purposes.
– trobinson
Mar 18 at 20:20
@terdon: tx for referencing the mywiki.wooledge.org page. It's nice to have a bunch of GPs neatly summarized in one place.
– Cbhihe
Mar 19 at 8:03
1
1
The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.
– 1nt3rn3t
Mar 18 at 16:59
The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.
– 1nt3rn3t
Mar 18 at 16:59
1
1
That
for loop is a very bad idea.Also known as bash pitfall #1.– terdon♦
Mar 18 at 17:04
That
for loop is a very bad idea.Also known as bash pitfall #1.– terdon♦
Mar 18 at 17:04
1
1
This
"{}" in your first command may even lead to code injection. Imagine you got files from me and there's a file literally named " & rm -rf ~ & : ".txt. Luckily for you -type -f is invalid, it just saved your home directory. Fix the typo and try again. :) terdon did it right: find … -exec sh -c '… "$1" …' foo {} ;.– Kamil Maciorowski
Mar 18 at 17:55
This
"{}" in your first command may even lead to code injection. Imagine you got files from me and there's a file literally named " & rm -rf ~ & : ".txt. Luckily for you -type -f is invalid, it just saved your home directory. Fix the typo and try again. :) terdon did it right: find … -exec sh -c '… "$1" …' foo {} ;.– Kamil Maciorowski
Mar 18 at 17:55
Thanks for the information! Yeah, the
-type -f is a typo I make constantly when using find, and I didn't notice it in my answer. Whoops. terdon's answer is better, but I'll leave this for comparative purposes.– trobinson
Mar 18 at 20:20
Thanks for the information! Yeah, the
-type -f is a typo I make constantly when using find, and I didn't notice it in my answer. Whoops. terdon's answer is better, but I'll leave this for comparative purposes.– trobinson
Mar 18 at 20:20
@terdon: tx for referencing the mywiki.wooledge.org page. It's nice to have a bunch of GPs neatly summarized in one place.
– Cbhihe
Mar 19 at 8:03
@terdon: tx for referencing the mywiki.wooledge.org page. It's nice to have a bunch of GPs neatly summarized in one place.
– Cbhihe
Mar 19 at 8:03
|
show 1 more 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.
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%2f507023%2fpipe-commands-inside-find-exec%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
