First, there is far too much inconsistency with symlink: rcnovell-tomcat7
--------------
Admin Console: Has one, but it throws the following error when used to "stop":
rcnovell-tomcat7 stop
Stopping tomcat7: su: user tomcat7 does not exist
--------------
MAG Appliance: Has one, but it does nothing:
rcnovell-tomcat7 stop
Stopping tomcat7:
--------------
Identity Server: Does NOT even have this "rcnovell-tomcat7" symlink present!
* interestingly it does have a BROKEN symlink within the /etc/init.d/ folder:
/etc/init.d/novell-tomcat7 -> /etc/opt/novell/tomcat7/init.d/tomcat7
--------------
Next... It is interesting to note that at least most of the NAM components have a new-to-NAM 3.2, component-specific service for calling up Tomcat now:
Admin Console: /etc/init.d/novell-ac
Identity Server: /etc/init.d/novell-idp
ESP-SSLVPN: I don't have this installed within beta currently, so no idea.
MAG: /etc/init.d/ --> novell-activemq, novell-agscd, novell-apache2, novell-appliance, novell-jcc, and novell-mag
But, there is a small problem here as well. Unlike in NAM 3.1.4 and all previous releases, there is no "rc" short command present within your command PATH, such as being able to just type "rcnovell-idp status" without any providing any pathing.
This should be fixed by creating symlinks to the various "rcnovell-*" shortened names within /usr/sbin
To recap, there are TWO main problems to separately fix:
1) Delete all references to this non-functional "rcnovell-tomcat7" and /etc/init.d/novell-tomcat7 init script. From ALL NAM compoenent types (AC, IDP, MAG, and ESP-SSLVPN).
2) Create "rcnovell-*" symlinks at /usr/sbin for all of the new init scripts NAM creates on any/all of the NAM component types (AC, IDP, MAG and ESP-SSLVPN). These facilitate quick location without having to perfix with a bunch of pathing since its in a location within you path, plus it is a common SUSE convention with all other services (and NAM has adhereted to this in the past with "rcnovell-tomcat" symlinked command in the past.
- Stefan
--------------
Admin Console: Has one, but it throws the following error when used to "stop":
rcnovell-tomcat7 stop
Stopping tomcat7: su: user tomcat7 does not exist
--------------
MAG Appliance: Has one, but it does nothing:
rcnovell-tomcat7 stop
Stopping tomcat7:
--------------
Identity Server: Does NOT even have this "rcnovell-tomcat7" symlink present!
* interestingly it does have a BROKEN symlink within the /etc/init.d/ folder:
/etc/init.d/novell-tomcat7 -> /etc/opt/novell/tomcat7/init.d/tomcat7
--------------
Next... It is interesting to note that at least most of the NAM components have a new-to-NAM 3.2, component-specific service for calling up Tomcat now:
Admin Console: /etc/init.d/novell-ac
Identity Server: /etc/init.d/novell-idp
ESP-SSLVPN: I don't have this installed within beta currently, so no idea.
MAG: /etc/init.d/ --> novell-activemq, novell-agscd, novell-apache2, novell-appliance, novell-jcc, and novell-mag
But, there is a small problem here as well. Unlike in NAM 3.1.4 and all previous releases, there is no "rc" short command present within your command PATH, such as being able to just type "rcnovell-idp status" without any providing any pathing.
This should be fixed by creating symlinks to the various "rcnovell-*" shortened names within /usr/sbin
To recap, there are TWO main problems to separately fix:
1) Delete all references to this non-functional "rcnovell-tomcat7" and /etc/init.d/novell-tomcat7 init script. From ALL NAM compoenent types (AC, IDP, MAG, and ESP-SSLVPN).
2) Create "rcnovell-*" symlinks at /usr/sbin for all of the new init scripts NAM creates on any/all of the NAM component types (AC, IDP, MAG and ESP-SSLVPN). These facilitate quick location without having to perfix with a bunch of pathing since its in a location within you path, plus it is a common SUSE convention with all other services (and NAM has adhereted to this in the past with "rcnovell-tomcat" symlinked command in the past.
- Stefan