Try running the redhat startup script that comes with the distribution its called
or you could run run.sh - c all &
Not sure why you could not copy a file though, surely you just needed to open another terminal window.
It is possible to start jboss as a daemon process that starts at linux boot up.
Essentially you need to creat a jboss script which you will store in your /etc/init.d directory and making links to this script in /etc/init.d/rc3.d and /etc/init.d/rc5.d for starting and stopping jboss.
Lool at the other examples in your init.d directory to see how to creat your jboss script.
If you look at the FAQ, there's a section entitled "Start JBoss on boot with Linux?" that, strangley enough, tells you how to start jboss on boot with Linux.....
PS, if you follow this approach you can also start/stop jboss any time using the service command.
I am using a debian machine and can't quite get this working.
I am trying to setup a nightly build to run a script that is going to stop jboss, run the build, start jboss
If i try and use the init scripts like suggested above and in the FAQ it asks for a password, that won't really work for a nightly build.
I am also trying to use ./run.sh -c & and it goes like normal except that it outputs everything to the console. If I throw that in the script it is going to appear as if the script is running.....and running......
anyone have any other ideas.
./run.sh -c all & will still direct output to the console. You could redirect like:
$ ./run.sh -c all > /dev/null 2>&1
this will send stdout and stderr to the bitbucket
or you can do:
$ nohup run.sh -c all &
this will prevent the HUP signal from terminating your run.sh process, and the stdout output will go to a file called nohup.out in curr dir.