HP-UX Reference (11i v2 03/08) - 1 User Commands A-M (vol 1)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

341

342

343

344

345

346

347

348

349

350

get(1) get(1)

ﬁles are named by replacing the leading

s with the tag. The g-ﬁle is an exception to this scheme: the g-

ﬁle is named by removing the

s. preﬁx. For example, s.xyz.c, the auxiliary ﬁle names would be

xyz.c, l.xyz.c, p.xyz.c, and z.xyz.c

, respectively.

The g-ﬁle, which contains the generated text, is created in the current directory (unless the

-p option is

used). A g-ﬁle is created in all cases, whether or not any lines of text were generated by the

get.Itis

owned by the real user. If the

-k

option is used or implied its mode is 644; otherwise its mode is 444.

Only the real user need have write permission in the current directory.

The l-ﬁle contains a table showing which deltas were applied in generating the retrieved text. The l-ﬁle is

created in the current directory if the

-l

option is used; its mode is 444 and it is owned by the real user.

Only the real user need have write permission in the current directory.

Lines in the l-ﬁle have the following format:

1. A blank character if the delta was applied;

* otherwise.

2. A blank character if the delta was applied or was not applied and ignored;

* if the delta was not applied and was not ignored.

3. A code indicating a "special" reason why the delta was or was not applied:

I: Included.

X: Excluded.

C: Cut off (by a -c option).

4. Blank.

5. SCCS identiﬁcation (SID).

6. Tab character.

7. Creation date and time (in the form YY/MM/DD HH:MM:SS).

8. Blank.

9. Login name of person who created delta.

The comments and MR data follow on subsequent lines, indented one horizontal tab character. A

blank line terminates each entry.

The p-ﬁle is used to pass information resulting from a

get with an -e

option along to delta. Its contents

are also used to prevent a subsequent execution of

get with an -e option for the same SID until delta is

executed or the joint edit ﬂag,

j, (see admin(1)) is set in the SCCS ﬁle. The p-ﬁle is created in the direc-

tory containing the SCCS ﬁle and the effective user must have write permission in that directory. Its

mode is 644 and it is owned by the effective user. The format of the p-ﬁle is: the gotten SID, followed by

a blank, followed by the SID that the new delta will have when it is made, followed by a blank, followed

by the login name of the real user, followed by a blank, followed by the date-time the

get was executed,

followed by a blank and the

-i option argument if it was present, followed by a blank and the

-x option

argument if it was present, followed by a new-line. There can be an arbitrary number of lines in the p-

ﬁle at any time; no two lines can have the same new delta SID.

The z-ﬁle serves as a lock-out mechanism against simultaneous updates. Its contents are the binary (2

bytes) process ID of the command (i.e.,

get) that created it. The z-ﬁle is created in the directory contain-

ing the SCCS ﬁle for the duration of get. The same protection restrictions as those for the p-ﬁle apply

for the z-ﬁle. The z-ﬁle is created mode 444.