[sane-devel] Problem with Sane over network
lucabert at lucabert.de
Sun Apr 12 21:00:36 BST 2020
Am 12.04.2020 um 21:19 schrieb Luca Bertoncello:
> So the problem _MUST_ be by scanbd/scanbm...
> Has someone an idea how to configure them in order to use the buttons
> _AND_ have access to the scanner from network?
So, I found the problem...
For someone other having the same issue:
the problem is, that scanbm.socket did NOT work exactly as saned.socket...
After <bigint> experiments/checks/exacrations I found that scanbm on
Debian Buster is configured to use daemon:scanner as user.
saned is configured to use saned:saned as user environment...
So, first of all, must disabled saned.socket:
systemctl disable saned.socket ; systemctl stop saned.socket
Then, systemctl edit --full scanbm at .service to change these settings:
ExecStart=/usr/sbin/scanbm -c /etc/scanbd/scanbd.conf
by the way I changed scanbm.socket, too and set MaxConnections=64
instead of MaxConnections=1, to reproduce exactly the configuration of
After a systemctl daemon-reload and restart of scandb/scanbm, I can use
the buttons of the scanner and the scanner itself from my PC (in another
(lucabert at lucabert.de)
More information about the sane-devel