path: scanbd_1.5.1-7/debian/scanbd.init
	egrep -x '(net)'        /etc/sane.d/dll.conf > /dev/null || do_abort "/etc/sane.d/dll.conf should contain the net backend"
	egrep -x '(net)'        /etc/scanbd/dll.conf > /dev/null && do_abort "/etc/scanbd/dll.conf must not contain the net backend"
	pidof saned > /dev/null && do_abort "It was detected that saned is already running. This will lead to problems. scanbd will not be started. Please stop saned before trying again. Most likely you activated RUN=yes in /etc/default/saned.  Change that to 'no'."
}


path: scanbd_1.5.1-7/debian/README.Debian
   "pidof scanbd" should return a number
5) make sure that your scanner is recognized
   "pidof scanbd && SANE_CONFIG_DIR=/etc/sane.d scanimage -L"
   This should list your scanner supported by the net (!) backend
6) stop scanbd


path: scanbd_1.5.1-7/debian/README.Debian
   "grep -e scanbd.*trigger /var/log/syslog"
4) make sure that scanbd is actually running
   "pidof scanbd" should return a number
5) make sure that your scanner is recognized
   "pidof scanbd && SANE_CONFIG_DIR=/etc/sane.d scanimage -L"


path: scanbd_1.5.1-7/debian/README.Debian
6) stop scanbd
7) test for direct scanbd support
   "pidof scanbd && echo "scanbd is still running and shouldn't. Please retry." ; SANE_CONFIG_DIR=/etc/scanbd scanimage -L"
   This should show you how scanbd addresses your scanner. It should NOT
   be the net backend you saw earlier. This is due to the design of