Yeah, I'd rather not run a command if there is a config file I can set
it in. I have been somewhat remis in my duties as a linux systems admin
in having not taken the time to really learn about systemd. But if it
requires you to run a command to configure services, then it's broken.
I looked for info on configuring services in systemd. I found a nice
blog post about why /etc/default/ files aren't really needed in systemd.
But the advice it gives doesn't seem to apply to espeakup. It says to
take the default config file which would be somewhere like /lib/systemd/
and copy it to /etc/systemd/ and edit it there. But there is no
espeackup config file anywhere in the systemd directories. I suspect
that espeakup is relying on the backwards compatibility features of
systemd. As someone who has ignored systemd as long as possible myself,
I can't fault the espeakup developers for that.
On 02/08/2016 05:24 PM, Jude DaShiell wrote:
Easier way than that, locate where espeakup has speakup_soft defined
as synthesizer and edit that and replace speakup_soft with none.
On Mon, 8 Feb 2016, Rob wrote:
Date: Mon, 8 Feb 2016 17:04:49
From: Rob <captinlogic@xxxxxxxxx>
Reply-To: Speakup is a screen review system for Linux.
<speakup@xxxxxxxxxxxxxxxxx>
To: jheim@xxxxxxxxxxxxx,
Speakup is a screen review system for Linux.
<speakup@xxxxxxxxxxxxxxxxx>
Subject: Re: keeping espeakup from starting at boot
John G Heim <jheim@xxxxxxxxxxxxx> wrote:
On the machines used by the other people in my department, I need to
keep espeakup from starting at boot time. We run ubuntu 15.10 so I
think this is a systemd question.
Wouldn't you just go systemctl disable espeakup?
_______________________________________________
Speakup mailing list
Speakup@xxxxxxxxxxxxxxxxx
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
_______________________________________________
Speakup mailing list
Speakup@xxxxxxxxxxxxxxxxx
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
