Bug 81025

Summary: behavior of select() on serial lines is different from vanilla kernel
Product: [Retired] Red Hat Linux Reporter: giulioo
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:50:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description giulioo 2003-01-03 16:08:00 UTC 
Description of problem:
This problem is already in bug 73376, but since that one is public and seems to
be left alone, I'm filing this just as a reminder, close as you wish.

There seem to be a problem in select() and or serial line management, where
mgetty  is not notified something is using serial line; this way mgetty cannot
reset modem with init-chat after process terminates using serial line.

How reproducible:
always
1. have mgetty on the line
2. cu -l ttyS0, type some char
3. note how in log mgetty is still waiting for chars on ttyS0
4. terminate cu
5. note in mgetty log init-chat is not rerun

  
As reported in 73376, vanilla kernels are OK.
Comment 1 giulioo 2003-05-14 18:21:54 UTC 

*** This bug has been marked as a duplicate of 73376 ***
Comment 2 Red Hat Bugzilla 2006-02-21 18:50:54 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.