Timeline for nohup output redirection to a different file
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 20, 2018 at 7:14 | comment | added | tripleee |
The file nohup.out will be created in the case of error output, too; but if you redirect both stdout and stderr, there cannot be any output, so the file will not be created. But the &> syntax is not POSIX-compliant; you're better off with the answer by Irshad Khan elsewhere on this page.
|
|
| Nov 4, 2015 at 18:58 | vote | accept | sds | ||
| Jan 21, 2015 at 8:29 | comment | added | Piotr Dobrogost |
GNU nohup says that it'll redirect stdout to a file if you specify nohup command > file Isn't redirection in case of nohup command > file being handled by shell and not nohup? If so then how can nohup take any action based on weather redirection is present or not?
|
|
| Feb 14, 2013 at 15:50 | comment | added | slhck |
GNU nohup says that it'll redirect stdout to a file if you specify nohup command > file. BSD nohup doesn't mention this at all, but it worked for me.
|
|
| Feb 14, 2013 at 15:45 | comment | added | grawity_u1686 |
Will it prevent nohup from performing its own redirection?
|
|
| Feb 14, 2013 at 15:44 | history | answered | slhck | CC BY-SA 3.0 |