Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You are using quite old JBoss version and I personally never see it. But I think it should be very similar to newer ones.</p> <p>Please try to put your user after when defining these variable:</p> <pre><code>JBOSSUS=jbs </code></pre> <p>The other solution is to setting these variable before executing running script:</p> <pre><code>export JBOSSUS=jbs; /etc/init.d/jboss start </code></pre> <p><strong>Update</strong></p> <p>I have just downloaded JBoss 3.2.7 and I checked the <code>jboss_init_redhat.sh</code> script (I hope you use these one as a templete for your starting script).</p> <p>In the file <code>jboss_init_redhat.sh</code> you can find such lines:</p> <pre><code>#define the user under which jboss will run, or use RUNASIS #to run as the current user JBOSSUS=${JBOSSUS:-"jboss"} </code></pre> <p>These line defines the new user name. It checks if the variable <code>JBOSSUS</code> is set up and if not is uses <code>jboss</code> user as default name.</p> <p>The second interesting part of these script:</p> <pre><code>if [ "$JBOSSUS" = "RUNASIS" ]; then SUBIT="" else SUBIT="su - $JBOSSUS -c " fi </code></pre> <p>You should know one thing: when you run automatically any script from init scripts it is always run as a <code>root</code> user. Thats why in the script should be command which change the effective user to someone else. And here you have these part of the script.</p> <p>It first checked if your username is <code>RUNASIS</code> and if it is <strong>yes</strong> - do nothing. In another case it run JBoss as a another user by using <code>su</code> command.</p> <p>In your case it should be sufficient to change <code>JBOSSUS</code> variable definition to something like that:</p> <p>JBOSSUS=jbs</p> <p>After that you can start these script as a <code>root</code> user and it should run JVM with JBoss with <code>jbs</code> user.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload