On Tue 06 Oct 2009 18:40 +0300, Ciprian Dorin, Craciun wrote: > On Tue, Oct 6, 2009 at 6:33 PM, David Houston <root@xxxxxxxxxxxxxxx> wrote: > > I Wonder weather it is your screen augments. Try using just -r rather than -RR > > > > Dave > > ------------- > > root@xxxxxxxxxxxxxxx > > cranky@xxxxxxxxxxxx > > > > > > > > On Tue, Oct 6, 2009 at 4:27 PM, Ciprian Dorin, Craciun > > <ciprian.craciun@xxxxxxxxx> wrote: > >> On Tue, Oct 6, 2009 at 6:04 PM, Aaron Griffin <aaronmgriffin@xxxxxxxxx> wrote: > >>> On Tue, Oct 6, 2009 at 7:18 AM, Ciprian Dorin, Craciun > >>> <ciprian.craciun@xxxxxxxxx> wrote: > >>>> Hello all! > >>>> > >>>> I'm having the following issue: after opening and closing some > >>>> shells within the same screen session, I'm left with a bunch of > >>>> defunct bash processes, that screen doesn't seem to wait for... Is > >>>> there any issue with screen? > >>>> > >>>> Or is there any issue in general, as Firefox plugin FireGPG seems > >>>> to do the same with gpg. (Which it didn't on Debian.) > >>> > >>> I've never noticed this myself. Are you sure you're actually exiting > >>> screen and not just detaching? > >> > >> Bellow is the output of `ps axf`. The problem is that screen > >> does't collect properly the defunct bash processes. > >> > >> 17030 ? S 0:00 urxvt -title x-shell -e > >> /home/ciprian/.bin/x-console -- screen -RR > >> 17032 pts/1 Ss+ 0:00 \_ screen -RR > >> 17036 ? Ss 0:00 \_ SCREEN -RR > >> 17037 pts/2 Rs 0:00 \_ /bin/bash > >> 17137 pts/2 R+ 0:00 | \_ ps axf > >> 17044 ? Zs 0:00 \_ [bash] <defunct> > >> 17046 ? Zs 0:00 \_ [bash] <defunct> > >> 17048 ? Zs 0:00 \_ [bash] <defunct> > >> 17050 ? Zs 0:00 \_ [bash] <defunct> > >> 17051 ? Zs 0:00 \_ [bash] <defunct> > >> 17054 ? Zs 0:00 \_ [bash] <defunct> > >> 17055 ? Zs 0:00 \_ [bash] <defunct> > >> 17057 ? Zs 0:00 \_ [bash] <defunct> > >> 17060 ? Zs 0:00 \_ [bash] <defunct> > > > Strange enough, it seems that only when using screen under X, it > behaves like this... (Directly in a VT works ok.) I imagine it would have something to do with x-console. `urxvt -e screen` works fine for me. I just noticed something odd... When I enter that command into a urxvt window with screen running, a new shell in the current screen will open rather than a new urxvt window with a new screen.
