Re: [HACKERS] set_ps_display on solaris x86
> "Bruce" == Bruce Momjian <[EMAIL PROTECTED]> writes: Bruce> Tom Lane wrote: >> Sailesh Krishnamurthy <[EMAIL PROTECTED]> writes: >> > Sadly, set_ps_display does not seem to have any effect in solaris >> > x86. At least ps only reports multiple postmaster processes and >> > arguments. >> >> IIRC, you have to use the "other" version of ps to see the process >> status on Solaris. I forget where it lives exactly, /usr/ucb maybe? Bruce> Yep, monitoring chapter mentions it: Thanks ! I was pointed to it by Kevin Brown in private email. He also showed me how to teach ddd to use the right command as a helper. Now I need to figure out how to get our sysadmins to make this value a global change when our students first start ddd - so that they can easily attach to the right postgres backend while debugging. -- Pip-pip Sailesh http://www.cs.berkeley.edu/~sailesh ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] set_ps_display on solaris x86
Tom Lane wrote: > Sailesh Krishnamurthy <[EMAIL PROTECTED]> writes: > > Sadly, set_ps_display does not seem to have any effect in solaris > > x86. At least ps only reports multiple postmaster processes and > > arguments. > > IIRC, you have to use the "other" version of ps to see the process > status on Solaris. I forget where it lives exactly, /usr/ucb maybe? Yep, monitoring chapter mentions it: Solaris requires special handling. You must use /usr/ucb/ps, rather than /bin/ps. You also must use two w flags, not just one. In addition, your original invocation of the postmaster must have a shorter ps status display than that provided by each backend. If you fail to do all three things, the ps output for each backend will be the original postmaster command line. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] set_ps_display on solaris x86
Sailesh Krishnamurthy <[EMAIL PROTECTED]> writes: > Sadly, set_ps_display does not seem to have any effect in solaris > x86. At least ps only reports multiple postmaster processes and > arguments. IIRC, you have to use the "other" version of ps to see the process status on Solaris. I forget where it lives exactly, /usr/ucb maybe? regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] set_ps_display on solaris x86
Our students are (unfortunately) on solaris x86 (unfortunate because I have to do another round of testing before I deploy pgsql code for them to hack). Sadly, set_ps_display does not seem to have any effect in solaris x86. At least ps only reports multiple postmaster processes and arguments. Is there some magic incantation to be chanted to get this to work ? Thanks ! -- Pip-pip Sailesh http://www.cs.berkeley.edu/~sailesh ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
