Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Transactional directory deployment details
edc
Is there a good/detailed reference on the file system "dance" that O.D. performs on a transactional edition deployment when a directory is replaced?
I know the basic high level steps OD goes through for a set of files (push all changing files to the target servers, name them XX.iwnew, wait and ensure the files all crossed the wire to all servers, then move originals to XX.iwold and new files move into place, make sure all went well, then clean up).
However, I'm lacking some understanding on how "deep" directories are changed when the DIRECTORY ITSELF is replaced. Specifically, if the file mode on a Unix directory changes. Is a complete copy made of the existing tree such that all the "new" files can then be placed in the "new" top level directory, or is some mixed order of file moves between the "old" directory and the "new" one performed?
Why I ask:
We have a situation where an external process is occasionally changing the mode (permissions) on a target Unix server. They are setting the group sticky bit - which should not cause a problem for us. But, when that occurs, upon the next edition deployment, OD replaces all the directories in an attempt to fix the modes. Even though only one or two "files" are actually changing in a deep directory tree, the entire (rather large) directory tree is reset.
Unfortunately, OD is running into a problem (Unix errno = 17) during these types of deployments. And then the rollback doesn't go well... resulting in an (almost) empty target directory.
Clearing the directory and redeploying works fine, so we can recover somewhat quickly. And subsequent deployments work great until the next mode change comes along.
Obviously, we need to kill that external process that is appropriately changing our file mode. However, logically that should not prevent OD from deploying a new edition, and I'm trying to understand why OD is failing when this occurs.
Any insight would be appreciated.
Find more posts tagged with
Comments
artor
Are you using directory camparision deployment with dateDifferent? what mode is getting changed through external script?
Regards,
A