here is the log
https://dl.dropboxusercontent.com/u/58850968/syslog3.log
--
View this message in context:
http://sane.10972.n7.nabble.com/weird-No-scanner-found-with-Scanimage-L-tp19894p19926.html
Sent from the SANE - Dev mailing list archive at Nabble.com.
--
sane-devel mailing list:
Am 12.07.2015 um 17:23 schrieb ylafont:
I added -7 for log and as soon as that was done i lost the net backend upon
reboot. here are the logs
NEt backend working (no -7)
https://www.dropbox.com/s/vnvvblkd9ue7sb2/syslog-net.log?dl=0
net backend missing. (with -7)
I added -7 for log and as soon as that was done i lost the net backend upon
reboot. here are the logs
NEt backend working (no -7)
https://www.dropbox.com/s/vnvvblkd9ue7sb2/syslog-net.log?dl=0
net backend missing. (with -7)
https://www.dropbox.com/s/e9ibafveiiumdzx/syslog-nonet.log?dl=0
--
i have so time to play with this today, also Scandb has always started with
both configuration with the init script and in /etc/rc.local the issue was
that the NEt interface would disappear when starting with the init script.
Do you want to send you both logs? one starting with the init method
Am 11.07.2015 um 13:43 schrieb ylafont:
i have so time to play with this today, also Scandb has always started with
both configuration with the init script and in /etc/rc.local the issue was
that the NEt interface would disappear when starting with the init script.
Do you want to send you
Here is the current config. let me know if i missed a file. I believe it is
scanbd 1.4.2
*/etc/sane.d/sane.conf*
#scan-client.somedomain.firm
#192.168.0.1
#192.168.0.1/29
#[2001:7a8:185e::42:12]
#[2001:7a8:185e::42:12]/64
192.168.1.0/24
*/etc/sane.d/net.config*
# This is the net backend config
The configuration looks good.
Please send me
1) the log file (with scanbd debug level=7) if started at a service at boot
2) the log file (with scanbd debug level=7) if started later
I assume that for some reason the scanner isn't present at boot time and
the appropriate event when it is later
I will have to spend more time with this
I disabled the init.d script
*sudo service scanbd stop
sudo update-rc.d. scanbd remove*
rebooted
started the service manually
*sudo service scanbd start *
and the NET backend remained.
again, when scanbd starts automatically via the init.d the
Am 07.07.2015 um 01:41 schrieb ylafont:
I will have to spend more time with this
I disabled the init.d script
*sudo service scanbd stop
sudo update-rc.d. scanbd remove*
rebooted
started the service manually
*sudo service scanbd start *
and the NET backend remained.
It
Am 05.07.2015 um 03:32 schrieb ylafont:
I have a weird problem, weird to me at least.
I have sane and scandb installed and setup with one issue. when I enable
scandb with
sudo update-rc.d scanbd enable and reboot scanbd startd properly and my
scripts work without any issues.
for some
scanbd grabs all devices it finds.
all user-level programms (e.g. scanimage) should use only the
net-backend with the host configured the scanbd is running on (in most
cases localhost but can be remote).
scanbd should use a configuration to reach the real scanners (local
connected or reachable
what can be reason for the NET device not to be found
Probably it does not yet exist when scandb starts. Even when startup
scripts are initiated in the proper order, the actual dependency may be
that a network script finishes (or something started by a
network script finishes) before scanbd
understood, but what can be reason for the NET device not to be found when
the scandb is running?
thanks Wilhelm.
--
View this message in context:
http://sane.10972.n7.nabble.com/weird-No-scanner-found-with-Scanimage-L-tp19894p19896.html
Sent from the SANE - Dev mailing list archive at
I have a weird problem, weird to me at least.
I have sane and scandb installed and setup with one issue. when I enable
scandb with
sudo update-rc.d scanbd enable and reboot scanbd startd properly and my
scripts work without any issues.
for some reason, i loose the net device that was
14 matches
Mail list logo
