[sane-devel] systemd and saned

[Guillaume Courtois]

Oups, I did not send it to the list :-(

Le 11/11/2017 17:21, Guillaume Courtois a écrit :
> Hi,
> 
> Yes, you have to create a systemd unit. It's pretty simple, I'm
> surprised you don't find any example on the internet.
> Basically, you create the file in the right format
> (your_service.service), put it in /etc/systemd/system and do systemctl
> enable your_service then systemctl start your_service and that's all.
> 
> On my debian sid, I already have this :
> 
> /lib/systemd/system# cat saned at .service
> [Unit]
> Description=Scanner Service
> Requires=saned.socket
> 
> [Service]
> ExecStart=/usr/sbin/saned
> User=saned
> Group=saned
> StandardInput=null
> StandardOutput=syslog
> StandardError=syslog
> Environment=SANE_CONFIG_DIR=/etc/sane.d
> # Environment=SANE_CONFIG_DIR=/etc/sane.d SANE_DEBUG_DLL=255
> 
> [Install]
> Also=saned.socket
> 
> Bye.
> 
> Le 11/11/2017 06:28, ToddAndMargo a écrit :
>> Dear Sane List,
>> 
>> Google is failing me here.
>> 
>> I need to get saned running as a service under systemd.
>> Does anyone have a paper on how to do this?
>> 
>> Do I need to write my own systemd script?
>> 
>> Many thanks,
>> -T
>> 
>> 
>> # find /usr/lib/systemd -iname \*saned\*
>> <nothing>
>> 
>> # yum --enablerepo=* whatprovides saned
>> sane-backends-1.0.24-9.el7.x86_64 : Scanner access software
>> Repo        : @sl
>> Matched from:
>> Filename    : /usr/sbin/saned
>> 
>> # rpm -qa sane-backends
>> sane-backends-1.0.24-9.el7.x86_64
>> 
>> --
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Computers are like air conditioners.
>> They malfunction when you open windows
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x6C853BC3.asc
Type: application/pgp-keys
Size: 1656 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20171111/c28ad418/attachment.key>