From: | Robert Lor <Robert(dot)Lor(at)Sun(dot)COM> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] Generic Monitoring Framework with DTrace patch |
Date: | 2006-07-22 13:19:52 |
Message-ID: | 44C225F8.5010206@sun.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Peter Eisentraut wrote:
>Here is a consolidated patch that contains all the files. I made some
>configure and makefile adjustments and put standard comment headers in
>all the files. You can use DTRACEFLAGS to pass options to configure,
>which should help sorting out the 32/64-bit issue. The problem of the
>*.d files is already gone in CVS.
>
>Since I don't have access to a Solaris system, this is untested for the
>DTrace-enabled case. The only thing left to do besides actually
>testing that case would be moving the probes.d file to a different
>location, since we probably don't want to have special-purpose files in
>src/backend.
>
>
>
I can't seem to apply the patch on Solaris. I ran the patch command from
the top of the src tree and got the following messages. When I tried to
enter a file name, it goes into infinite loop. What did I do wrong?
-bash-3.00$ patch -p0 -u < /var/tmp/dtrace-patch.diff
Looks like a unified context diff.
The next patch looks like a unified context diff.
The next patch looks like a unified context diff.
The next patch looks like a unified context diff.
The next patch looks like a unified context diff.
File to patch:
Regards,
-Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2006-07-22 13:45:24 | Re: [PATCHES] Generic Monitoring Framework with DTrace patch |
Previous Message | Hannu Krosing | 2006-07-22 07:49:29 | Re: "hot standby" system |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2006-07-22 13:45:24 | Re: [PATCHES] Generic Monitoring Framework with DTrace patch |
Previous Message | Robert Treat | 2006-07-22 12:36:27 | Re: Mark change-on-restart-only values in postgresql.conf |