Hm. I upgraded to the latest Debian testing stuff (including a new
libc) and now the problem has disappeared.
Oh well :).
--
---
Paul D. Smith <[EMAIL PROTECTED]> HASMAT--HA Software Mthds & Tools
"Please remain calm.
On Tue, Oct 01, 2002 at 10:58:56AM -0400, Paul Smith wrote:
> I'm seeing a very bizarre behavior on my Debian GNU/Linux box (3.0).
> I'm using the official packaged version of fvwm from unstable
> (2.4.10-2). I had this same problem with the fvwm from testing (2.4.8)
> so I upgraded, but upgrading
rxvts,
exited from them, then looked for defunct processes.
I tried:
exec rxvt
exec exec rxvt
exec rxvt &
exec exec rxvt &
then
ps -aef | grep defunct
--
Dan Espen E-mail: [EMAIL PROTECTED]
--
Visit the official FVWM web page at http://www.fvwm.org/>.
T
%% Dan Espen <[EMAIL PROTECTED]> writes:
de> Have you set ExecUseShell or $SHELL?
I set ExecUseShell to /bin/sh.
--
---
Paul D. Smith <[EMAIL PROTECTED]> HASMAT--HA Software Mthds & Tools
"Please remain calm...I may
"Paul Smith" <[EMAIL PROTECTED]> writes:
> %% "Smith, Paul [BL60:430:EXCH]"<[EMAIL PROTECTED]> writes:
>
> sp> The issue is that any process I start either from fvwm directly or
> sp> from FvwmButtons will go after I exit it. It stays
> sp> defunct forever, with a parent of the fvwm proces
%% "Smith, Paul [BL60:430:EXCH]"<[EMAIL PROTECTED]> writes:
sp> The issue is that any process I start either from fvwm directly or
sp> from FvwmButtons will go after I exit it. It stays
sp> defunct forever, with a parent of the fvwm process, until I
sp> restart fvwm.
No one has any idea
I'm seeing a very bizarre behavior on my Debian GNU/Linux box (3.0).
I'm using the official packaged version of fvwm from unstable
(2.4.10-2). I had this same problem with the fvwm from testing (2.4.8)
so I upgraded, but upgrading didn't help.
I'm sure that this has not always behaved this way, b
