lkml.org 
[lkml]   [2003]   [Feb]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectBadness between recent signal changes and minicom.

Hey there.

I had been using minicom on 2.5.59 for some time with no problems. After
finally upgrading that system to 2.5.62, minicom decided it didn't want to
run anymore. An strace of it reveals that it's receiving -ECHILD from
wait4(2) after executing lockdev, although lockdev appears to exit
normally.

For the record, this is a Redhat 7.3 system, with the following versions
of the relevant programs:

minicom-2.00.0-3
lockdev-1.0.0-16

I backtracked through kernel versions, and eventually through individual
changesets to find the patch that causes the change in behavior. It has
the heading of:

ChangeSet@1.914.91.10, 2003-02-06 12:49:30-08:00, mingo@elte.hu
[PATCH] signal-fixes-2.5.59-A4

and can otherwise be seen here:

http://linux.bkbits.net:8080/linux-2.5/cset@1.914.91.10?nav=index.html|ChangeSet@-4w


Unfortunately, it is quite a large diff, and I am quite happy maintaining
my ignorance of the signal code. However, I'm wondering if there is
anything to do be done about. I am more than happy to upgrade the relevant
software, though I am wondering if the change in behavior was intentional.


Thanks,

-pat


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.036 / U:2.436 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site