Message-Id: <m0zYuyn-000EBPC@orion.SAPserv.Hamburg.dsh.de>
From: jwieck@debis.com (Jan Wieck)
Subject: Re: [HACKERS] Open 6.4 items
To: winter@jurai.net (Matthew N. Dodd)
Date: Thu, 29 Oct 1998 17:31:19 +0100 (MET)
Cc: scrappy@hub.org, maillist@candle.pha.pa.us, brook@trillium.NMSU.Edu,
	jwieck@debis.com, hackers@postgreSQL.org
Reply-To: jwieck@debis.com (Jan Wieck)
In-Reply-To: <Pine.BSF.4.02.9810291023170.17054-100000@sasami.jurai.net> from
	"Matthew N. Dodd" at Oct 29, 98 10:24:36 am
Content-Type: text

>
> 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) #