Hi,
On Fri, 11.04.2003, 11:09, Henning Meier-Geinitz wrote:
> I guess changing printf (...) to
> fprintf (stderr, ...) may be enough but I haven't even loked at the code.
Humm, I'm no C programmer, but I replaced all occurences of printf(...) to
fprintf (stderr, ...) as you proposed. And: It wo
On 2003.04.11 00:59 Karl O. Pinc wrote:
> I know little of sane, but I'd not expect 'saned -d' to work when
> started from xinetd. I'd think you'd have to get rid of the -d.
> You'd use 'saned -d' in a terminal window to debug, then switch to
> regular 'saned' when it's working and you run it fro
Hi,
On Fri, Apr 11, 2003 at 06:38:12AM +0200, Joerg Napp wrote:
> after solving the PATH issue with the AS6E driver I ran into another
> problem which prevents saned from being started from xinetd.
>
> Thhe situation is: sane Version 1.0.11, as6edriver version 0.4.9, scanning
> from a workstation
Hello again,
after solving the PATH issue with the AS6E driver I ran into another
problem which prevents saned from being started from xinetd.
Thhe situation is: sane Version 1.0.11, as6edriver version 0.4.9, scanning
from a workstation after runnding saned -d on the linux box works fine.
When I
