pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: jwieck@debis.com
To: winter@jurai.net
Cc: scrappy@hub.org
Cc: maillist@candle.pha.pa.us
Cc: brook@trillium.NMSU.Edu
Cc: jwieck@debis.com
Cc: hackers@postgreSQL.org
Subject: Re: [HACKERS] Open 6.4 items
Date: Thu, 29 Oct 1998 17:31:19 +0100 (MET)
Message-ID: <m0zYuyn-000EBPC@orion.SAPserv.Hamburg.dsh.de> (raw)
In-Reply-To: <Pine.BSF.4.02.9810291023170.17054-100000@sasami.jurai.net>

>
> On Thu, 29 Oct 1998, The Hermit Hacker wrote:
> >  Solaris just doesn't have any mechanisms to work around the
> > limitation, I guess *shrug* It really sucks when you want to SIGHUP
> > the "parent process", which, under FreeBSD at least, is the one that
> > states: -accepting connections, but under Solaris they are *all* the
> > same :)
>
> $ ps -eaf
>      UID   PID  PPID  C    STIME TTY      TIME CMD
>     root     0     0  0   Oct 12 ?        0:01 sched
>     root     1     0  0   Oct 12 ?        0:15 /etc/init -
> ...
>
> You'll note the 'PPID' field.
>
> 3 guesses what that stands for.
>

    Don't see how this is related to the topic - sorry.

    PPID  is  the  parent process ID. sched has no parent (it's a
    kernel pseudo process) and init has sched as father. For  all
    other  processes  the  PPID  is set to init's PID at the time
    their father dies (you'll see lot's of PPID=1).

    But this all has nothing to do with changing the  CMD  column
    of the ps output from inside a running process.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#======================================== jwieck@debis.com (Jan Wieck) #





view thread (141+ messages)  latest in thread

Message-ID: <m0zYuyn-000EBPC@orion.SAPserv.Hamburg.dsh.de>
Permalink:  ../m0zYuyn-000EBPC@orion.SAPserv.Hamburg.dsh.de/
Also on:    postgresql.org/message-id/m0zYuyn-000EBPC@orion.SAPserv.Hamburg.dsh.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: jwieck@debis.com, winter@jurai.net, scrappy@hub.org, maillist@candle.pha.pa.us, brook@trillium.NMSU.Edu, hackers@postgreSQL.org
  Subject: Re: [HACKERS] Open 6.4 items
  In-Reply-To: <m0zYuyn-000EBPC@orion.SAPserv.Hamburg.dsh.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox