Timeline for Does nohup work across a pipe?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 8, 2020 at 18:00 | comment | added | Wolph |
@KévinBerthommier the & is placed at the right location. Did you forget the quotes perhaps?
|
|
| Dec 8, 2020 at 17:26 | review | Suggested edits | |||
| Dec 11, 2020 at 22:40 | |||||
| Jul 31, 2017 at 2:40 | comment | added | Wolph |
@RoVo I think I may have placed the & at the wrong location with the original answer, try the updated answer :)
|
|
| Jul 31, 2017 at 2:40 | history | edited | Wolph | CC BY-SA 3.0 |
edited body
|
| Jul 28, 2017 at 7:32 | comment | added | pLumo |
I did not change the first EOF. EOF is working, but not EOF &. Just opens a new line. I use GNU bash, version 4.3.48(1)-release (x86_64-pc-linux-gnu). The first option works for me though, just needed bash -c for having bash builtins.
|
|
| Jul 27, 2017 at 21:53 | comment | added | Wolph |
@RoVo: the EOF depends on the earlier EOF and is the standard for multiline input in bash-like shells. If you changed the <<EOF to something else the EOF at the end needs to change too. Which shell (and version) are you using?
|
|
| May 15, 2017 at 22:04 | comment | added | Wolph |
The $SHELL contains your currently running shell, on most Linux systems this will be /bin/bash but it could be /usr/bin/zsh or something else. The advantage of using the $SHELL variable is that this way the command will be executed using your regular shell settings.
|
|
| May 15, 2017 at 18:09 | comment | added | santiago arizti |
can someone please explain what is $SHELL and why we need it?
|
|
| Nov 13, 2014 at 17:19 | vote | accept | Jasmine Lognnes | ||
| Nov 13, 2014 at 16:47 | history | edited | Wolph | CC BY-SA 3.0 |
deleted 41 characters in body
|
| Nov 13, 2014 at 15:17 | history | answered | Wolph | CC BY-SA 3.0 |