This seems to correspond with what I have tried; I attempter setting log_destination in the config file (as James suggested) and the server wouldn't start

, but changing run.sh to point to the location worked.  Not a problem, I'll just create a modified run.sh script to not collide with hg updates.

chris

On Sep 12, 2012, at 2:32 PM, Nate Coraor <nate@bx.psu.edu> wrote:

> On Sep 12, 2012, at 1:09 PM, Fields, Christopher J wrote:
>
>> Simple question: is there a way within universe_wsgi.ini to point to a specific location where Galaxy log (and possibly PID) files can be dropped?  I've searched for this but couldn't find an answer beyond locally modifying run.sh, but it's entirely possible I'm missing something obvious.
>>
>> We want to have the logs stored on the server side in /var/log or /var/spool, not on our NFS share.  The way run.sh is currently grabbing server information it seems as if we need to have something like this in the [server:*] config section:
>>
>> [server:/var/log/galaxy/web0]
>>
>> which doesn't seem right.  Maybe something like the following (per server)?
>>
>> [server:web0]
>> use = egg:Paste#http
>> port = 8080
>> host = 127.0.0.1
>> use_threadpool = true
>> threadpool_workers = 7
>> log_dir=/var/log/galaxy/
>>
>> or simply (for all log and/or PID files):
>>
>> log_dir=/var/log/galaxy/
>
> Hi Chris,
>
> It can't be done through the config file.  You have to use the --log-file and --pid-file from the command line.
>
> --nate
>
>>
>> chris
>> ___________________________________________________________
>> Please keep all replies on the list by using "reply all"
>> in your mail client.  To manage your subscriptions to this
>> and other Galaxy lists, please use the interface at:
>>
>> http://lists.bx.psu.edu/
>


___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

  http://lists.bx.psu.edu/