Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
EA Issue
mangetak
Hi,
As said in Doc, one can set Extended Attributes onto files or directories. We are having an issue in the second case not being able to set EAs to directories.
We get this error:
<b>"EA lookup failed, server returned error 2439"</b>
when executing this:
/opt/iw-home/bin/iwextattr -s 'xxxx = xxxx' /iwmnt/default/main/branch/WORKAREA/workarea/directory
Any one has faced this issue before?
Thanks in advance
Find more posts tagged with
Comments
Adam Stoller
What page of what document for which version of TeamSite for which platform are you looking at?
I just checked a couple of CLT documents (one for 5.5.2 and the other for 6.1) and neither of them claimed you could set EAs on directories (which, as you have found out - you can't -- because directories are not versioned).
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
mangetak
Oh yeah, I was wrong about that. I got that information from the command help executing:
/opt/iw-home/bin/iwextattr -h
Then you get this message saying you can set extendeded attributes on directories:
Usage: iwextattr [-s attr=value | -g attr | -d attr | -l] [-f] vpath
Set, get, or delete extended attributes of the file
or directory specified in the vpath.
The vpath is in the form:
[//server]/archive{[/branch]+}/{EDITION,WORKAREA}/dirpath
-h Print this message.
-v Print version string.
-s attr=value Set to .
-s attr Set reading value from stdin.
-g attr Get the value of .
-d attr Delete attribute .
-c Clear (delete) all EAs for this file.
-e Enumerate attribute names.
-l List attributes and values.
-r Use to filter attribute names (requires -l or -e)
-u Encode/decode EA values to/from UTF8 on input/output.
-x Read and write XML with -s and -l options.
If no option is specified, attributes are listed as with -l.
lhdavis
Maybe that was written with the intention of being able to assign an extended attribute to all the files that exist under the directory specified. I have not tried that as I will typically loop through the directory or a given filelist and add any extended attributes that way.
Did you have files existing under your directory when you tested to see if the extended attribute is applied to the files, rather than the directory?
Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov
mangetak
Yes i have files under that directory and guess it does not work tha way.
Thanks a lot anyway
Adam Stoller
Hmm - I'd suggest you file a bug with Support on that - as the usage information is clearly wrong. It will probably get filed as "low" priority, but better it gets filed than not.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com