Henning Meier-Geinitz 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/bu
Hi,
On Mon, Nov 22, 2004 at 09:37:17AM +0900, Olaf Meeuwissen wrote:
> Hmm, haven't checked that. Does this mean that saned was not designed
> to run in standalone mode (when _not_ debugging)?
Yes. Well, in fact you can run saned standalone with debug messages
turned off but it's still not what
Henning Meier-Geinitz writes:
> Hi,
Hi Henning,
> On Fri, Nov 19, 2004 at 06:33:57PM +0900, Olaf Meeuwissen wrote:
>> I tried running saned in standalone mode (after stopping inetd). It
>> immediately exists successfully (exit status 0). That is:
>>
>> # saned && echo OK
>> OK
>
> That
Hi,
On Fri, Nov 19, 2004 at 06:33:57PM +0900, Olaf Meeuwissen wrote:
> I tried running saned in standalone mode (after stopping inetd). It
> immediately exists successfully (exit status 0). That is:
>
> # saned && echo OK
> OK
That can't work. You'll get an error in syslog about a failing
I was wondering if someone could help me out.
Setup: sane-backends-1.0.13
net backend enabled
localhost uncommented in net.conf and saned.conf
inetd.conf as per saned(8) manual page
Problem: saned does not seem to reply (except when in debug mode).
What I would expect is out
Hi,
have you tried the troubleshooting section at
http://penguin-breeder.org/sane/saned/ ? I'm pretty sure that should
solve your problem
kind regards
-- jochen
