[pca] Question on setting up local caching proxy for pca
Rajiv Gunja
opn.src.rocks at gmail.com
Wed Jul 9 16:35:30 CEST 2008
Sweet Success !!
---
Rajiv G Gunja
2008/7/9 Gurugunti, Mahesh <Mahesh.Gurugunti at alliancebernstein.com>:
> I was able to figure out,
>
> on the client side my patchurl was pointing to wrong location.
>
> Thanks.
>
> Mahesh
>
> ------------------------------
> *From:* pca-bounces at lists.univie.ac.at [mailto:
> pca-bounces at lists.univie.ac.at] *On Behalf Of *Gurugunti, Mahesh
> *Sent:* Wednesday, July 09, 2008 9:30 AM
>
> *To:* PCA (Patch Check Advanced) Discussion
> *Subject:* Re: [pca] Question on setting up local caching proxy for pca
>
> On the server /pcarepo (patchdir) is owned by "daemon"
>
> bash-3.00# uname -a
> SunOS amaeng3 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Fire-280R
> bash-3.00# ps -ef |grep htt
> daemon 19698 27976 0 09:24:27 ? 0:00
> /usr/local/apache2/bin/httpd -k start
> daemon 19692 27976 0 09:24:27 ? 0:00
> /usr/local/apache2/bin/httpd -k start
> daemon 19704 27976 0 09:24:35 ? 0:00
> /usr/local/apache2/bin/httpd -k start
> daemon 19690 27976 0 09:24:27 ? 0:00
> /usr/local/apache2/bin/httpd -k start
> daemon 19696 27976 0 09:24:27 ? 0:00
> /usr/local/apache2/bin/httpd -k start
> daemon 19694 27976 0 09:24:27 ? 0:00
> /usr/local/apache2/bin/httpd -k start
> root 27976 1 1 Feb 08 ? 7:28
> /usr/local/apache2/bin/httpd -k start
> bash-3.00# ls -ld /pcarepo
> drwxrw-r-- 2 daemon daemon 40960 Jul 9 09:23 /pcarepo
> bash-3.00#
>
> What I fail to understand is on client side when "pca -d patchnum" is
> initiated , its trying to write into cgi-bin directory, somehow its thinkng
> that cgi-bin is the patch download directory.
>
> "Connecting to amaeng3.acml.com|10.80.61.32|:80... connected.
> HTTP request sent, awaiting response... 500 Can't write to patch download
> directory /export/opt/jumpstart/www/cgi-bin/.
> 09:23:38 ERROR 500: Can't write to patch download directory
> /export/opt/jumpstart/www/cgi-bin/.."
>
> Does it have anything to do with pca-proxy.cgi script, does it need some
> tweeking somewhere?
>
> Mahesh
>
>
> ------------------------------
> *From:* pca-bounces at lists.univie.ac.at [mailto:
> pca-bounces at lists.univie.ac.at] *On Behalf Of *Rajiv Gunja
> *Sent:* Wednesday, July 09, 2008 9:17 AM
> *To:* PCA (Patch Check Advanced) Discussion
> *Subject:* Re: [pca] Question on setting up local caching proxy for pca
>
> Mahesh,
> "Can't write to patch download directory"
>
> You patch directory should be "owned" by the daemon which starts the
>>> httpd on your PCA Proxy/Cache Server. On my server *webservd* is the ID
>>> which starts httpd, so I have my /pca/Patches directory owned by *
>>> webservd* and make sure u have at least *764* as permission.
>>>
>>
> Let us know how your fare.
>
> -GGR
>
> ---
> Rajiv G Gunja
>
> 2008/7/9 Gurugunti, Mahesh <Mahesh.Gurugunti at alliancebernstein.com>:
>
>> I added debug=1 to client side pca.conf and re-ran, here is what it
>> spits out
>>
>> bash-3.00# ~mgurug/PCA/pca --d 119254
>> Option download: 1
>> Option xrefdir: /var/pca
>> Option patchdir: /var/pca
>> Option patchurl: http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi?
>> Option xrefurl: http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi?
>> Option debug: 1
>> Option wgetq:
>> ARGV: 119254
>> Version: 20080519-01
>> Config files: /etc/pca.conf
>> Using /usr/sfw/bin/wget (1.10.2, 11002)
>> Prerequisites for threads not met, setting threads to 0
>> Never update
>> Expanded patch list: 119254
>> xref now : Wed Jul 9 08:51:32 2008
>> xref current: Tue Jul 8 15:02:26 2008
>> xref age : 64146
>> Downloading xref file to /var/pca/patchdiag.xref
>> Trying http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi?
>> --08:51:32--
>> http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi?patchdiag.xref
>> => `/var/pca/patchdiag.xref'
>> Resolving amaeng3.acml.com... 10.80.61.32
>> Connecting to amaeng3.acml.com|10.80.61.32|:80... connected.
>> HTTP request sent, awaiting response... 200 OK
>> Length: 2,721,225 (2.6M) [text/plain]
>>
>> 100%[========================================================================================>]
>> 2,721,225 303.36K/s ETA 00:00
>>
>> 08:51:41 (303.26 KB/s) - `/var/pca/patchdiag.xref' saved [2721225/2721225]
>>
>> old xref age: 2
>> new xref age: 2
>> Reading from /usr/bin/showrev -p
>> Using /var/pca/patchdiag.xref from Jul/07/08
>> Bad patch installed: 126365-06
>> 121133-02 required by 119254: already installed
>> Host: amadv889 (SunOS 5.10/Generic_127127-11/sparc/sun4u)
>> List: 119254
>>
>> Patch IR CR RSB Age Synopsis
>> ------ -- - -- --- ---
>> -------------------------------------------------------
>> 119254 53 < 57 RS- 7 SunOS 5.10: Install and Patch Utilities Patch
>>
>> Downloading 119254-57 (1/1)
>> Trying http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi?
>> --08:51:46-- http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi?119254-57
>> => `/var/pca/119254-57.tmp'
>> Resolving amaeng3.acml.com... 10.80.61.32
>> Connecting to amaeng3.acml.com|10.80.61.32|:80... connected.
>> HTTP request sent, awaiting response... 500 Can't write to patch download
>> directory /export/opt/jumpstart/www/cgi-bin/.
>> 08:51:46 ERROR 500: Can't write to patch download directory
>> /export/opt/jumpstart/www/cgi-bin/..
>>
>> Failed
>> Failed (no Sun Online Account data)
>> Failed (patch not found)
>>
>> ------------------------------------------------------------------------------
>> Download Summary: 1 total, 0 successful, 0 skipped, 1 failed
>> bash-3.00#
>>
>>
>> My client machine is amadv889 and local server is amaeng3, I did not quite
>> understand
>> "write to patch download directory /export/opt/jumpstart/www/cgi-bin/" ,
>> which user is trying to write, is it the webuser trying to write something
>> onto cgi-bin directory on the server amaeng3??
>>
>> Mahesh
>>
>> ------------------------------
>> *From:* pca-bounces at lists.univie.ac.at [mailto:
>> pca-bounces at lists.univie.ac.at] *On Behalf Of *Rajiv Gunja
>> *Sent:* Tuesday, July 08, 2008 6:28 PM
>>
>> *To:* PCA (Patch Check Advanced) Discussion
>> *Subject:* Re: [pca] Question on setting up local caching proxy for pca
>>
>> Mahesh,
>> This is odd. Please add debug=1 on the client side too and run pca -d 119254
>> and see what error messages you get and where it is pointing to.
>>
>> -GGR
>>
>> ---
>> Rajiv G Gunja
>>
>> 2008/7/8 Gurugunti, Mahesh <Mahesh.Gurugunti at alliancebernstein.com>:
>>
>>> Server side /etc/pca.conf, just added "debug=1" at the end of pca.conf
>>> on server side, I don't see any error file generated in /tmp on server side.
>>>
>>> bash-3.00# uname -a
>>> SunOS amaeng3 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Fire-280R
>>>
>>> bash-3.00# cat /etc/pca.conf
>>> xrefdir=/pcarepo
>>> patchdir=/pcarepo
>>> user=myusername
>>> passwd=mypasswd
>>> wgetproxy=http://gmdvproxy.acml.com:8080
>>> debug=1
>>>
>>>
>>> Ran following on the client side
>>> bash-3.00# uname -a
>>> SunOS amadv889 5.10 Generic_127127-11 sun4u sparc SUNW,Sun-Fire-V440
>>> bash-3.00# ~mgurug/PCA/pca --d 119254
>>> Using /var/pca/patchdiag.xref from Jul/07/08
>>> Host: amadv889 (SunOS 5.10/Generic_127127-11/sparc/sun4u)
>>> List: 119254
>>>
>>> Patch IR CR RSB Age Synopsis
>>> ------ -- - -- --- ---
>>> -------------------------------------------------------
>>> 119254 53 < 57 RS- 6 SunOS 5.10: Install and Patch Utilities Patch
>>>
>>> Downloading 119254-57 (1/1)
>>> Trying http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi?
>>> Failed
>>> Failed (no Sun Online Account data)
>>> Failed (patch not found)
>>>
>>> ------------------------------------------------------------------------------
>>> Download Summary: 1 total, 0 successful, 0 skipped, 1 failed
>>>
>>> ps monitoring on the client machine spits out following when above was
>>> run
>>> /usr/sfw/bin/wget -q --timeout=3600 -O /var/pca/119254-57.tmp
>>> http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi?119254-57
>>>
>>> I don't see anything downloaded in /var/pca with that patch number.
>>> However what is confusing is its able to put patcdiag.xref file when I
>>> delete it from /var/pca directory on the client side. I am sure its fetching
>>> it from local server(amaeng3).
>>>
>>> Mahesh
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------
>>> *From:* pca-bounces at lists.univie.ac.at [mailto:
>>> pca-bounces at lists.univie.ac.at] *On Behalf Of *Rajiv Gunja
>>> *Sent:* Tuesday, July 08, 2008 4:42 PM
>>> *To:* PCA (Patch Check Advanced) Discussion
>>>
>>> *Subject:* Re: [pca] Question on setting up local caching proxy for pca
>>>
>>> Mahesh,
>>> 1. Please paste your Server Side /etc/pca.conf
>>> 2. If you have debug=1 in your /etc/pca.conf, then on the Server (PCA
>>> Proxy) side there will be a file /tmp/pca-proxy-debug.txt If you can paste
>>> the relevant text of this transaction here, it would help to know why it is
>>> not communicating.
>>>
>>> Usually, when I get that error, it usually means that my PCA Proxy
>>> /etc/pca.conf is not correct.
>>>
>>> -GGR
>>>
>>> ---
>>> Rajiv G Gunja
>>>
>>>
>>> 2008/7/8 Gurugunti, Mahesh <Mahesh.Gurugunti at alliancebernstein.com>:
>>>
>>>> Rajiv,
>>>>
>>>> Thanks for your inputs.
>>>>
>>>> On Server, looks like it works well after I cofigured /etc/pca.conf
>>>>
>>>>
>>>> bash-3.00# uname -a
>>>> SunOS amaeng3 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Fire-280R
>>>> bash-3.00# ~mgurug/PCA/pca -d 138421
>>>> Using /pcarepo/patchdiag.xref from Jul/07/08
>>>> Host: amaeng3 (SunOS 5.10/Generic_118833-17/sparc/sun4u)
>>>> List: 138421
>>>>
>>>> Patch IR CR RSB Age Synopsis
>>>> ------ -- - -- --- ---
>>>> -------------------------------------------------------
>>>> 138421 -- < 01 --- 29 SunOS 5.10: PostgresSQL 8.3 jdbc patch
>>>>
>>>> Downloading 138421-01 (1/1)
>>>> Skipped (file exists)
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Download Summary: 1 total, 0 successful, 1 skipped, 0 failed
>>>>
>>>> However on the client when I execute
>>>>
>>>> bash-3.00# ./pca -d 118666
>>>> Using /var/pca/patchdiag.xref from Jun/20/08
>>>> Host: amadv889 (SunOS 5.10/Generic_127127-11/sparc/sun4u)
>>>> List: 118666
>>>>
>>>> Patch IR CR RSB Age Synopsis
>>>> ------ -- - -- --- ---
>>>> -------------------------------------------------------
>>>> 118666 15 < 16 -S- 132 JavaSE 5.0: update 15 patch (equivalent to JDK
>>>> 5.0u15)
>>>>
>>>> Downloading 118666-16 (1/1)
>>>> Trying http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi?
>>>> Failed
>>>> Failed (no Sun Online Account data)
>>>> Failed (patch not found)
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Download Summary: 1 total, 0 successful, 0 skipped, 1 failed
>>>>
>>>> my client side /etc/pca.conf looks as below
>>>>
>>>> bash-3.00# cat /etc/pca.conf
>>>> patchdir=/var/pca
>>>> xrefdir=/var/pca
>>>> patchurl=http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi?
>>>> xrefurl=http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi?
>>>>
>>>> Any ideas ??
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------
>>>> *From:* pca-bounces at lists.univie.ac.at [mailto:
>>>> pca-bounces at lists.univie.ac.at] *On Behalf Of *Rajiv Gunja
>>>> *Sent:* Tuesday, July 08, 2008 10:14 AM
>>>> *To:* jonathan.whitehouse at zimmer.com; PCA (Patch Check Advanced)
>>>> Discussion
>>>> *Subject:* Re: [pca] Question on setting up local caching proxy for pca
>>>>
>>>> Addendum: On the Client, you should be able to do:
>>>>
>>>> pca -d 137048-01
>>>>
>>>> NO need of using the other parameters.
>>>>
>>>> -GGR
>>>>
>>>> ---
>>>> Rajiv G Gunja
>>>>
>>>> 2008/7/8 Rajiv Gunja <opn.src.rocks at gmail.com>:
>>>>
>>>>> Here is how I have mine setup:
>>>>>
>>>>> Server: /etc/pca.conf
>>>>> user=userid
>>>>> passwd=password
>>>>> patchdir=/pca/Patches/
>>>>> xrefdir=/pca/Patches/
>>>>> wgetproxy=http://proxy.home.com:80
>>>>> syslog=user
>>>>> dltries=5
>>>>> threads=5
>>>>> debug=1
>>>>>
>>>>> Client: /etc/pca.conf
>>>>> patchdir=/var/pca
>>>>> xrefdir=/var/pca
>>>>> patchurl=http://pcaproxy.home.com/Patches/pca-proxy.cgi?
>>>>> xrefurl=http://pcaproxy.home.com/Patches/pca-proxy.cgi?
>>>>>
>>>>> 1. Make sure that you DO NOT have any http_proxy settings on the Client
>>>>> server for ROOT or Other IDs which use pca.
>>>>>
>>>>> 2. Make sure you have CGI Enabled on the HTTPD Server. Create test.cgi
>>>>> with the following contents and make sure it is executable. This will be a
>>>>> good test if your HTTPD support cgi execution
>>>>> #!/bin/sh
>>>>>
>>>>> # disable filename globbing
>>>>> set -f
>>>>>
>>>>> echo Content-type: text/plain
>>>>> echo
>>>>>
>>>>> echo CGI/1.0 test script report:
>>>>> echo
>>>>>
>>>>> echo argc is $#. argv is "$*".
>>>>> echo
>>>>>
>>>>> echo SERVER_SOFTWARE = $SERVER_SOFTWARE
>>>>> echo SERVER_NAME = $SERVER_NAME
>>>>> echo GATEWAY_INTERFACE = $GATEWAY_INTERFACE
>>>>> echo SERVER_PROTOCOL = $SERVER_PROTOCOL
>>>>> echo SERVER_PORT = $SERVER_PORT
>>>>> echo REQUEST_METHOD = $REQUEST_METHOD
>>>>> echo HTTP_ACCEPT = "$HTTP_ACCEPT"
>>>>> echo PATH_INFO = "$PATH_INFO"
>>>>> echo PATH_TRANSLATED = "$PATH_TRANSLATED"
>>>>> echo SCRIPT_NAME = "$SCRIPT_NAME"
>>>>> echo QUERY_STRING = "$QUERY_STRING"
>>>>> echo REMOTE_HOST = $REMOTE_HOST
>>>>> echo REMOTE_ADDR = $REMOTE_ADDR
>>>>> echo REMOTE_USER = $REMOTE_USER
>>>>> echo AUTH_TYPE = $AUTH_TYPE
>>>>> echo CONTENT_TYPE = $CONTENT_TYPE
>>>>> echo CONTENT_LENGTH = $CONTENT_LENGTH
>>>>>
>>>>> Let us know once you have done this and still have issues.
>>>>>
>>>>> -GGR
>>>>>
>>>>> ---
>>>>> Rajiv G Gunja
>>>>>
>>>>> 2008/7/8 Jonathan L Whitehouse <jonathan.whitehouse at zimmer.com>:
>>>>>
>>>>> Can amaeng3.acml.com talk to the net? In essence amaeng3 is acting
>>>>>> as a proxy…
>>>>>>
>>>>>>
>>>>>>
>>>>>> Can you run just pca on amaeng3 and have it go to sunsolve?
>>>>>>
>>>>>>
>>>>>>
>>>>>> On amaeng3 make sure your /etc/pca.conf is setup as normal.
>>>>>>
>>>>>>
>>>>>>
>>>>>> ---
>>>>>>
>>>>>> *Jonathan Whitehouse*
>>>>>>
>>>>>> *Systems Engineer - IT, Server Support*
>>>>>>
>>>>>> *MS 5221*
>>>>>>
>>>>>> *1800 W. Center Street*
>>>>>>
>>>>>> *Warsaw**, IN 46580***
>>>>>>
>>>>>> *(574) 371-8684*
>>>>>>
>>>>>> *(574) 377-2829 (cell)*
>>>>>>
>>>>>> *jonathan.whitehouse at zimmer.com*
>>>>>>
>>>>>>
>>>>>> ------------------------------
>>>>>>
>>>>>> *From:* pca-bounces at lists.univie.ac.at [mailto:
>>>>>> pca-bounces at lists.univie.ac.at] *On Behalf Of *Gurugunti, Mahesh
>>>>>> *Sent:* Tuesday, July 08, 2008 9:44 AM
>>>>>> *To:* pca at lists.univie.ac.at
>>>>>> *Subject:* [pca] Question on setting up local caching proxy for pca
>>>>>>
>>>>>>
>>>>>>
>>>>>> I have setup a server that contacts sun and using my SOA account
>>>>>> downloads and installs patches. This works fine.
>>>>>>
>>>>>>
>>>>>>
>>>>>> I am in the process of setting up local PCA server , I followed all
>>>>>> the instruction on this page
>>>>>>
>>>>>>
>>>>>>
>>>>>> *http://www.par.univie.ac.at/solaris/pca/usage.html*
>>>>>>
>>>>>>
>>>>>>
>>>>>> of copying pca as pca-proxy.cgi
>>>>>>
>>>>>> settting /etc/pca-proxy.conf
>>>>>>
>>>>>> restarted httpd (amaeng3 is the planned local PCA server)
>>>>>>
>>>>>> etc....
>>>>>>
>>>>>>
>>>>>>
>>>>>> On the client I issued
>>>>>>
>>>>>>
>>>>>>
>>>>>> pca -X . --xrefurl=http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi--patchurl=http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi
>>>>>> -d <http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi-d> 137048-01
>>>>>>
>>>>>>
>>>>>>
>>>>>> it comes back as
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Downloading xref file to /root/./patchdiag.xref
>>>>>> Trying http://amaeng3.acml.com/cgi-bin/pca-proxy.cgi?
>>>>>> Failed
>>>>>>
>>>>>>
>>>>>>
>>>>>> Any ideas? Also, I need to know if there is any config involved on
>>>>>> client side.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks in advance.
>>>>>>
>>>>>> Mahesh
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> -----------------------------------------
>>>>>>
>>>>>> The information contained in the linked e-mail transmission and any attachments may be
>>>>>>
>>>>>> privileged and confidential and is intended only for the use of the person(s) named in the
>>>>>>
>>>>>> linked e-mail transmission. If you are not the intended recipient, or an employee or agent
>>>>>>
>>>>>> responsible for delivering this message to the intended recipient, you should not review,
>>>>>>
>>>>>> disseminate, distribute or duplicate this e-mail transmission or any attachments . If you
>>>>>>
>>>>>> are not the intended recipient, please contact the sender immediately by reply e-mail and
>>>>>>
>>>>>> destroy all copies of the original message. We do not accept account orders and/or
>>>>>>
>>>>>> instructions related to AllianceBernstein products or services by e-mail, and therefore will
>>>>>>
>>>>>> not be responsible for carrying out such orders and/or instructions. The linked e-mail
>>>>>>
>>>>>> transmission and any attachments are provided for informational purposes only and should not
>>>>>>
>>>>>> be construed in any manner as any solicitation or offer to buy or sell any investment
>>>>>>
>>>>>> opportunities or any related financial instruments and should not be construed in any manner
>>>>>>
>>>>>> as a public offer of any investment opportunities or any related financial instruments. If
>>>>>>
>>>>>> you, as the intended recipient of the linked e-mail transmission, the purpose of which is to
>>>>>>
>>>>>> inform and update our clients, prospects and consultants of developments relating to our
>>>>>>
>>>>>> services and products, would not like to receive further e-mail correspondence from the
>>>>>>
>>>>>> sender, please "reply" to the sender indicating your wishes. Although we attempt to sweep
>>>>>>
>>>>>> e-mail and attachments for viruses, we will not be liable for any damages arising from the
>>>>>>
>>>>>> alteration of the contents of this linked e-mail transmission and any attachments by a third
>>>>>> party or as a result of any virus being passed on.
>>>>>>
>>>>>> Please note:
>>>>>>
>>>>>> Trading instructions sent electronically to Bernstein shall not be deemed accepted until a
>>>>>>
>>>>>> representative of Bernstein acknowledges receipt electronically or by telephone. Comments in
>>>>>>
>>>>>> the linked e-mail transmission and any attachments are part of a larger body of investment
>>>>>>
>>>>>> analysis. For our research reports, which contain information that may be used to support
>>>>>> investment decisions, and disclosures, see our website at
>>>>>> www.bernsteinresearch.com.
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -----------------------------------------
>>>> The information contained in the linked e-mail transmission and any attachments may be
>>>>
>>>> privileged and confidential and is intended only for the use of the person(s) named in the
>>>>
>>>> linked e-mail transmission. If you are not the intended recipient, or an employee or agent
>>>>
>>>> responsible for delivering this message to the intended recipient, you should not review,
>>>>
>>>> disseminate, distribute or duplicate this e-mail transmission or any attachments . If you
>>>>
>>>> are not the intended recipient, please contact the sender immediately by reply e-mail and
>>>>
>>>> destroy all copies of the original message. We do not accept account orders and/or
>>>>
>>>> instructions related to AllianceBernstein products or services by e-mail, and therefore will
>>>>
>>>> not be responsible for carrying out such orders and/or instructions. The linked e-mail
>>>>
>>>> transmission and any attachments are provided for informational purposes only and should not
>>>>
>>>> be construed in any manner as any solicitation or offer to buy or sell any investment
>>>>
>>>> opportunities or any related financial instruments and should not be construed in any manner
>>>>
>>>> as a public offer of any investment opportunities or any related financial instruments. If
>>>>
>>>> you, as the intended recipient of the linked e-mail transmission, the purpose of which is to
>>>>
>>>> inform and update our clients, prospects and consultants of developments relating to our
>>>>
>>>> services and products, would not like to receive further e-mail correspondence from the
>>>>
>>>> sender, please "reply" to the sender indicating your wishes. Although we attempt to sweep
>>>>
>>>> e-mail and attachments for viruses, we will not be liable for any damages arising from the
>>>>
>>>> alteration of the contents of this linked e-mail transmission and any attachments by a third
>>>>
>>>> party or as a result of any virus being passed on.
>>>>
>>>> Please note:
>>>> Trading instructions sent electronically to Bernstein shall not be deemed accepted until a
>>>>
>>>> representative of Bernstein acknowledges receipt electronically or by telephone. Comments in
>>>>
>>>> the linked e-mail transmission and any attachments are part of a larger body of investment
>>>>
>>>> analysis. For our research reports, which contain information that may be used to support
>>>>
>>>> investment decisions, and disclosures, see our website at
>>>> www.bernsteinresearch.com.
>>>>
>>>
>>>
>>>
>>>
>>>
>>> -----------------------------------------
>>> The information contained in the linked e-mail transmission and any attachments may be
>>>
>>> privileged and confidential and is intended only for the use of the person(s) named in the
>>>
>>> linked e-mail transmission. If you are not the intended recipient, or an employee or agent
>>>
>>> responsible for delivering this message to the intended recipient, you should not review,
>>>
>>> disseminate, distribute or duplicate this e-mail transmission or any attachments . If you
>>>
>>> are not the intended recipient, please contact the sender immediately by reply e-mail and
>>>
>>> destroy all copies of the original message. We do not accept account orders and/or
>>>
>>> instructions related to AllianceBernstein products or services by e-mail, and therefore will
>>>
>>> not be responsible for carrying out such orders and/or instructions. The linked e-mail
>>>
>>> transmission and any attachments are provided for informational purposes only and should not
>>>
>>> be construed in any manner as any solicitation or offer to buy or sell any investment
>>>
>>> opportunities or any related financial instruments and should not be construed in any manner
>>>
>>> as a public offer of any investment opportunities or any related financial instruments. If
>>>
>>> you, as the intended recipient of the linked e-mail transmission, the purpose of which is to
>>>
>>> inform and update our clients, prospects and consultants of developments relating to our
>>>
>>> services and products, would not like to receive further e-mail correspondence from the
>>>
>>> sender, please "reply" to the sender indicating your wishes. Although we attempt to sweep
>>>
>>> e-mail and attachments for viruses, we will not be liable for any damages arising from the
>>>
>>> alteration of the contents of this linked e-mail transmission and any attachments by a third
>>>
>>> party or as a result of any virus being passed on.
>>>
>>> Please note:
>>> Trading instructions sent electronically to Bernstein shall not be deemed accepted until a
>>>
>>> representative of Bernstein acknowledges receipt electronically or by telephone. Comments in
>>>
>>> the linked e-mail transmission and any attachments are part of a larger body of investment
>>>
>>> analysis. For our research reports, which contain information that may be used to support
>>>
>>> investment decisions, and disclosures, see our website at
>>> www.bernsteinresearch.com.
>>>
>>
>>
>>
>>
>>
>> -----------------------------------------
>> The information contained in the linked e-mail transmission and any attachments may be
>>
>> privileged and confidential and is intended only for the use of the person(s) named in the
>>
>> linked e-mail transmission. If you are not the intended recipient, or an employee or agent
>>
>> responsible for delivering this message to the intended recipient, you should not review,
>>
>> disseminate, distribute or duplicate this e-mail transmission or any attachments . If you
>>
>> are not the intended recipient, please contact the sender immediately by reply e-mail and
>>
>> destroy all copies of the original message. We do not accept account orders and/or
>>
>> instructions related to AllianceBernstein products or services by e-mail, and therefore will
>>
>> not be responsible for carrying out such orders and/or instructions. The linked e-mail
>>
>> transmission and any attachments are provided for informational purposes only and should not
>>
>> be construed in any manner as any solicitation or offer to buy or sell any investment
>>
>> opportunities or any related financial instruments and should not be construed in any manner
>>
>> as a public offer of any investment opportunities or any related financial instruments. If
>>
>> you, as the intended recipient of the linked e-mail transmission, the purpose of which is to
>>
>> inform and update our clients, prospects and consultants of developments relating to our
>>
>> services and products, would not like to receive further e-mail correspondence from the
>>
>> sender, please "reply" to the sender indicating your wishes. Although we attempt to sweep
>>
>> e-mail and attachments for viruses, we will not be liable for any damages arising from the
>>
>> alteration of the contents of this linked e-mail transmission and any attachments by a third
>>
>> party or as a result of any virus being passed on.
>>
>> Please note:
>> Trading instructions sent electronically to Bernstein shall not be deemed accepted until a
>>
>> representative of Bernstein acknowledges receipt electronically or by telephone. Comments in
>>
>> the linked e-mail transmission and any attachments are part of a larger body of investment
>>
>> analysis. For our research reports, which contain information that may be used to support
>>
>> investment decisions, and disclosures, see our website at
>> www.bernsteinresearch.com.
>>
>
>
>
>
>
> -----------------------------------------
> The information contained in the linked e-mail transmission and any attachments may be
>
> privileged and confidential and is intended only for the use of the person(s) named in the
>
> linked e-mail transmission. If you are not the intended recipient, or an employee or agent
>
> responsible for delivering this message to the intended recipient, you should not review,
>
> disseminate, distribute or duplicate this e-mail transmission or any attachments . If you
>
> are not the intended recipient, please contact the sender immediately by reply e-mail and
>
> destroy all copies of the original message. We do not accept account orders and/or
>
> instructions related to AllianceBernstein products or services by e-mail, and therefore will
>
> not be responsible for carrying out such orders and/or instructions. The linked e-mail
>
> transmission and any attachments are provided for informational purposes only and should not
>
> be construed in any manner as any solicitation or offer to buy or sell any investment
>
> opportunities or any related financial instruments and should not be construed in any manner
>
> as a public offer of any investment opportunities or any related financial instruments. If
>
> you, as the intended recipient of the linked e-mail transmission, the purpose of which is to
>
> inform and update our clients, prospects and consultants of developments relating to our
>
> services and products, would not like to receive further e-mail correspondence from the
>
> sender, please "reply" to the sender indicating your wishes. Although we attempt to sweep
>
> e-mail and attachments for viruses, we will not be liable for any damages arising from the
>
> alteration of the contents of this linked e-mail transmission and any attachments by a third
>
> party or as a result of any virus being passed on.
>
> Please note:
> Trading instructions sent electronically to Bernstein shall not be deemed accepted until a
>
> representative of Bernstein acknowledges receipt electronically or by telephone. Comments in
>
> the linked e-mail transmission and any attachments are part of a larger body of investment
>
> analysis. For our research reports, which contain information that may be used to support
>
> investment decisions, and disclosures, see our website at
> www.bernsteinresearch.com.
>
>
>
>
> -----------------------------------------
> The information contained in the linked e-mail transmission and any attachments may be
>
> privileged and confidential and is intended only for the use of the person(s) named in the
>
> linked e-mail transmission. If you are not the intended recipient, or an employee or agent
>
> responsible for delivering this message to the intended recipient, you should not review,
>
> disseminate, distribute or duplicate this e-mail transmission or any attachments . If you
>
> are not the intended recipient, please contact the sender immediately by reply e-mail and
>
> destroy all copies of the original message. We do not accept account orders and/or
>
> instructions related to AllianceBernstein products or services by e-mail, and therefore will
>
> not be responsible for carrying out such orders and/or instructions. The linked e-mail
>
> transmission and any attachments are provided for informational purposes only and should not
>
> be construed in any manner as any solicitation or offer to buy or sell any investment
>
> opportunities or any related financial instruments and should not be construed in any manner
>
> as a public offer of any investment opportunities or any related financial instruments. If
>
> you, as the intended recipient of the linked e-mail transmission, the purpose of which is to
>
> inform and update our clients, prospects and consultants of developments relating to our
>
> services and products, would not like to receive further e-mail correspondence from the
>
> sender, please "reply" to the sender indicating your wishes. Although we attempt to sweep
>
> e-mail and attachments for viruses, we will not be liable for any damages arising from the
>
> alteration of the contents of this linked e-mail transmission and any attachments by a third
>
> party or as a result of any virus being passed on.
>
> Please note:
> Trading instructions sent electronically to Bernstein shall not be deemed accepted until a
>
> representative of Bernstein acknowledges receipt electronically or by telephone. Comments in
>
> the linked e-mail transmission and any attachments are part of a larger body of investment
>
> analysis. For our research reports, which contain information that may be used to support
>
> investment decisions, and disclosures, see our website at
> www.bernsteinresearch.com.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.univie.ac.at/mailman/private/pca/attachments/20080709/a2b346bc/attachment-0001.html
More information about the pca
mailing list