RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Package using wrong path for storing log and pid files.

Version-Release number of selected component (if applicable):
speech-dispatcher-0.7.1-13.el7.x86_64

Actual results:
log files and pid files stored in /root/.speech-dispatcher/

Expected results:
log and pid files stored in /var/log/ and /var/run/

Running speech-dispatcher as a system service doesn't make sense since we ship it configured (in /etc/speech-dispatcher/speechd.conf) to auto-spawn a user instance whenever the client side library needs it.

It might make sense to run it as a service in case of distributed deployments where the daemon runs in one host and clients access it over a TCP connection but that will only work if users/sysadmins configure it specifically for that.

As I see it, we should just stop shipping the systemd .service file (it's a Fedora modification, not upstream).

If we really want to support the system service use case we need to ship a different config file for it and point the daemon at it with a command line argument.