|
|
1.1 ! root 1: .TH UCACHE 1 "630 MTG" ! 2: .SH NAME ! 3: ucache \- List and remove objects in the Application cache ! 4: .SH SYNOPSIS ! 5: .B ucache ! 6: .SH DESCRIPTION ! 7: After being downloaded, the program ! 8: .I ucache ! 9: will cache itself as a global command and exits. ! 10: The user can access the command through the \fBMore\fR ! 11: submenu under the item \fIucache\fR displayed with a garbage ! 12: can icon. An arrow from the item directs the user to a ! 13: submenu that lists sequentially all objects (commands and ! 14: applications) that are currently in the terminal's Application ! 15: cache. ! 16: .PP ! 17: The names listed in the \fIucache\fR submenu are the ! 18: \fImenu names\fR of the objects. Menu names are names that ! 19: cached applications use to advertise themselves in the ! 20: \fBMore\fR menu. They may be different from \fItag names\fR ! 21: which uniquely identify an object in the Application cache. ! 22: (For further discussion, see \fIcache(3L)\fR.) If an ! 23: object in the Application cache does not have a menu name, ! 24: its tag name is displayed instead. ! 25: .PP ! 26: Items in the \fIucache\fR submenu may be greyed. Greyed ! 27: items mean they cannot be selected for removal because: ! 28: .IP "\f3\(em\f1" ! 29: they have been cached with the \fBA_PERMANENT\fR bit set ! 30: (see \fIcache(3L)\fR). In this case, the item names are ! 31: displayed with a lock icon, and they can never be uncached ! 32: by \fIucache\fR. ! 33: .ce ! 34: \f3or\f1 ! 35: .IP "\f3\(em\f1" ! 36: they have been requested (used) by some running process. ! 37: If all processes using the object exit or are deleted, then the ! 38: item's name corresponding to the object will be un-greyed. ! 39: .PP ! 40: Items that are not greyed can be selected for removal. All caching ! 41: information concerning the object will be erased and the memory freed. ! 42: Note that \fIucache\fR can remove itself from the Application cache. ! 43: ! 44: ! 45: .SH SEE ALSO ! 46: cache(3L), cmdcache(3L), decache(3L).
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.