Seth,
Jean-Marie should not have to specific the path when running "red5" script from within the path where the script is located. This indicates that the script "red5" exists in the directory "/etc/init.d" and that the script is executable; root@vps-1105323-11088:~# ls -al /etc/init.d/red5 -rwxr-xr-x 1 root root 2169 Sep 5 17:21 /etc/init.d/red5 And therefore running the following command paces the terminal into the "/etc/init.d" directory; root@vps-1105323-11088:~# cd /etc/init.d The fact that the current directory is in fact "/etc/init.d" is indicated by "/etc/init.d" in the below command, and the current user is "root", which to me says that the command "red5" should be able to be executed, so why is "-bash: red5: command not found" reported. root@vps-1105323-11088:/etc/init.d# <mailto:root@vps-1105323-11088:/etc/init.d> red5 -bash: red5: command not found Jean-Marie, You could try Seth's suggestion of running "/etc/init.d/red5 start" but to get an idea of what is happening in the server I would suggest you run this sequence of commands, and then email us the output, if they are giving any error messages; ls -al /etc/init.d/red5 netstat -anp | grep java /etc/init.d/red5 stop netstat -anp | grep java /etc/init.d/red5 start netstat -anp | grep java Thanks, George Kirkham -----Original Message----- From: Seth Galitzer [mailto:sg...@ksu.edu] Sent: Thursday, 6 September 2012 8:23 AM To: openmeetings-user@incubator.apache.org Subject: Re: red5 start script not work for me vps-1105323-11088 On 09/05/2012 05:11 PM, George Kirkham wrote: > I do find this statement a bit of a concern "-bash: red5: command not > found" and wonder why or how this gets reported. > [SNIP] > > root@vps-1105323-11088:~# cd /etc/init.d > root@vps-1105323-11088:/etc/init.d# <mailto:root@vps-1105323-11088:/etc/init.d#> red5 > -bash: red5: command not found > You must include the full path to run this command: # /etc/init.d/red5 start In most (maybe all?) linux/unix distros, the current directory is not in the search path. So when you did ~# cd /etc/init.d /etc/init.d# red5 the shell did not know where to find the command. By including the full path, you are telling the shell where to find it. Looking at the rest of your output, it does look like the service is running just fine and you should be able to access it using the proper URL as suggested by George Kirkham. Seth -- Seth Galitzer Systems Coordinator Computing and Information Sciences Kansas State University http://www.cis.ksu.edu/~sgsax <http://www.cis.ksu.edu/~sgsax> sg...@ksu.edu <mailto:sg...@ksu.edu> 785-532-7790
