[sane-devel] saned at service environment question
Olaf Meeuwissen
paddy-hack at member.fsf.org
Sat Nov 25 09:09:09 UTC 2017
Hi ToddAndMargo,
ToddAndMargo writes:
> Dear list,
>
> In the man page, the script for saned at .service shows:
# OK, you are reading the documentation, just rather selectively ;-)
> Environment=SANE_CONFIG_DIR=/etc/sane.d
> # If you need to debug your configuration uncomment the next line and
> # change it as appropriate to set the desired debug options
> # Environment=SANE_DEBUG_DLL=255 SANE_DEBUG_BJNP=5
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1091566#c8
> also adds:
>
> #Environment=SANE_DEBUG_DLL=128 SANE_DEBUG_NET=128
>
> Question:
> Do you un-comment the all, or only uncomment one of them?
You add the SANE_DEBUG_* variables for the backends you want to debug.
In your case, you probably want to look at least at SANE_DEBUG_DLL and
SANE_DEBUG_NET and the backend that supports your particular scanner.
> Question:
>
> Should it not be?
>
> Environment=SANE_CONFIG_DIR=/etc/sane.d SANE_DEBUG_DLL=255
> SANE_DEBUG_BJNP=5 SANE_DEBUG_NET=128
>
> all run togther with spaces as the demlimier?
Please read the systemd documentation. I vaguely seem to remember all
the Environment "assignments" are run together by systemd, though.
# Disclaimer: I no longer use systemd.
> Questions:
>
> What is
> SANE_CONFIG_DIR=/etc/sane.d
An environment variable that tells the dll (and most other backends)
where to look for their configuration. See sane-dll(5).
> SANE_DEBUG_DLL=255
> SANE_DEBUG_BJNP=5, and
> SANE_DEBUG_NET=128
Environment variables that tell each of the backend how much to log.
Larger values produce more output. What and how much exactly differs
between backends.
Hope this helps,
--
Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27
GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9
Support Free Software https://my.fsf.org/donate
Join the Free Software Foundation https://my.fsf.org/join
More information about the sane-devel
mailing list