Re: flexfax: Re: egetty

[Matthias.Apitz@SOFTCON.de]

Julio C Spinelli wrote:
    
    Sorry that it took so long for me to follow on on this subject, but I 
    have been very busy at work.
    
    After thorough investigation I found that the problem in Linux 2.0.29 
    is that when Getty:run does a dup2 to duplicate the modem file 
    descriptor into the standard output, in the child process, this destroys the file 
    descriptor that point to the modem in the parent process. Why does 
    this happens, it escapes me totally. I may look into the kernel 
    source during my vacations (may be not...)
    
    Whenever the dup2 is executed in the child the parent process can not 
    read or write to the modem when the child exits.

Try to separate this problem from HylaFAX by writing a small
C example (without using HylaFAX at all) and post a problem
report about this to the linux developers news groups.
    
    The only way I managed to make it work for Linux is to have the 
    egetty have uid 0 and open and close the modem itself. By doing this 
    the only change needed in Getty.c++ is an additional if statement 
    that does not do any dup2 is done when egetty is called.
    
    Matthias, are you interested in this for the pl2?

Without knowledge about the problem in the Linux kernel I'm
unsure to apply a patch like skipping the dup(2) and let
egetty re-open the modem again. I'll try to find the time
to reproduce this on the Linux box of my son.

	matthias