Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-4988

When using service wrapper on solaris, RUN_AS_USER property doesn't work

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • jboss-fuse-6.3
    • jboss-fuse-6.2.1, jboss-fuse-6.3
    • Karaf
    • None
    • % %
    • Hide

      1. unzip JBoss Fuse 6.2.1.GA on solaris machine
      2. feature:install wrapper
      3. wrapper:install -n <serviceName> -d <displayName> -D <description>
      4. set RUN_AS_USER to non-root user
      5. ln -s InstallDir/bin/ServiceName-service /etc/init.d/ServiceName-service
      6. ln -s /etc/init.d/ServiceName-service /etc/rc3.d/S30ServiceName-service
      7. reboot machine, the service won't start on boot time

      Show
      1. unzip JBoss Fuse 6.2.1.GA on solaris machine 2. feature:install wrapper 3. wrapper:install -n <serviceName> -d <displayName> -D <description> 4. set RUN_AS_USER to non-root user 5. ln -s InstallDir/bin/ServiceName-service /etc/init.d/ServiceName-service 6. ln -s /etc/init.d/ServiceName-service /etc/rc3.d/S30ServiceName-service 7. reboot machine, the service won't start on boot time
    • 6.3 Sprint 4 (Mar 28 - Apr 29)

    Description

      I used the steps described in service wrapper documentation for solaris (see the Solaris steps).
      I set the RUN_AS_USER property to non-root user. There has to be one additional step in the service wrapper configuration, which is described in the solaris documentation - ln /etc/init.d/ServiceName-service /etc/rcn.d/SxxServiceName-service.

      When the RUN_AS_USER property is not defined, the service starts with no problem.

      Attachments

        Issue Links

          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ENTESB-4989 Improve fuse init scripts

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              lburgazz@redhat.com Luca Burgazzoli
              tplevko@redhat.com Tomas Plevko
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: