Re: Fetchmail reports "input in flex scanner failed"

On 2019-05-21 07:59, Matthias Andree wrote:
> Flex does not currently generate code to break down and relay the error
> in detail has been written yet.
> 
> With flex 2.6.4, the error gets reported if ferror() returns an error
> state and errno isn't EINTR.
> 
> Fetchmail isn't made to cope with files being intermittently
> unavailable. Make sure the file is readable at all times.
> For instance, if your $HOME is on NFS, you must use "hard" mounts (which
> block until the file server is available), so that you have reliable
> semantics for file I/O.

Thanks for the information, Matthias!

I thought that if there is a possibility to improve the error reporting, it will certainly make fetchmail better, for example, it can additionally check ferrno() value.

It is difficult to trace the problem if I/O error happens from time to time as the message "input in flex scanner failed" sounds for me that there is something wrong with ~/.fetchmailrc syntax.

-- 
With best regards,
Dmitry