Re: [sane-devel] (no subject)

[Louis Lagendijk]

On Mon, 2016-12-12 at 20:42 -0500, junt...@gmail.com wrote:
> Hi it's me again.  Don't know if you gave up on me but I am trying
> again from the beginning.  I have scanned via USB and now am
> attempting to get it working over my wifi.

What kind of scanner? How do you want to run over wifi? Sane directly
over wifi to the scanner or using saned to the machine that has the
usb-connection to the scanner?
> 
> On step two it says:
which instructions? 

> Step 2: Tell SANE to run as a server (saned)
> systemd only
> Execute at a terminal:
> sudo nano /etc/systemd/system/saned.socket
> and input exactly:
> # Defaults for the saned initscript, from sane-utils
> 
> # To enable under systemd please read README.Debian
> # Set to yes to start saned under SysV
> RUN=no

this looks suspicious. Should this not be a file in /etc/default? I am
not a Debian user (is this Debian?) Check the README.Debian as
instructed. This does not look like a normal systemd socket file...

You are probably mixing systemd and non-systemd instructions

/Louis

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] (no subject)

[Jörn-Ingo Weigert]

Hi juntjoo, it would help when you give us some more details, like used
sane version, used distribution.

Beside that, your systemd command seems not correct, as "...invalid
argument". Please check the manuals to systemd/sysctrl and the content of
the involved saned.socket definitions.

Kind regards,

jiweigert

Am 14.12.2016 13:38 schrieb :

Hi it's me again.  Don't know if you gave up on me but I am trying again
from the beginning.  I have scanned via USB and now am attempting to get it
working over my wifi.

On step two it says:
Step 2: Tell SANE to run as a server (saned)

systemd only

   -

   Execute at a terminal:

   sudo nano /etc/systemd/system/saned.socket

   and input exactly:

   # Defaults for the saned initscript, from sane-utils# To enable
under systemd please read README.Debian# Set to yes to start saned
under SysVRUN=no# Set to the user saned should run
asRUN_AS_USER=sanedmoniker@pc:~$ cat
/etc/systemd/system/saned.socket[Unit]Description=saned incoming
socket[Socket]ListenStream=6566Accept=yesMaxConnections=1[Install]WantedBy=sockets.target



but when I opened up this terminal there was

"run=yes

exit"

and I pasted your instructions in between those lines not knowing if I was
supposed to or paste over them both.  Was I right?


And then down to step three:


Step 3: Tell saned who to share with

Assuming you don't need to control access to the scanner, we will add the
line "192.168.0.0/24" (share with everyone on the local network) after "##
Access list":

## Access list192.168.0.0/24


I did this part but you explained in the beginning we were assuming that my
network address is 192.168.0.1.  I don't know if this is the case or if I
need to worry about it.  Do I or is this a default network address?  Could
this be why I'm having problems?


Then I went to step 4 "clean up tasks:".  Maybe I went too far but I did it
anyway and got this:

ben@Hal:~$ sudo systemctl enable saned.socket
Failed to execute operation: Invalid argument
ben@Hal:~$ sudo systemctl start saned.socket
Failed to start saned.socket: Unit saned.socket is not loaded properly:
Invalid argument.
See system logs and 'systemctl status saned.socket' for details.



Well I think I've gone far enough and will wait for your instruction.
Would love to get this scanner wireless.
Thanks

--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

iscan compile problems on Mandrake 9.1 (was Re: [sane-devel] (no subject))

[Olaf Meeuwissen]

On Sat, Aug 23, 2003 at 03:17:45PM +0200, Florian Reichert wrote:
 On Wed, 20 Aug 2003 13:26:22 +0900, Olaf Meeuwissen o...@epkowa.co.jp 
 wrote:
 
 On Tue, Aug 19, 2003 at 02:23:10PM +0200, flori...@gmx.net wrote:
 
 make[1]: Entering directory `/root/iscan-1.5.2/frontend'
 
 Gack!!  Am I right in thinking that you build your sources are root in 
 root's home directory?  You're better of building as a normal user and
 only switch to root for the installation.
 
 No You are wrong :) The tarball is in root's home directory, but the 
 compiling is done by a normal user, because my /home was damaged in that 
 moment. I kno wthat is not verry well done, but I think on a single user 
 maschine 

Even on a single user machine, I prefer not to shoot myself in the foot 
:-)
-- 
Olaf MeeuwissenEPSON KOWA Corporation, ECS
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!   -- I hack, therefore I am --   LPIC-2

iscan compile problems on Mandrake 9.1 (was Re: [sane-devel] (no subject))

[Florian Reichert]

On Wed, 20 Aug 2003 13:26:22 +0900, Olaf Meeuwissen o...@epkowa.co.jp 
wrote:

 On Tue, Aug 19, 2003 at 02:23:10PM +0200, flori...@gmx.net wrote:
 Hello!

 I have problems compiling iscan 1.5.2!

 What sources did you download?

 What am I missing?

 My system is mandrake 9.1 sane is compiled (Version 1.0.12).

 You'll need the gcc-3.x experimental sources.  Either the tarball or the 
 SRPM.

You are right, I got the wron tarball! I will try the other one tese days.

 Thanks Florian!

 make[1]: Entering directory `/root/iscan-1.5.2/frontend'

 Gack!!  Am I right in thinking that you build your sources are root in 
 root's home directory?  You're better of building as a normal user and
 only switch to root for the installation.

No You are wrong :) The tarball is in root's home directory, but the 
compiling is done by a normal user, because my /home was damaged in that 
moment. I kno wthat is not verry well done, but I think on a single user 
maschine 

Regard Florian


-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

iscan compile problems on Mandrake 9.1 (was Re: [sane-devel] (no subject))

[Olaf Meeuwissen]

On Wed, Aug 20, 2003 at 01:26:22PM +0900, Olaf Meeuwissen wrote:
 On Tue, Aug 19, 2003 at 02:23:10PM +0200, flori...@gmx.net wrote:
  Hello!
  
  I have problems compiling iscan 1.5.2!
 
 What sources did you download?
 
  What am I missing?
  
  My system is mandrake 9.1 sane is compiled (Version 1.0.12).
 
 You'll need the gcc-3.x experimental sources.  Either the tarball or the 
 SRPM.

I've just tried compiling iscan from the iscan-1.5.2-1.redhat.8.0.tar.gz 
tar-ball on a mostly default Mandrake-9.1 system.  Only had to chase 
down a missing development package (libimlib1-devel), but had no trouble 
otherwise in getting it compiled.

-- 
Olaf MeeuwissenEPSON KOWA Corporation, ECS
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!   -- I hack, therefore I am --   LPIC-2

iscan compile problems on Mandrake 9.1 (was Re: [sane-devel] (no subject))

[Olaf Meeuwissen]

On Tue, Aug 19, 2003 at 02:23:10PM +0200, flori...@gmx.net wrote:
 Hello!
 
 I have problems compiling iscan 1.5.2!

What sources did you download?

 What am I missing?
 
 My system is mandrake 9.1 sane is compiled (Version 1.0.12).

You'll need the gcc-3.x experimental sources.  Either the tarball or the 
SRPM.

 Thanks Florian!
 
 make[1]: Entering directory `/root/iscan-1.5.2/frontend'

Gack!!  Am I right in thinking that you build your sources are root in 
root's home directory?  You're better of building as a normal user and
only switch to root for the installation.

The rest of the log shows messages that are indicative of trying to 
build iscan from the gcc-2.9x sources on a system that uses gcc-3.x
for its default compiler.

HTH,
-- 
Olaf MeeuwissenEPSON KOWA Corporation, ECS
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!   -- I hack, therefore I am --   LPIC-2