On Thu, 25 Nov 1999, Niclas Hedhman wrote:
>
> No report of open file.
> Also, no symbolic link in the file system to the /dev/ttyS0
>
> I just had a hunch that some daemon, stepped in and open the port for a second and
> then released it again.
First Hint: look at the corresponding files of the "cron"
daemon; disable them for a while (kill crond)!
But this will most likely make you see that nothing changes
after doing this...
I assume that the serial subsystem itself is responsible for the
problem.
Furthermore:
Perhaps one of the Kernel's companions works on the serials,
I don't really believe this but would be graceful on some hint
from anyone...
but up to now I say from my expierience:
even if no other process opens the port we have the problem!!!
(of course I may be fundamentally wrong! The hope of beeing
corrected was the reason to subscribe this list)
>
> I can live with the reset of the port, although I can imagine others (such as
> modem connections) can not.
I can live with it too, but this is not the reason I issued my
primary mail: We have found a failure in the OS and this problem
should be solved.
At least the workaround should be published !!!
>
> Niclas
>
Gerald
--
++++++++++++
+ Gerald Emig, Engelstr. 17, D - 66564 Ottweiler
+ Tel.+Fax +49 6858 6197
++++++++++++
-
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to [EMAIL PROTECTED]
