Re: FVWM: fvwm2.4.6 freeze

From: Mikhael Goikhman <migo_at_homemail.com>
Date: Wed, 10 Apr 2002 11:56:47 +0000

On 10 Apr 2002 13:13:55 +0200, szonyi calin wrote:
>
> if you have in fvwm2rc lines like this
> + "text" Exec program
> instead of
> + "text" Exec exec program
> this could be the cause
>
> Fvwm is waiting for a comand to finnish and it is
> busy until that command finishes

No, this is not correct. Exec is always done in a forked process that is
not waited. Exec is asynchronous. PipeRead is synchronous.

"Exec" and "Exec exec" have exactly the same effect from the window
manager point of view. Some shells (say, GNU bash) even add "exec"
themselves if needed, so program is executed with no additional fork.
Other shells fork, so there are 2 processes, shell and program.

Regards,
Mikhael.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Apr 10 2002 - 06:57:20 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:52 BST