Henning Meier-Geinitz <henn...@meier-geinitz.de> writes: >> > There haven't been any bugs in saned that stopped it from starting or >> > detecting the scanner for years so that's not the root of the problem. >> > >> > Have you checked that saned is allowed to access your scanner? I.e. if >> > the device file (e.g. /proc/bus/usb/001/003) is writable by saned:saned? >> >> Like I mentioned, when running saned in debugging mode there is no >> problem at all. > > Do yur run saned as user saned:saned in stand-alone mode? If you run > it as normal user or root the permissions may be ok but from inetd > it's usually run as saned:saned.
The inetd setup was such that saned was run as root.root. I know this is not a good idea ;-) -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2
