 
| Sender: |
|
| Date: |
Tue, 23 Sep 2008 09:04:25 +0100 |
| MIME-version: |
1.0 |
| Reply-To: |
|
| Content-type: |
text/plain; format=flowed; charset=ISO-8859-1 |
| Subject: |
|
| From: |
|
| Content-disposition: |
inline |
| In-Reply-To: |
|
| Content-transfer-encoding: |
7BIT |
| Comments: |
|
| Parts/Attachments: |
|
|
Jon Peatfield wrote:
> Looking more closely the problem seems to affect the sl52 boxes I can
> look at but not sl50 or sl51 systems (as far as I can tell anyway).
We have some SL5.0 boxes that do not behave properly....
> Now I don't really understand why this wasn't needed in sl50/sl51,
... which would explain some of your puzzlement.
Your investigation suggests that the exact sequence in which things
start is critical. You have to start lockd but then not use it until it
has been configured. That's very fragile, but could easily survive a
few rounds of testing - don't the awkward bugs always do that?
For now, I'm sticking with configuring modprobe...
Shane
--
Shane Voss, Computing Officer, School of GeoSciences, University of
Edinburgh
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
|
|
|
