Skip site navigation (1) Skip section navigation (2)

Re: diagnosing a db crash - server exit code 2

From: Armin Resch <reschab(at)gmail(dot)com>
To: bricklen <bricklen(at)gmail(dot)com>
Cc: Robert Burgholzer <rburghol(at)vt(dot)edu>, pgsql-admin(at)postgresql(dot)org
Subject: Re: diagnosing a db crash - server exit code 2
Date: 2011-09-29 17:00:36
Message-ID: CAGo0LBR4nRZpQPBO7Z962LXPxan9=arjtiAXxk043RQtg2oX5g@mail.gmail.com (view raw or flat)
Thread:
Lists: 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(at)gmail(dot)com> wrote:

> On Wed, Sep 28, 2011 at 12:54 PM, Robert Burgholzer <rburghol(at)vt(dot)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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>

In response to

pgsql-admin by date

Next:From: Joe ConwayDate: 2011-09-29 17:29:41
Subject: Re: diagnosing a db crash - server exit code 2
Previous:From: Maria L. WilsonDate: 2011-09-29 16:24:13
Subject: Re: constraint triggers

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group