Number: 296

Date: 26-Mar-84 14':33':26

Submitter: Sannella.PA

Source: Halasz.pa

Subject: Handle better Leaf error': 1001 (Broken Leaf)

Assigned To: 

Attn: vanMelle.pa

Status: Open

In/By: 

Problem Type: Design - UI

Impact: Annoying

Difficulty: Hard

Frequency: Intermittent

Priority: Perhaps

System: Communications

Subsystem: PUP Protocols

Machine: 

Disk: 

Lisp Version: 

Source Files: Leaf

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: 

Description: '
Date': 23 Mar 84 11':49 PST'
From': Halasz.pa'
Subject': Lisp': Leaf error': 1001'
To': LispSupport.pa'
cc': '
Lisp-System-Date': 15-Mar-84 00':13':18'
Machine-Type': Dorado'
'
What the hell is a "Leaf error': 1001" and why isn''t there a more informative msg in the prompt window when this error occurs?'
'
'
Frank'
'
-----'
'
Date':  9 Apr 84 12':38 PST'
From': vanMelle.pa'
AR 296': Difficulty': Moderate (Leaf Error 1001 is undocumented, so some investigation required).'
'
-----'
Date': 30 May 84 16':24 PDT'
From': MikeDixon.pa'
Subject': Lafite': Leaf error': 1001 trying to browse folder'
To': LafiteSupport.pa'
'
Lafite System Date':  8-Apr-84 17':20':45'
Lisp System Date': 28-May-84 19':09':20'
'
i just closed the only browser i had open (choosing don''t update).  now i can''t browse any of my mail folders -- it sez ''leaf error': 1001''.  what kind of error msg is that?!?!?'
'
-----'
Date':  3 Jun 84 15':43 PDT'
From': vanMelle.pa'
'
Not a very informative error, I agree, but then the official list of IFS error messages does not include #1001, so the default error handler has a hard time being more informative.'
'
Anyway, 1001 turns out to be "Broken Leaf", a feature peculiar to the Leaf protocol.  What it means is that you had some file open, but hadn''t done anything with it in a while, then somebody else on another machine tried to access the file in a conflicting way (reading a file you had open for write, or vice versa).  In this situation, the Leaf server breaks your access to the file and gives access to the other guy.  This is supposed to be some sort of insurance against a crashed host holding onto a file for too long, but in reality it''s a major headache for implementors.'
'


Workaround: 

Test Case: 

Edit-By: vanMelle

Edit-Date:  3-Jun-84 15':47':56