Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.13.0
-
None
Description
Current Situation
- YADE4DMZ does not use the Profile->Operation->... ->TransferOptions ->Transactional setting and always transfers files transactionally.
- This causes a suffix or prefix such as "~" to be temporarily added to the names of target files as long as the file transfer has not been completed.
- The suffix or prefix will then be removed once transfer has been successful.
- In some situations (e.g. when the rename operation is not allowed), the YADE4DMZ transfer fails.
Desired Behaviour
- YADE4DMZ should allow transfers without a rename operation.
Maintainer Note
- For compatibility reasons, the default behavior remains transactional.
- This can be switched off if TransferOptions->Transactional is set to false in the respective transfer profile.
- this setting is applied to all transfers (to/from jump host).
- If only the transfer from the jump host should no longer be transactional, the JumpCommand can be extended:
- Fragments->ProtocolFragments->JumpFragment->JumpCommand = <yade_home>/bin/yade.cmd|sh -transactional=false
Patch
- Note:
- It is enough to apply the patch to the YADE client calling the jump command.
- The YADE client on the jump host does not need to be patched.
- Patches are available for download with YADE releases:
-
- YADE Standalone Client 1.13.12 - download the patch: yade_1.13.12-PATCH-1.YADE-608.zip [sha256] [sig] [tsr]
- YADE Standalone Client 1.13.18 - download the patch: yade_1.13.18-PATCH-1.YADE-608.zip [sha256] [sig] [tsr]
- YADE Standalone Client 1.13.19 - download the patch: yade_1.13.19-PATCH-1.YADE-608.zip [sha256] [sig] [tsr]
- How to apply the patch:
- YADE CLI Client (JS1, JS7):
- YADE as JITL job for JobScheduler 1.13 (JS1):
- unzip the patch yade_<release>-PATCH-1.
YADE-608.jar to the ./lib/patches directory of JobScheduler Master or Agent that run the YADE job and perform a restart.
- unzip the patch yade_<release>-PATCH-1.