Bug 125434 - after creating a service - service configuration errors "error:tss2_rc2:unrecognized service"
after creating a service - service configuration errors "error:tss2_rc2:unrec...
Product: Fedora
Classification: Fedora
Component: system-config-services (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
Depends On:
  Show dependency treegraph
Reported: 2004-06-07 00:05 EDT by MournBlade
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-06-07 16:37:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description MournBlade 2004-06-07 00:05:26 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET 
CLR 1.1.4322)

Description of problem:
I am attempting to run the TeamSpeak software as a service. I have 
created the init.d file and the symbolic links in the rc"n".d files. 
When I try to start the service, (in GUI and command line) it reads 
error:Tss2_rc2:unrecognized service or just unrecognized service.

This same script worked in Fedora Core 1 as well as RH-7,8&9.

I'm wondering if there is now a file that is checked as a security 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create an init.d shell script to run an application as a service.
2. Create the symbolic links in the rc.d folders.
3. Start the service by GUI or by cmdline > service "scriptname" 

Additional info:
Comment 1 MournBlade 2004-06-07 13:33:07 EDT
I am able to execute the script normally.
sh tss2_rc2 start
./ tss2_rc2 start <---- both work normally

service tss2_rc2 start <---- doesn't work unrecognized service
Comment 2 MournBlade 2004-06-07 16:37:37 EDT
Nevermind; was a problem between the keyboard and chair.
/me kicks self for not checking permissions.

Note You need to log in before you can comment on or make changes to this bug.