[Linux-parport] parport not automatically released by child process

Tim Waugh twaugh at redhat.com
Thu Jan 15 10:25:32 GMT 2004

On Wed, Jan 14, 2004 at 03:06:16PM +0100, Eddy De Greef wrote:

> on some older 2.4 kernels, I experience the following problem:
> when a process opens /dev/parport0 and then forks, and the child 
> claims the port and exits without releasing it, the parent process
> can no longer claim the port. I would expect that the port is 
> automatically released when the child exits. 

The kernel driver doesn't get to know that the child exited.  They are
sharing the same file descriptor.

If the child instead opened /dev/parport0 itself everything should
work as expected -- or, of course, if the child releases the port

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.infradead.org/pipermail/linux-parport/attachments/20040115/ce2b23bc/attachment.bin

More information about the Linux-parport mailing list