From: | Mathijs Brands <mathijs(at)ilse(dot)nl> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Larry Rosenman <ler(at)lerctr(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL-ports <pgsql-ports(at)postgresql(dot)org>, PostgreSQL-Admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Re: [PORTS] pgmonitor and Solaris |
Date: | 2001-03-28 22:51:26 |
Message-ID: | 20010329005126.D26435@ilse.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers pgsql-ports |
On Wed, Mar 28, 2001 at 05:33:05PM -0500, Bruce Momjian allegedly wrote:
> Sure 'ps -U' will work, but it was reported that on Solaris, plain ps
> can't show the postgres status display, while ucb/ps can. I don't need
> specific columns. What I need is the postgres status parameters, and if
> possible, a user restriction to ps for performance reasons.
My mistake. Have a look at this snippet from the ps manpage:
| args The command with all its arguments as a string. The
| implementation may truncate this value to the field
| width; it is implementation-dependent whether any
| further truncation occurs. It is unspecified whether
| the string represented is a version of the argument
| list as it was passed to the command when it started,
| or is a version of the arguments as they may have been
| modified by the application. Applications cannot
| depend on being able to modify their argument list and
| having that modification be reflected in the output of
| ps. The Solaris implementation limits the string to
| 80 bytes; the string is the version of the argument
| list as it was passed to the command when it started.
Note the last line...
The following must also seem familiar ;)
| The Hermit Hacker <scrappy(at)hub(dot)org> writes:
| > On Wed, 29 Apr 1998, Bruce Momjian wrote:
| >> No reason for the exec(). I believe the only advantage is that it gives
| >> us a separate process name in the 'ps' listing. I have looked into
| >> simulating this.
| > Under FreeBSD, there is:
| > setproctitle(3) - set the process title for ps 1
| > This isn't available under Solaris though, last I checked...
|
| Setting the process title from C is messy, but there is a readily
| available reference. The Berkeley sendmail distribution includes code
| to emulate setproctitle on practically every platform. See conf.h and
| conf.c in any recent sendmail release. Warning: it's grotty enough to
| make a strong man weep. Don't read near mealtime ;-)
|
| regards, tom lane
Regards,
Mathijs
--
It's not that perl programmers are idiots, it's that the language
rewards idiotic behavior in a way that no other language or tool has
ever done.
Erik Naggum
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-03-28 23:07:46 | Re: [HACKERS] Re: [PORTS] pgmonitor and Solaris |
Previous Message | Mathijs Brands | 2001-03-28 22:34:53 | Re: [HACKERS] Re: [PORTS] pgmonitor and Solaris |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-03-28 23:07:46 | Re: [HACKERS] Re: [PORTS] pgmonitor and Solaris |
Previous Message | Mathijs Brands | 2001-03-28 22:34:53 | Re: [HACKERS] Re: [PORTS] pgmonitor and Solaris |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-03-28 23:07:46 | Re: [HACKERS] Re: [PORTS] pgmonitor and Solaris |
Previous Message | Tom Lane | 2001-03-28 22:38:18 | Re: Cygwin PostgreSQL Regression Test Problems (Revisited) |