On 9/24/12 12:40 PM, Nate Coraor wrote:
On Sep 19, 2012, at 9:50 AM, Jennifer Jackson wrote:
repost to galaxy-dev
On 9/7/12 6:39 PM, Lukasz Lacinski wrote:
Dear All,
I use an init script that comes with Galaxy in the contrib/ subdirectory
to start Galaxy. The log file
--log-file
Galaxy should probably be shutdown with --stop-daemon (depending on
how you are running it).
In the future we can look at making the logging handle the HUP signal.
-- jt
On Tue, Sep 25, 2012 at 11:40 AM, Scott McManus scottmcma...@gatech.edu wrote:
Lukasz-
How are you stopping the process?
I use start-stop-daemon that sends SIGTERM (which is a default signal sent to a
service that is being asked to stop) to Galaxy to let Galaxy store all
information in a database, close files, etc., and terminate itself. When Galaxy
process is terminated, both shell and python scripts (Galaxy
On Sep 25, 2012, at 6:57 AM, Lukasz Lacinski wrote:
On 9/24/12 12:40 PM, Nate Coraor wrote:
On Sep 19, 2012, at 9:50 AM, Jennifer Jackson wrote:
repost to galaxy-dev
On 9/7/12 6:39 PM, Lukasz Lacinski wrote:
Dear All,
I use an init script that comes with Galaxy in the contrib/
On Sep 25, 2012, at 12:35 PM, Lukasz Lacinski wrote:
I use start-stop-daemon that sends SIGTERM (which is a default signal sent to
a service that is being asked to stop) to Galaxy to let Galaxy store all
information in a database, close files, etc., and terminate itself. When
Galaxy
On Sep 19, 2012, at 9:50 AM, Jennifer Jackson wrote:
repost to galaxy-dev
On 9/7/12 6:39 PM, Lukasz Lacinski wrote:
Dear All,
I use an init script that comes with Galaxy in the contrib/ subdirectory
to start Galaxy. The log file
--log-file /home/galaxy/galaxy.log
specified in the
