Re: emelfM2 pre-release available
- From: <tpgww@xxxxxxxxxxx>
- To: emelfm2@xxxxxxxxxxxxx
- Date: Sat, 23 Dec 2006 09:44:21 -0500
On Fri, 22 Dec 2006 16:22:20 -0500
"Jonathan A. Irwin" <jnthn_gmane@xxxxxxxxx> wrote:
> On Sat, 23 Dec 2006 00:46:49 -0500
> <tpgww@xxxxxxxxxxx> wrote:
>
>
> > First, can you check for anything informative about waitpid() for your
> > specific glibc ?
>
> Well, I have a generic man page "waitpid," but it obviously doesn't relate
> to my current libc, as it's dated June, 2001, and glibc-2.3.5 is from 2005.
>
> I do have the texinfo documentation, but I really don't know what sections
> to look in. It's a bit of a large attachment to send to the list (about
> 920 KB). I could send it to you off-list if you like.
I found this:
... the linux kernel that I have to use (2.4.21 patched to death) doesn't
support the option WCONTINUED for syscall waitpid ... The new glibc-2.3.5 I
just got installed doesn't care about this though.
So it seems there may be a disconnect between kernel and glibc.
With this in mind, I've updated the command execution code in svn. Perhaps you
might give that a try.
> >> What's worse... apparently I can no longer quit e2 without killing child
> >> processes.
> >
> > That's a deliberate change. Not for any compelling reason, but to
> > make commands consistent with actions (which must be cancelled when a
> > session ends) and a probably-mistaken concern about managing zombie
> > processes. It could readily be reversed.
>
> Well, since you introduced the option to skip warnings about running
> children when quitting, I've been happily running that way without any
> issues regarding "zombified" children that I've ever noticed.
>
> > Leaving aside any surprise about the change, I wonder which is the
> > "proper" way to handle this ?
>
> I don't know. I'm not sure I've ever seen a GUI file manager that kills
> children on exit, though. It's mighty inconvenient, IMO. Maybe it could
> be worked out as a user preference?
Closing any? terminal emulator (well, I tried only gnome-terminal, Tracker and
xterm) aborts all running processes started in the terminal (but maybe not so
for any daemon process??).
After closing an e2 session, any continuing child process has no stdin, stdout
or stderr capability, and redundant open pipes will be lying around ...
Continuation could be made optional, generally and/or session-specific.
Regards
Tom
--
Users can unsubscribe from the list by sending email to
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by
logging into the web interface.
Other related posts: