padioleau wrote:

Dear Galaxy developers,

I have two questions:

First, when Galaxy is launched in daemon mode, there is no error returned if Galaxy does not start properly. For instance if the database needs to be updated, the daemon will succeed (no error code is returned) even though Galaxy is not started. I would like to know if it is possible to change that.

Hi Ismael, Because the process detaches and runs in the background, it returns immediately and has no knowledge of what happens after. This is done by the WSGI framework (Paste, http://pythonpaste.org/) and a quick look doesn't reveal any way to delay when the daemonization happens.

Second, and for something completely different, I would like to know how I can get within a tool wrapper access to Galaxy configuration arguments like 'new_file_path' for example.

You can access this at: $__app__.config.new_file_path --nate

Thanks,

Ismael