Edit - Unix & Linux Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Re: there's nothing wrong. Daemons should really open either "/dev/null" or a logger on file descriptors 1 and 2 before execve'ing other programs. Otherwise, you may end up with log output on data files. Bear in mind that even if the program doesn't appear to output anything to std{out,err}, libraries may. Even glibc can output to stderr if LIBC_FATAL_STDERR_ is set ot if it cannot open "/dev/tty".

ninjalj
– ninjalj

2013-11-11 16:43:01 +00:00
Commented Nov 11, 2013 at 16:43
@ninjalj On fd 2, yes. But on fd 0, I don't see any reason. Any file opened by a daemon should be closed before executing an unrelated process regardless of the descriptor.

Gilles 'SO- stop being evil'
– Gilles 'SO- stop being evil'

2013-11-11 22:09:14 +00:00
Commented Nov 11, 2013 at 22:09

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »