* Add .tedit files for Lafite manual and release notes -- PDFs on Google Drive * use 'docs' for subfolder name; wliminate dup * Remove duplicate LAFITEMANUAL-GLOSSARY-CUSTOMER.TEDIT --------- Co-authored-by: Nick Briggs <nicholas.h.briggs@gmail.com>
35 lines
28 KiB
Plaintext
35 lines
28 KiB
Plaintext
1
|
||
|
||
A USER'S GUIDE TO LAFITE
|
||
1
|
||
|
||
A USER'S GUIDE TO LAFITE
|
||
TROUBLESHOOTING LAFITE PROBLEMS
|
||
1
|
||
|
||
TROUBLESHOOTING LAFITE PROBLEMS
|
||
1
|
||
|
||
|
||
12. TROUBLESHOOTING
|
||
LAFITE PROBLEMS
|
||
6
|
||
|
||
Although Lafite is a robust system, you may occasionally encounter minor problems when using it. This chapter describes the most common Lafite problems and how to prevent and/or recover from them.
|
||
2
|
||
|
||
Lafite Confuses You With a Previous User
|
||
1
|
||
|
||
If you log into Lafite with the correct name and password but the Browse menu shows no folders or shows someone else's folders, Lafite may be confusing you with a previous user. If you are running in a sysout in which someone else has been using Lafite, you need to take some action to get Lafite to work on your mail files and in your name. When you change the user identity by logging in as yourself, Lafite notices that the current user has changed and attempts to authenticate you. However, Lafite still doesn't know how you want your Lafite customized; in particular, what your known mail folders are.
|
||
To get Lafite to recognize your identity, you should first turn Lafite off by choosing Quit from the status window or by calling (LAFITE 'OFF). Then log in again. Type (GREET) in the executive window; you will be asked for the name of your initialization file if there isn't one on your workstation's disk. When this has been loaded, restart Lafite.
|
||
2
|
||
|
||
File Server Is Slow
|
||
1
|
||
|
||
If your mail files are stored on a remote file server that is particularly unresponsive, the mail server connection over which new mail is retrieved may time out (that is, end communication with your file server) before the file server acknowledges receipt of the messages. The usual consequence of this is that your in-box is not flushed, so your new mail is in two places: your in-box, awaiting retrieval, and your mail file, to which it was just retrieved. A less common occurrence is that the mail server times out partway through the retrieval process, resulting in a Lisp break. You can type ^ after the prompt in the break window to return to the state before the Get Mail started.
|
||
If this is often a problem for you, you may want to adopt the following procedure to maintain the flexibility of remote mail files while utilizing the speed and reliability of the local disk. Keep most of your mail files on the remote server, as usual, but keep your Active Mail file, the one to which you usually retrieve mail, on your local disk. Retrieve mail to this file and dispatch from there to your remote files (using Move To) some or all of the messages you wish to keep. Mail files on disk have very predictable performance during Get Mail, which is good for both you and the mail server. Files on disk are also less subject to other vagaries of remote servers (e.g., sudden crashes) that sometimes cause problems with mail files (see figure 27). And if you tend to delete much of your incoming mail after reading it once, you may find it faster to keep your Active Mail on disk, even if your remote server isn't unreliable.
|
||
|