# Networked Sane

Sven Riedel (Sven.Riedel@tu-clausthal.de)
Mon, 10 May 1999 11:03:51 +0200

- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Dean@Home: "Re: saned troubles"
- Previous message: Norman Elliott: "re Mustek scanner"
- Next in thread: Milon Firikis: "Re: Networked Sane"
- Reply: Milon Firikis: "Re: Networked Sane"

Hi,
I'm currently trying to use sane over the network. I installed sane as an
inetd service and added the corresponding port to /etc/services (lets
call this Machine A). The machine calling A (lets call it B) was added to
A's saned.conf, and A was added to B's net.conf. the entry "net" is the
first in Bs dll.conf.
Running saned -d on A, and calling xscanimage on B runs fine. Running plain
saned (manually) on A won't let B connect. And having saned as a pure inetd
service results in Bs xscanimage to segfault.
Both A and B have sane 1.01 installed. Any thoughts on how to handle this?
ssh'ing over to A and calling saned -d by hand is not exactely what I call
elegant :)

Regs,
Sven

    --
    Sven Riedel 				sr@gimp.org
    Leibnizstr. 24 / App. 106		sven.riedel@tu-clausthal.de
    38678 Clausthal

    --
    Source code, list archive, and docs: http://www.mostang.com/sane/
    To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

     Next message: Dean@Home: "Re: saned troubles"
     Previous message: Norman Elliott: "re Mustek scanner"

     Next in thread: Milon Firikis: "Re: Networked Sane"
     Reply: Milon Firikis: "Re: Networked Sane"