I have had it happen occasionally, but didn't pay attention to the
details. Perhaps I forget to put --reload sometimes. Also, it seems
that sometimes the Galaxy processes do not all stop with --stop-daemon.
I wrote the text below as a recipe for people in my lab to restart in
those situation
On Oct 18, 2012, at 1:43 AM, Todd Oakley wrote:
> Yes, daemon/stop-daemon is the best way. However, to stop a process that was
> not started with --daemon, this is what I do:
>
> ps aux | grep galaxy
>
> Identify the process numbers for 3 Galaxy processes, which will change every
> time Gala
Yes, daemon/stop-daemon is the best way. However, to stop a process that was
not started with --daemon, this is what I do:
ps aux | grep galaxy
Identify the process numbers for 3 Galaxy processes, which will change every
time Galaxy is restarted.
For example this line:
galaxy 11638 0.0 0.
Thanks. Helped me!
On Thu, Oct 18, 2012 at 11:02 AM, Enis Afgan wrote:
> With a certain version of Python there's been an issue stopping Galaxy
> using ctrl+C. You can use 'sh run.sh --daemon' to have the process run in
> the background and then 'sh run.sh --stop-damemon' to stop it.
>
> Hope th
With a certain version of Python there's been an issue stopping Galaxy
using ctrl+C. You can use 'sh run.sh --daemon' to have the process run in
the background and then 'sh run.sh --stop-damemon' to stop it.
Hope this helps,
Enis
On Thu, Oct 18, 2012 at 4:12 PM, Sachit Adhikari <
sachit.techner..
5 matches
Mail list logo
