fvwm2 causes stdin to be closed when execing within tcl/tk

Peter L. Peres plp-ysDPMY98cNQDDBjDh4tngg at public.gmane.org
Mon Jan 26 16:31:47 UTC 2004


On Sat, 24 Jan 2004, Lennart Sorensen wrote:

> And what should they be connected to?  /dev/null?  If fvwm is silly
> enough to close stdin, stdout and stderr and then uses fork/exec to
> launch other programs, then fvwm is a broken window manager, since it is
> reasonable to assume whoever launches an interactive application is
> doing so from an interactive environment where those FIDs are available.
> Well at least I think so.

GUIs have no obligation for stdin,stdio etc. Any program meant to be run
in the background or under a GUI must take care of them itself. Why
wouldn't Apache log to stderr ? Because it's a daemon.

Peter
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml





More information about the Legacy mailing list