|
|
1.1 root 1:
2:
3: msgs Command msgs
4:
5:
6:
7:
8: Read messages intended for all COHERENT users
9:
10: mmssggss [-_q] [_n_u_m_b_e_r]
11:
12: mmssggss selects and displays messages that are intended to be read
13: by all COHERENT users. Messages are mailed to the login mmssggss.
14: They should contain information meant to be read once by most
15: users of the system.
16:
17: The command msgs normally is in a user's .pprrooffiillee, so that it is
18: executed every time he logs in. When invoked, it prompts the
19: user with the identifier of the user who sent the message and the
20: message's size. msgs then asks the user if he wishes to see the
21: rest of the message. The user should reply with one of the
22: following:
23:
24:
25: yy Display the message.
26: <rreettuurrnn> Display the message.
27: nn Skip this message and go to the next one.
28: - Redisplay the last message.
29: qq Quit mmssggss.
30: _n_u_m_b_e_r Display message _n_u_m_b_e_r; then continue.
31:
32:
33: If environmental variable PAGER is defined, msgs will ``pipe''
34: each message through the command specified in PAGER. For ex-
35: ample, the .pprrooffiillee command line:
36:
37:
38: export PAGER="exec /bin/scat -1"
39:
40:
41: would invoke /bin/scat for each message with the command line ar-
42: gument -1 (the digit one).
43:
44: mmssggss writes into the file $(HHOOMMEE)/.mmssggssrrcc the number of the next
45: message the user will see when he invokes mmssggss. mmssggss keeps all
46: messages in the directory /uussrr/mmssggss; each message is named with a
47: sequential number, which indicates its message number. The file
48: /uussrr/mmssggss/bboouunnddss contains the low and high numbers of the mes-
49: sages in the directory; mmssggss determines whether a user has not
50: read a message by comparing the information in $(HHOOMMEE)/.mmssggssrrcc
51: with that in /uussrr/mmssggss/bboouunnddss. If the contents of
52: /uussrr/mmssggss/bboouunnddss are incorrect, the problem can be fixed by
53: removing that file; mmssggss will create a new bboouunnddss file the next
54: time it is run.
55:
56: When the contents of a message are no longer needed, simply
57: remove that message. Avoid removing the bboouunnddss file and the
58: highest numbered message at the same time.
59:
60: msgs accepts the following command-line options:
61:
62:
63:
64: COHERENT Lexicon Page 1
65:
66:
67:
68:
69: msgs Command msgs
70:
71:
72:
73: -qq Query whether there are messages; print ``There are new mes-
74: sages'' if there are, and ``No new messages'' if not. The
75: command mmssggss -qq is often used in profile scripts.
76:
77: _n_u_m_b_e_r
78: Start at message _n_u_m_b_e_r rather than at the message recorded
79: in $(HHOOMMEE)/.mmssggssrrcc. If _n_u_m_b_e_r is greater than zero, then
80: start with that message; if _n_u_m_b_e_r is less than zero, then
81: begin _n_u_m_b_e_r messages before the one recorded in
82: $(HHOOMMEE)/.mmssggssrrcc.
83:
84: ***** Files *****
85:
86: /uussrr/ssppooooll/mmaaiill/mmssggss -- Mail messages file
87: /uussrr/mmssggss/[11-99]* -- Data base
88: /uussrr/mmssggss/bboouunnddss -- File that contains message number bounds
89: $(HHOOMMEE)/.mmssggssrrcc -- Number of next message to be presented
90:
91: ***** See Also *****
92:
93: commands, mail, PAGER, scat
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:
126:
127:
128:
129:
130: COHERENT Lexicon Page 2
131:
132:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.