[OpenSPARC-T2-DV] / tools / perl-5.8.0 / doc / MHonArc / app-diagnos.html

<HTML>
<HEAD>
<TITLE>MHonArc v2.5 -- Appendix: Diagnostics</TITLE>
</HEAD>
<!--
<BODY background="ssbg75.jpg"
      text="#000000" link="#0000ee" vlink="#551a8b" alink="ff0000">
-->
<BODY>

<!--X-NavButtons-Start-->
<table width="100%">
<tr valign="top">
<td align="left"><nobr><a href="app-rcfileexs.html"><img src="prev.png"border=0 alt="[Prev]"></a>&nbsp;&nbsp;&nbsp;</nobr></td><td align="center" width="99%"><a href="mhonarc.html"><img src="up.png" border=0 alt="[TOC]"></a><a href="faq/faq.html"><img src="faq.png" border=0 alt="[FAQ]"></a><a href="app-bugs.html"><img src="bug.png" border=0 alt="[Bugs]"></a><a href="http://www.mhonarc.org/"><img src="home.png" border=0 alt="[Home]"></a></td><td align="right"><nobr>&nbsp;&nbsp;&nbsp;<a href="app-utilsprg.html"><img src="next.png" border=0 alt="[Next]"></a></nobr></td></tr></table>
<!--X-NavButtons-End-->

<HR>

<H1><A NAME="diagnostics">Appendix: Diagnostics</A></H1>

<P>Three types of messages exist in MHonArc:
<EM>Informative</EM> messages, <EM>Warnings</EM>, and
<EM>Errors</EM>. <EM>Informative</EM> messages give you the
current status of MHonArc's execution.  <EM>Warnings</EM>
signify undesired conditions, but are <EM>not</EM> critical in
MHonArc's exection.  <EM>Errors</EM> signify critical
conditions that inhibit MHonArc from finishing its task.  </P>

<P>Another set of messages exists that are generated from the Perl
interpreter itself.  MHonArc tries its best to catch any
conditions that may cause Perl to abnormally abort, but conditions
may arise where this is not possible.  </P> <P>This section describes
the various diagnostics MHonArc may produce and messages
Perl may produce.  </P>

<!--X-TOC-Start-->
<ul>
<li><a href="#infomsgs">Informative messages</a>
<li><a href="#warnings">Warnings</a>
<li><a href="#errors">Errors</a>
<li><a href="#perlmsgs">Perl Messages</a>
</ul>
<!--X-TOC-End-->

<hr>
<H2><A NAME="infomsgs">Informative messages</A></H2>

<P>Informative messages may be suppressed via the
<A HREF="resources/quiet.html">QUIET</A> resource.
Only the more important Informative messages are listed here.  </P>

<h4>No new messages</h4>

<P>No new mail messages exist when performing an add operation to an
archive. This can occur if an empty <EM>MH</EM> mail folder, or empty
mailbox file, is passed to MHonArc; or the folder
contains messages already in the archive.
</P>

<h4>Trying to lock mail archive ...</h4>

<P>The statement means that a lock file is in place for the archive
you are trying to update.  Normally, an existing lock file implies
that another MHonArc process is currently using the archive,
and other MHonArc processes will wait awhile to see if the
archive will be unlocked.
The time MHonArc waits can be modified
by the <a href="resources/locktries.html">LOCKTRIES</a> and
<a href="resources/lockdelay.html">LOCKDELAY</a> resources.
</P>

<P>There are times when a lock file exists, but no
MHonArc process is modifying the archive. This can occur
if MHonArc is abnormally terminated.  If you know that no
other MHonArc process is editing the archive you are
try to modify, then manually remove the lock file or use the
<A HREF="force.html">FORCE</A> resource.
</P>
<table border=0 cellpadding=4>
<tr valign=top>
<td><strong><font color="red">WARNING</font></strong></td>
<td><p>If <a href="resources/lockmethod.html">LOCKMETHOD</a>
is set to <tt>flock</tt>, then the lock file should never be
manually deleted.  When MHonArc abnormally terminates, then the
lock will be automatically released when the <tt>flock</tt> method
is used.  A stale lock can still occur under the <tt>flock</tt>
method if for some reason a MHonArc
process hangs.  In this case, just kill the offending process and
the lock will automatically be released.
</p>
</td>
</tr>
</table>

<hr>
<H2><A NAME="warnings">Warnings</A></H2>

<P>Warning messages denote some undesired event occurred, but the
event is not severe enough to cause program termination.  </P>

<h4>Warning: Could not find date for message</h4>

<P>MHonArc was unable to find a date for a
mail message, or could not parse the date if the date is not
in a common format.  The message is given the current date
if no date is found.
</P>

<h4>Warning: Database (<var>dbversion</var>)
!= program (<var>prgversion</var>) version</h4>

<P>Indicates that the version of MHonArc updating an archive
is different from the version of MHonArc that created the
database file. Problems can arise if the database file changes in
format from different version of MHonArc. See the release
notes of the MHonArc distribution if changes in the databse
format will effect older archives.  </P>

<h4>Warning: Unable to create <var>outdir/dbfile</var></h4>

<P>Indicates MHonArc was unable to create the
database file <var>dbfile</var> for the mail archive
created/modified in <var>outdir</var>. This message can occur if
<var>outdir</var> permissions changed during MHonArc
execution, the existing <var>dbfile</var> is read-only, or the
file system is full.  </P>

<P>This warning can be severe because no future add operations can
be performed to the archive.  </P>

<h4>Warning: Unable to open footer: <var>footer</var></h4>

<P>MHonArc was unable to open the footer file,
<var>footer</var>, for inclusion into the index page. Make sure
<var>footer</var> exists, and is readable by you.  </P>

<h4>Warning: Unable to open header: <var>header</var>
</h4>

<P>MHonArc was unable to open the header file,
<var>header</var>, for inclusion into the index page. Make sure
<var>header</var> exists, and is readable by you.  </P>

<h4>Warning: Unable to open <var>folder</var></h4>

<P>MHonArc was unable to open the specified mail
<var>folder</var> for reading. Make sure <var>folder</var>
exists and is readable (and executable if a directory) by you.  </P>

<h4>Warning: Unable to open message: <var>folder/message</var>
</h4>

<P>MHonArc was unable to open the specified <EM>MH</EM>
mail message <var>folder/message</var> for reading. Make sure
<var>folder/message</var> exists and is readable by you.  </P>

<h4>Warning: Unable to open resource file: <var>file</var>
</h4>

<P>MHonArc was unable to open the resource file,
<var>file</var>, for reading. Make sure <var>file</var> exists, and
is readable by you.  </P>

<h4>Warning: Undefined time zone: "<var>timezone</var>"
</h4>

<P>MHonArc has found an unrecognized timezone
acronym, <var>timezone</var>, in a mail
message. You can tell MHonArc about other timezone
acronyms, and their hour offset to UTC, by using the <A
HREF="resources/timezones.html">TIMEZONES</A> resource
</P>

<P>The timezone UTC (or GMT) is used for an undefined timezone acronyms.
</P>

<hr>
<H2><A NAME="errors">Errors</A></H2>

<P>Errors denote conditions that cause MHonArc to abort
execution.  </P>

<P>Some error conditions may cause the MHonArc archive to
become corrupted. If the error occurs when MHonArc is writing
files, you may have to recreate the archive from the original messages.
</P>

<h4>ERROR: Database read error of <var>dbfile</var></h4>

<P>An error occured when trying to read an archive's database. The
error can occur if the database file is not readable or the file
got corrupted.  </P>

<h4>ERROR: Unable to create <var>file</var></h4>

<P>MHonArc was unable to create <var>file</var>. This
message can occur if the directory being written to is not writable, a
read-only file with the same name exists, or the file system is full.
</P>

<h4>ERROR: Unable to create lockfile after <var>#</var> tries
</h4>

<P>The statement means that MHonArc timed-out trying to obtain a
lock on the archive.  You may be able to avoid time-out problems
by modifying the <a href="resources/locktries.html">LOCKTRIES</a> and
<a href="resources/lockdelay.html">LOCKDELAY</a> resources.
</P>

<P>Sometimes a lock file exists, but no MHonArc
process is modifying the archive. This can occur if
MHonArc is abnormally terminated.  If you know that no
other MHonArc process is editting the archive you are
try to modify, then manually remove the lock file or use the
<a href="resources/force.html">FORCE</a> resource.
</P>

<table border=0 cellpadding=4>
<tr valign=top>
<td><strong><font color="red">WARNING</font></strong></td>
<td><p>If <a href="resources/lockmethod.html">LOCKMETHOD</a>
is set to <tt>flock</tt>, then the lock file should never be
manually deleted.  When MHonArc abnormally terminates, then the
lock will be automatically released when the <tt>flock</tt> method
is used.  A stale lock can still occur under the <tt>flock</tt>
method if for some reason a MHonArc
process hangs.  In this case, just kill the offending process and
the lock will automatically be released.
</p>
</td>
</tr>
</table>

<h4>ERROR: Unable to open <var>file</var></h4>

<P>MHonArc was unable to open <var>file</var> for reading. Make
sure <var>file</var> exists, and is readable by you.  </P>

<h4>ERROR: Unable to require <var>perl-library</var></h4>

<p>Make sure you properly installed MHonArc.  Also
make sure Perl is installed properly if the library is a standard
Perl library.
</p>

<hr>
<H2><A NAME="perlmsgs">Perl Messages</A></H2>

<P>Generally, if execution is aborted and the following error messages
appear, then you will have to manually delete the lock file since
MHonArc will not have the chance to delete the file.  </P>

<h4>Can't locate file in @INC at <var>file</var> line number.
</h4>

<P>A library that MHonArc tried to load was not found
in the Perl include search paths. This error usually implies
that MHonArc was not installed correctly. Make sure that
MHonArc was installed via the <CODE>install.me</CODE> program
that is provided in the MHonArc distribution.  </P>

<h4><var>file</var> did not return a true value at file line number.</h4>

<P>If you are using your own MIME filters with MHonArc, make
sure the library files return a true value, like <tt>1</tt>.  </P>

<HR>
<!--X-NavButtons-Start-->
<table width="100%">
<tr valign="top">
<td align="left"><nobr><a href="app-rcfileexs.html"><img src="prev.png"border=0 alt="[Prev]"></a>&nbsp;&nbsp;&nbsp;</nobr></td><td align="center" width="99%"><a href="mhonarc.html"><img src="up.png" border=0 alt="[TOC]"></a><a href="faq/faq.html"><img src="faq.png" border=0 alt="[FAQ]"></a><a href="app-bugs.html"><img src="bug.png" border=0 alt="[Bugs]"></a><a href="http://www.mhonarc.org/"><img src="home.png" border=0 alt="[Home]"></a></td><td align="right"><nobr>&nbsp;&nbsp;&nbsp;<a href="app-utilsprg.html"><img src="next.png" border=0 alt="[Next]"></a></nobr></td></tr></table>
<!--X-NavButtons-End-->

<HR>
<address>
$Date: 2001/12/24 14:38:07 $ <br>
<img align="top" src="monicon.png" alt="">
<a href="http://www.mhonarc.org"
><strong>MHonArc</strong></a><br>
Copyright &#169; 1997-2000, <a href="http://www.mhonarc.org/~ehood/"
>Earl Hood</a>, <a href="mailto:mhonarc@mhonarc.org"
>mhonarc@mhonarc.org</a><br>
</address>

</BODY>
</HTML>
Commit	Line	Data
86530b38 AT	1	<HTML>
	2	<HEAD>
	3	<TITLE>MHonArc v2.5 -- Appendix: Diagnostics</TITLE>
	4	</HEAD>
	5	<!--
	6	<BODY background="ssbg75.jpg"
	7	text="#000000" link="#0000ee" vlink="#551a8b" alink="ff0000">
	8	-->
	9	<BODY>
	10
	11	<!--X-NavButtons-Start-->
	12	<table width="100%">
	13	<tr valign="top">
	14	<td align="left"><nobr><a href="app-rcfileexs.html"><img src="prev.png"border=0 alt="[Prev]"></a>   </nobr></td><td align="center" width="99%"><a href="mhonarc.html"><img src="up.png" border=0 alt="[TOC]"></a><a href="faq/faq.html"><img src="faq.png" border=0 alt="[FAQ]"></a><a href="app-bugs.html"><img src="bug.png" border=0 alt="[Bugs]"></a><a href="http://www.mhonarc.org/"><img src="home.png" border=0 alt="[Home]"></a></td><td align="right"><nobr>   <a href="app-utilsprg.html"><img src="next.png" border=0 alt="[Next]"></a></nobr></td></tr></table>
	15	<!--X-NavButtons-End-->
	16
	17	<HR>
	18
	19	<H1><A NAME="diagnostics">Appendix: Diagnostics</A></H1>
	20
	21	<P>Three types of messages exist in MHonArc:
	22	<EM>Informative</EM> messages, <EM>Warnings</EM>, and
	23	<EM>Errors</EM>. <EM>Informative</EM> messages give you the
	24	current status of MHonArc's execution. <EM>Warnings</EM>
	25	signify undesired conditions, but are <EM>not</EM> critical in
	26	MHonArc's exection. <EM>Errors</EM> signify critical
	27	conditions that inhibit MHonArc from finishing its task. </P>
	28
	29	<P>Another set of messages exists that are generated from the Perl
	30	interpreter itself. MHonArc tries its best to catch any
	31	conditions that may cause Perl to abnormally abort, but conditions
	32	may arise where this is not possible. </P> <P>This section describes
	33	the various diagnostics MHonArc may produce and messages
	34	Perl may produce. </P>
	35
	36	<!--X-TOC-Start-->
	37	<ul>
	38	<li><a href="#infomsgs">Informative messages</a>
	39	<li><a href="#warnings">Warnings</a>
	40	<li><a href="#errors">Errors</a>
	41	<li><a href="#perlmsgs">Perl Messages</a>
	42	</ul>
	43	<!--X-TOC-End-->
	44
	45	<hr>
	46	<H2><A NAME="infomsgs">Informative messages</A></H2>
	47
	48	<P>Informative messages may be suppressed via the
	49	<A HREF="resources/quiet.html">QUIET</A> resource.
	50	Only the more important Informative messages are listed here. </P>
	51
	52	<h4>No new messages</h4>
	53
	54	<P>No new mail messages exist when performing an add operation to an
	55	archive. This can occur if an empty <EM>MH</EM> mail folder, or empty
	56	mailbox file, is passed to MHonArc; or the folder
	57	contains messages already in the archive.
	58	</P>
	59
	60	<h4>Trying to lock mail archive ...</h4>
	61
	62	<P>The statement means that a lock file is in place for the archive
	63	you are trying to update. Normally, an existing lock file implies
	64	that another MHonArc process is currently using the archive,
65	and other MHonArc processes will wait awhile to see if the
66	archive will be unlocked.
67	The time MHonArc waits can be modified
68	by the <a href="resources/locktries.html">LOCKTRIES</a> and
69	<a href="resources/lockdelay.html">LOCKDELAY</a> resources.
70	</P>
71
72	<P>There are times when a lock file exists, but no
73	MHonArc process is modifying the archive. This can occur
74	if MHonArc is abnormally terminated. If you know that no
75	other MHonArc process is editing the archive you are
76	try to modify, then manually remove the lock file or use the
77	<A HREF="force.html">FORCE</A> resource.
78	</P>
79	<table border=0 cellpadding=4>
80	<tr valign=top>
81	<td><strong><font color="red">WARNING</font></strong></td>
82	<td><p>If <a href="resources/lockmethod.html">LOCKMETHOD</a>
83	is set to <tt>flock</tt>, then the lock file should never be
84	manually deleted. When MHonArc abnormally terminates, then the
85	lock will be automatically released when the <tt>flock</tt> method
86	is used. A stale lock can still occur under the <tt>flock</tt>
87	method if for some reason a MHonArc
88	process hangs. In this case, just kill the offending process and
89	the lock will automatically be released.
90	</p>
91	</td>
92	</tr>
93	</table>
94
95	<hr>
96	<H2><A NAME="warnings">Warnings</A></H2>
97
98	<P>Warning messages denote some undesired event occurred, but the
99	event is not severe enough to cause program termination. </P>
100
101	<h4>Warning: Could not find date for message</h4>
102
103	<P>MHonArc was unable to find a date for a
104	mail message, or could not parse the date if the date is not
105	in a common format. The message is given the current date
106	if no date is found.
107	</P>
108
109	<h4>Warning: Database (<var>dbversion</var>)
110	!= program (<var>prgversion</var>) version</h4>
111
112	<P>Indicates that the version of MHonArc updating an archive
113	is different from the version of MHonArc that created the
114	database file. Problems can arise if the database file changes in
115	format from different version of MHonArc. See the release
116	notes of the MHonArc distribution if changes in the databse
117	format will effect older archives. </P>
118
119	<h4>Warning: Unable to create <var>outdir/dbfile</var></h4>
120
121	<P>Indicates MHonArc was unable to create the
122	database file <var>dbfile</var> for the mail archive
123	created/modified in <var>outdir</var>. This message can occur if
124	<var>outdir</var> permissions changed during MHonArc
125	execution, the existing <var>dbfile</var> is read-only, or the
126	file system is full. </P>
127
128	<P>This warning can be severe because no future add operations can
129	be performed to the archive. </P>
130
131	<h4>Warning: Unable to open footer: <var>footer</var></h4>
132
133	<P>MHonArc was unable to open the footer file,
134	<var>footer</var>, for inclusion into the index page. Make sure
135	<var>footer</var> exists, and is readable by you. </P>
136
137	<h4>Warning: Unable to open header: <var>header</var>
138	</h4>
139
140	<P>MHonArc was unable to open the header file,
141	<var>header</var>, for inclusion into the index page. Make sure
142	<var>header</var> exists, and is readable by you. </P>
143
144	<h4>Warning: Unable to open <var>folder</var></h4>
145
146	<P>MHonArc was unable to open the specified mail
147	<var>folder</var> for reading. Make sure <var>folder</var>
148	exists and is readable (and executable if a directory) by you. </P>
149
150	<h4>Warning: Unable to open message: <var>folder/message</var>
151	</h4>
152
153	<P>MHonArc was unable to open the specified <EM>MH</EM>
154	mail message <var>folder/message</var> for reading. Make sure
155	<var>folder/message</var> exists and is readable by you. </P>
156
157	<h4>Warning: Unable to open resource file: <var>file</var>
158	</h4>
159
160	<P>MHonArc was unable to open the resource file,
161	<var>file</var>, for reading. Make sure <var>file</var> exists, and
162	is readable by you. </P>
163
164	<h4>Warning: Undefined time zone: "<var>timezone</var>"
165	</h4>
166
167	<P>MHonArc has found an unrecognized timezone
168	acronym, <var>timezone</var>, in a mail
169	message. You can tell MHonArc about other timezone
170	acronyms, and their hour offset to UTC, by using the <A
171	HREF="resources/timezones.html">TIMEZONES</A> resource
172	</P>
173
174	<P>The timezone UTC (or GMT) is used for an undefined timezone acronyms.
175	</P>
176
177	<hr>
178	<H2><A NAME="errors">Errors</A></H2>
179
180	<P>Errors denote conditions that cause MHonArc to abort
181	execution. </P>
182
183	<P>Some error conditions may cause the MHonArc archive to
184	become corrupted. If the error occurs when MHonArc is writing
185	files, you may have to recreate the archive from the original messages.
186	</P>
187
188	<h4>ERROR: Database read error of <var>dbfile</var></h4>
189
190	<P>An error occured when trying to read an archive's database. The
191	error can occur if the database file is not readable or the file
192	got corrupted. </P>
193
194	<h4>ERROR: Unable to create <var>file</var></h4>
195
196	<P>MHonArc was unable to create <var>file</var>. This
197	message can occur if the directory being written to is not writable, a
198	read-only file with the same name exists, or the file system is full.
199	</P>
200
201	<h4>ERROR: Unable to create lockfile after <var>#</var> tries
202	</h4>
203
204	<P>The statement means that MHonArc timed-out trying to obtain a
205	lock on the archive. You may be able to avoid time-out problems
206	by modifying the <a href="resources/locktries.html">LOCKTRIES</a> and
207	<a href="resources/lockdelay.html">LOCKDELAY</a> resources.
208	</P>
209
210	<P>Sometimes a lock file exists, but no MHonArc
211	process is modifying the archive. This can occur if
212	MHonArc is abnormally terminated. If you know that no
213	other MHonArc process is editting the archive you are
214	try to modify, then manually remove the lock file or use the
215	<a href="resources/force.html">FORCE</a> resource.
216	</P>
217
218	<table border=0 cellpadding=4>
219	<tr valign=top>
220	<td><strong><font color="red">WARNING</font></strong></td>
221	<td><p>If <a href="resources/lockmethod.html">LOCKMETHOD</a>
222	is set to <tt>flock</tt>, then the lock file should never be
223	manually deleted. When MHonArc abnormally terminates, then the
224	lock will be automatically released when the <tt>flock</tt> method
225	is used. A stale lock can still occur under the <tt>flock</tt>
226	method if for some reason a MHonArc
227	process hangs. In this case, just kill the offending process and
228	the lock will automatically be released.
229	</p>
230	</td>
231	</tr>
232	</table>
233
234	<h4>ERROR: Unable to open <var>file</var></h4>
235
236	<P>MHonArc was unable to open <var>file</var> for reading. Make
237	sure <var>file</var> exists, and is readable by you. </P>
238
239	<h4>ERROR: Unable to require <var>perl-library</var></h4>
240
241	<p>Make sure you properly installed MHonArc. Also
242	make sure Perl is installed properly if the library is a standard
243	Perl library.
244	</p>
245
246	<hr>
247	<H2><A NAME="perlmsgs">Perl Messages</A></H2>
248
249	<P>Generally, if execution is aborted and the following error messages
250	appear, then you will have to manually delete the lock file since
251	MHonArc will not have the chance to delete the file. </P>
252
253	<h4>Can't locate file in @INC at <var>file</var> line number.
254	</h4>
255
256	<P>A library that MHonArc tried to load was not found
257	in the Perl include search paths. This error usually implies
258	that MHonArc was not installed correctly. Make sure that
259	MHonArc was installed via the <CODE>install.me</CODE> program
260	that is provided in the MHonArc distribution. </P>
261
262	<h4><var>file</var> did not return a true value at file line number.</h4>
263
264	<P>If you are using your own MIME filters with MHonArc, make
265	sure the library files return a true value, like <tt>1</tt>. </P>
266
267	<HR>
268	<!--X-NavButtons-Start-->
269	<table width="100%">
270	<tr valign="top">
271	<td align="left"><nobr><a href="app-rcfileexs.html"><img src="prev.png"border=0 alt="[Prev]"></a>   </nobr></td><td align="center" width="99%"><a href="mhonarc.html"><img src="up.png" border=0 alt="[TOC]"></a><a href="faq/faq.html"><img src="faq.png" border=0 alt="[FAQ]"></a><a href="app-bugs.html"><img src="bug.png" border=0 alt="[Bugs]"></a><a href="http://www.mhonarc.org/"><img src="home.png" border=0 alt="[Home]"></a></td><td align="right"><nobr>   <a href="app-utilsprg.html"><img src="next.png" border=0 alt="[Next]"></a></nobr></td></tr></table>
272	<!--X-NavButtons-End-->
273
274	<HR>
275	<address>
276	$Date: 2001/12/24 14:38:07 $ <br>
277	<img align="top" src="monicon.png" alt="">
278	<a href="http://www.mhonarc.org"
279	><strong>MHonArc</strong></a><br>
280	Copyright © 1997-2000, <a href="http://www.mhonarc.org/~ehood/"
281	>Earl Hood</a>, <a href="mailto:mhonarc@mhonarc.org"
282	>mhonarc@mhonarc.org</a><br>
283	</address>
284
285	</BODY>
286	</HTML>