1 12/22/80  enter_carry_request, ecr
 2 
 3 Syntax:  ecr paths {-control_args}
 4 
 5 
 6 Function:  Queues a segment or subtree to be carried to another site.
 7 
 8 
 9 Arguments:
10 paths
11    are the pathnames of segments and directories.  In the case of a
12    directory, the entire subtree is carried.  The star convention
13    is allowed.
14 
15 
16 Control arguments:
17 -destination DEST, -ds DEST
18    specifies a destination site, where DEST is up to 23 characters
19    long.  The carry queue used is named DEST.carry.ms.  If no
20    destination is specified, it is carry.ms, the name added to the
21    queue for the default destination.
22 -queue_dir PATH, -qd PATH
23    specifies the queue's parent directory.  The default is
24    >daemon_dir_dir>carry_dir.
25 -new_dir PATH, -nd PATH
26    applies to the preceding path argument and causes the entry to be
27    loaded under PATH instead of its original parent.
28 -notify, -nt
29    sends mail to the requestor when the request is dumped.
30 -no_notify, -nnt
31    suppresses sending of mail when the request is dumped. (Default)
32 
33 
34 -no_trim
35    suppresses the deletion, when requests are loaded at the target
36    site, of entries in target subtrees that do not appear in the
37    corresponding subtrees at the sending site. (Default)
38 -trim
39    deletes entries in subtrees at the target site that do not exist in
40    the corresponding subtrees at the sending site.  The default is
41    -no_trim.
42 -user STR
43    where STR is of the form Person_id.Project_id, specifies the owner
44    of the carried entries at the target site, if different from the
45    user requesting the carry.  When an entry cannot be loaded in place,
46    this control argument causes access to the retrieved copy to be set
47    for STR, rather than for the requesting user.  It is needed if the
48    requestor is registered with a different name at each site.  Default
49    for STR is the User_id of the requesting user.
50 
51 
52 Access required:
53 1. s to all carry administrators on the parent directory.
54 2. sma to the user and to all carry administrators on all directories
55    in a subtree being carried.
56 3. r to the user and to all carry administrators on a segment being
57    carried or on all segments in a subtree being carried.
58 
59 
60    If the user does not have sa access to the parent directory at the
61 target site, the entry is not loaded and a copy is loaded instead in a
62 directory under >daemon_dir_dir>carry_dir>copies.
63 
64 
65    If any directories in the pathname of a target entry do not exist,
66 they are created.
67 
68 
69 Notes:
70    See also list_carry_requests and cancel_carry_request.  The carry
71 queue is read periodically and the requested entries are dumped on a
72 tape. This tape is mailed to the target site, where it is loaded.
73 
74 
75    The process that dumps and loads carry tapes belongs to a carry
76 administrator, a user with r and d extended access to the queue.  In
77 most cases, there is only one carry administrator, for example
78 Carry.Multics.*