Re: diagnosing a db crash - server exit code 2 - Mailing list pgsql-admin

From Armin Resch
Subject Re: diagnosing a db crash - server exit code 2
Date
Msg-id CAGo0LBR4nRZpQPBO7Z962LXPxan9=arjtiAXxk043RQtg2oX5g@mail.gmail.com
Whole thread Raw
In response to Re: diagnosing a db crash - server exit code 2  (bricklen <bricklen@gmail.com>)
List pgsql-admin
In a bourne-type shell you could use:

$ nohup [your_cmd] >[your_log_file] 2>&1 &

Then you should be able to safely disconnect your terminal.

Cheers,
-ar

On Thu, Sep 29, 2011 at 11:08 AM, bricklen <bricklen@gmail.com> wrote:
On Wed, Sep 28, 2011 at 12:54 PM, Robert Burgholzer <rburghol@vt.edu> wrote:
> If anyone has any suggestions as to how to run the trace via a nohup command
> or something, that would be cool, since then I could let it run in the
> background.

If you have "screen" installed, maybe try it in a screen session.

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

pgsql-admin by date:

Previous
From: "Maria L. Wilson"
Date:
Subject: Re: constraint triggers
Next
From: Joe Conway
Date:
Subject: Re: diagnosing a db crash - server exit code 2