You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hadoop.apache.org by sam liu <sa...@gmail.com> on 2014/04/24 18:05:52 UTC
What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
Hi Experts,
When the nodemanager log-dirs not exists, I think
LocalDirsHandlerService#serviceInit will invoke
DirectoryCollection#createDir to create the log dirs, and chmod 755 to it.
However, when nodemanager log-dirs already exists and with a non 755
permission(like 775), I found its permission will still be changed to 755,
after starting nodemanager. But, I do not think
DirectoryCollection#createDir did that operation.
What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
Re: What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Not 755, but yeah. See DefaultContainerExecutor.createAppLogDirs(). You may
have to debug more though.
+Vinod
Hortonworks Inc.
http://hortonworks.com/
On Fri, Apr 25, 2014 at 8:42 AM, sam liu <sa...@gmail.com> wrote:
> My version is 2.1.0 and the cluster uses DefaultContainerExecutor. Is it
> possible that DefaultContainerExecutor change the permission of existing
> nodemanager log-dir to 755?
>
>
> 2014-04-25 0:54 GMT+08:00 Vinod Kumar Vavilapalli <vi...@apache.org>:
>
>>
>> Which version of Hadoop are you using? This part of code changed a
>> little, so asking.
>>
>> Also, is this in secure or non-secure mode (DefaultContainerExecutor vs
>> LinuxContainerExecutor)? Either of those two classes do some more
>> permission magic and you may be running into those.
>>
>> +Vinod
>> Hortonworks Inc.
>> http://hortonworks.com/
>>
>> On Thu, Apr 24, 2014 at 9:05 AM, sam liu <sa...@gmail.com> wrote:
>>
>>> Hi Experts,
>>>
>>> When the nodemanager log-dirs not exists, I think
>>> LocalDirsHandlerService#serviceInit will invoke
>>> DirectoryCollection#createDir to create the log dirs, and chmod 755 to it.
>>>
>>> However, when nodemanager log-dirs already exists and with a non 755
>>> permission(like 775), I found its permission will still be changed to 755,
>>> after starting nodemanager. But, I do not think
>>> DirectoryCollection#createDir did that operation.
>>>
>>> What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
>>>
>>>
>>
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity
>> to which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>
>
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Not 755, but yeah. See DefaultContainerExecutor.createAppLogDirs(). You may
have to debug more though.
+Vinod
Hortonworks Inc.
http://hortonworks.com/
On Fri, Apr 25, 2014 at 8:42 AM, sam liu <sa...@gmail.com> wrote:
> My version is 2.1.0 and the cluster uses DefaultContainerExecutor. Is it
> possible that DefaultContainerExecutor change the permission of existing
> nodemanager log-dir to 755?
>
>
> 2014-04-25 0:54 GMT+08:00 Vinod Kumar Vavilapalli <vi...@apache.org>:
>
>>
>> Which version of Hadoop are you using? This part of code changed a
>> little, so asking.
>>
>> Also, is this in secure or non-secure mode (DefaultContainerExecutor vs
>> LinuxContainerExecutor)? Either of those two classes do some more
>> permission magic and you may be running into those.
>>
>> +Vinod
>> Hortonworks Inc.
>> http://hortonworks.com/
>>
>> On Thu, Apr 24, 2014 at 9:05 AM, sam liu <sa...@gmail.com> wrote:
>>
>>> Hi Experts,
>>>
>>> When the nodemanager log-dirs not exists, I think
>>> LocalDirsHandlerService#serviceInit will invoke
>>> DirectoryCollection#createDir to create the log dirs, and chmod 755 to it.
>>>
>>> However, when nodemanager log-dirs already exists and with a non 755
>>> permission(like 775), I found its permission will still be changed to 755,
>>> after starting nodemanager. But, I do not think
>>> DirectoryCollection#createDir did that operation.
>>>
>>> What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
>>>
>>>
>>
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity
>> to which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>
>
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Not 755, but yeah. See DefaultContainerExecutor.createAppLogDirs(). You may
have to debug more though.
+Vinod
Hortonworks Inc.
http://hortonworks.com/
On Fri, Apr 25, 2014 at 8:42 AM, sam liu <sa...@gmail.com> wrote:
> My version is 2.1.0 and the cluster uses DefaultContainerExecutor. Is it
> possible that DefaultContainerExecutor change the permission of existing
> nodemanager log-dir to 755?
>
>
> 2014-04-25 0:54 GMT+08:00 Vinod Kumar Vavilapalli <vi...@apache.org>:
>
>>
>> Which version of Hadoop are you using? This part of code changed a
>> little, so asking.
>>
>> Also, is this in secure or non-secure mode (DefaultContainerExecutor vs
>> LinuxContainerExecutor)? Either of those two classes do some more
>> permission magic and you may be running into those.
>>
>> +Vinod
>> Hortonworks Inc.
>> http://hortonworks.com/
>>
>> On Thu, Apr 24, 2014 at 9:05 AM, sam liu <sa...@gmail.com> wrote:
>>
>>> Hi Experts,
>>>
>>> When the nodemanager log-dirs not exists, I think
>>> LocalDirsHandlerService#serviceInit will invoke
>>> DirectoryCollection#createDir to create the log dirs, and chmod 755 to it.
>>>
>>> However, when nodemanager log-dirs already exists and with a non 755
>>> permission(like 775), I found its permission will still be changed to 755,
>>> after starting nodemanager. But, I do not think
>>> DirectoryCollection#createDir did that operation.
>>>
>>> What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
>>>
>>>
>>
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity
>> to which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>
>
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Not 755, but yeah. See DefaultContainerExecutor.createAppLogDirs(). You may
have to debug more though.
+Vinod
Hortonworks Inc.
http://hortonworks.com/
On Fri, Apr 25, 2014 at 8:42 AM, sam liu <sa...@gmail.com> wrote:
> My version is 2.1.0 and the cluster uses DefaultContainerExecutor. Is it
> possible that DefaultContainerExecutor change the permission of existing
> nodemanager log-dir to 755?
>
>
> 2014-04-25 0:54 GMT+08:00 Vinod Kumar Vavilapalli <vi...@apache.org>:
>
>>
>> Which version of Hadoop are you using? This part of code changed a
>> little, so asking.
>>
>> Also, is this in secure or non-secure mode (DefaultContainerExecutor vs
>> LinuxContainerExecutor)? Either of those two classes do some more
>> permission magic and you may be running into those.
>>
>> +Vinod
>> Hortonworks Inc.
>> http://hortonworks.com/
>>
>> On Thu, Apr 24, 2014 at 9:05 AM, sam liu <sa...@gmail.com> wrote:
>>
>>> Hi Experts,
>>>
>>> When the nodemanager log-dirs not exists, I think
>>> LocalDirsHandlerService#serviceInit will invoke
>>> DirectoryCollection#createDir to create the log dirs, and chmod 755 to it.
>>>
>>> However, when nodemanager log-dirs already exists and with a non 755
>>> permission(like 775), I found its permission will still be changed to 755,
>>> after starting nodemanager. But, I do not think
>>> DirectoryCollection#createDir did that operation.
>>>
>>> What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
>>>
>>>
>>
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity
>> to which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>
>
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
Posted by sam liu <sa...@gmail.com>.
My version is 2.1.0 and the cluster uses DefaultContainerExecutor. Is it
possible that DefaultContainerExecutor change the permission of existing
nodemanager log-dir to 755?
2014-04-25 0:54 GMT+08:00 Vinod Kumar Vavilapalli <vi...@apache.org>:
>
> Which version of Hadoop are you using? This part of code changed a little,
> so asking.
>
> Also, is this in secure or non-secure mode (DefaultContainerExecutor vs
> LinuxContainerExecutor)? Either of those two classes do some more
> permission magic and you may be running into those.
>
> +Vinod
> Hortonworks Inc.
> http://hortonworks.com/
>
> On Thu, Apr 24, 2014 at 9:05 AM, sam liu <sa...@gmail.com> wrote:
>
>> Hi Experts,
>>
>> When the nodemanager log-dirs not exists, I think
>> LocalDirsHandlerService#serviceInit will invoke
>> DirectoryCollection#createDir to create the log dirs, and chmod 755 to it.
>>
>> However, when nodemanager log-dirs already exists and with a non 755
>> permission(like 775), I found its permission will still be changed to 755,
>> after starting nodemanager. But, I do not think
>> DirectoryCollection#createDir did that operation.
>>
>> What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
>>
>>
>
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
Re: What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
Posted by sam liu <sa...@gmail.com>.
My version is 2.1.0 and the cluster uses DefaultContainerExecutor. Is it
possible that DefaultContainerExecutor change the permission of existing
nodemanager log-dir to 755?
2014-04-25 0:54 GMT+08:00 Vinod Kumar Vavilapalli <vi...@apache.org>:
>
> Which version of Hadoop are you using? This part of code changed a little,
> so asking.
>
> Also, is this in secure or non-secure mode (DefaultContainerExecutor vs
> LinuxContainerExecutor)? Either of those two classes do some more
> permission magic and you may be running into those.
>
> +Vinod
> Hortonworks Inc.
> http://hortonworks.com/
>
> On Thu, Apr 24, 2014 at 9:05 AM, sam liu <sa...@gmail.com> wrote:
>
>> Hi Experts,
>>
>> When the nodemanager log-dirs not exists, I think
>> LocalDirsHandlerService#serviceInit will invoke
>> DirectoryCollection#createDir to create the log dirs, and chmod 755 to it.
>>
>> However, when nodemanager log-dirs already exists and with a non 755
>> permission(like 775), I found its permission will still be changed to 755,
>> after starting nodemanager. But, I do not think
>> DirectoryCollection#createDir did that operation.
>>
>> What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
>>
>>
>
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
Re: What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
Posted by sam liu <sa...@gmail.com>.
My version is 2.1.0 and the cluster uses DefaultContainerExecutor. Is it
possible that DefaultContainerExecutor change the permission of existing
nodemanager log-dir to 755?
2014-04-25 0:54 GMT+08:00 Vinod Kumar Vavilapalli <vi...@apache.org>:
>
> Which version of Hadoop are you using? This part of code changed a little,
> so asking.
>
> Also, is this in secure or non-secure mode (DefaultContainerExecutor vs
> LinuxContainerExecutor)? Either of those two classes do some more
> permission magic and you may be running into those.
>
> +Vinod
> Hortonworks Inc.
> http://hortonworks.com/
>
> On Thu, Apr 24, 2014 at 9:05 AM, sam liu <sa...@gmail.com> wrote:
>
>> Hi Experts,
>>
>> When the nodemanager log-dirs not exists, I think
>> LocalDirsHandlerService#serviceInit will invoke
>> DirectoryCollection#createDir to create the log dirs, and chmod 755 to it.
>>
>> However, when nodemanager log-dirs already exists and with a non 755
>> permission(like 775), I found its permission will still be changed to 755,
>> after starting nodemanager. But, I do not think
>> DirectoryCollection#createDir did that operation.
>>
>> What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
>>
>>
>
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
Re: What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
Posted by sam liu <sa...@gmail.com>.
My version is 2.1.0 and the cluster uses DefaultContainerExecutor. Is it
possible that DefaultContainerExecutor change the permission of existing
nodemanager log-dir to 755?
2014-04-25 0:54 GMT+08:00 Vinod Kumar Vavilapalli <vi...@apache.org>:
>
> Which version of Hadoop are you using? This part of code changed a little,
> so asking.
>
> Also, is this in secure or non-secure mode (DefaultContainerExecutor vs
> LinuxContainerExecutor)? Either of those two classes do some more
> permission magic and you may be running into those.
>
> +Vinod
> Hortonworks Inc.
> http://hortonworks.com/
>
> On Thu, Apr 24, 2014 at 9:05 AM, sam liu <sa...@gmail.com> wrote:
>
>> Hi Experts,
>>
>> When the nodemanager log-dirs not exists, I think
>> LocalDirsHandlerService#serviceInit will invoke
>> DirectoryCollection#createDir to create the log dirs, and chmod 755 to it.
>>
>> However, when nodemanager log-dirs already exists and with a non 755
>> permission(like 775), I found its permission will still be changed to 755,
>> after starting nodemanager. But, I do not think
>> DirectoryCollection#createDir did that operation.
>>
>> What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
>>
>>
>
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
Re: What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Which version of Hadoop are you using? This part of code changed a little,
so asking.
Also, is this in secure or non-secure mode (DefaultContainerExecutor vs
LinuxContainerExecutor)? Either of those two classes do some more
permission magic and you may be running into those.
+Vinod
Hortonworks Inc.
http://hortonworks.com/
On Thu, Apr 24, 2014 at 9:05 AM, sam liu <sa...@gmail.com> wrote:
> Hi Experts,
>
> When the nodemanager log-dirs not exists, I think
> LocalDirsHandlerService#serviceInit will invoke
> DirectoryCollection#createDir to create the log dirs, and chmod 755 to it.
>
> However, when nodemanager log-dirs already exists and with a non 755
> permission(like 775), I found its permission will still be changed to 755,
> after starting nodemanager. But, I do not think
> DirectoryCollection#createDir did that operation.
>
> What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
>
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Which version of Hadoop are you using? This part of code changed a little,
so asking.
Also, is this in secure or non-secure mode (DefaultContainerExecutor vs
LinuxContainerExecutor)? Either of those two classes do some more
permission magic and you may be running into those.
+Vinod
Hortonworks Inc.
http://hortonworks.com/
On Thu, Apr 24, 2014 at 9:05 AM, sam liu <sa...@gmail.com> wrote:
> Hi Experts,
>
> When the nodemanager log-dirs not exists, I think
> LocalDirsHandlerService#serviceInit will invoke
> DirectoryCollection#createDir to create the log dirs, and chmod 755 to it.
>
> However, when nodemanager log-dirs already exists and with a non 755
> permission(like 775), I found its permission will still be changed to 755,
> after starting nodemanager. But, I do not think
> DirectoryCollection#createDir did that operation.
>
> What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
>
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Which version of Hadoop are you using? This part of code changed a little,
so asking.
Also, is this in secure or non-secure mode (DefaultContainerExecutor vs
LinuxContainerExecutor)? Either of those two classes do some more
permission magic and you may be running into those.
+Vinod
Hortonworks Inc.
http://hortonworks.com/
On Thu, Apr 24, 2014 at 9:05 AM, sam liu <sa...@gmail.com> wrote:
> Hi Experts,
>
> When the nodemanager log-dirs not exists, I think
> LocalDirsHandlerService#serviceInit will invoke
> DirectoryCollection#createDir to create the log dirs, and chmod 755 to it.
>
> However, when nodemanager log-dirs already exists and with a non 755
> permission(like 775), I found its permission will still be changed to 755,
> after starting nodemanager. But, I do not think
> DirectoryCollection#createDir did that operation.
>
> What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
>
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Which version of Hadoop are you using? This part of code changed a little,
so asking.
Also, is this in secure or non-secure mode (DefaultContainerExecutor vs
LinuxContainerExecutor)? Either of those two classes do some more
permission magic and you may be running into those.
+Vinod
Hortonworks Inc.
http://hortonworks.com/
On Thu, Apr 24, 2014 at 9:05 AM, sam liu <sa...@gmail.com> wrote:
> Hi Experts,
>
> When the nodemanager log-dirs not exists, I think
> LocalDirsHandlerService#serviceInit will invoke
> DirectoryCollection#createDir to create the log dirs, and chmod 755 to it.
>
> However, when nodemanager log-dirs already exists and with a non 755
> permission(like 775), I found its permission will still be changed to 755,
> after starting nodemanager. But, I do not think
> DirectoryCollection#createDir did that operation.
>
> What codes to chmod 755 to "yarn.nodemanager.log-dirs"?
>
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.