[sane-devel] saned at service environment question
ToddAndMargo at zoho.com
Sat Nov 25 09:33:11 UTC 2017
On 11/25/2017 01:09 AM, Olaf Meeuwissen wrote:
> 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 ;-)
>> # 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
>> also adds:
>> #Environment=SANE_DEBUG_DLL=128 SANE_DEBUG_NET=128
>> 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.
>> 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.
>> What is
> An environment variable that tells the dll (and most other backends)
> where to look for their configuration. See sane-dll(5).
>> SANE_DEBUG_BJNP=5, and
> 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,
Not really, but thank you for trying.
What systemd documentation are you speaking of?
More information about the sane-devel