Re: nohup Versus setsid

 Janis Papanagnou <janis_papanagnou+ng@hotmail.com>:

>
A long time passed that I used nohup - I thought there was an option to define the output file - but if I inspect the specs it seems that redirection of stdin suffices to choose arbitrary files. >

 If you substitute stdout for stdin you'll get what the standard  describes in  (<https://pubs.opengroup.org/onlinepubs/9799919799/utilities/nohup.html#tag_20_89_03>):  If standard error is a terminal and standard output is open but  is not a terminal, all output written by the named utility to its  standard error shall be redirected to the same open file  description as the standard output.    nohup a_command ... >> an_arbitrary_file

(Did I misread the POSIX specs?) >

 Other than that you read "stdin" where the POSIX specs write  "stdout", no.