Re: Using absolute path for ExecStart in espeakup.service

[john doe <johndoe65534@mail.com>]

On 2/21/2019 7:32 PM, Samuel Thibault wrote:
> Hello,
>
> john doe, le jeu. 21 févr. 2019 19:24:18 +0100, a ecrit:
>> On 1/10/2019 9:31 PM, Samuel Thibault wrote:
>>> Hello,
>>>
>>> john doe, le jeu. 10 janv. 2019 18:09:35 +0100, a ecrit:
>>>> According to the below message and to (1, 'execstart=') the command
>>>> 'ExecStart' should use a fully qualified path when 'execstop=' is not
>>>> specified.
>>>
>>>> Observed on Debian Stretch.
>>>
>>> This is fixed in stretch-proposed-updates's version 1:0.80-5+deb9u3, to
>>> be included in next Scretch.
>>>
>>
>> While upgrading espeakup to that version I get:
>>
>> Preparing to unpack .../42-espeakup_1%3a0.80-5+deb9u3_amd64.deb ...
>> Failed to stop espeakup.service: Unit espeakup.service not loaded.
>> invoke-rc.d: initscript espeakup, action "stop" failed.
>> dpkg: warning: subprocess old pre-removal script returned error exit
>> status 5
>
> Yes, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922503
>
> We can't really fix this unfortunately. A workaround is to fix the issue
> by hand in /lib/systemd/system/espeakup.service, by adding /bin/ to
>
> ExecStart=sh -c 'modprobe speakup_soft && /usr/bin/espeakup -V ${VOICE}'
>
> so it looks like
>
> ExecStart=/bin/sh -c 'modprobe speakup_soft && /usr/bin/espeakup -V "${VOICE}"'
>

Thank you, Samuel.

I took a different approach:

$ mkdir -p /etc/systemd/system/espeakup.service.d
$ printf "[Service]\nExecStart=/bin/sh -c 'modprobe speakup_soft &&
/usr/bin/espeakup -V \"\${VOICE}\"'" >
/etc/systemd/system/espeakup.service.d/service.conf

Note that this e-mail is folded by my mailer.

--
John Doe