Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
A
auto-tx
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
vamp
auto-tx
Commits
f78558a5
Commit
f78558a5
authored
7 years ago
by
Niko Ehrenfeuchter
Browse files
Options
Downloads
Patches
Plain Diff
Explain notifications and transfer spooling.
parent
bdbe31c7
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+19
-2
19 additions, 2 deletions
README.md
with
19 additions
and
2 deletions
README.md
+
19
−
2
View file @
f78558a5
...
...
@@ -33,7 +33,10 @@ goals:
transfers, as well as on transfer interruptions (system being shutdown or
similar).
-
**Error reporting:**
in addition to user notifications, the service will send
error notifications via email to a separate admin address.
error notifications via email to a separate admin address. Optionally, the
service offers the possibility to monitor free disk space on the local disks
and send notifications to the admins as well. Various measures are implemented
to prevent the service from flooding you with emails.
-
**Tray Application:**
complementary to the service an application running in
the system tray is provided, showing details on what's going on to the user.
-
**Headless and GUI:**
submitting a folder for transfer can either be done by
...
...
@@ -53,7 +56,21 @@ For any user that should be allowed to use the transfer service, a dedicated
folder has to exist on this network share, the name of the folder being the
(short) AD account name (i.e. the login name or
*sAMAccountName*
) of the user.
-
spooling
After the user initiates a transfer (i.e. hands over a folder to the AutoTx
service), the folder gets
**immediately**
moved to the
*spooling*
location on
the same disk. This is done to prevent users from accidentially messing with
folders subject to being transferred as well as for internal bookkeeping of what
has to be transferred.
When no other transfer is running and all system parameters are within their
valid ranges, the AutoTx service will start copying the files and folders to a
temporary transfer directory inside the target location. Only when a transfer
has completed, it will be moved from the temporary location over to the user's
folder. This has the benefit that a user can't accidentially access data from
incomplete transfers as well as it serves as a kind of implicit notification: if
a folder shows up in their location, the user will know it has been fully
transferred.
-
temp location
-
finalize
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment