Hi, Ok, I see the issue. After taking a second look, I realised that both (xsane and scanimage) freeze infinitely (> 15 minutes). They did not reach any timeout. Scanimage is just more verbose. And they behave identical in whatever order they are called. Sorry for the noise. But still... a more realistic timeout would be nice, followed be an error message. If technically possible/reasonable.
Cheers, Simon Julien BLACHE schrieb: > Simon Wenner <[EMAIL PROTECTED]> wrote: > > Hi, > > >> My scanner is attached to my Debian Etch box and shared on the network. >> I access it with a Lenny box. >> If the firewall (firehol) on the server is configured too restrictive, >> i.e. only the saned control port (6566) is reachable, >> xsane just freezes and has to be killed. This is very confusing for the >> user. >> > > Standard TCP/IP issue. If you're dropping packet, the connecting side > has no way whatsoever to know that and a very long timeout will > eventually be reached. No problem here. > > >> Scanimage at least reports an "Error during device I/O". >> > > There's no reason why XSane and scanimage would behave differently, > except maybe if you tried scanimage after XSane. It'd be nice if you > could try it again both way around and track the problem down, if > there is any. > > JB. > >
signature.asc
Description: OpenPGP digital signature
